Dead node after inclusion and restarting device

Configuration Z-Wave
1

Hi Guys,

I have a TBKHome TZ88 and its been working for if not years on smartthings. I am migrating over to HA and am using a ZMEEUZB1 (which was on firmware 5.5). I have 2 other devices connected any they work fine.

I have included the TZ88 and it workings without issues, however when I move the device and therefore power it off and back on, it fails to communicate on the z wave network and the logs show its a presumed dead.

Any thoughts? I’ve tried a bunch of stuff including the painful manual update of the ZMEEUZB1. I cannot seem to find firmware for the TZ88 (which I think could be the problem).

2020-04-16 02:27:07.658 Detail, Node014,   ZW_SEND_DATA Request with callback ID 0x3f received (expected 0x3f)
2020-04-16 02:27:07.658 Info, Node014, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-04-16 02:27:07.658 Warning, Node014, WARNING: Device is not a sleeping node.
2020-04-16 02:27:07.658 Error, Node014, ERROR: node presumed dead
2020-04-16 02:27:07.658 Detail, Node001,   Expected callbackId was received
2020-04-16 02:27:07.658 Detail, Node001,   Expected reply was received
2020-04-16 02:27:07.658 Detail, Node001,   Message transaction complete
2020-04-16 02:27:07.658 Detail,
2020-04-16 02:27:07.658 Detail, Node014, Removing current message
2020-04-16 02:27:07.658 Detail, Node014, Notification: Notification - Node Dead
2020-04-16 02:27:07.659 Error, Node014, ERROR: Dropping command because node is presumed dead
2020-04-16 02:27:07.659 Detail, Node014, Removing current message
2020-04-16 02:27:07.659 Error, Node014, ERROR: Dropping command because node is presumed dead
2020-04-16 02:27:07.659 Detail, Node014, Removing current message
2

I have a Z-Wave device which is indirectly connected using a Z-wave switch as relay station.
When I reboot my HA device (an RPI 4 with Aeon Stick) or disconnect the z-wave device from power and then reconnect it sometimes needs quite a time until the device is functional again. In this period the devices is reported dead.

So my advice is to wait several hours before giving up. In my experience the device will report back in time.

regards
Chris

3

Thanks for that advice I will test it now.

Edit: So 6 hours on and no difference. I’ve gone to the manufacture to see if there is any firmware updates. They have nothing on there site.

4

Hi.

Did you find a solution with your dead node @FlangeMonkey ?
Ty

5

I did and I’m surprised I didn’t post the resolution. although its was some 10 months ago, it feel like years thanks to recent events.

I’m really trying to recall what resolved it. If I recall correctly, I left it plugged in when first pairing it. When I got to it the next day, I could move it without issues. I see people healing the network after joining devices, so that might be why.

What problems are you experiencing?

6

My problem is here : Add Fibaro Roller Shutter 3 node to Zwave JS

To resume: Node is always with dead statut. (Fibaro Roller Shutter 3).
But, it seems it’s a problem with USB. Has i’m using SSD on USB3 and it may interfere with ZWave, Zigbee… (More information here, thx to @bjornskj Lesson learned: Z-Wave and USB SSD boot from USB3)

I bought USB extension, i’ll test it Tuesday when I get the cable.

7

I sore that, whatever the problem is, getting the radio away from the computer should help.