Thank you. I will wait on the next version of MM. 👌

@sdetweil ahh that makes sense … I’ll keep that in mind!

@lornetw
(I removed the original post of mine and re-wrote it.)

905783f8-08aa-458f-92bc-7a48765ee7db-image.png
You can see + CREATE CONFIDENTIALS in upper side.
You can ignore CONFIGURE CONSENT SCREEN. (Or at least later you can configure it.)

40d74e9c-9432-47d8-8c7d-33b3c17015f9-image.png
After click +CREATE CONFIDENTIALS, you will meet the options, you can select OAuth client ID.

Then you will meet this.
d477f2b3-c938-48d9-94cb-98a0ff765ebc-image.png

@Extra I am having the same issue. Most of the news I see is new but I have news that is showing from 4 5 and 6 months ago as well. I have tried multiple different ways to format the config with the same problems everytime. Did you ever figure this out?

@karsten13 i thought that as well but it didn’t change anything

@jimmy_382837 awesome!!

well the problem was I think about privileges to issue the xrandr command from a shell. I got it worked out with xhost + and it works fine now. Thanks a lot for your help.

@Vizulize this module is working on my mirror, thank you!

@videogame95 this is another module that documents too much for the config.js …

modules:[ // DO NOT ADD THIS LINE... these only show where the lines should be placed. { // start of module definition module: 'MMM-AlexaControl', position: 'middle_center', config:{ image: true, pm2ProcessName: "mm", vcgencmd: "vcgencmd" } } // end of module definition ] // DO NOT ADD THIS LINE

@sdetweil Thanks for your response! I’ve restarted the whole host system (Raspberry Pi 4) several times and the message is gone.
Regarding your hint: I’ve actually tried it but hadnt any luck in identifying the correct DOM node. Also searching in the DOM tree for the word didn’t return any item.

Nevermind: Issue is gone since restarting the whole system 🙂

@gonzonia
A few modules have similar names; which one are you using exactly?