@cheminge also, what is the default behavior if the module(s) are not in the ‘current’ timeframe? or not in any schedule?

I tried to install the module , but I don’t get any data on my mirror, just “Next ISS fly over”, “Visible”, “Max Height” “Appears” and “Disappears”. Has anyone have suggestions to solve this? { module: 'MMM-ISS', position: 'bottom_right', config: { // These values must come from available locations on the SpotTheStation site: https://spotthestation.nasa.gov/ country: "Netherlands", region: "Flevoland", city: "Almere", minElevation: 40 // 40 Lowest elevation for the panel to show up } },

@torafadora maybe change the paths to ‘modules/MMM-GoogleTasks/…filename’ as the module is executed w MagicMirror running in the MagicMirror folder

@BKeyport ah, but description is an optional field

@sdetweil THANKS to YOU for your huge effort here in this place! Ralf

@sdetweil , yes it was startet under the wrong User. Now it is working. Thanks :)

It was the fade! when I switch the fade to 0, even the refresh of 1 seconds works and displays perfectly. @sdetweil you are brilliant! Thank you!

@mvrlogins yes, doing test run. because your (all of you) MagicMirror systems have been built and are important to you, i am very cautious about making changes. we update MagicMirror 4 times a year, i dont need to crash your system every time!! so upgrade is a 2 part process also, many users, not yet knowing the system design, change MagicMirror files which should not and do not need to be modified. but IF modified, the update will fail unless forced AND your changes (which you may not remember) will be lost 1st is test, make no changes if all goes well 2nd pass, actually DO the upgrade, same command, with an additional parameter , apply there is a second copy/paste line in the doc for this you only did pass 1, test mode

@sdetweil I am not using the MMM-RemoteControl. The only other modules I have so far is Nest-Status and Screencast. Changing the module config language to ‘false’ allowed the program to launch and everything is functional now. It is just using the module default now. Thanks for the help!

he had nvm installed too, conflicts with n ( nodejs version of nvm)

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