As an update, based on the pointers from @KARSTEN13 and @SDETWEIL, have a workaround. Had three issues going on. 1: I found that on a graceful reboot (shutdown -r now) that it would generally start fine, but not on an ungraceful reboot (power cycle the machine). Looks like when it was ungraceful reboot, the labwc container would show with uptime of (for example) five hours when ‘docker ps’, even though the machine was rebooted 20min ago after ‘docker compose up’ was executed by install.sh. Whereas the magicmirror container would have recently started. I assume kind of lock file confusing things? Workaround was to change the first ‘docker compose up’ install.sh to ‘docker compose up -d --force-recreate’ 2: I’d also included a pause and --force-recreate at the end of the install.sh and noted it was never executing as per @KARSTEN13’s suggestion. Looked like the install.sh script was hanging at docker compose pull. Commented that out. 3: Lastly, the initial ‘docker compose up -d --force-recreate’ in install.sh would still fail often with the mm container restarting with logs as per the original post. With a 7 min pause and then second ‘docker compose up -d --force-recreate’ it seems to start the second time well (3min wasn’t enough, 5min was better, 7min seems to work). Workaround is a bit on the slow side, at some point will see if can refactor it a bit so that a pull for updates occurs. Extract of resulting install.sh below. _info "--> Pulling docker images and starting magicmirror" # need sudo for docker here if docker was installed with this script # use up so mm can start if there are already local images _info "--> Pre Start Pause for 2min" sleep 120 _info "--> Start and recreate" $_sudo docker compose up -d --force-recreate #_info "--> Pull Pause for 1 min" #sleep 60 # pull new images #_info "--> Image Pull" #$_sudo docker compose pull #_info "--> Restart Pause for 1 min" #sleep 60 # restart (only if new images pulled) #_info "--> Restart stopped" #$_sudo docker compose up -d _info "--> Final Pause for 7 min" sleep 720 _info "--> Final start and recreate" $_sudo docker compose up -d --force-recreate if [[ "$_sudo" == "sudo" ]]; then _info "--> Reboot needed, starting in 120 sec. (use ctrl-c to skip)" sleep 120 sudo reboot now fi # cleanup $_sudo docker image prune -f

@sdetweil No worries. Thanks for the response.

@sdetweil I did not see this, sorrz about that. Now both work perfectly thank you

@Sandy2503 see the 3rd party module list, linked in the header above

@chrisfr1976 Thank you for sharing. This helped me it seems it was an issue with my conditions using the ev.title.search(‘string’) solved my issue. eventTransformer: (ev) => { if (ev.calendarName === "Trash") { const trash = []; ev.color = 'gray'; if (ev.title.search('Altpapiertonne') > -1) { trash.push("fa-solid fa-trash trash-blue") } if (ev.title.search('Gelbe Tonne') > -1) { trash.push("fa-solid fa-trash trash-yellow") } if (ev.title.search('Biotonne') > -1) { trash.push("fa-solid fa-trash trash-brown") } if (ev.title.search('Restmülltonne') > -1) { trash.push("fa-solid fa-trash trash-black") } ev.symbol = trash; if (trash.length === 0) { ev.symbol = []; ev.color = "none"; } } return ev; } } } [image: ycfzpQ5G]

@karsten13 Thanks! That worked! Somehow I missed that FAQ :) – Rune

@jlward73 ah, no buttons. i’ve never used this carousel feature i use MMM-pages and MMM-pageindicator

Thank you again I will leave it like this thanking you too afraid of hurting

@Dexter1088 awesome

@wyovino shouldn’t need to, the os is ending . all processes will be stopped

@atl944 said in Weather issue: do you have any good resources for MagicMirror in general what do you mean? there is the doc, linked in the top menu https://docs.magicmirror.builders/configuration/introduction.html#basic-configuration-of-magicmirror2 and here of course we don’t provide any video tutorials, altho others have done that for some solutions i am the moderator here, but also module developer, and support the install/upgrade scripts, and backup/restore scripts too…

@mmmmh OK, Here’s what I did: I can control everything else with Scenes2 and for CalendarExt I use Remote-Control’s REST API.

@JMac yes

@FalcoonnnnPUNCH correct. NEVER use sudo for any MagicMirror related commands sudo makes everything owned by root where no user can modify just use my install/upgrade scripts. listed in alternative install section of MagicMirror doc

@mrsmith81 and the fix

@DDE12 yes

@neo_anderson you can try it out See https://forum.magicmirror.builders/post/123306 There is more info before that post, but this gets you the latest version

@sdetweil OK, tanks anyway. It seems there is something special in my mirror. Not that magic but unfortunate…

@Old_Death I do not know this module specifically But some things At the top you have two module: In js this is allowed, but the last one wins This means you have two instances of the schedule module About MagicMirror , this is called a single page web application We can only show or hide content. Pages, carousel, voice reco, profile switcher and module scheduler hide and show modules for different purposes As I understand it the scheduler module looks at the individual modules for a property to describe when it should be shown ( from-to) Scheduler has no ui of its own. So all info about images etc belong to the module that can display them. So all those parms need to move And the targeted modules do not KNOW anything about Scheduler, they will be shown or hidden Any properties added to be used by another module are unknown

@pclark2 woohoo!!