Have I posted to correct forum? Please direct me if not. TY

Hi All,

I have a few AEOTECT recessed door sensors and have always been able to get them discovered after a couple tries of adding and removing the device. In this case, I have two new sensors and no matter what I can think of trying, they show up as "ZY049 V1 Alarm" with sub-device "ZY 049 Wake UP". I expect to see the Door-Window Sensor, the Power Alarm, etc. (screenshot attached showing the new device at top, and existing device ZY 033 about midway down the device list.

I have recently upgraded EISY to 6.0, but can't find anything in release notes to support the problem I'm having. I have Z-WAVE module 21100.

A few notes:

• EISY occasionally hangs when I attempt to "Update with Interview", only hard reset brings it back (this problem is secondary)

• Java is updated to v8 build 471, but problem occurred before java update (cache was cleared)

• Other Z-Wave devices in the EISY work fine, including a sensor with same firmware and model

• Two different new sensors exhibit this behavior

Looking for any help. Thanks folks.

:walkman99

Edited Thursday at 01:44 AM5 days by walkman9999
unsure if I've posted to correct forum

Adding new ZWave devices is always a bit hit and miss. They always end up working, leaving you wondering what exactly was needed. If you rub your belly twice and then touch your left elbow, it works better... Or maybe not.

If these are battery powered, bring them close to a line powered ZWave device for optimal signal strength. Often doing a factory reset on the device helps. You might even try starting with an exclude procedure first.

Thanks for quick reply. In this case, I've repeated the procedure 17 times (last device was 033, this one is now 055). I can't really expect any additional iterations to work.

Comms don't seem to be a problem, I'm in proximity to the dongle and the add and remove commands seem to be responsive. I've performed factory reset on the sensor multiple times and according to the LED blink sequence, it has been successful. Any idea if factory reset on Z-Wave dongle (ZWAVE->Advanced->Factory reset Dongle) is a good move. Will it remove any devices I have in the network?

I also tried the log events during add/remove sequences (ZWAVE->Capture log), but the log was empty of events. Just showing the TAIL commands but zero bytes of logging data.

Other than the rubbing belly trick (which I will now try and report back), any other suggestions?

No real new suggestions, unfortunately. Factory resetting the dongle would very likely delete your other ZWave devices. ZWave is rather cryptic to work with, with few diagnostic tools compared to Insteon.

@walkman9999

What is node "337" above the other 2 nodes for your Aerotec sensor.

Post a screenshot of that node

I'm not 100% sure of the terminology, but 337 is the container for the entire network. It is where devices go when I "remove from folder".

Edit: screenshot attached

Edited Thursday at 02:53 PM5 days by walkman9999
added screeenshot

What Zwave dongle are you using, the UDI Zwave or a 3rd party?

I noticed you have 3 nodes for ZY055 basic control, there should only be one node.

If ZY055 is the device your have a problem with then put it in the linking mode, and do an exclude device from your controller. Once all the devices' nodes are removed from the controller do a factory reset on the device, then include it into you controoller.

Note: each time you add a zwave device to the controller the number will increment by one, i.e. 055 will become 056.

I am using the EISY with UDI ZWAVE module that plugs into the device's USB port, model 21100.

I performed factory reset on the AEOTEC device each time I exclude. LEDs indicate that the reset was successful.

I have repeated the remove/include process multiple times. Both inclusion and removal are quick. Removal works as expected with all components removed from EISY tree. Inclusion triggers the interview and the result is some subset of the total components of the device showing up, sometimes just the alarm and wake-up, other times (as pictured) with everything except the "Alarm Controller" which is the main component that the subs get nested under when present.

Is there a separate option for "exclude" (rather than remove)?
Any other tips? Happy to keep experimenting, but I've tried any combination of EISY ZWave menu items I can think of.

thank you for your input and info

When you "removed" the device did you use EXCLUDE in the zwave menu or just delete it from your device tree?

The proper way to remove a zwave device is to use exclude, and put the device into the wakeup/linking mode.

Being that the device is battery powered you may need to move it close the the controller when you include it

There should be no need to use the "Update with interview" option.

I removed with:
EISY-> ZWAVE-> remove a ZWAVE device menu

The process work well. I've heard folks refer to "exclude", but I assume that remove is the ESIY equivalent.

The reason I use the "Update with interview option" is because the device is "connected", but the subcomponents were not discovered correctly.

In ther EISY zwave menu remove is the same as exclude

When you removed the device were all of the nodes of the device removed from your device tree

Did you try bringing the device closer to the eisy when you added/included it. You should also try doing a reboot on the eisy before you include it. That's really the only other option I can suggest.

I don't suspect comms as the problem - the rest of the ZWAVE network works well, and include and remove commands seem "snappy".

I understand we're reaching the end of the troubleshooting road, I appreciate the suggestions.

What's uncommon is that you have 3 instances of ZY055 basic control, you should only have one.

When you installed the device did you select S0 for security?

Have you rebooted the eisy after removing the device and before installing it again

If the above doesn't resolve the problem you should contact Aeotec support, they're very responsive.

Support : Aeotec Help Desk

@walkman9999

Take a look at this post

https://forum.universal-devices.com/topic/45830-weird-device-adding-after-v6/

I did not reboot between attempts, I will try that. The extra instances just appeared - seems like I'm getting bad interview data maybe. The results of interviews is not predictable. I do not use security, it is not enabled in EISY or on the devices.

I do have the issue described in the link you provided. I just assumed it is a "dot zero" type of bug that will be patched. It doesn't seem to affect operations in a direct way.

Thanks you for the helpful info. There is a certain "wife window" that I can work on home automation. She is supportive but I sense that that window is closed until the weekend. I will pick it up then.