Black screen after 2.13 update - tentatively resolved

[sdetweil]

@swvalenti

//requiresVersion: “2.1.0”,
??

[swvalenti]

Correct, only pokemon had 2.1.0 I didnt see 2.1.0 in darksky just 2.2.0

[sdetweil]

@swvalenti and u commented it out in darksky, yes?

show errors

[swvalenti]

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-YvJxUhUeeIN7m4Y4YEc1FVS+YDCNVK6VsHIHx5z29EE='), or a nonce ('nonce-...') is required to enable inline execution.
main.js:487 Initializing MagicMirror.
translator.js:129 Loading core translation file: translations/en.json
translator.js:154 Loading core translation fallback file: translations/en.json
loader.js:176 Load script: modules/default/alert//alert.js
module.js:513 Module registered: alert
loader.js:148 Bootstrapping module: alert
loader.js:176 Load script: modules/default/alert/notificationFx.js
loader.js:153 Scripts loaded for: alert
loader.js:195 Load stylesheet: modules/default/alert/notificationFx.css
loader.js:195 Load stylesheet: vendor/css/font-awesome.css
loader.js:155 Styles loaded for: alert
translator.js:102 alert - Load translation fallback: translations/en.json
/home/pi/MagicMirror…rity-warnings.js:95 Electron Security Warning (Insecure Resources) This renderer process loads resources using insecure
  protocols.This exposes users of this app to unnecessary security risks.
  Consider loading the following resources over HTTPS or FTPS. 
 - http://0.0.0.0:8080/css/main.css
- http://0.0.0.0:8080/fonts/roboto.css
- http://0.0.0.0:8080/socket.io/socket.io.js
- http://0.0.0.0:8080/vendor/node_modules/nunjucks/browser/nunjucks.min.js
- http://0.0.0.0:8080/js/defaults.js
- http://0.0.0.0:8080/config/config.js
- http://0.0.0.0:8080/vendor/vendor.js
- http://0.0.0.0:8080/modules/default/defaultmodules.js
- http://0.0.0.0:8080/js/logger.js
- http://0.0.0.0:8080/translations/translations.js
- http://0.0.0.0:8080/js/translator.js
- http://0.0.0.0:8080/js/class.js
- http://0.0.0.0:8080/js/module.js
- http://0.0.0.0:8080/js/loader.js
- http://0.0.0.0:8080/js/socketclient.js
- http://0.0.0.0:8080/js/main.js
- http://0.0.0.0:8080/fonts/node_modules/roboto-fontface/fonts/roboto-condensed/Roboto-Condensed-Regular.woff2
- http://0.0.0.0:8080/translations/en.json
- http://0.0.0.0:8080/translations/en.json
- http://0.0.0.0:8080/modules/default/alert//alert.js
- http://0.0.0.0:8080/modules/default/alert/notificationFx.js
- http://0.0.0.0:8080/modules/default/alert/notificationFx.css
- http://0.0.0.0:8080/vendor/css/font-awesome.css
- http://0.0.0.0:8080/vendor/node_modules/@fortawesome/fontawesome-free/css/all.min.css
- http://0.0.0.0:8080/vendor/node_modules/@fortawesome/fontawesome-free/css/v4-shims.min.css
  
 
For more information and help, consult
https://electronjs.org/docs/tutorial/security.
 This warning will not show up
once the app is packaged.
loader.js:157 Translations loaded for: alert


0.0.0.0/:4 Uncaught SyntaxError: Unexpected token / in JSON at position 44
    at JSON.parse (<anonymous>)
    at XMLHttpRequest.xhr.onreadystatechange (translator.js:22)

[sdetweil]

@swvalenti let me work on it. is that a pi0 perhaps, running chrome instead of electron?

[swvalenti]

No sir it is a pi3b+ running buster

[sdetweil]

@swvalenti after looking at my dev console I see the same content security warning, but it is not fatal… just a warning…

I added the

requiresVersion: "2.1.0",

to the calendar and it worked fine,
then commented out

//requiresVersion: "2.1.0",

still worked ok…

and didn’t need that meta tag…

so, there must be something else going on…

can u rename the config.js out of the way (config.js.save)
and copy the sample

cp config.js.sample config.js 

and try MM again

[spitzlbergerj]

@m0bed said in Black screen after 2.13 update - tentatively resolved:

@m0bed So, I changed my config found out that this modules dont work at the moment:
MMM-Homematic-Heaters

The problem are the comments in the two translation files . Remove the comments and it will work again.

Since MMM-Homematic-Heaters seems to be no longer maintained, I have forked the module MMM-Homematic-Thermostats from it and developed it further. There the error is fixed. Maybe changing the module will help :-)

[swvalenti]

Somehow it was the MMM-DailyPokemon jacking all things up. Removed and all is working fine again.

[sdetweil]

@swvalenti probably the comments in the translation files, en and fr