@ELMAGO Hi,

i just released a new version of the module which has a new option delayNext that can be added to each command.
The module then starts the command and waits this amount of milliseconds before the next one is processed.
So in your case you can add a delayNext: 1000 to each of the commands to give your server some time between the calls.

@ELMAGO Hi,

thats right. The module does not support multi instance configurations.
You will need to copy the complete module folder and change some things to get it work.
But to me it looks like your server is stressed with the 16 calls straight after each other. So you do not need more parallelism but less.
So i will check if i can at a configurable delay after each command to stretch the time the calls get made to your server a little bit.

@digied Great to hear that. You are welcome.

@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