@core Please provide any log. Execute pm2 log MagicMirror (if you are using pm2), reproduce the issue and post the log here.

When posting the log it is recommended to add it in a code block for better readability.

:clinking_beer_mugs:

@bimbim2401 Yep, on Windows its F12, on macOS its alt + cmd + i.

• Open the Network-Tab
• Look for the status code 101 (Switching Protocols) or just look for the type websocket
• Open the request
• Inspect the Socket as you wish (View frames, headers…)

@sharmstr Yep, thats true.

• Change *.css or Javascript file => Just reload the Webinterface (ctrl + r)
• Change config.json => Reload the Webinterface will do it 90%, else restart MagicMirror

@sharmstr Yeah, I always prefere to restart the whole MagicMirror using pm2 restart MagicMirror. Also pm2 is watching the config.json file for any changes and will execute the restart the MagicMirror automatically.

@jtmoore81 Well, this mirror is running pm2 there should be a watcher task running. Try to execute pm2 list to see if your MagicMirror is handled by it.

@sharmstr That’ll only apply the changes to the UI, not to the underlaying node modules.

@jtmoore81 Not really. Do you use pm2?

@rak This module is called MMM-forecast-io I am using it too:grinning_face_with_smiling_eyes:

@bimbim2401 Well, my Python times are a long time ago. Just try to run this script ans log the output. I also highly recogmend you to open Chrome and look at the Websocket frames.

@bimbim2401 Well, in Chrome I can see. That the MagicMirror Webclient establishes a Websocket connection to ws://IP:8080/socket.io/?EIO=3&transport=websocket&sid=SOME_ID. You can clearly see the communication, as the communication is not encrypted at all.