Zwave network problems

[roblom]

Ok for about 4 months I'm trying to get my zwave network working but without success. And today my patience is over.
I have a Aeon S2 stick on a Raspberry Pi with the latest Domoticz updated 5 minuets ago. I have several zwave devices like some Wall plugs from Neo, from Fibaro, some door sensors from Aeotec and Fibaro.
The Aeotec recessed door sensors I can't get to work. They can be added and the value in the OpenZWave Control Panel does change (from 0 to 255) when I get a magnet near it but the value in Domoticz does not change.
The Neo plugs can be added and do work sometimes but 2 of the 3 get strange values for the usage (like a daily usage of 21.474.838.908kWh). Also they are unstable and mostly after a reboot of Domoticz they get the unknown value or gives time-outs in Domoticz again.
The Fibaro door sensor was unable to remove and after a hard reset of the stick it can't be added again.

I've tried the following things
- Updated the stick
- did a hard reset of the stick
- Placed new batteries in the battery powered devices
- Removed all the nodes and re-added them again
Then it works again for some time. Mostly until a reboot.

After updating to Buster which was needed for Domoticz 2020.0 it all started, then adding or removing zwave devices or restarting the zwave stick causes a crash of Domoticz. Theze crashes where almost gone after the update to 2020.1. But still the zwave network was very unstable. Devices become dead or give timeouts and type and id gets 0x0000. After removing the dead node and trying to add it again is hard and doesn't work like it should work.
I've searched a lot trying to find a solution but all I read is other people with the same problem and people who never had the problem but no solutions.
I hope somebody can help or can give a solution that really help.

[efarmer1]

samo here, no solution yet

domoticz 20.20.2
Yadahl on Synology nas

[TSkar]

Seeing it is a rebranded Aeotek stick, might this be related to viewtopic.php?f=24&t=29013 ?
..if so, connecting it through a USB hub might solve at least some of the issues.

[roblom]

I don't know if it's related but my stick is connected in a powered USB hub.

[rgroothuis]

I've a Raspberry Pi 4 with indeed a powered USB hub in which the Aeon Z-Ware stick is inserted. I've about 24 Fibaro Z-Wave devices connected and 2 Qubino. The Domoticz version is:

Screenshot 2021-01-15 at 14.14.47.png (48.86 KiB) Viewed 2552 times

The OpenZWave USB Version is: 1.6-1033-g3661f170. And I've to say, I do not have any problems, it is a stable working solution for the last 6 month.

[lost]

..if so, connecting it through a USB hub might solve at least some of the issues.

Not sure this USB3 related issue on PI4 (fixed in recent gen5 now on sale) also concerns S2 version (older, zwave not +).
Maybe more related to issues following OZW 1.6 merge in Domoticz?

[jefft]

It might apply to others; certainly, I suspect it applies to the Gen5 and USB3 in systems other than Pi... I have the older Gen5 Aeotec stick and it goes mad sometimes, OpenZWave won't report any devices and thinks the homeID is 0x00000000. A replug and reboot sometimes fixes it; several times I've had to restore a backup of the z-stick's internal EEPROM to fix it. I'm using an Intel PC, but some of the USB ports are USB3.0. I don't think the z-stick is very keen on USB extension cables either, even short ones.

[mgrafr]

Excused my english which is a google translation.
I have been looking for several days now as to why my Zwave is not working properly and I think from reading your answers that I have found the problem.
I had an installation of domoticz, a version of 2019, installed on a Proxmox virtual machine, OpenZwave 1.4, and an Everspring stick… .. everything worked perfectly.
Since the update to Domoticz 2020. 2 and zwave 1.6, my Zwave devices only work for a few hours and then they remain dormant all the time; my popp radiator thermostat didn't want to include.
I started by replacing the Everspring stick with a ZME_UZB1 stick, the result was disappointing as I had a lot of trouble with the latter to include the devices.
So I bought an Aeotec z-stick gen5 stick, it really is the best Zwave stick; the inclusion went quickly but the problem remains, devices do not respond from the same date (within a few minutes).
So I agree with some of you that the problem is with openZwave 1.6; I will therefore reinstall Domoticz with version 1.4 of openZwave, .... I will keep you posted on the outcome.

[JeroenL]

Hi,

What you could try is using the Simplicity software to configure your stick, once all devices are added using this software, move the stick to Domoticz.
using the Simplicity Studio tool on my Windows laptop to fix the issue. I used to set my controller as secondary, which I did not manage through Domoticz.

Download the software, I found it through here:

https://aeotec.freshdesk.com/support/so ... -download-

[roblom]

Almost a year later. Still the same problems, devices stop responding, battery percentages disappear, Fibaro smoke devices with temperature sensors stops reporting, aeotec door sensors stops responding.
Recently I invested in Fibaro wall plugs to replace the neo wall plugs, I hoped this solved the problems but it seems it doesn't make any difference.
I'm frustrated because I spend quite some money on good hardware, and waited patiently until the problems where solved in Domoticz.
Of course I understand Domoticz is free and built by volunteers but can somebody tell me what the problem is and if there is some kind of plan or roadmap because for me it seems the zwave problems in Domoticz are not on the top list. And maybe I need to see if there is some other platform where the zwave does work, which I not really want because all of the other things work fine for me.

[heggink]

Moroen is working on a plugin to integrate zwave node js. So far, it seems to work really well but will take some time to mature.

Sent from my SM-G980F using Tapatalk

[roblom]

Thank you for your response and good to hear it's not a dead end.
But for me; what is the current problem and are three ways to solve it? Because despite the fact that there are a lot of users with the same problem, there are also users that have no problems at all, so what do they have different?

[roblom]

Does anyone know what the problem is? For now I have for example no energy updates from my Fibaro wall plugs any more. While they do switch so there is a connection. Also most battery powered devices (Fibaro and Aeotec) stop responding after a while (also on new batteries).

[GSV3Miac]

No power data from my wallplugs either.. Both fibaro gen 6 uk, and aeotec equivalent. Also no power numbers coming back from aeotec CT clamp power meter zw095.. Seems like all power values have vanished. Ozw control panel shows the devices, they talk, but no data values are shown. Can I / we roll back Ozw somehow?

Several zwave devices show types of 0, and re adding them didn't help.

[GSV3Miac]

My problems seem to be related to corrupted ozwcache_0x....xml file in the /config folder. Deleted it and the networks is slowly rebuilding a working version, although still missing power number for a recent fibaro type G wallplug .. I think there is no .xml for it in the config folder.

[roblom]

My problems seem to be related to corrupted ozwcache_0x....xml file in the /config folder. Deleted it and the networks is slowly rebuilding a working version, although still missing power number for a recent fibaro type G wallplug .. I think there is no .xml for it in the config folder.

That probably work for a few days or weeks but at some point you end up in the same situation as before.
Easiest way to fix it again is to use the update device info. Then most of the times it start updating the usage again, until it stops again...

[lost]

That probably work for a few days or weeks but at some point you end up in the same situation as before.
Easiest way to fix it again is to use the update device info. Then most of the times it start updating the usage again, until it stops again...

Only had issue with one metering device: Qubino Smart-Meter at the head of my home electric circuit. Same node, but associated hardware moved so already used ones have to be replaced then deleted.

Quite strange, but in the process I lost most of old stored data as you can see from graphs (I updated on 13/05):

graphW.jpg (82.71 KiB) Viewed 2078 times

This device also lost it's parameters, including those dealing with power reports that were reset to default 10% change... Saw it indirectly because this (usually) heavy talker on my z-wave network triggered z-stick soft resets at night due to this setup:

controller.jpg (42.51 KiB) Viewed 2078 times

With heavier consumption at night (to benefit from lower electricity price) & more stable, 10% of 6kW that's 600W change needed to get a report. Sometimes this was over 15mn setup... Had to setup 2% again and issue was over.

Take care of this setup, already had big stability issues in the past (when I started, with only scheduled heating control & no devices reporting data frequently) due to incorrect values for the system.

That's only 1.5 week since update, but for now this mostly works as expected. I also appreciate z-wave restarting very quickly in 1.6 compared to my previous 1.4 based open-zwave (was still using old-stable v4.10717 before upgrading to 2021.1).

All battery devices needed a wake-up for immediately stopping showing zeroed IDs, except one: Fibaro keyfob needed re-inclusion.