I’m a newbie - I just purchased my Vera3 recently. I have 3 Aeon Multisensors, all purchased from Amazon recently. 2 of them are seemingly working perfectly - they are active in the web interface, and showing motion, temp, humidity and light. All the readings seem to reflect reality. However, the third Multisensor will not show temp or light. It’s giving a humidity reading, and seems to accurately respond to motion, but it’s light level and temp “windows” are blank.
I’ve excluded / included it a couple of times, and it’s very consistent in not showing temp or light.
The settings on all three Multisensors match. All 3 display
– Version: 6,3,28,1,18,
– Capabilities: 82,156,0,4,32,1,R,B,RS,|48,49:5,112,114,128,132:2,133,134,
All three devices have been acquired for at least 3 days.
It did take a little while for the first two to report sensor values, but they now do so consistently.
All three were sitting on my desk when originally configured. The troublesome unit is still sitting right next to the Vera3.
Any ideas? Is this unit broken, or is it some kind of configuration issue that I’m missing?
You’ve done all the right troubleshooting steps. With three units all using the same firmware and configurations, but one unit not working properly, it must be assumed that that unit is bad. Return and replace it.
IIUC, it is showing the temperature and light level widgets, but they are not showing a reading?
If so, can you confirm how long you waited for the readings to show up / have you reloaded Vera / reloaded the web page / do the values show when using an app on your phone / tablet (if you have one)?
Try a triple click on the black button on the Aeon, so the red LED comes on and stays lit, then do a [tt]Poll now[/tt] in Vera, then a triple click so the red LED turns off.
All,
Thanks for the help! Here’s the latest - I received an email reply from Chris at Aeon Labs. The temp and light levels appeared almost immediately upon making his suggested configuration changes. FYI, the Aeon Multisensor instruction manual (which documents the configuration settings) can be found here: http://www.smarthus.info/support/manuals/zw_sikkerhet/aeotec_multisensor_tech.pdf
Here’s our exchange:
Hi James,
Add a configuration setting 101, then set the desired value to 225, also set the Data size to 4 byte dec
Then add configuration setting 111, then set the desired value to 240, also set the Data size to 4 byte dec
I’ve attached the engineering specifications to this email, it has a list of all the parameters available for the Multisensor.
Make sure to wake up the Multisensor when you want to save your configurations. You can find the information on how to do that in the instruction manual.
When you are done configuring, put the Multisensor back to sleep to ave some battery life.
If you have the Multisensor connected to USB, the Multisensor will always be awake.
Cheers,
Chris
Chris,
That seems to have worked. Thanks! Now I’m really curious why this sensor needs those configuration settings, when the other two multisensors are working fine without them.
James
Hi James,
Vera has an auto update for parameter configurations. But sometimes, with battery devices (general Z-Wave battery devices such as the Multisensor) may go to sleep before getting all configurations.
In your case, 2 of the 3 multisensors were able to get all the automatic changes, while the 3rd multisensor had issues with getting the data and went to sleep before it gathered all the data. This can happen on occasion.
@JamesHaskell, agree with Z-waver, sharing the technical details provides an invaluable knowledge base for those who have issues afterwards. Thank you, sir.
That remains a bit of a mystery. Aeotec appear to indicate that the wake-up mechanism did not complete (success)fully (which is I why I suggested trying a forced poll with the device awake), and instead had you use the auto-push mechanism to work around it. It doesn’t seem to explain why your 3rd sensor had these symptoms, even when freshly included and located directly next to Vera.
The wake-up not completing has been discussed here in the past, but in light of devices with short wakeup timeouts and outside of direct radio reach.
(The tech spec had been posted before, on the master topic, but is buried deep in there.)