@RonR I have completed the fixes for this problem as a general solution… thanks for pointing it out. git pull in the module folder to get the fix (on docker you have to docker exec into the container first)

@TAGinside said in MMM-ISS-Live error 153: @karsten13 @karsten13 made some changes to the environment of the module on github, I reloaded the module and the error is gone. Thanks for the help, sorry it took so long to acknowledge the fix.

@RonR you opened this in general, not troubleshooting, so it can’t be closed

@OrangeMirror the current docker setup will only work for multiple instances IF you use the MM_CONFIG_FILE environment variable to run instances off different config files, or the MM_PORT env variable to override the port if using the same config.js all the files will come from the ONE folder tree ~/magicmirror so this means you would have to setup multiple entries in the compose.yaml to launch multiple instances (with the different config parms) You have to change the container name too this is because all the DATA used by the container is external (on docker host filesystem) and not IN the container an example NOT using docker, but same idea here https://docs.magicmirror.builders/configuration/introduction.html#advanced-configuration-and-frequently-asked-how-to-configure-examples

@RonR there a bunch of config options not listed in the readme i think showMarquee:false [image: 1754787212070-img_2117.png]

OK, that helps make sense now. Thanks

@RonR i dont know that module. we provide support for google calendars as part of the base package. get the ical format url, public or private and put that in the url: property see the startup config.js which uses a calendarlabs url to get the url open your calendar in a web browser, select the specific source in the left nav, click the 3 dot menu to the right, settings scroll down to sharing, select the ical format url (not embed) or secret url