Bug994 Posted October 9 Posted October 9 (edited) I have an Aeotec Z-Wave Wallmote Quad (ZW130-A) that had been working well for quite some time with my 994 and the Z-wave board. It showed up as multiple nodes in ISY and I was able to use the four buttons in multiple programs. This device didn't migrate properly when I migrated to eisy - showed as Placeholder and no attempts at Synchronize > Update with Interview would bring it back (which worked for some of my Z-wave devices). I was able to do a Remove which worked fine. However, when I re-add it as a new Z-wave device, I'm not getting anything except a single node in my device tree: "ZY 088 Wall Controller" Any ideas why I'm not getting all my nodes when I re-add my device? I haven't tried re-booting my eisy yet, but that shouldn't be needed, right? Here are my logs: Tue 10/08/2024 06:13:11 PM : ---- Start Adding Devices - S2 Standard --- Tue 10/08/2024 06:13:11 PM : [ZWAVE-INCL-S2STD] Start Include with S0/S2 or non-secure Tue 10/08/2024 06:13:11 PM : [ZWAVE-INCL-S2STD] Added 'CommandAdded' callback 0xd6a8468 Tue 10/08/2024 06:13:11 PM : Z-Wave Listening for Z-Wave devices to add to the network Tue 10/08/2024 06:13:15 PM : Z-Wave Z-Wave device detected, start adding to network Tue 10/08/2024 06:13:15 PM : Z-Wave Z-Wave device detected, retrieving info Tue 10/08/2024 06:13:15 PM : [ZW-INTERVIEW-38 ] Add interview running entry for 88 Tue 10/08/2024 06:13:16 PM : [Device 88] Waiting on interview complete (timeout in 578) Tue 10/08/2024 06:13:18 PM : [Device 88] Waiting on interview complete (timeout in 538) Tue 10/08/2024 06:13:20 PM : [Device 88] Waiting on interview complete (timeout in 498) Tue 10/08/2024 06:13:22 PM : [Device 88] Waiting on interview complete (timeout in 458) Tue 10/08/2024 06:13:24 PM : [Device 88] Waiting on interview complete (timeout in 418) Tue 10/08/2024 06:13:26 PM : [Device 88] Waiting on interview complete (timeout in 378) Tue 10/08/2024 06:13:28 PM : [Device 88] Waiting on interview complete (timeout in 338) Tue 10/08/2024 06:13:30 PM : [Device 88] Waiting on interview complete (timeout in 298) Tue 10/08/2024 06:13:32 PM : [Device 88] Waiting on interview complete (timeout in 258) Tue 10/08/2024 06:13:34 PM : [Device 88] Waiting on interview complete (timeout in 218) Tue 10/08/2024 06:13:36 PM : [Device 88] Waiting on interview complete (timeout in 178) Tue 10/08/2024 06:13:38 PM : [Device 88] Waiting on interview complete (timeout in 138) Tue 10/08/2024 06:13:40 PM : [Device 88] Waiting on interview complete (timeout in 98) Tue 10/08/2024 06:13:42 PM : [Device 88] Waiting on interview complete (timeout in 58) Tue 10/08/2024 06:13:44 PM : [Device 88] Waiting on interview complete (timeout in 18) Tue 10/08/2024 06:13:46 PM : [Device 88] Waiting on interview complete (timeout in 0) Tue 10/08/2024 06:13:46 PM : [ZW-INTERVIEW-38 ] Device 88 : Interview Done with some non-conforming features : total=0 successful=0 attempted=0 Tue 10/08/2024 06:13:46 PM : ZWAVE-WORKQ-35 Queue sync device 88 (initialize) Tue 10/08/2024 06:13:46 PM : ZWAVE-WORKQ-35 Start sync device 88 Tue 10/08/2024 06:13:46 PM : [ZWAVE-SYNC 88] Rebuilding all existing ISY files/objects for Z-Wave device Tue 10/08/2024 06:13:46 PM : [SYNC-DEVICE 88.0] Root database 4.24.1 mfg=0.0.0 Tue 10/08/2024 06:13:46 PM : [SYNC-DEVICE 88.0] Set commands will now be accepted by the controller Tue 10/08/2024 06:13:46 PM : [ZWAVE-SYNC 88] Not multichannel Tue 10/08/2024 06:13:47 PM : [SYNC-DEVICE 88] Initializing associations to ISY Tue 10/08/2024 06:13:47 PM : ZWAVE-WORKQ-36 Queue write device updates for node 88, full=false Tue 10/08/2024 06:13:47 PM : ZWAVE-WORKQ-35 Finished sync device 88 Tue 10/08/2024 06:13:47 PM : ZWAVE-WORKQ-36 Start write device updates for node 88, full=false Tue 10/08/2024 06:13:47 PM : ZWAVE-WORKQ-36 Finished write device updates for node 88, full=false Tue 10/08/2024 06:14:37 PM : Z-Wave Z-Wave device added Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=32 (0x20) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=89 (0x59) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=90 (0x5A) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=91 (0x5B) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=94 (0x5E) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=96 (0x60) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=112 (0x70) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=113 (0x71) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=114 (0x72) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=115 (0x73) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=122 (0x7A) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=128 (0x80) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=132 (0x84) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=133 (0x85) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=134 (0x86) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=142 (0x8E) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=37 (0x25) : uid=88.0 Tue 10/08/2024 06:14:37 PM : [ZWAVE-INCL-S2STD] 'CommandAdded' callback: ccId=38 (0x26) : uid=88.0 Tue 10/08/2024 06:14:37 PM : Z-Wave Idle Tue 10/08/2024 06:14:37 PM : Z-Wave Idle Tue 10/08/2024 06:14:37 PM : Z-Wave Idle Thanks... Edited October 9 by Bug994 wording Quote
Techman Posted October 9 Posted October 9 Are you on an eisy or polisy. What is your firmware and UI version? A few things you can try: exclude the device from you controller, charge the battery, and then bring the device close ot your controller and include it. Quote
Bug994 Posted October 9 Author Posted October 9 Thanks for the quick reply. eisy, 5.8.4 for both firmware and UI, Z-Wave module is 21100 I successfully removed the device and it re-adds OK when I do "Add a Z-Wave Device" - but it doesn't seem to do a "full" add. I did bring it down to the eisy device and added it just a foot or two from the antenna on the Z-Wave dongle. I'll let the device charge overnight and give it another shot in the morning. Quote
Bug994 Posted October 10 Author Posted October 10 I tried a number of things and still no luck. It's not a critical device for me, so I'm not too broken up about it. Would be nice to get it going some day though... Quote
Techman Posted October 10 Posted October 10 Have you tried doing a factory reset on the Aeotec device? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.