Domoticz delay to send command - Unstability

[Ronald42]

Dear All,

I'm new to this forum and using Domoticz for 9 months now.

Configuration:
- Domoticz installed on NAS Synology
- AEON LABS Zstick Gen 5
- 9 Fibaro Roller Shutter FGRM222

I have lot of issues to have all my roller shutter working properly although my initial config worked quite well. All my devices has been detected and incorporated in the ZWave NW, I created LUA scripts and scnerios which worked well as well however, the way the NW operates seems to be completely erratic, sometimes when I trigger command it's almost instantaneous, sometime it can take up to 40 min !!! It could work for weeks in a row, then start not to be reliable, then back OK without me touching anything.

What I've done to try to improve:
1 - Upgrade to latest version of DSM 6.0
2 - Upgrade to latest Domoticz version (V3.5877)
3 - Restart the SAN everynight
4 - Restart the Domoticz everynight
5 - I found always the same node often in Sleeping state without any way to have him back to normal state - I removed the node from the NW suspecting and HW issue on the device and the NW doesn't really operate better.

I was planning to extend with new sensor but I can't really trust the installation, I need to stabilize before introducing more sensible devices (motion sensor, alarm, lights, doorway open). If the doorway open 40min after I press the button, this is not very ... modern.

What I noticed is that my Network is very randomly meshed (see the two attachments). The devices are 3 to 4 meters each with simple 5cm brick walls in between.

Please help as I'm about to give up.

Thx for your help,

[Egregius]

NW2.png is not good. How long was the system running then?
Reboot every night is also not good. I find the Zwave network become more reliable after 24 hours of uptime.
What's in the logfile?

[Domosapiens]

If I look at config/fibaro/fgrm222.xml
each fgrm222 should have only 3 Groups.
And Group 3 is the lifeline, so a 1 must be there for the connection with the Z-Wave controller.

My suggestion:
Stop Open Zwave (disable the Z-Wave controller)
Remove from your config/zwcfg_0blabla.xml the nodes with more then 3 Groups. (the whole section from "<Node>" up-to "</Node>"
Start Open Zwave.
Let Open Zwave/Domotics re-discover your faulty nodes.
Add, if needed, a 1 to Group 3 of each node

[Ronald42]

It's been now two weeks the system is running on this state (like on NW2.png) without any improvement. No errors in the log, although quite often I have this message.

"OpenZWave: Received timeout notification from HomeID: 4135369048, NodeID: 10 (0x0a)"

I'll stop the restart every night I let you know should it improve.

Then I'll update the config as suggested in your post Domosapiens.

Thx for your help