@angeliKITTYx I had a little trouble with the google calender stuff because at first I didn’t realize I had to get a google developer account and then I could setup the api’s. Every once in a while, especially if my mirror has been unplugged for 24 hours, I have to do the authorize again. Also I have to first delete the token file that gets created. The authorize script won’t over write the token. Maybe look at the instructions for the MMM-GoogleCalendar might help you? The two modules seem very similar.

@uok825 Is it the default newsfeed module that is causing this or a different third party newsfeed module?

@JohnGalt have you tried MMM-OpenWeatherForecast instead? It seems to work better for me adn it uses the OpenWeather Map api too.

@grssll is your relay already wired to your pi? And does it already work when you use the command line to change the state of the GPIO pin?

@jedilkeme Are you playing audio on your mirror? Or just including it as an output source as if it were a player along with other speakers and wanting it to display? If you are just playing to the mirror with a speaker in it, maybe switch hardware to something like this… ScoutMakes FM Radio Board - STEMMA QT / Qwiic? there is lots of example code. And the data can be obtained over i2c . The you can use a notifications module like wishmaster270 suggests.

https://www.adafruit.com/product/5651?gad_source=1&gclid=CjwKCAiAq4KuBhA6EiwArMAw1CkSTxJ_mtdJMa8nsHrugQ0K9NQJjcs-J5pREWLWUQjjNugFIrnUJRoCwfkQAvD_BwE

@grssll Does your led strip have it’s own remote control? is it rf or blue tooth? or wi-fi? Could you emulate that in your pi on the command line? It is possible to have the module in the pi execute a command line script , like the monitor on and off command.

Depending on how your led strip is controlled, Maybe you could use IFTTT. Lots of led light brands will work with it, if the lights are wi-fi based.

Just suggesting some ideas.

@jedilkeme maybe looking for RDS or RBDS decoding will help. One standard is used in North America (don’t remember which the other is European).
There are some fm receiver projects for the pi that discuss getting the meta data. https://hackaday.com/2021/09/07/an-inexpensive-fm-receiver-for-the-raspberry-pi/ could maybe lead you to info you need. Though I am not sure if bluetooth audio is encoded into the audio stream in the same way as FM. It likely is. But again, maybe not.

@Feedy88 said in MMM-Pir Issue:

localhost to 0.0.0.0

localhost is normally the same as 127.0.0.1 for most computers. Why are you wanting it to be 0.0.0.0?

@grssll what ‘relay’ are you talking about?

I got the Vilros V4 mirror so I didn’t have to source stuff. And I want to know the impact of the construction and venting limitations on the new RaspberryPi 5 that I have. I have installed MMM-Pinfo and having problems. I think that the rpi5 is too fast for async to get the data before the pi trying to use it. Or something like that. I tried out some of the other cpu stats modules and they all have problems. But they are pretty old too. MMM-Pinfo works on my rpi4. And all my other modules are displaying fine. I’ve disabled the other modules to make sure they weren’t a problem and I think it comes down to the node_helper.js in the MMM-Pinfo. Or the package systeminformation being updated broke something. But then I think the error would be different. For sure nothing is coming back from systeminfomation. I only see the loading messages.

here is what is in my pm2 logs:

at new Promise (<anonymous>:null:null)
0|MagicMir |     at Class.getCPUInfo (/home/kelly/MagicMirror/modules/MMM-Pinfo/node_helper.js:167:16)
0|MagicMir |     at Class.collectDynamicInfo (/home/kelly/MagicMirror/modules/MMM-Pinfo/node_helper.js:82:20)
0|MagicMir |     at Class.scheduler (/home/kelly/MagicMirror/modules/MMM-Pinfo/node_helper.js:69:9)
0|MagicMir | 
0|MagicMir | (Use `electron --trace-warnings ...` to show where the warning was created)
0|MagicMir | [25.01.2024 23:15.36.946] [ERROR] (node:7179) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

And this forum topic made me think my pi is too fast and so maybe Pinfo needs working over maybe sothe script can wait on the answer from the systeminformation?

https://forum.magicmirror.builders/topic/15539/async-functions-inside-node_helper-js/5

i’m not sure quite how to start, but I will try if you all think that is what is probably going on. I’m not quite a newbie but haven’t touched this since last year and I’m definitely no expert.