Domoticz Z-Wave issues

[Plantje]

I am getting more and more frustrated with some of the Z-Wave stuff.

For example...This was on the 8th of April

1.png (23.72 KiB) Viewed 1018 times

The temperature indicates that it was last seen on 24-03-2020 at 16:17:38

2.png (13.47 KiB) Viewed 1018 times

However, the controller has last seen the node on 08-04-2020 at 08:32:10 with a battery percentage of 55

3.png (40.04 KiB) Viewed 1018 times

Most frustrating is that all devices beneath it have been seen last in March or even in 2019!

This is how I configure all my smoke detectors:
• “Temperature report interval” set to 720 to get a report every hour
• “Low battery alarm” set to 120 to get a notification every 10 minutes if the battery runs low. Otherwise I cannot distinguish between low battery alarm and loss of Z-Wave range.
• “12. Temperature report hysteresis” set to 0 to make sure the temperature is always reported even though the difference is less than 1 degree Celcius.
The wake up interval is set to an hour.

That's why I think it is this strange that these devices get lost.

Configuring the devices is very frustrating as well. Time and again I have to configure the device and apply the configuration. I have to do that up to 10 times before I can retrieve the configuration and it is set to my preferences. Sometimes parts do get applied and other parts do not get applied.

Another frustration here is that I have to figure this out myself time and again. This home AUTOMATION. Shouldn't this be arranged for me?

Final remark and reason for raising this: Is this issue caused by Domoticz, Z-Wave, Fibaro/smoke detector, Aeonlabs Z-Wave stick, fact that I run Domoticz on Windows, fact that the hardware of my Domoticz server is rather old and not really fast or a combination of this all?

[Plantje]

And one more example:

4.png (13.23 KiB) Viewed 1016 times

5.png (34.14 KiB) Viewed 1016 times

6.png (314.47 KiB) Viewed 1016 times

This way I am spending way more time maintaining my home automation than I should be.

In all fairness: the controller has also seen this device two days ago for the last time, so I am charging the battery for it.

[EddyG]

You should state your configuration. Domoticz version etc.
Look around in this forum and you will find that several people (including me) have Zwave problems with stables 2020.1 and 2020.2
Solution is not yet found, but will hopefully soon be found.

[Plantje]

Windows 10 running 2020.2
But this has been going on for the past years and versions.

[EddyG]

A hardware device can have several 'software' devices.
Not all of them get updated every time. Some of them only once when they are created.
Then next update when there is an alarm or so.
My Watersensor has 5 devices of which 1 is only updated when there is a water flood.
The same applies for my Smoke detector etc....
Did you look at the settings of your Koolmonoxide Temperature.
Mostly there are some settings controlling the behaviour of the device.
Including when a temperature should be updated.
In my Fibaro PIR there is a hysteresis setting for the Lux and temperature.
This is to avoid battery drain.

[Plantje]

Ok, fair enough, not every device checks in regularly.

In case of the Fibaro smoke detectors some of them (hard to pinpoint which one) beep every now and then. None of them indicate to be low on battery and the Z-Wave hardware screen indicates that they have all been seen recently. It is just pretty cumbersome

I am going to keep a little more a keen eye on these devices.

[EddyG]

You could check by replacing the battery by a new one and see if the beep stops.

[Plantje]

The beeping is very intermittent. An low battery beep is either every hour or every 10 minutes (if the device picked up the settings)
It seems to be a Z-Wave range loss

[FearNaBoinne]

You should state your configuration. Domoticz version etc.
Look around in this forum and you will find that several people (including me) have Zwave problems with stables 2020.1 and 2020.2
Solution is not yet found, but will hopefully soon be found.

Yeah, I am having issues with Z-wave too... I'm getting pretty frustrated, and the WAF has gone through the floor!

Neo Coolcam PIR sensor just showed up with ID/Type 0x0000/0x0000 after replacing an almost empty battery, and nothing I tried will get it to go back to the correct type NOR will it receive the PIR movement messages...
The ZWave Dashboard sees it just fine tho!
(The 2nd one, same model, works just fine BTW?!)

[EddyG]

May be this got solve your error too: https://www.domoticz.com/forum/viewtopi ... 24&t=32568

[Plantje]

Thanks! Will look into this!

[FearNaBoinne]

May be this got solve your error too: https://www.domoticz.com/forum/viewtopi ... 24&t=32568

Don't know whether it fixes it permanently, but for now the PIR is working again... Interesting fact: The problematic devices after reboot are the securely added devices... So there definitely seems to *something* there!

[EddyG]

For me it does. After ALL new devices are created and every device is 'included' again.
When the ozwcache*xml file is completely filled every reboot or restart of Domotics went smoothly, no problems anymore.
Wait 24 hours to get every devices created.
So I hope it works for you too.