Hi, I don’t use that module, but you could try mmm-soccerlivescore module, which works for me

Hi everybody I have a problem with the latest version of MM and my Domoticz module. I use this Domoticz module (link below) and when i start MM, i have a error message on console like Domoticz could not load data Access to XMLHttpRequest at… from origine http://0.0.0.0:8080 has been block by CORS policy. the request client is not a secure context and… [link text](https://forum.magicmirror.builders/topic/11123/mmm-domoticz-cannot-read-property-0-of-undefined/14?page=2link url) I try different things but still not working: i try this link but nothing : usecoreproxy [link text]https://github.com/MichMich/MagicMirror/issues/2714#issuecomment-1024627426(link url) i try this link but nothing: websecurity = false [link text]https://forum.magicmirror.builders/topic/16131/mmm-hue-cors-policy-issue/2(link url) Can you help me please ?

I don’t know about the Pi3, but on the Pi4 you just go to display settings and tell it to go vertical… easier than all this programming that I never got to work with my MM

Hi everybody and @bugsounet I just updated MMM-google assistant and MMM-assistant2display an now i have an error with spotify. I can’t see on the bottom of my screen the listening music. In console i have these errors: spotify.js:1 Uncaught TypeError: Cannot read property 'src' of null at Spotify.updateSongInfo (spotify.js:1) at Spotify.updateCurrentSpotify (spotify.js:1) at Class.socketNotificationReceived (MMM-Assistant2Display.js:1) at module.js:250 at Socket.<anonymous> (socketclient.js:39) at Socket../node_modules/component-emitter/index.js.Emitter.emit (index.js:145) at Socket.emitEvent (socket.js:253) at Socket.onevent (socket.js:240) at Socket.MMSocket.self.socket.onevent (socketclient.js:33) at Socket.onpacket (socket.js:204) updateSongInfo @ spotify.js:1 updateCurrentSpotify @ spotify.js:1 socketNotificationReceived @ MMM-Assistant2Display.js:1 (anonymous) @ module.js:250 (anonymous) @ socketclient.js:39 ./node_modules/component-emitter/index.js.Emitter.emit @ index.js:145 emitEvent @ socket.js:253 onevent @ socket.js:240 MMSocket.self.socket.onevent @ socketclient.js:33 onpacket @ socket.js:204 (anonymous) @ index.js:21 ./node_modules/component-emitter/index.js.Emitter.emit @ index.js:145 ondecoded @ manager.js:207 (anonymous) @ index.js:21 ./node_modules/component-emitter/index.js.Emitter.emit @ index.js:145 add @ index.js:117 ondata @ manager.js:199 (anonymous) @ index.js:21 ./node_modules/component-emitter/index.js.Emitter.emit @ index.js:145 onPacket @ socket.js:387 (anonymous) @ socket.js:196 ./node_modules/component-emitter/index.js.Emitter.emit @ index.js:145 onPacket @ transport.js:103 onData @ transport.js:96 ws.onmessage @ websocket.js:108 My config.js is the same before and after the update. and token on spotify is ok Do you have a solution ? thx

I it working now for you? :)

@MisterT good !

Solved see module in health section

@mistert electron is enforcing more things than before… see this post for a possible workaround https://forum.magicmirror.builders/topic/16384/node-helper-access-control-allow-origin/2?_=1645457720236

@MisterT Great it worked for you. Please mark the post as Resolved if you are happy that it worked.

@mumblebaj Hello, did you fix it ? I got kind of same issue…

Hi I just install magic mirror on my raspberry pi 3 b+ and i install the wallberry theme module. In order to see the unsplash wallpaper, an app must be create on unsplash website to obtain a secret api code. But after few days, unsplash sends me a mail witch says that my app is not compatible with unsplash rules. The mail below: The way you currently have your app designed violates point 3 of the API Usage Guidelines - You cannot replicate the core user experience of unsplash.com The best way to make sure your application doesn’t violate this guideline is to integrate Unsplash inside an existing app that offers more value than simply the Unsplash integration. Some examples: ✓ the Ghost integration brings Unsplash inside Ghost’s editor to improve the workflow of finding beautiful images. Without the integration, the app still offers a lot of value to its users. ✕ a wallpaper app that returns Unsplash images for downloading. Without the integration, the app has no content. Because your app is a wallpaper app, it currently violates the above API Usage Guideline. We’re all for remixing and open-source, but the API costs us a non-trivial amount of money to host, operate, and provide support for. We’d prefer not to be paying to actively support apps that are offering similar or competing services. Therefore, we’ve disabled your application. You are still more than welcome to use our API, just not in this specific way. Thanks for understanding, and I’m more than happy to elaborate on anything if you need me to. Can anybody says me the problem and provide me a solution. Thanks for next answers