@unaccomplished
Hi,

just tried your config in my setup and everything worked as expected.

The question is…where are the differences in your and mine setup.

As a first try you can replace embedElementType: "webview," with embedElementType: "iframe,".

If the embeded pages does not block embedding iframe should work and you do not weaken any security settings of the electron browser.

Additionally you can replace "frameborder=0", with "frameborder=1",. You should see two boxes at least then. Even if the sites could not be embedded.

@sdetweil Are you sure you set the security settings of electron? Without them electron will not support webview and will not display anything.

@BKeyport Sorry, to one I’m the documentation is the correct one.

Great to hear it is working.

@sdetweil
Hi Sam,

you are right. But i do not want the content to be fixed as some users want the content to be recreated after the configured interval.

I just released a new version 0.0.8 of the module which introduces a updateDomOnShow option. If the option is set to false the module uses the old html elements after a resume. Maybe this fixes the issue.

@sdetweil Hi, the module calls the updateDom function every time it gets resumed in the current implementation.

I am not sure if I can implemt a block option to skip the update dom but reset the timer for the regular updates.

@JohnGalt
Hi,

you will need to change line 108 in MMM-DynamicWeather.js and line 130 in MMM-DynamicWeather.ts.

Both show this at the moment:

this.url = "https://api.openweathermap.org/data/2.5/weather?appid=" + this.config.api_key; 

And you will need to change it to:

this.url = "https://api.openweathermap.org/data/3.0/onecall?appid=" + this.config.api_key;

But no guarantee this will work.

@JohnGalt
Hi,

this module uses the old OpenWeater Map Api in version 2.5 to get the current weather.
This version of the Api stopped working recently.
The module needs to be migrated to the new version 3 Api.
As the data is returned in nearly the same format as before it might be enough to change the version in the hard coded Url of 2.5 to 3.

You will also need to get a new Api key for the new version. You will need to provide credit card information but 1000 calls a day a free.

Just to make clear.
The requestDelay is only used for the time between the start of the mirror and the first fetch of the data.
For all following the updateInterval in seconds is used.

The module sends is weather info, too. But I think both modules are not capable of use the info provided by notification at the moment

@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};

@BKeyport Hi, can you make a screenshot of the things styled outside MagicMirror so we can see how it should look exactly?
Maybe you will need some additional classes in your module config to make it possible to select the different elements jn CSS.

@Cr4z33 Hi, you will first need the URL of the RTSP stream of your camera.
In the next step you will need to subscribe to the topic in the file mqttDictionary.js

var mqttHook = [
    {
      mqttTopic: "DahuaVTO/VideoTalkLog/Event",
      mqttPayload: [
        {
           jsonpath: "Action", 
           conditions: [
                       {
                         type: "eq",
                         value: "Pulse"
                       },
                     ],
          mqttNotiCmd: ["doorbell"]
        },
      ],
    },
  ];
var mqttNotiCommands = [
    {
      commandId: "doorbell",
      notiID: "RTSP-PLAY",
      notiPayload: "YOUR-STREAM-URL" 
    },
  ]; 

But you will need to find a way to stop the stream in any way.

@BKeyport
Hi and sorry for the late reply.
I am not sure if I will have time to test your case the next days.

I think your main problem is that you try to use “normal” styling directives for the layout but I use flexbox css as the basic.

You can find a short tutorial at:
https://css-tricks.com/snippets/css/a-guide-to-flexbox/

Edit:
Had 5 minutes and did a quick check.
I think the following two statements are a good starting point:

.MMM-ValuesByNotification .vbn .groupsWrapper {
  flex-direction: row;
}

.MMM-ValuesByNotification .vbn .valueWrapper {
  flex-direction: row;
}