looks like you still have an old labwc image, try from /opt/mm/run folder:
docker compose pull
docker compose up -d
looks like you still have an old labwc image, try from /opt/mm/run folder:
docker compose pull
docker compose up -d
@plainbroke did you do an npm install after the git pull?
@hahawoooooo I also recommend using the classes approach to config
modules:[
[ "page1"],
[ "page2"],
],
"fixed": ["fixed"]
. Etc
Then for the modules you want on page1
Add
classes:"page1",
In the config below module: line
This was so much easier for me
@raymonvdm can you show the log?
I always recommend testing with manual start after you make a module change
pm2 stop all
cd ~/MagicMirror
npm start
if it comes up ok, ctrl-q, or alt-spacebar, c
then pm2 status
and pm2 start xxxx
where xxxx is the name or number on the row for your application
@chrga ok. Should be nothing to stop it
Did you try my Module and the examples on the alert module
did you add the ViewNotifications module so you could see it being broadcast
The structure of the notification is exactly the same as if you were coding it in a running module
@chrga also, for debugging, install
MMM-ViewNotifications
@chrga MagicMirror has to be configured to allow remote access
In config.js
address:”0.0.0.0”,
ipWhitelist:[],
@chrga see my curl to notification module
Just a simple http post
https://github.com/sdetweil/MMM-CurlToNotification
Let me know if you get another black screen without mm start after reboot (I want to know if it is fixed or not …)
Can you please show me again the output of docker compose config (so I can check if you have the latest changes)?
@Racing88 as I said, not module developer. That’s how I would have made them different