Strange Zwave Devices

[tibbar]

How come one of the sudden some strange devices show up in y ISY.

One of my devices is on/off receptacle with address ZW013_1 and today couple new once showed up:

ZW013 Energy Meter and ZW013 Multilevel Switch.

How do I deal with it?

[oberkc]

You do not have these two devices and have made no attempt to add any zwave devices?  Do you have the Z-wave card installed in your ISY, along with the z-wave software?

[tibbar]

Of Course I have Zwave card. I have 14 Z wave devices. I did not try to add any new devices recently. I have couple On/Off switches with energy metering feature and one Aeon Labs first gen energy meter but they are ZW019, ZW029 and ZW017.

[tibbar]

Also just noticed another " Energy Meter" ZW028_143, I have a GE Outdoor Module with that address (ZW028).

And another one of my GE Outdoor Modules ZW007 have a exclamation mark saying that ISY can not communicate with it but I can turn it on and off fine.

[stusviews]

Try Z-Wave > Tools > Heal Z-Wave Network.

[tibbar]

Did the Heal, cleared java cache, still the same.

[danbutter]

Did you delete some zwave devices prior to this?

Isy never reuses a zwave address it seems. So if you have more than 13 devices it would seem that you had to have deleted something before. I had some strange issues like this when leaving the admin console open too long.

I would see things all wrong from current status.

Have to close the admin console and start over to see normal statuses again.

Not sure if related, but sounds similar to what I have experienced.

[mwester]

The ISY does not have a pre-defined database of zwave devices, thus it does not know in advance which nodes to create -- it creates them on-the-fly when it gets a message from a device.  So, nodes can appear long after you add the main node -- in the "correct" case, this would happen when the new node is heard from for the first time.

 

I've observed bogus nodes being added to existing devices - for example, the Aeon multisensor in my garage just got a "wind speed" node added -- which would be way cool if the device actually had a wind speed sensor.  But it doesn't, so the node is useless garbage.

 

You can just ignore the added, useless nodes - or if the entire node that was added is bogus, just delete it.  No harm done.  For my multisensor, it's on the same screen with the real readings, so deleting it is probably a bad idea -- I'm just ignoring it for now.

[tibbar]

Did you delete some zwave devices prior to this?

Isy never reuses a zwave address it seems. So if you have more than 13 devices it would seem that you had to have deleted something before. I had some strange issues like this when leaving the admin console open too long.

I would see things all wrong from current status.

Have to close the admin console and start over to see normal statuses again.

Not sure if related, but sounds similar to what I have experienced.

Thanks for trying but I do not think its related.

[tibbar]

The ISY does not have a pre-defined database of zwave devices, thus it does not know in advance which nodes to create -- it creates them on-the-fly when it gets a message from a device.  So, nodes can appear long after you add the main node -- in the "correct" case, this would happen when the new node is heard from for the first time.

 

I've observed bogus nodes being added to existing devices - for example, the Aeon multisensor in my garage just got a "wind speed" node added -- which would be way cool if the device actually had a wind speed sensor.  But it doesn't, so the node is useless garbage.

 

You can just ignore the added, useless nodes - or if the entire node that was added is bogus, just delete it.  No harm done.  For my multisensor, it's on the same screen with the real readings, so deleting it is probably a bad idea -- I'm just ignoring it for now.

Thanks it seams it is the same case here.