@lavolp3
this is the result I have :

./js/main.js
./js/module.js
./clientonly/index.js

Seems to be linked to the core system itself only and not to any particular module?
I’ve already made a git pull for MM itself but it’s already up to date.

@lavolp3
Done…I can indeed see strange things…

2019-02-15T22:45:59 <log> Launching application. (/home/pi/MagicMirror/js/electron.js:82 App.<anonymous>)
2019-02-15T22:45:59 <error> 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 <error> (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 <error> (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 <error> (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 <error> (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 <error> (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 <error> (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 <info> MMM-Logging updated config received, reloading console (/home/pi/MagicMirror/modules/MMM-Logging/node_helper.js:30 Class.socketNotificationReceived)

What do you think?

Regards

Hi,

Considering adding voicecontrol capabilities to my MM by using MMM-Hotword or voiceontrol on my pi3.

Do you think that think kind of mic would do the job?

Sipeed

Will the module be able to recognize it?

Regards

You can adjust the full MM body border into the custom.css file.
(/MagicMirror/css/custom.css)

like that (play with the values until you’re happy) :

body {
  margin: 20px; 
  height: calc(100% - 40px);
  width: calc(100% - 40px);
}

You should maybe also check the settings of your screen itself (depending if you have that issue outside MM or not).

@lavolp3
OK I will give it a try this weekend and check the logs.
Disabling them on by one (through the config.js) will not help?

@lavolp3

Here is the list of the modules I’m using :

It’s a lot…So it seems difficult to identify the one causing the issue, don’t you think so? Maybe you know an analysis method that could help?

Do you think that by “disabled : true” then one by one, it could work to identify which one is causing the issue?

Regards

@Mykle1 @lavolp3 @robiv8
.appledouble : found the rootcause!!
I believe it’s because I mounted my raspberry Pi as a share on my MacBook.
By making “all hidden files visible” on the Pi, I noticed that ALL (literally ALL) folders on the Pi where showing an .appledouble folder with a lot of files inside…
By removing the .appledouble folder which was into the /MagicMirror/Modules one…this error message stopped.
I’m convinced this .appledouble folder will be created again later my the MacOs…Nevertheless, I’m now sure that this error message was not causing any trouble in the end…So everything fine.

Anyway, thanks for support!!

@bibi
I’ve already made some trials with 1mm thin wood. Forget about it.
You will find the product data sheet with some recommandation at the bottom of below page :
link text

I’ve tried behing 2mm wood, with a hole (3mm diameter), it works fine. Not so ugly…

Let’s see.

Regards

Hi,
I’ve the PAJ7620u2 one.
I’m experiencing some stability issue with it (it always stops working after some minutes) but overall it’s great. I will post about the stability issue later on.

I’m interested into how you guys are using the sensor in a "beautiful way).
Before buying it, I thought I could cover it with some “speaker fabric” but it’s not working neither…

Do you have some smart ideas on your side on how to hide it?

Regards

I’ve searched the forum again and ZERO mention to .appledouble issue…
No one experienced that?

There are some monitors (TV mainly) which have automatic control of the brightness (based on a sensor). Maybe it’s that.
Was it present before PIR instalation Y/N? this can guide you.

From MHO, PIR sensor has Nothing to do with that (but not 100% Sure).

Regards

oh! I will look on the module again as I didn’t saw the famous screws you’re referring too…

Don’t worry @AgP42 , you already did a great job! Thanks again for that.

For the time being I will leave it like that (with your workaround) and if I have time on my side, I will maybe try to update MMM-PIRSensor. Maybe I could do it with trial and error method.

Thanks to the latest update of your module and MMM-GroveGestures (from @Sean ) , I end up with a perfect user experience :

• On my page 1 (main MM page), up / down gestures are handling news RSS details, etc…
• On my page 2, I have your iFrame and I’m able to change youtube live channels by up / down gestures also.

Perfect!

The Remote Control you are working on looks great also!

A bientôt et bonne continuation!! (tu as laissé qques indices dans ton code :-)

The sensor I’m using doesn’t offer this option, unfortunatly.
link text

Thinking of it again :

Would it not be more “sustainable” to PR MMM-PIRSensor by putting a second notification trigger “USER_PRESENCE, Screen Off” after the timeout delay.
Then, we could play within MMM-SmartWebDisplay with that one instead of the only USER PRESENCE false, true.
By doing that + adding the option to use it or not, it would make the full thing more reliable and generic.

If I believe it’s somewhere here :

                else if (value == valueOff) {
                    self.sendSocketNotification('USER_PRESENCE', false);
                    if (!self.config.powerSaving){
                        return;
                    }

                    self.deactivateMonitorTimeout = setTimeout(function() {
                        self.deactivateMonitor();
                    }, self.config.powerSavingDelay * 1000);
                }
            });

maybe you should let your module more generic that what you currently did.
If someone wants to STOP the video based on any other notification (like USER PRESENCE, false) he will always have the possibility to use MMM-NotificationTrigger to convert user presence to stop.

Up to you.

If you’re not keen to update that point (which I could understand), I believe I can maybe modify things a little bit myself to manage it.

Maybe the modification should be done directly in MMM-PIR Sensor, which should only trigger PRESENCE FALSE once the additional delay is over and not before…

No you’re right I don’t.

I believe I understood the issue :

• It seems the PIR sensor I’m using is very sensitive and triggering “USER PRESENCE FALSE” very easily.
• I’m able to manage it in MMM-PIR sensor module thanks to the additional delay option which I put to 30 seconds which is preventing the screen to turn ON / OFF every 2 seconds.

But this is then triggering the issue I’m referring to above for MMM-SmartWebDisplay.

Does that makes sense? It’s the only explanation I found for now.

I think it’s because of PIR Sensor “USER PRESENCE” notification!!!
(I don’t wnat any interaction between PIR and video), I only use PIR to turn screen ON / OFF.

And this issue is not new since your morning correction…It’s new for me because I installed PIR this morning!!!

Regards

@AgP42
Centering frame is OK now.
Lagging seems to be much better.
But it seems that new issue is happening. I get constant (uncontrolled) change between status Playing and Stopped which is stopping the video.

Strange.

Review :

• Using a list of several URL is working. Seems more “slow / laggy” than with iFrame-Ping and only one URL. Strange but OK.

• URL rotation is working great. (maybe a bit slow because of reloading needs, but I guess than there is not much you can do for that?)

• URL NEXT / PREV / PLAY / PAUSE is working like a charm. Which was my initial need, so perfect.

So all in all, a major and well managed update. Good job @AgP42 .

One thing :

Even by using the same size (% or px) parameter as in previous iFrame-Ping, the picture is much more smaller (tiny!!!) in this new module. Strange but nothing critical.

I’m displying youtube channels and “middle_center” parameter.

Nevertheless, when I increase the size of it, the centering is not working well. Indeed, the margin remains the same on left side, meaning the frame is off-centered on the right side of the screen.

Hope this can be fixed easily (I tried to look at it myself, .css, etc… but I’m not skilled enough). Maybe it’s something I’m doing wrong on my side…