Has anybody been able to get the Aeotec NanoMote Quad (ZWA003) configured on Vera? I’m use VeraEdge and have tried adding it as a generic z-Wave device, but it keeps hanging with a message saying “Waiting for wakeup to configure device”. I’m on a VeraEdge with firmware 1.7.4001.
-MC
Hello,
Please note that we have made a request to our development team to work on integrating this device, with our platform.
When the message “Waiting for wake-up to configure device” shows up, you need to force the device to wake-up, while it’s closer to the unit ( 3 -5 feet away ). Please check the manual and try to do this procedure.
Thank you and Have a nice day,
Assuming the correct manual:
Pressing and holding button for 5 seconds and then release so the NanoMote Quad will wake upitself and send wake-up notification out to Z-Wave Controller. After that, it can be operated toupdate parameters, OTA, and detect battery level etc.
C
I did try that, but just to be sure I unpaired/deleted the device and re-added it - waking up the NanoMote when the first “waiting for wakeup” message appeared on the UI. The device is 1 foot from the Vera controller. It seemed to get farther along this time, but was still not configured. I tried doing “Configure Node Right Now” which produced error message “ERROR: Unable to get any information on node”, here is a snip from the log the NanoMote is device 154:
03/11/19 8:36:31.321 JobHandler_LuaUPnP::HandleActionRequest device: 154 service: urn:micasaverde-com:serviceId:HaDevice1 action: Reconfigure <0x74104520>
08 03/11/19 8:36:31.321 JobHandler_LuaUPnP::HandleActionRequest argument id=lu_action <0x74104520>
08 03/11/19 8:36:31.322 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:HaDevice1 <0x74104520>
08 03/11/19 8:36:31.322 JobHandler_LuaUPnP::HandleActionRequest argument action=Reconfigure <0x74104520>
08 03/11/19 8:36:31.322 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=154 <0x74104520>
08 03/11/19 8:36:31.322 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.056853965149841756 <0x74104520>
02 03/11/19 8:36:31.322 Device_Basic::m_eConfigured_set device 154 was -1 now 0 zw clear <0x74104520>
06 03/11/19 8:36:31.323 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:HaDevice1 variable: Configured was: -1 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0x11e26f8/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.323 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:HaDevice1 variable: LastUpdate was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.324 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: ConfiguredWakeupInterval was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.324 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: Capabilities was: 83,156,1,4,24,1,R,B,RS,|85,89S,90S,91S,94,108,112S,114S,115S,122S,128S,132S,133S,134S,152,159, now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.324 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: VersionInfo was: 3,4,61,1,2 now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.325 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: FirmwareInfo was: 881,769,22860 now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.325 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: ManufacturerInfo was: 881,258,3 now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.325 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: Neighbors was: now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x74104520>
06 03/11/19 8:36:31.326 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: LastReset was: 0 now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.326 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: MultiChEndpoint was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.326 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: MultiChCapabilities was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.326 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: AssociationNum was: 0 now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.327 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: ConfiguredName was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.327 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: ConfiguredVariable was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.327 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: ConfiguredAssoc was: EMPTY now: *RECONFIG* #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.328 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: NodeInfo was: 55,5e,6c,98,9f, now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.328 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: MeterType was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.328 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: MeterScale was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.329 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: SetPointInfo was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.329 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: SensorMlType was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.329 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: SensorBiType was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.330 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: SensorMlScale was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.330 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: SubscribedAlarms was: EMPTY now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x74104520>
02 03/11/19 8:36:31.351 Device_Basic::m_eConfigured_set device 154 was 0 now -2 zw configuring <0x74104520>
06 03/11/19 8:36:31.352 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:HaDevice1 variable: Configured was: 0 now: -2 #hooks: 0 upnp: 0 skip: 0 v:0x11e26f8/NONE duplicate:0 <0x74104520>
06 03/11/19 8:36:31.354 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusText was: OK now: #73: Please wait! Getting the name #hooks: 0 upnp: 0 skip: 0 v:0x1300e50/NONE duplicate:0 <0x76504520>
06 03/11/19 8:36:33.023 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: NodeInfo was: now: 55,5e,6c,98,9f, #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x76504520>
06 03/11/19 8:36:33.024 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: PollSettings was: EMPTY now: 10800 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x76504520>
06 03/11/19 8:36:33.024 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: Capabilities was: now: 83,156,1,4,24,1,R,B,RS,|85,94,108,152,159, #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x76504520>
06 03/11/19 8:36:33.025 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: Neighbors was: now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x76504520>
06 03/11/19 8:36:33.025 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: LastReset was: now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x76504520>
06 03/11/19 8:36:33.025 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: AssociationNum was: now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x76504520>
04 03/11/19 8:36:33.026 <Job ID="18" Name="getnodedetails 73" Device="154" Created="2019-03-11 8:36:31" Started="2019-03-11 8:36:31" Completed="2019-03-11 8:36:33" Duration="1.672377000" Runtime="1.670719000" Status="Successful" LastNote=""/> <0x76504520>
02 03/11/19 8:36:33.027 ZWJob_ConfigureNode::Run job job#17 :conf_jh#73 dev:154 (0x1461460) P:14 S:1 Id: 17 node 73 aborting because of ZWJob_GetNodeDetails job#18 :getnodedetails 73 dev:154 (0x1365d90) P:13 S:4 Id: 18 with status 4 and 5 commands quit 0 <0x76504520>
02 03/11/19 8:36:33.027 Device_Basic::m_eConfigured_set device 154 was -2 now -1 zw configuring nr1 <0x76504520>
06 03/11/19 8:36:33.027 Device_Variable::m_szValue_set device: 154 service: urn:micasaverde-com:serviceId:HaDevice1 variable: Configured was: -2 now: -1 #hooks: 0 upnp: 0 skip: 0 v:0x11e26f8/NONE duplicate:0-MC
I’ve been able to get it working with my Vera Edge. I ran into the same issues/messages as you but with some persistence managed to get it working.
It’s some time ago so I can’t remember exactly what I did. Sorry.
I would really love to see this added too… I can get it to pair but it only shows up as a single button device. I event tried adding it as a WallMote Quad and that didn’t work.
I can’t even get it to pair, super-disappointed to see it still isn’t supported in the latest firmware push. 
-MC
I also bought an Aeotec NanoMote Quad (ZWA003) I am experiencing all of the issues mentioned above. It would be nice to be able to use it the Vera Plus. This device should have some better support with the latest firmware / Operating system. I suppose there isn’t good functionality as of yet.
Thanks
Hello, are you able to report any updated from the development team wi9th the compatibility for the ZWA003? Would be really useful to use the NanoMote Quad with the Vera Edge. Thanks
In my quest to find a reliable z-wave keyfob I recently checked the list of supported remote controllers and was surprised to find a new device, Hank HKZW-SCN04 4 Button controller. I never heard of Hank, but since the device was supported I bought one, it paired easily with my VeraPlus and I was able to assign scenes to the 4 buttons easily. It appeared to work fine, but within 24 hours:
The HKZW-SCN04 started reporting that it was attempting to configure the device, but waiting for WAKEUP. This device NEVER wakes up unless you press and hold a button for 4 or 5 seconds, the WAKEUP value can only be 0. When I initiated the WAKEUP the status changed that it was configuring the device, but never finished - I did this at least 10-15 times.
Other devices started reporting problems that never existed before, in particular ALL 5 of my RTOA thermostats were reporting that the device could not be found.
I unpaired/removed the Hank, and then did a Configure Now on each of the RTOA thermostats and voila, everything is now OK again. It has been 24 hours and no devices are reporting problems. This Hank controller seems pretty good, although they really should have provided a small hole/lanyard so it could be attached to a key ring - and the back cover on mine does NOT fit tight so I’d be concerned about it falling off and getting lost. Still I wouldn’t mind trying to get this to work (maybe epoxy a lanyard to the side of the unit for use on a key ring), does anybody have any thoughts on why the device wouldn’t configure after I woke it up, or why it would cause other devices to be unreachable?
This also makes me ask if Vera could whip up support for this relatively unknown device, WHY can’t they whip up the same support for the Aeotec ZWA003?!?!? It should be fairly simple, I think it behaves nearly identical to the MiniMote - and the ZWA003 is already supported on Smart Things and HA.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules