Z-Wave reliability (Fibaro smoke detectors configuration reset)
Moderator: leecollings
-
- Posts: 451
- Joined: Friday 16 October 2015 7:58
- Target OS: Windows
- Domoticz version:
- Contact:
Z-Wave reliability (Fibaro smoke detectors configuration reset)
In my setup I have 11 smoke sensors and 1 CO sensor. All Fibaro devices.
Now this morning I wanted to check on the reported temp in the living room and I noticed it had not reported back for a while: Checked the Z-Wave settings and it did show as recently "seen" Checked the settings and they had been reset. Normally I set the following settings:
• “Temperature report interval” to 720
• “Low battery alarm” to 120 (that way I can distinguish a low battery report from a signal lost report)
• “12. Temperature report hysteresis” to 0 (so I am sure the temperature is being reported)
For that one smoke sensor I noticed it was reset to the default vaules. How is this possible?
Then I checked other smoke sensors and they too had all their configuration (re)set to default values. However, they all do seem to report the temperature every 5 minutes. What is going on here?
Then there's two other weird things:
* Every now and then I see an unknown device in the Z-Wave list
* The garage smoke detector turns up like this: In the past years I have posted several questions on reliability of Z-Wave devices.
I guess the general question is: Ho can I gain more control over my Z-Wave devices and network?
In most cases everything seems to work, but every now and then a device doesn't respond (for a while), needs to be added again, configuration is gone etc etc.
Currently I have a network heal planned for 4 AM in the night. And every night my Windows Domoticz server gets a reboot.
There don't seem to be any errors in the logging. Clicking the plus sign next to a device has never seemed to have any effect.
Edit: If a smoke detector turns up as not seen for a while in the devices and I run a self test by pushing the button, it is ok. If I check the connection by pushing the button, it shows it is (in)directly connected to the controller. So, from that side everything seems ok.
Now this morning I wanted to check on the reported temp in the living room and I noticed it had not reported back for a while: Checked the Z-Wave settings and it did show as recently "seen" Checked the settings and they had been reset. Normally I set the following settings:
• “Temperature report interval” to 720
• “Low battery alarm” to 120 (that way I can distinguish a low battery report from a signal lost report)
• “12. Temperature report hysteresis” to 0 (so I am sure the temperature is being reported)
For that one smoke sensor I noticed it was reset to the default vaules. How is this possible?
Then I checked other smoke sensors and they too had all their configuration (re)set to default values. However, they all do seem to report the temperature every 5 minutes. What is going on here?
Then there's two other weird things:
* Every now and then I see an unknown device in the Z-Wave list
* The garage smoke detector turns up like this: In the past years I have posted several questions on reliability of Z-Wave devices.
I guess the general question is: Ho can I gain more control over my Z-Wave devices and network?
In most cases everything seems to work, but every now and then a device doesn't respond (for a while), needs to be added again, configuration is gone etc etc.
Currently I have a network heal planned for 4 AM in the night. And every night my Windows Domoticz server gets a reboot.
There don't seem to be any errors in the logging. Clicking the plus sign next to a device has never seemed to have any effect.
Edit: If a smoke detector turns up as not seen for a while in the devices and I run a self test by pushing the button, it is ok. If I check the connection by pushing the button, it shows it is (in)directly connected to the controller. So, from that side everything seems ok.
-
- Posts: 230
- Joined: Friday 03 April 2015 20:44
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Germany (near dutch border)
- Contact:
Re: Z-Wave reliability (Fibaro smoke detectors configuration reset)
Hi,
I am having troubles with z-wave as well.. nodes disappear; deleted nodes (deleted with zen tools, because the "delete button" doesn't work in Domoticz) reappear spontaneously; latency problems (up to 30 seconds sometimes!) ; nodes just don't respond sometimes.
It is extremely unstable...
Is there an expert on this forum who can help me/us?
Hans
I am having troubles with z-wave as well.. nodes disappear; deleted nodes (deleted with zen tools, because the "delete button" doesn't work in Domoticz) reappear spontaneously; latency problems (up to 30 seconds sometimes!) ; nodes just don't respond sometimes.
It is extremely unstable...
Is there an expert on this forum who can help me/us?
Hans
-
- Posts: 451
- Joined: Friday 16 October 2015 7:58
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Z-Wave reliability (Fibaro smoke detectors configuration reset)
What I also stated in a different topic:
If I can trust something will be done with the findings I am willing to create some documentation on Z-Wave when it comes to:
A lot of new betas are being delivered I think; no actual releases.Plantje wrote: ↑Thursday 11 April 2019 7:57 Perhaps it is possible to bundle more Z-Wave issues into one feature request/bug fix request.
What would you think how this can be improved? I would think something like the following:
- Better Z-Wave communication between controller and devices
- Better handling of the Z-Wave data (if you change the configuration or if you get the configuration from a node, just wake up the node and get the freaking data
)
- This would improve a lot, I think: If you click the plus sign next to a node that equals the following. Retrieve current configuration, remove node, add node, apply configuration, update previously configured devices to now be attached to the node.
If I can trust something will be done with the findings I am willing to create some documentation on Z-Wave when it comes to:
- Bugs
- Issues
- Feature requests
- Requirements
- ...anything else?
-
- Posts: 451
- Joined: Friday 16 October 2015 7:58
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Z-Wave reliability (Fibaro smoke detectors configuration reset)
So, I have been playing around a little bit. This way the smoke detector in the living room reports temperature again and the smoke detector in the garage has a normal indication.
Furthermore, my CO detector has been removed and added again. This because, although it was sending feedback, I couldn't change the configuration.
So that now all seems to be up and running....
And...when going into the bathroom I noticed the multisensory did sense me coming in... but the lights were not switched on. Upon switching the lights on manually using the KaKu switch, they immediately went off. So, the script is running. And while looking at the humidity, temperature and lux: they are all reported every 5 minutes the past period. So, connection with Z-Wave is good as well.
Where does this go wrong then?!
This is getting frustrating!
Furthermore, my CO detector has been removed and added again. This because, although it was sending feedback, I couldn't change the configuration.
So that now all seems to be up and running....
And...when going into the bathroom I noticed the multisensory did sense me coming in... but the lights were not switched on. Upon switching the lights on manually using the KaKu switch, they immediately went off. So, the script is running. And while looking at the humidity, temperature and lux: they are all reported every 5 minutes the past period. So, connection with Z-Wave is good as well.
Where does this go wrong then?!
This is getting frustrating!
-
- Posts: 230
- Joined: Friday 03 April 2015 20:44
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Germany (near dutch border)
- Contact:
Re: Z-Wave reliability (Fibaro smoke detectors configuration reset)
Like I mentioned before... Its very, very unstable... I was trying to solve the z-wave issues for more than 4 whole days and it it is still not optimal... Deleted nodes just show up again... God knows from where they come.. latency is extrem sometimes ...I hope there's an expert here...
Regards, Hans
Regards, Hans
-
- Posts: 550
- Joined: Tuesday 17 June 2014 22:14
- Target OS: NAS (Synology & others)
- Domoticz version: 4.10538
- Location: NL
- Contact:
Re: Z-Wave reliability (Fibaro smoke detectors configuration reset)
My 18 nodes network is pretty stable, but not as good as I experienced it 2 stable releases ago. It would be really nice to see improvements
Synology NAS, slave PI3, ZWave (Fibaro), Xiaomi zigbee devices, BTLE plant sensor, DzVents, Dashticz on tablet, Logitech Media Server
-
- Posts: 451
- Joined: Friday 16 October 2015 7:58
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Z-Wave reliability (Fibaro smoke detectors configuration reset)
I currently have 28 nodes. That is manageable, but the most frustrating thing is the lack of control.
Like mentioned above: the lack of control is frustrating! You fix own end and another end starts to fail.DutchHans wrote: ↑Thursday 11 April 2019 14:34 Like I mentioned before... Its very, very unstable... I was trying to solve the z-wave issues for more than 4 whole days and it it is still not optimal... Deleted nodes just show up again... God knows from where they come.. latency is extrem sometimes ...I hope there's an expert here...
Regards, Hans
And as mentioned before: I am really willing to look into the first steps and getting some functional requirements and create technical requirements from there. But someone has to be willing to do something with them.
I will also look into helping out with the actual coding, since it is open source. But there is so much that I need to and want to do, that I don't think I will have time for that in the coming years!
-
- Posts: 54
- Joined: Thursday 23 June 2016 14:41
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: NL
- Contact:
Re: Z-Wave reliability (Fibaro smoke detectors configuration reset)
since december the zwave is unstable. As you can see here: https://www.domoticz.com/forum/viewtopi ... =6&t=25950
it is the state in Domoticz that is incorrect an not getting the right state. Even the trick to correct is is not working since then.
it is the state in Domoticz that is incorrect an not getting the right state. Even the trick to correct is is not working since then.
-
- Posts: 451
- Joined: Friday 16 October 2015 7:58
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Z-Wave reliability (Fibaro smoke detectors configuration reset)
Thanks for replying here. I will check your other topic as well
-
- Posts: 451
- Joined: Friday 16 October 2015 7:58
- Target OS: Windows
- Domoticz version:
- Contact:
Re: Z-Wave reliability (Fibaro smoke detectors configuration reset)
Went through the other topics, but it seems to be quite different from what I am experiencingcommentator wrote: ↑Wednesday 24 April 2019 21:16 since december the zwave is unstable. As you can see here: viewtopic.php?f=6&t=25950
it is the state in Domoticz that is incorrect an not getting the right state. Even the trick to correct is is not working since then.
Who is online
Users browsing this forum: No registered users and 1 guest