@cweinhofer Hi,

I do not know ESPHome but it looks like it sends the data via MQTT.
So you can use MMM-MQTTbridge to receive messages and MMM-ValuesByNotification to format and display them.

@digied Just released a new version which fixes the host part replacement

@digied Perfect. I will look into the module to check if I can accept self signed certificates and why the host part is not replaced correctly.

Edit:
You should be able to set the cam with by adding some CSS to the file MagicMirror/css/custom.css:

.MMM-SynologySurveillance .cam { 
    width: 100%; 
 }

@digied Hi,

it’s nearly perfect. Now the needed library and the access to the NAS works.
The output of your log shows that the fetched URL contains the hostname of your NAS AND the IP.
Maybe there is a bug in my replaceHostname function.
Your config contains a replaceHostPart set to true.
Can you set it to false please.

Edit: Now that I see all your posts things are clearer ;-)

@digied That log looks totally different than the other one. What did you change?

@digied
There two things i do not understand…

• Did you modify your package.json? The original one of the module contains “syno”: “latest” as a dependency. Which will install version 2.2.0 currently. But the part of your package.json contains “syno”: “^1.0.0” which will install the latest 1.x version. I did not use any 1.X version in my module and do not know if the surveillance part did already exist in this old version. Please use the original version of the package.json. No need to make any changes to it.
• Why did you need to use sudo for npm install? Only files in the module folder get modified by npm install of this module. There is no need to use sudo in a regular installation. Installing things with sudo may break things and it is not sure that the version of npm of the current user is used. Please do not use sudo for npm install. And never install with npm -g global option.

@karsten13
Hi,
and done: Issue

Found an article that there is a developer who is providing a replacement api for darksky which is called Pirate Weather.
If i read correctly it should be a plugin-in replacement for Darksky and only the URLs in the modules need to be changed as the same data structures are used.
As i do not use any Darksky modules i did not test it but i found it interesting and it might be worth looking at it.

@nkc Hi,

i think you can use my MMM-CommandToNotification module to call the script periodically and send it’s output as a notification.
You then can use my MMM-ValuesByNotification module to display the value of the notification.

@Nathaniel Hi,

the module ia available on Github MMM-MplayerRadio.

@TK421_VT
Hi and sorry,

i did not see that it is working now. Yes you can adjust the size (as suggested in the documentation) by adding a few lines to your custom.css file:

.MMM-EmbedURL .embed .embeded {
    width: 800px;
    height: 400px;
}

@digied
I tried to reproduce the error you are get with your config but it does not appear in all these cases:

• forgot to install npm install
• user does not exist
• user does exist but does not have the permissions
• host is wrong and does not exist
• host is a different host which does exist

What version of the module are you using? You can find the version in the package.json file.
What version of MagicMirror are you using?
How did you install the module?
What version of Synology DSM are you using?
What version of Synology Surveillance are you using?
Are there any errors in the Logs before this errors which may are related?

@TK421_VT
I took your whole config, copied to my mirror and only changed the ip address to my needs. Everything is working fine here. It takes a second to fetch the information of the weather but it is displayed as it should.

The only thing i think is left that can cause the problems is that not electron is used to display the mirror.

Edit:
Did not see that it is working now. Please read my other post about sizing instead

@Peter
@karsten13

Just released version 0.0.7 of my MMM-Screen-Powersave-Notification module which supports either vcgencmd, tvservice and now also xrandr.

@Peter
No stupid question more a lack of information/documentation of me ;-)

You can call the script with the GPIO number as first argument. In your case it should be:

./testGPIO.py 17

After some research i am pretty sure the problem is the graphics stack in your case. I am working on a solution for the problem

@sdetweil
I think it is more a problem of the graphical stack. Just checked my new installation of today.
With “vc4-kms-v3d” my test commands from above result in the screen being unchanged after i changed back to the “vc4-fkms-v3d” driver in the “/boot/config.txt” and a reboot everything is working as before.
I run the kernel 5.15.84-v7l+ at the moment.

@sdetweil I saw your post about firmware level in one of the other posts. Additionally i think it is depending of the graphical driver used (vc4-kms-v3d vs vc4-fkms-v3d).
But if it works with the posted command most of the modules should be fine.

@Peter
There can be a lot of reasons why the PIR modules are not working anymore.
What module did you use in the previous setup?
Did you run “npm install” in the module again? Or did you only copy the directory to the new setup?
Are there any errors during the installation of the module?

You can use my test script to check if the sensor it self triggers an event.

Next step would be to test if the command which controls the screen. Most modules use vcgencmd

If you run the following command to display should be shut off and 20 seconds later it should be shut on again.
Best way is to run the command via ssh shell.

/usr/bin/vcgencmd display_power 0; echo "Display should now be off"; sleep 20; /usr/bin/vcgencmd display_power 1; echo "And now it should be on again"

@karsten13

You are right. I think optionalDependencies would be a great solution. Module developers could then add a hint to run npm ci in the MagicMirror directory to their installations instructions.

As the container it self is untouched it should be no problem. It only causes @electron/rebuild to be installed the next time the script is called.

@karsten13
They are stored in the node_modules folder of the module which should be persistent

Edit: Do not misunderstand me. In my opinion the best way to solve the electron-rebuild problems of a lot of modules would be to put “@electron/rebuild” as a dependency to “package.json” of MagicMirror.