All devices suddenly report: OpenZWave: Received Node Dead notification from HomeID

[dennis_montanje]

Since tonight all wave devices suddenly report OpenZWave: Received Node Dead notification from HomeID. All seems fine until 2 minutes after reboot when the devices report dead starting from the lowest NodeID.

Nothing was changes to the configuration. I've tried several soft reset, reboots and updated to the latest version (V3.4834).

Does any one has an idea how to troubleshoot?

Thank you in advance!

[dennis_montanje]

The nodes became alive after pressing the tamper button on each of the nodes. very strange behavior.

[hamish]

I get the same error. But it seems to be a 'busy' issue... In that the LAST registered device goes 'dead' seemingly when the controller (RazBerry) is asked to do more work than normal.

e.g. If I enable polling on all devices (Because sometimes the manual switch change is missed) then the last added device will go dead fairly shortly afterwards... Until I restart domoticz. Sometimes I have to reboot as well.

It all seems a bit... disconnected from reality. Devices go dead, but topology swears they are reachable. Usually direct from the controller. You can't get them back, without a restart. domoticz refuses to send commands to them. I have 3x different switch types. It happens to the Aeotec (mini-SS2), and Fibaro (RGBW)/ Not happened to the Qubino so far, but I have nothing connected to that yet apart from power.

Strangely on the Aeotec, SOMETIMES it will come back by manually toggling the state on/off via the switch connected to it. (Std UK pull cord type). But not always.

Wondering if OZW is to blame... (The OZW console isn't much help. It swears 'dead' devices are reachable via the topology diagram. But I can't get the stats working on it...

Running the latest stable version of domoticz, raspberry pi binary image downloaded a couple of says ago...

[DomoSeb]

I think I have the same issue, however no idea how to solve it. Is this comming from my aeon zwave stick or is this domoticz/ozw behavior going faulty... Are your errors the same as mine (stated underneath):

Code: Select all

2016-04-20 07:04:01.892 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 3 (0x03)
2016-04-20 07:04:11.898 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 4 (0x04)
2016-04-20 07:04:21.903 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 5 (0x05)
2016-04-20 07:04:31.909 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 6 (0x06)
2016-04-20 07:04:41.915 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 4 (0x04)
2016-04-20 07:04:51.922 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 4 (0x04)
2016-04-20 07:05:02.040 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 3 (0x03)
2016-04-20 07:05:12.047 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 4 (0x04)
2016-04-20 07:05:22.055 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 5 (0x05)
2016-04-20 07:05:32.063 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 6 (0x06)
2016-04-20 07:05:42.071 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 2 (0x02)
2016-04-20 07:05:52.133 OpenZWave: Received timeout notification from HomeID: 25481108, NodeID: 3 (0x03)

[evansnp]

I'm seeing similar behavior using a RaZberry controller. I'm starting to think that it's an issue with the z-wave driver in Domoticz, as I have run my system for 24 hours, just using the Z-way software, and have seen no timeouts, dead nodes etc. I'm going to leave it for another 24 hours to prove (or disprove) that it's not a controller error, but a device driver issue in Domoticz.

[jjnj]

I have the same issue with the Z-Wave S2 stick. Running on Windows 10

Code: Select all

OpenZWave: Received timeout notification from HomeID: 25486549, NodeID: 32 (0x20)

And after some time the connection appears to be lost in Domoticz and there is no way to switch the device on or off, it only appears to be for powered nodes (without battery)

Log from the stick itself

Code: Select all

Dumping queued log messages

2016-04-21 22:27:26.133 4988 ERROR: Dropping command, expected response not received after 1 attempt(s)

End of queued log message dump

log message dump

It's being a serious issue right now. Hope we can find a fix.

[JuanUil]

I have the same problem

[evansnp]

Update: I've been running with just the z-way software for 48 hours now, and all devices are present, no timeouts, no dead nodes, and the network routing is all green. There is definitly something wrong with the z-wave implementation in Domoticz. Please can we have an idea about a fix for this, as I'd much rather use the Domoticz interface

[Egregius]

I presume Z-way soft is only possible on the razberry and not with a usb stick?

[evansnp]

Hi Egregius; I believe that it works with either. I think that you may need a license if you use it with a non 'zwave.me' device though.

[hamish]

TBH, I'm about to throw my toys out of the pram with zWave... I have a setup with two controllers. A RaZBerry and an Aeotec Gen5. On separate RPi-2's. The RaZBerry is the master domoticz, but the secondary controller. The Aeotec is a slave domoticz, but is the primary controller for the zWave network.

The RaZBerry (master/secondary) is in the hall and the Aeotec (slave/primary) is in my office (Both on First Floor). I have a Fibaro RGBW that's literally 90cm from the Aeotec. The Master says its dead even though the Aeotec can see it (WTF!) except when I switch it on via the slave. THEN the master says it's OK (Suddenly) about 50% of the time. The groups & network meanwhile says there's a path between all devices.

Until 2 hours ago I had a Qubino 2 relay in my shed reporting power and switching fine. Contactable by the slave, not the master (Even though the master was pretty much literally between the slave and Qubino). A restart of Domoticz on the master later and it's ok.. No hold on, now t's dead again... 5 minutes later another device goes dead.

zWave is so frustrating... There's no good tools for diagnosing issues. It's really a plug & pray protocol. And I'm not religious, so that is NOT going to help.

Sometime it works. Usually it doesn't. And when it's flakey it's really flakey... And for some reason, so dependent on the software driving the controller. Lots of things that look fine on the zwave.me software just plain flat out don't work on domoticz and OZW. And since OZW is really just taking to the controller and not doing the controlling itself, I really con't see what that would make a difference unless OZW just isn't capable of talking to the controller... Which I don't really see is the issue. (Could be, but I'd expect to see some messages that ere just plain not decoded by OZW if that were the case).

Anyway... rant over.. Time for sleep, I've been for a visit to the brewery... That always sets me off. Maybe zWave will have recovered for a while in the morning when I get up...

H

[MAidEN]

I have the same problem, my zwave controller is a Sigma Designs UZB Z-Wave +

Many times I have timeout notification from a Qubino. Is particulary embarrasing because the Qubino controll a radiator when temperature is cold!

On zwave control panel, my node is dead. He restart randomly after health repair, or domoticz reboot, or worst physicaly association with controller (like first install.. )

Can you say, if you can configure notification (mail for exemple) when we have timeout errors messages from zwave device?

I Hope this problem will be fix because is really embarrassing for zwave community users!

[MAidEN]

Update: I've been running with just the z-way software for 48 hours now, and all devices are present, no timeouts, no dead nodes, and the network routing is all green. There is definitly something wrong with the z-wave implementation in Domoticz. Please can we have an idea about a fix for this, as I'd much rather use the Domoticz interface

evansnp, can you explain how do you test with z-way software ? Is universal software?

[MrJens]

I experienced a similar issue to what is described above when I installed a new RPi with Razberry and Domoticz. My first RPi+Razberry with basically the same configuration had been working without any issues for six months.

The solution that finally worked for me was to roll back to an older firmware of my RPi, by executing the following command (sudo rpi-update commit-id), which downloads and installs firmware version 4.1.17-v7.

Code: Select all

sudo rpi-update 0764e7d78d30658f9bfbf40f8023ab95f952bcad

Domoticz Version on both Raspberries.
V3.4834, Build Hash: 8398125, Build Date: 2016-03-02 08:43:51

Firmware on non-functional Raspberry.
4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linu

Firmware on functional Raspberry.
4.1.17-v7+ #834 SMP Mon Feb 1 15:17:54 GMT 2016 armv7l GNU/Linux

[Yustmenl]

I experienced a similar issue to what is described above when I installed a new RPi with Razberry and Domoticz. My first RPi+Razberry with basically the same configuration had been working without any issues for six months.

The solution that finally worked for me was to roll back to an older firmware of my RPi, by executing the following command (sudo rpi-update commit-id), which downloads and installs firmware version 4.1.17-v7.

Code: Select all

sudo rpi-update 0764e7d78d30658f9bfbf40f8023ab95f952bcad

Would this sulution also work for a PI3?

[MAidEN]

I experienced a similar issue to what is described above when I installed a new RPi with Razberry and Domoticz. My first RPi+Razberry with basically the same configuration had been working without any issues for six months.

The solution that finally worked for me was to roll back to an older firmware of my RPi, by executing the following command (sudo rpi-update commit-id), which downloads and installs firmware version 4.1.17-v7.

Code: Select all

sudo rpi-update 0764e7d78d30658f9bfbf40f8023ab95f952bcad

Domoticz Version on both Raspberries.
V3.4834, Build Hash: 8398125, Build Date: 2016-03-02 08:43:51

Firmware on non-functional Raspberry.
4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linu

Firmware on functional Raspberry.
4.1.17-v7+ #834 SMP Mon Feb 1 15:17:54 GMT 2016 armv7l GNU/Linux

Thanks a lot, i had a firmware above 4.1.17 on my rasp pi 2, after downgrade to 4.1.17-v7+, my zwave network is very stable, no more timeout notifications after fews months!

[Westcott]

Wow, I've just found this topic and thought something like "What's my RPi's firmware version got to do with Z-wave stability?"
Anyway I'm giving it a try.
Already my BLE devices are working again, having stopped last June.
I think one of my Fibaro FGMS001s is reporting regularly again.

MrJens - thanks muchly
Another update tomorrow...

[hamish]

Small nit... That's not the firmware... That's the kernel version you're looking at. The firmware is something like

Code: Select all

root@piman-202:/home/hamish# /opt/vc/bin/vcgencmd version
Mar 15 2016 14:47:28 
Copyright (c) 2012 Broadcom
version 1bf9a9a77026af9128a339c82d72e331d3532ee4 (clean) (release)
root@piman-202:/home/hamish#

As opposed to the kernel version...

Code: Select all

root@piman-202:/home/hamish# cat /proc/version 
Linux version 4.1.19-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #858 SMP Tue Mar 15 15:56:00 GMT 2016
root@piman-202:/home/hamish#

[johpe]

I experienced a similar issue to what is described above when I installed a new RPi with Razberry and Domoticz. My first RPi+Razberry with basically the same configuration had been working without any issues for six months.

The solution that finally worked for me was to roll back to an older firmware of my RPi, by executing the following command (sudo rpi-update commit-id), which downloads and installs firmware version 4.1.17-v7.

Code: Select all

sudo rpi-update 0764e7d78d30658f9bfbf40f8023ab95f952bcad

Domoticz Version on both Raspberries.
V3.4834, Build Hash: 8398125, Build Date: 2016-03-02 08:43:51

Firmware on non-functional Raspberry.
4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linu

Firmware on functional Raspberry.
4.1.17-v7+ #834 SMP Mon Feb 1 15:17:54 GMT 2016 armv7l GNU/Linux

Thanks a lot, that did the trick for me and solved my problem.

Does anyone know which newer versions of the firmware works with z-wave?
My guess is that there ought to be some newer versions that will work

Best regards,
johpe

[pikapt]

I'm also having this issue, i've tried the previous firmware update but my pi didn't restart after that..