When the boss talks… :-)
Indeed it seems easier as @Sean proposed if you use his new MMM-Spotify module. (Which I will try soon also).
I’ve learnt one more thing myself.
Thanks.

Correct.

Hi,

I believe you can do it with MMM-NotificationTrigger and MMM-RemoteControl.
i.e :
When Spotify stops, send notification “SPOTIFY STOP”. (within Spotify module)

When “SPOTIFY STOP” is received by MMM-NotificationTrigger, send “HIDE MODULE Spotify” to MMM-RemoteControl.

Of course, code is not correctly written, but that’s how I would do it. MMM-NotificationTrigger and MMM-RemoteControl are pretty easy to use.

FYI, I’m already doing that with news / compliments modules. When news article is made bigger by the “Article_more-details” notification, then the compliment module is hidden.
Once “article-less-details” is triggered, then the compliment module is shown again.

Regards

@sdetweil
Thanks for your support, works fine!

Last thing :

i.e : we are on March 11th.
fulldayevent starts on March 9th and finishes on 13th
Thanks to you, the event only starts to show on 11th.
Unfortunatly, it “only” shows on 11th. not on 12 and 13th.

Looking at how the dateheaders part is written, I believe it’s impossible, correct? (as the event display date is only based on one dateasstring…)

@Radu_Stancu
Hi,

Did you considered using (and maybe tweaking a bit) the MMM-GroveGestures module and “only” replace the Grove Gesture Sensor (PAJ7620u2) by the Flick one?

It’s maybe a bit “basic thinking” from me but the MMM-GroveGestures plugin is really working great and both sensor seems to be based on the same working method / supplier / …
So maybe worth to consider it, don’t you think?

(would eb great for me at least, as I’m using MMM-GroveGestures and I’m interested into switching to the flick one).

Regards

hi Sam @sdetweil

I’ve tried following but I believe this is not the way to do it.
It seems I can’t figure out how the dateheaders mode is working…

I “only” want that fulldayevents which started earlier than today stops to be displayed in earlier dates and only starts today…

		for (var e in events) {
			var event = events[e];
			var dateAsString = moment(event.startDate, "x").format(this.config.dateFormat);
			var dateAsString2 = moment(now, "x").format(this.config.dateFormat);
			if(this.config.timeFormat === "dateheaders"){
				if(lastSeenDate !== dateAsString){
					var dateRow = document.createElement("tr");
					dateRow.className = "normal";
					var dateCell = document.createElement("td");

					dateCell.colSpan = "3";
						if (event.fullDayEvent) {
							dateCell.innerHTML = dateAsString2;
							} else {
							date.Cell.innerHTML = dateAsString;
							}
					dateRow.appendChild(dateCell);
					wrapper.appendChild(dateRow);

					if (e >= startFade) {			//fading
						currentFadeStep = e - startFade;
						dateRow.style.opacity = 1 - (1 / fadeSteps * currentFadeStep);
					}

					lastSeenDate = dateAsString;
				}
			}

Don’t you think that it’s maybe something to be added in line 449?

Thanks @sdetweil
I will try that.
Nevertheless, it seems strange … because from my understading, everything which is between line 264 and 364 seems to be linked to “not dateheaders” format.

Hi,

When I’m in dateheaders mode, the fulldayevents are always displayed on the start date.

I would like it to be displayed starting today’s date even if the fulldayevent started days before.

i.e : I’ve a fulldayevent which started on March 6th and finishes tomorrow.
In the dateheaders view, event is displayed on March 6th date. Which I don’t want.
What I would like is to see it in today’s + tomorrow’s header.

I’ve already tried to modify calendar.js line 258 in several ways but don’t manage to get it done. (maybe it’s even not the right line to modify…)

Would appreciate if someone could help me in this! Thanks already.

Hi,@Sean @sworrs

did you solve your icon issue?
Mine are not showing neither…Several calendars, all not showing the icons. Strange…

@lavolp3 :-)
Let’s see what will happen to mine then!! But to be honest, I’m also afraid that this is the kind of things which is never really “finished”…
Who cares…As soon as we enjoy??
(the issue then becomes the quantity of unfinished things…)

OK, thanks for your support in that!
Now let’s move to the next issue…MMM-GroveGestures…(I will open a second post for that).
After those one are fixed, my MM will be nearly perfect and will be very close to use it in real life!!!

@lavolp3
OK, I will try the fix

Just to be sure. I didn’t noticed any real effect of this issue.
I was mainly trying to solve it before I’m experiencing stability issues with MMM-GroveGestures and wanted to be sure that this “promise” thing is not the root cause before raising the MMM-GroveGestures issue.

Do you think that it is now clear that my MMM-GroveGestures issue and this one are not linked (meaning I can look at the GroveGesture issue in parallel)

@lavolp3
Thanks for explanation.

I’ve just raised it on Git on an existing issue log.

Don’t you think it can be linked to the .appledouble thing. Remember that :

2019-02-15T22:45:59  Launching application. (/home/pi/MagicMirror/js/electron.js:82 App.)
2019-02-15T22:45:59  ERROR! Could not find main module js file for .AppleDouble (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_helper.js:258 Class.loadModuleDefaultConfig)
2019-02-15T22:46:03  (node:6793) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'refs' of undefined (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:03  (node:6793) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:03  (node:6793) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: Cannot read property 'refs' of undefined (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:03  (node:6793) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): TypeError: Cannot read property 'refs' of undefined (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:03  (node:6793) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): TypeError: Cannot read property 'refs' of undefined (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:04  (node:6793) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): TypeError: Cannot read property 'refs' of undefined (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:08  MMM-Logging updated config received, reloading console (/home/pi/MagicMirror/modules/MMM-Logging/node_helper.js:30 Class.socketNotificationReceived)

Because the .appledouble error is refering to Remote Control also.

So…you just have the same issue now but never noticed it before?

@lavolp3
I have the original version from Jopyth.
S***, I hoped it would have been easier to figure out!!

I just Git Pulled… Was already up to date

I confirm…
No error message anymore after disabling MMM-RemoteControl.

Wao…and now?? Do you have a clue about next step or should I raise an issue into MMM-ControlRemote git?

@lavolp3
thx

Here is the result

pi@MagicPi:~/MagicMirror/modules $ find . -maxdepth 2 -exec grep -nwl  .then 2>/dev/null {} +
./MMM-Remote-Control/node_helper.js
./MMM-Remote-Control/installer.sh
./MMM-BackgroundSlideshowInfo/README.md
./MMM-NotificationTrigger/README.md
pi@MagicPi:~/MagicMirror/modules $ 

So… Remote Control I believe…
I will try to disable it and see what happens.

@lavolp3
!!! it’s not your fault, it’s shame on me!!!

Anyway, I just did it…Result is zero…Nothing…

pi@MagicPi:~/MagicMirror/modules $ find . -maxdepth 2 -exec grep -nwl  Promise 2>/dev/null {} +
pi@MagicPi:~/MagicMirror/modules $ 

So…disable them one by one is the next analysis step??

Indeed…It will also avoid the USB latence issue which I saw in several threads…

There are tons of mic arrays (mainly called ReSpeaker). Some of them are expensive (79USD).

I just found that one which already includes connexion board to the Pi, only have 4 mics but is cheaper. Seems to be a good comprise.

link text

I just need to figure out how to connect it to the Pi without using / covering the full GPIO as I already have 2 others sensors connected on it.