I have a UI5 Vera3, and an Aeon 4-in-1 motion sensor on USB power. The sensor included fine, and works almost fine. The only problem is that motion notifications are severely delayed – like, for minutes (it feels as if they get delivered when Vera polls the sensor every 10 minutes). I used this same sensor on batteries for a bit, and that worked fine. But then I deleted it from Vera, and reincluded it while USB-powered, and this craziness started. Any ideas on how to troubleshoot this?
Did you delete or exclude the device? What’s the first number in Capabilities under the Settings tab?
Deleted (I assumed that process also properly excludes device from the network). The Capabilities are:
210,156,0,4,32,1,L,R,B,RS,|48,49:5,112,114,128,132:2,133,134,
[quote=“twka90, post:3, topic:186046”]Deleted (I assumed that process also properly excludes device from the network). The Capabilities are:
210,156,0,4,32,1,L,R,B,RS,|48,49:5,112,114,128,132:2,133,134,[/quote]
Delete and Exclude are not the same. Alot of times a deleted device just pops right back up as the z-wave scans and still has the device stored just not on the dash board.
It registered correctly as a mains powered device. Try excluding then include the device. FYI the first number in capabilities tells you if it’s battery powered or not. Per the micasaverde wiki:(http://wiki.micasaverde.com/index.php/ZWave_Command_Classes)
If the Capability is >= 128 then the device listens for commands, otherwise it’s a battery operated device that only wakes up occasionally.
To close the thread. Excluding the sensor, and then bringing it back appears to have worked.