Z-wave unstable

[ZatarraNL]

Hello everybody,

For over a few years I use domoticz with Z-wave. And I must say that Z-wave has proofed to be very unreliable.

The problem:
Randomly all devices disappear in the setup-page of my AeonZWaveUSB hardware. Result: no device can be directed through domoticz.

I didn't have much problem with it, because the (only one) lamp can be switched locally. It's a qubino flush dimmer. But last week I installed zigbee2MQTT with a few ikea bulbs. The Z-wave lamp has been set in a group to switch together on and off with the zigbee bulbs, controlled by the z-wave qubino switch. This works until the qubino devices disappear in domoticz. So now the problem has become urgent...

Situation:
Domoticz version 4.10717 on a debian 9 virtual machine (Windows 10 host).
OpenZwave: Version: 1.4-3335-g74e05982-dirty
Interface: Aeotec Gen 5 Z-Wave Plus USB Interface
Switch: Qubino ZMNHDD1 Flush Dimmer+
Sensors: 2x Neo CoolCam Battery Powered PIR Sensor+

What I currently do:
The virtual machine is set to restart every night. This way everything normally works in the morning.

What doesn't work:
A restart of domoticz doesn't work. Only a reboot of the compleet virtual machine works.

If anyone can help my figure out what the problem is, or where to find it (which logs etc.), that would be very appreciated.

Edit: I just enabled logging the Aeotec Gen 5 stick. I hope the OZW_Log.txt will give some insight. To be continued.

[Egregius]

I think you just need more main powered nodes. Z-wave is very reliable here.

[ZatarraNL]

What do you mean exactly with 'main powered nodes'? You mean nodes without batteries? I have one interface and one switch non stop powered. That should work, shouldn't it?

[ben53252642]

Majority of my home is still powered by Z-Wave but I've been actively replacing every bit I can with Zigbee devices.

[Egregius]

I've read multiple times that you need more mains powered nodes. I thinks starting from 4 to 5 things will get stable. Anyway, the more mains powered nodes you'll add the more stabler it'll become. At my home 45 nodes of 77 total are mains powered. Never miss a switch command, everything rock solid.
But, it's a radio signal. A lot depends on interference, materials of the walls/floors etc. RFXcom was a nightmare here.
I also have small amount of Zigbee devices and they work well also.

[jake]

Disappearing from the zwave hardware page is a strange thing. A device can end up on the dead node list when there is radio interference, but should always be there. It must be a software issue or a faulty stick.

For myself, I frequently had some devices on the dead node list. Turned out that moving the zwave stick out of the way of my hot water heating pipes for more than 20 cm, completely solved the problem.

[candrea77]

I've got a similiar setup.

Domoticz running Virtual by QNAP virtualization Station , on Linux Debian.

By let me spent two words on my previous setup.

My first home automation was Fibaro.
An endless bug every update.
An the main problem : if your controller get broken you need to send it to home (maybe polland )
Appened 1 times after that I've searh for other solution

Then I switched to domoticz using raspberry :
Main advantage : I get 2 AEOTEC ZWAVE USB : I can backup all the zwave controller stuff from the 1st and restore to the 2nd
More and More problem wth device that don' respond to command and freeze

Hardware Upgrade : I switched to a barebone from gigabyte with more cpu power.
System was stable (only few freeze)
Lessons learned : less cpu power ... less usb power .... more freeze.

After that I've tried the virtual way (my current setup) : same consideration.
Actually I'm fine wih linux (becouse i require less cpu power and my virtual system based on corei3 is sufficient)
WIndows was no good for me.

So , if you are running in some freeze, take a look to the system and maybe try it physically and then switch to virtual only if all the setup is ok.

I'm wayting for the first zwave controller based on 700 chipset and Z/IP protocol.
Maybe it can solve more other problem.

[ZatarraNL]

[/quote]

Disappearing from the zwave hardware page is a strange thing. A device can end up on the dead node list when there is radio interference, but should always be there. It must be a software issue or a faulty stick.

I can imagine you are right here. I've had dead nodes earlier, but that's not it. Maybe there's something in de software going wrong. That's why I decided to activate the logs. Strange enough, everything works since then. I haven't had a problem with the list going blank.

What I could try: I have another domoticz-server on a Rpi to measure my energy usage (as a slave-domoticz). I prefer that one to be left alone so it doesn't crash in any way, but I could try to put the zwave stick in the Rpi. I don't have to reconnect all the nodes, right? The devices would appear on the Rpi-domoticz out of the box with all devices functional? But actually this test is not really functional, because I don't want it to stay in the Rpi, and any results wouldn't help me finding any software issues on the virtual machine. I actually don't expect the devices to disappear as they currently do on the virtual machine.

For myself, I frequently had some devices on the dead node list. Turned out that moving the zwave stick out of the way of my hot water heating pipes for more than 20 cm, completely solved the problem.

I dont expect any jammers around the zwave stick. Although the distance between the devices is quite long. 3 stories. The devices are on the ground floor while the stick is on the second floor (or third floor, depending on the way you count... ).
What did the lack of signal result in? What did you notice happened? Devices missing? Or dead nodes?

Actually I'm fine wih linux (becouse i require less cpu power and my virtual system based on corei3 is sufficient)
WIndows was no good for me.

So , if you are running in some freeze, take a look to the system and maybe try it physically and then switch to virtual only if all the setup is ok.

It's not actually a freeze. I expect it's more like a driver thing or something. So it doesn't have anything to do with de domoticz setup. And running it in a Virtual machine has saved me some hours work, because making a backup is very easy. Would't want it any other way. And the machine has other functions as well.

[jaha]

I've read multiple times that you need more mains powered nodes. I thinks starting from 4 to 5 things will get stable. Anyway, the more mains powered nodes you'll add the more stabler it'll become. At my home 45 nodes of 77 total are mains powered. Never miss a switch command, everything rock solid.
But, it's a radio signal. A lot depends on interference, materials of the walls/floors etc. RFXcom was a nightmare here.
I also have small amount of Zigbee devices and they work well also.

How long does it take for you ta run like a scene "goodnight" where it switches off everything? I se many timeouts when i do so and the scene takes around 60 seconds and sometimes misses devices. But if i send a command to one device its instant.

[Egregius]

I would say instant:

Some logging of my pass2php script:

Code: Select all

2019-09-24 22:19:36.080  (STORE)		=> 8Hall-1	=> On	(pass2php.php:40)
2019-09-24 22:19:36.081  (STORE)		=> Weg	=> 1	(8Hall-1.php:29)
2019-09-24 22:19:36.081  (SWITCH)		 => hall => Off ()
2019-09-24 22:19:36.083  (SWITCH)		 => garageled => Off ()
2019-09-24 22:19:36.086  (SWITCH)		 => pirliving => Off ()
2019-09-24 22:19:36.087  (SWITCH)		 => pirinkom => Off ()
2019-09-24 22:19:36.090  (SWITCH)		 => eettafel => Off ()
2019-09-24 22:19:36.092  (SWITCH)		 => zithoek => Off ()
2019-09-24 22:19:36.101  (STORE)		=> hall	=> 0	(pass2php.php:40)
2019-09-24 22:19:36.110  (STORE)		=> garageled	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.114  (STORE)		=> pirliving	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.120  (STORE)		=> pirinkom	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.121  (STORE)		=> eettafel	=> 0	(pass2php.php:40)
2019-09-24 22:19:36.125  (STORE)		=> zithoek	=> 0	(pass2php.php:40)
2019-09-24 22:19:36.294  (SWITCH)		 => bureel => Off ()
2019-09-24 22:19:36.296  (SWITCH)		 => jbl => Off ()
2019-09-24 22:19:36.299  (SWITCH)		 => terras => Off ()
2019-09-24 22:19:36.302  (SWITCH)		 => keuken => Off ()
2019-09-24 22:19:36.304  (SWITCH)		 => inkom => Off ()
2019-09-24 22:19:36.313  (STORE)		=> bureel	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.318  (STORE)		=> jbl	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.329  (STORE)		=> terras	=> 0	(pass2php.php:40)
2019-09-24 22:19:36.332  (STORE)		=> keuken	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.336  (STORE)		=> inkom	=> 0	(pass2php.php:40)

The SWITCH lines are commands sent to domoticz to switch off.
The STORE lines are the returns of domoticz that it's done.
So in yesterday the system had to switch off 11 devices after I pushed the button 8Hall-1. That took 0,255 seconds to complete.
And yes, they're actually of then.
Sometimes, but rather rarely, it takes like a second or 2-3 to complete. Missed commands are so rarely I would call it once a year or something.

[jaha]

I would say instant:

Some logging of my pass2php script:

Code: Select all

2019-09-24 22:19:36.080  (STORE)		=> 8Hall-1	=> On	(pass2php.php:40)
2019-09-24 22:19:36.081  (STORE)		=> Weg	=> 1	(8Hall-1.php:29)
2019-09-24 22:19:36.081  (SWITCH)		 => hall => Off ()
2019-09-24 22:19:36.083  (SWITCH)		 => garageled => Off ()
2019-09-24 22:19:36.086  (SWITCH)		 => pirliving => Off ()
2019-09-24 22:19:36.087  (SWITCH)		 => pirinkom => Off ()
2019-09-24 22:19:36.090  (SWITCH)		 => eettafel => Off ()
2019-09-24 22:19:36.092  (SWITCH)		 => zithoek => Off ()
2019-09-24 22:19:36.101  (STORE)		=> hall	=> 0	(pass2php.php:40)
2019-09-24 22:19:36.110  (STORE)		=> garageled	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.114  (STORE)		=> pirliving	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.120  (STORE)		=> pirinkom	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.121  (STORE)		=> eettafel	=> 0	(pass2php.php:40)
2019-09-24 22:19:36.125  (STORE)		=> zithoek	=> 0	(pass2php.php:40)
2019-09-24 22:19:36.294  (SWITCH)		 => bureel => Off ()
2019-09-24 22:19:36.296  (SWITCH)		 => jbl => Off ()
2019-09-24 22:19:36.299  (SWITCH)		 => terras => Off ()
2019-09-24 22:19:36.302  (SWITCH)		 => keuken => Off ()
2019-09-24 22:19:36.304  (SWITCH)		 => inkom => Off ()
2019-09-24 22:19:36.313  (STORE)		=> bureel	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.318  (STORE)		=> jbl	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.329  (STORE)		=> terras	=> 0	(pass2php.php:40)
2019-09-24 22:19:36.332  (STORE)		=> keuken	=> Off	(pass2php.php:40)
2019-09-24 22:19:36.336  (STORE)		=> inkom	=> 0	(pass2php.php:40)

The SWITCH lines are commands sent to domoticz to switch off.
The STORE lines are the returns of domoticz that it's done.
So in yesterday the system had to switch off 11 devices after I pushed the button 8Hall-1. That took 0,255 seconds to complete.
And yes, they're actually of then.
Sometimes, but rather rarely, it takes like a second or 2-3 to complete. Missed commands are so rarely I would call it once a year or something.

Okey here is my log.

2019-09-25 17:28:54.645 Status: User: admin initiated a scene/group command
2019-09-25 17:28:54.760 Error: OpenZWave: Node has failed (or is not alive), Switch command not sent! (NodeID: 16, 0x10)
2019-09-25 17:28:54.864 Error: OpenZWave: Node has failed (or is not alive), Switch command not sent! (NodeID: 7, 0x07)
2019-09-25 17:28:55.019 Activating Scene/Group Device: Led diskbänk (Off)
2019-09-25 17:28:55.070 Activating Scene/Group Device: Sovrum taklampa (Off)
2019-09-25 17:28:55.121 Activating Scene/Group Device: Fönster V-rum (Off)
2019-09-25 17:28:55.121 OpenZWave: Domoticz has send a Switch command!, Level: 0, NodeID: 29 (0x1d)
2019-09-25 17:28:55.121 (Z-WAVE) Usage (Unknown)
2019-09-25 17:28:55.122 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:28:55.125 (Z-WAVE) Light/Switch (Fönster V-rum)
2019-09-25 17:28:55.176 Activating Scene/Group Device: Matsal fönster (Off)
2019-09-25 17:28:55.176 OpenZWave: Domoticz has send a Switch command!, Level: 0, NodeID: 30 (0x1e)
2019-09-25 17:28:55.176 (Z-WAVE) Usage (Unknown)
2019-09-25 17:28:55.177 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:28:55.179 (Z-WAVE) Light/Switch (Matsal fönster)
2019-09-25 17:28:55.230 Activating Scene/Group Device: Tv bänk (Off)
2019-09-25 17:28:55.230 OpenZWave: Domoticz has send a Switch command!, Level: 0, NodeID: 34 (0x22)
2019-09-25 17:28:55.231 (Z-WAVE) Color Switch (Tv bänk)
2019-09-25 17:28:55.282 Activating Scene/Group Device: V-rum golvlampa Höger (Off)
2019-09-25 17:28:55.282 OpenZWave: Domoticz has send a Switch command! NodeID: 28 (0x1c)
2019-09-25 17:28:55.285 (Z-WAVE) Light/Switch (V-rum golvlampa Höger)
2019-09-25 17:28:55.336 Activating Scene/Group Device: V-rum golvlampa Vänster (Off)
2019-09-25 17:28:55.336 OpenZWave: Domoticz has send a Switch command! NodeID: 72 (0x48)
2019-09-25 17:28:55.336 (Z-WAVE) Usage (Unknown)
2019-09-25 17:28:55.337 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:28:55.344 (Z-WAVE) Light/Switch (V-rum golvlampa Vänster)
2019-09-25 17:28:55.395 Activating Scene/Group Device: Taklampa tv-rum (Off)
2019-09-25 17:28:55.395 OpenZWave: Domoticz has send a Switch command! NodeID: 73 (0x49)
2019-09-25 17:28:55.396 (Z-WAVE) Usage (Unknown)
2019-09-25 17:28:55.396 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:28:55.400 (Z-WAVE) Light/Switch (Taklampa tv-rum)
2019-09-25 17:28:55.451 Activating Scene/Group Device: Fönsterlampa tv-rum (Off)
2019-09-25 17:28:55.451 OpenZWave: Domoticz has send a Switch command! NodeID: 73 (0x49)
2019-09-25 17:28:55.452 (Z-WAVE) Usage (Unknown)
2019-09-25 17:28:55.452 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:28:55.458 (Z-WAVE) Light/Switch (Fönsterlampa tv-rum)
2019-09-25 17:28:55.509 Activating Scene/Group Device: Utelampa dörr (Off)
2019-09-25 17:28:55.509 OpenZWave: Domoticz has send a Switch command! NodeID: 12 (0x0c)
2019-09-25 17:28:55.509 (Z-WAVE) Usage (Unknown)
2019-09-25 17:28:55.510 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:28:55.515 (Z-WAVE) Light/Switch (Utelampa dörr)
2019-09-25 17:28:55.626 (Z-WAVE) Usage (Unknown)
2019-09-25 17:28:55.627 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:28:55.070 Error: OpenZWave: Node has failed (or is not alive), Switch command not sent! (NodeID: 24, 0x18)
2019-09-25 17:28:58.329 (Z-WAVE) Usage (Unknown)
2019-09-25 17:28:58.330 (Z-WAVE) General/kWh (Hus förbrukning)
2019-09-25 17:28:58.860 (Z-WAVE) Light/Switch (Spottar S2 1 click)
2019-09-25 17:28:59.103 Activating Scene/Group: [Diskbänk]
2019-09-25 17:28:59.103 Activating Scene/Group Device: Led bänk (On)
2019-09-25 17:28:59.154 Activating Scene/Group Device: Led diskbänk (On)
2019-09-25 17:28:59.103 Status: User: Admin initiated a scene/group command
2019-09-25 17:29:00.766 Status: OpenZWave: Received timeout notification from HomeID: 3369634837, NodeID: 19 (0x13)
2019-09-25 17:29:01.213 (Z-WAVE) Light/Switch (Hallampa vägg)
2019-09-25 17:29:01.903 (Z-WAVE) Usage (Unknown)
2019-09-25 17:29:01.904 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:29:07.493 Status: OpenZWave: Received timeout notification from HomeID: 3369634837, NodeID: 3 (0x03)
2019-09-25 17:29:08.072 (Z-WAVE) Light/Switch (Trapplampa)
2019-09-25 17:29:09.021 (Z-WAVE) Usage (Unknown)
2019-09-25 17:29:09.021 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:29:09.856 (Z-WAVE) Usage (Unknown)
2019-09-25 17:29:09.857 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:29:10.689 (Z-WAVE) Usage (Unknown)
2019-09-25 17:29:10.689 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:29:15.429 Status: OpenZWave: Received timeout notification from HomeID: 3369634837, NodeID: 30 (0x1e)
2019-09-25 17:29:17.098 (Z-WAVE) Usage (Unknown)
2019-09-25 17:29:17.099 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:29:17.405 (Z-WAVE) Usage (Unknown)
2019-09-25 17:29:17.406 (Z-WAVE) General/kWh (kWh Meter)
2019-09-25 17:29:18.330 (Z-WAVE) Usage (Unknown)
2019-09-25 17:29:18.335 (Z-WAVE) General/kWh (Hus förbrukning)
2019-09-25 17:29:19.452 (Z-WAVE) Usage (Unknown)

[Egregius]

You have a dead node.
Do you need al those kWh and usage? Disable those or limit the reports of them.