Z-wave Notification sensor ( in red )

[ronh123]

Any one an idea what this can be?
(See picture ) In the hardware overview of the Z-wave devices a Unknow item description Notification Server, No ID and in sleep mode?
Unable to delete it up till now.
Thanks Ron

[AllesVanZelf]

Ik have the same kind off red node.

Unable to remove it, and I'm not sure where it comes from.

[galinette]

I had the same after upgrading to the latest stable domoticz. This corresponded to a Fibaro Door Sensor, and it wasn't working anymore. So I switched back to the previous version... Latest "stable" is extremely crappy regarding zwave.

[ronh123]

Cleaned up the 'ghost' items with the AEOTEC configuration tool.
Actions: Delete the nodes in Domoticz Z-wave overview. And remember the NodeIDX
They will stay in the command panel ( Bedienings paneel ) of Z-wave. That's ok.
Poweroff your Domoticz
Backup your stick previous to this network management actions. Just in case of failures.
(I did test on a backup stick first).
The tool:
Backup via zwave_500.exe ( https://domoticz.com/forum/viewtopic.php?f=24&t=37202 )
Z-Wave command class configuration tool download.
https://help.aeotec.com/support/solutio ... -download- ( follow the instructions )
Install ( will take some minutes, and need to register ) and via Tools, select Z-wave and network management you can manage the nodes.
Delete failed nodes.
I'm up and running again without any strange nodes now.

[roblom]

Or check if it's failed, if yes then you can delete it. Both actions can be done in Domoticz or ozw config.

[lost]

On the first message, we have 2 nodes (red one + neo water leakage detector just on top) with zeroed IDs.
When such issue happen, that's usually fixed after triggering a node wake-up (for most modules, that's a triple click on association button) for those battery powered or a power-off-on on 220Vac ones.
This probably results from incomplete node queries sometimes happening during domoticz/OZW restarts. Looks some modules do not handle zwave network congestion (or missed message sends while controller side if off) that may happen in such startup phase.

[wulfy]

Hi there,

same problem here.
Did someone found a solution? Fibaro door sensors kept beeing not recognized
How did you fall back to previous version? I m on last stable version and there is no way to go back without compiling source.

tx

wulfy

[lost]

How did you fall back to previous version? I m on last stable version and there is no way to go back without compiling source.

You did not stopped domoticz service & archived old install directory before upgrading to new stable?

This is what is advised, because even if you find an install archive of previous stable (on my side, I always keep them as a new stable always kicks old one out) your likely to have DB issues: Upgrade is managed, but downgrade is not.