@Ray
Hi, I do not know your set up nor do I know when the “in one day” changes to the next day at OpenWeaterMap.
I use the API Key exactly in this module and only have one instance of the mirror running…
I just checked my statistics at OpenWeaterMap and I do have at about 112 calls a day. Which is correct as my mirror is shutdown between 11:30pm and 5am.

Maybe it is a matter of your timezone and calls of the last day are counted in the current one.

What does your statistic look like

https://home.openweathermap.org/statistics/onecall_30

Edit:
And one small side note. Even if you use different keys the calls a summarized per account

@sdetweil In default the module calls the Api every 10 minutes.

@megagprime You will need to update to the new fork of the module.
It does not matter if the old settings worked for years as the provider shut down the old api and you need to use the new api if you want some information to be displayed again.
The original module did not provide a way to change the url the information is fetched of. Even if you add the apiBaseUrl to the settings the old module will ignore it.
I released a new version IN MY FORK yesterday which uses the new URL in default. So no need to set the base URL in the settings anymore. The version in my fork before yesterday needed the parameter in the config to work with the new api.

So either change to my fork and update with:

cd ~/MagicMirror/modules/MMM-OpenWeatherForecast

git remote set-url origin https://github.com/Tom-Hirschberger/MMM-OpenWeatherForecast.git

git pull

rm -rf node_modules package-lock.json

npm install

Or remove the old module folder and reinstall from this Url:

My Fork

@megagprime

Hi and sorry for the late reply.
I am pretty busy with my kids and do not have much time to code at the moments.

I changed the default url of the module to version 3.0 as 2.5 has been shut down in June.

I also updated the Readme to respect the latest changes.

Are you sure you use my fork of the module and not the original one?

The url of my fork is https://github.com/Tom-Hirschberger/MMM-OpenWeatherForecast/blob/master/README.md

@Cr4z33 Hi and welcome back.
I still do not have a glue about the RTSP module.

Can you please provide your RTSP config. I try to reproduce the problem but do not have much time to test at the moment.

@Sceetch Hi, yes, you will need to add it to the end of the single line that is in the file

@Sceetch
Hi,

on older OS Versions (i.e. Bullseye) the file is located under /boot/cmdline.txt

@Sceetch
Hi, a user of my Screensave module reported a similar problem a couple of days ago and worked out a solution.
Maybe take a look at the troubleshooting section at the end of my readme under
https://github.com/Tom-Hirschberger/MMM-Screen-Powersave-Notification

@Cr4z33 Hi,

think I found the problem.
You need to send streamX as value where X is the number of the stream in the configuration of MMM-RTSPStream.
You will need to configure the camera information in the MMM-RTSPStream module and only will be able to start the stream by notification

@Cr4z33 The two datatstructures are arrays containing objects. So you can simply append the two objects…

var mqttHook = [
  {
    mqttTopic: "zigbee2mqtt/BTicino F20T60A",
    mqttPayload: [
      {
        payloadValue: "",
        mqttNotiCmd: ["POWERMETER"],
        mqttPayload: ""
      },
    ],
  },
  {
      mqttTopic: "DahuaVTO/VideoTalkLog/Event",
      mqttPayload: [
        {
           jsonpath: "Action", 
           conditions: [
                       {
                         type: "eq",
                         value: "Pulse"
                       },
                     ],
          mqttNotiCmd: ["doorbell"]
        },
      ],
    },
];

var mqttNotiCommands = [
  {
    commandId: "POWERMETER",
    notiID: "POWERMETER_VALUES",
  },
  {
      commandId: "doorbell",
      notiID: "RTSP-PLAY",
      notiPayload: "YOUR-STREAM-URL" 
    },
];

module.exports = { mqttHook,  mqttNotiCommands};