@twosquirrels I’m having the same issue as you. An issue with the Uber API perhaps?

@jdahli1 Anyone have any thoughts as to what else to try? I have had no luck so far. Mirror continues to not turn back on randomly. Nothing I have changed so far seems to have worked. Any thoughts are appreciated.

@Hawking So running that command has the same result - nothing happens until I ctrl + c. I have been messing with the hdmi_* commands, but no luck so far.

@Hawking Thank you for the reply. Running that command does not appear to do anything. I let it sit for a minute and the command never completes, nor does the screen come on. It will sit until I ctrl + c. I will start to mess with the hdmi settings and see if that makes any difference.

So after far too many months, I’ve finally gotten my mirror put together. Everything is working great, except for this module (sometimes). After a reboot everything works at least once, meaning that the monitor will turn off when no motion is detected and turn on once motion is detected. Sometimes, it will work correctly for an entire day. Others, it will work once and then the monitor will not turn back on until I reboot the pi. After the monitor refuses to wake up, I receive the following in the pm2 logs when it does detect motion.

0|mm       | monitor :state 0x7ee68dbc [HDMI unknown AR x38128 HDCP], 2129038664x4287062190 @ 45744.00Hz, interlaced
0|mm       | monitor :state 0x7ee8bdbc [HDMI unknown AR x13552 HDCP], 2129182024x4287062190 @ 21168.00Hz, interlaced
0|mm       | monitor has been deactivated
0|mm       | monitor :state 0x7ebe5dbc [HDMI unknown AR x25840 HDCP], 2126404936x4287062190 @ 33456.00Hz, interlaced
0|mm       | monitor :state 0x7e9afdbc [HDMI unknown AR x13552 HDCP], 2124086600x4287062190 @ 21168.00Hz, interlaced
0|mm       | monitor has been deactivated
0|mm       | monitor :state 0x7e8dadbc [HDMI unknown AR x21744 HDCP], 2123214152x4287062190 @ 29360.00Hz, interlaced
0|mm       | monitor :state 0x7efdcdbc [HDMI unknown AR x54512 HDCP], 2130562376x4287062190 @ 62128.00Hz, interlaced```

Does anyone have any thoughts on how to prevent this from happening? Is there a better place to look at logs other than pm2 to see exactly what is happening. It is very odd to me that it works for different amounts of time after each reboot.

For what it’s worth, when the screen stops waking up, I can navigate to rasperrybi.local:8080 in a browser and all of the modules are up and running.

Any thoughts or comments are appreciated.

@danielis Fingers crossed, this appears to be working! The mirror has turned on and off a dozen times now with no processor or RAM issues.

@in_a_days I guess I do run more modules than what “fit” the screen, but they’re cool and I can’t make up my mind which ones I want to keep lol.

However, I don’t believe that is the issue here. I have disabled all but three modules and still face the same issue. The second time the screen goes to sleep, it will not wake up. It doesn’t seem to matter what the CPU load or RAM is at.

Watching the pm2 logs, I get an uncaught exception error when the screen is supposed to wake up, but that is all the details I get from it. (That I know how to see, still new to this)

@strawberry-3.141 Working perfectly. Thanks!

@trividar I’m having a similar issue. My mirror will turn on and off a few times, but after a few minutes it will peg the RAM and completely lock up the pi. Not sure what to try next.

Thank you for this. Everything is working perfectly except for my time, which is three hours off. How would one go about changing time zones? The time on my clock module is correct to my location.