Within terminal these work flawlessly.
vcgencmd display_power 0 to turn off
vcgencmd display_power 1 to turn on
However my cron job isn’t turning my monitor back on. Any suggestions? This is my cron job
0 14 * * * root /usr/bin/vcgencmd display_power 1 >/del/null 2>&1
0 23 * * * root /usr/bin/vcgencmd display_power 0 >/dev/null 2>&1
Am I missing something?
Would anyone be so kind to explain what I’ve done here?
pi@raspberrypi:~ $ cd ~/MagicMirror
pi@raspberrypi:~/MagicMirror $ git status
On branch master
Your branch is up to date with ‘origin/master’.
Changes not staged for commit:
(use “git add …” to update what will be committed)
(use “git restore …” to discard changes in working directory)
modified: installers/mm.sh
modified: modules/default/clock/clock.js
Untracked files:
(use “git add …” to include in what will be committed)
0
Cron/
core
installers/pm2_MagicMirror.json
run-start.sh
Good call on the new ip address. Thanks Sam. everythings up and running again
restarting modem and router didnt help any when I was testing dongle-less.
It’s working fine now with the dongle, I just wish I understood what caused the built-in wifi to drop
Ideally I would like to avoid using the dongle all together, but the Pi doesn’t seem to want to stay connected without the dongle. Yes, I can take the mirror off the wall and connect a mouse and keyboard.
I have a wireless keyboard/mouse on the way to avoid needing to take the mirror off the wall constantly.
Not sure what the problem is. suddenly my pi and subsequently magic mirror had lost wifi connection.
I inserted a wifi dongle into the raspberry pi4 which seems to now allow the pi to connect to wifi uninterrupted.
However with the wifi dongle, VNC no longer works from my pc to troubleshoot AND the magic mirror remote app (the best) has also stopped connecting.
Any advice on where to start troubleshooting?
I think I am having a similar issue. The entire mirror refresh rate gets slower and slower the longr the mirror has been on
Any solution found?
Thank you for the response. I only looked at the link quickly, but I’m not sure that its the issue. Unless I am misunderstanding syncing time as described.
My issue is more about the pi taking incrementally longer to refresh each module, I only mention the clock module because the seconds display is the most noticeable. Still very much open to any thoughts or suggestions
I’ve been modifying my mirror for a little while now, and have my config file pretty cleaned up. But have a question.
I’ve noticed after a fresh restart of the pi, everything runs very smoothly. Modules update perfectly and on time. The clock modules seconds display is perfectly in time. However, over time, the modules start lagging on their refresh rates. The clock modules “seconds” display - instead of every second, starts updating every other second. And after being on for a full day or two, every 5-10 seconds.
I only mention the clock module because it is the most noticeable, but other modules are also experiencing similar refresh issues.
This seems like a fixable issue, but I’m not positive where to being looking.
Hopefully I’ve described the problem correctly.
Can anyone offer any suggestions?
Thank you so much
Nick
I used Bear glass in brooklyn. Very good prices. I payed 150 for a 28"x 17" piece of glass
The remote control module works wonderfully.
The only issue is one of the modules does not dim with the others. Not sure why. MMM-RAIN_MAP stays bight regardless of the level of dim within the remote control app. Any thoughts?
N
@sdetweil
Hi Sam. Yes, I did. Unfortunately because I am on a Pi4 they are unable to troubleshoot…
I reinstalled the module fresh and retrieved a new API from api.mta.info, not clear on the error
socketNotificationReceived: “TRAIN_TABLE”:
Array(2)
MMM-nyc-transit.js:332 Uncaught TypeError: Cannot read property ‘fadeSpeed’ of undefined
at Class.socketNotificationReceived (:8080/modules/MMM-ny…-nyc-transit.js:332)
at module.js:245
at Socket. (socketclient.js:38)
at Socket…/node_modules/component-emitter/index.js.Emitter.emit (socket.io.js:1915)
at Socket.emit (socket.io.js:1544)
at Socket.emitEvent (socket.io.js:1161)
at Socket.onevent (socket.io.js:1135)
at Socket.MMSocket.socket.onevent (socketclient.js:32)
at Socket.onpacket (socket.io.js:1089)
at Manager…/node_modules/component-emitter/index.js.Emitter.emit (socket.io.js:1915)
I tried reinstalling a MMM-nyc-transit module.
Once I’ve inserted the code into the config file, the MM screen goes black, and I do not have access to web developer window.
Removing the MM-nyc-transit config file brings everything back…
Any ideas?
I’m running into this exact issue today. New install has not resolved. Neither has requesting a new API key. Any suggestions?
Thank you Sam. I’ll check this out:)
Ohhh ok. I’ve been trying to redirect, if that’s the right word, the MAC address I believe is the Pi.
But getting errors that the address is currently in use…
I’m using the Motorola SURFboard SBG6580-G228.
I haven’t yet modified anything, but still have connection through the mmm-remotecontrol and VNC for some reason.
N
TBH I don’t know the difference. Ideally whichever is safest and won’t slow down or effecct other devices on wifi…
N
Hi there. I’ve had your great module working in the past, and I’ve been having some issues since a fresh install. Getting error repeated over and over,
socketNotificationReceived: “TRAIN_TABLE”:
Array(2)
MMM-nyc-transit.js:332 Uncaught TypeError: Cannot read property ‘fadeSpeed’ of undefined
at Class.socketNotificationReceived (:8080/modules/MMM-ny…-nyc-transit.js:332)
at module.js:245
at Socket. (socketclient.js:38)
at Socket…/node_modules/component-emitter/index.js.Emitter.emit (socket.io.js:1915)
at Socket.emit (socket.io.js:1544)
at Socket.emitEvent (socket.io.js:1161)
at Socket.onevent (socket.io.js:1135)
at Socket.MMSocket.socket.onevent (socketclient.js:32)
at Socket.onpacket (socket.io.js:1089)
at Manager…/node_modules/component-emitter/index.js.Emitter.emit (socket.io.js:1915)
Any suggestions?
Thank you so much for your time and amazing module.
Nick