I have installed a new Aeon sensor on my garage door. It will sometime go into the configure mode. I have to take it down and click the tamper switch 3 times(per instructions) to put it back to the operating mode. Sometimes I don’t catch it and it will run down the battery in just a couple days.
Any ideas?
I have started setting my Automatically Configure answer to “NO” on the settings tab of the device. I installed three Aeon Labs door/window sensors about a month ago. I excluded then included the sensor right beside vera2 then waited 5 secs and clicked on Configure Node Right Now in the setting tab of the device. This allowed me to configure each of the sensors manually. However, when I ran a heal manually or a heal occurred automatically at 2 AM, these sensor gave a message “unable to configure”. Fortunately, I was still present in that home so I did the above steps all over again. With the Automatically Configure answer set to NO, they seem to work just fine including giving battery levels. I have tried to see if Vera2 (1.1.1245) can automatically configure these sensors on three different occassions and it failed to do so each time after waiting at least 6 hrs after a heal was run! I have been in touch with MCV about this issue but have not gotten a satisfactory response. They have offered to allow me to load the latest beta but can’t assure me that this problem will be fixed!
Wonderful. I just set mine to no. I guess i will see in the next few days. I also have a Home manageable I have not had a problem with this one. I like the Aeon because of the size.
You may have to start over with your Aeon Labs sensors by excluding then including then “configure node right now” within 10 secs of including to get it configured properly. Then answer NO to the Automatically Configure question to keep Vera from misconfiguring it. If vera didn’t configure it properly then just setting the answer to NO alone will probably not undo the harm.
If you are local to this sensor it is a minor inconvenience. If you are 3000 mi away as I am from one of my vacation homes, repairing and reconfiguring is not a minor problem.
MCV recommended that I upgrade to beta 1338 to see if this would remedy my problem. At first after I completed a heal after the upgrade, all 6 of my battery operated sensors displayed “unable to get any information on”. However about an hour later only the 3 Aeon Labs window/door sensors continue to display this message. It doesn’t appear that the latest firmware upgrade has solved this problem. I will give vera more time to properly configure those 3 sensors but I am not optimistic. Then I will try to restore my backup with dongle backup to see if it will restore my previous settings. Otherwise, I will have to travel to that home (135 mi each way) to exclude, include and then “configure node right now” each sensor to get it to configure properly again.
Somebody owes me about $20 in batteries. I have changed the auto configure to no. It goes to configure mode and then runs the battery down. So much for the 2 year battery life . Is this a Aeon or Vera problem. The door sensors are the more unreliable module I have.
I starting to get very disappointed in this stuff.
[quote=“aecchalet, post:4, topic:168875”]You may have to start over with your Aeon Labs sensors by excluding then including then “configure node right now” within 10 secs of including to get it configured properly. Then answer NO to the Automatically Configure question to keep Vera from misconfiguring it. If vera didn’t configure it properly then just setting the answer to NO alone will probably not undo the harm.
If you are local to this sensor it is a minor inconvenience. If you are 3000 mi away as I am from one of my vacation homes, repairing and reconfiguring is not a minor problem.[/quote]
I used the above technique and it seems to work fine now. It’s a bit of a hassle to jump through those hoops for a “simple” sensor. Hopefully MCV will address this.
One question what are you guys setting the wake up interval to? Mine is set to the default of 1800 seconds. I have polling set to zero. I question the need of having the device wakeup at all. It seems like it would just burn the batteries.
Sounds like we have multiple reports. I’ve seen it too. I’ll file a bug on it.
Mine seems to work after an exclude / include. After a day or 2 I have hit the tamper switch 3 times to exit the config mode. If I don’t catch it the battery goes dead. I am going to rig a 3v power wart for the power and see how longs it works with good power.
The one Hawkings HRDS1 I have works great. I think my only problem here is I used rechargable batteries in it. It didn’t last long. I put Energizers in now. Will see how long it will last.
I can’t find the HRDS1 anywhere. Somebody said they discontinued them. I can’t find any other manufacturers except the Aeon.
The HRDS1 has come back on the market.
What type of rechargeable battery did you use? Sanyo eneloop are the best rechargeable batteries out there. However, rechargeable batteries hold a smaller charge and die quicker when used regularly than good lithium batteries of comparable size. However eneloops are in a class of long self discharge and have very long shelf lifes if stored at the proper temperature. Sanyo eneloops are more expensive than Energizer ultimate lithium batteries but the eneloops can be recharged up to 1500 times! (Eneloops are available in AAA and AA sizes.) These should be great if you live in or close to the house with these sensors. That is not the case for either of my homes with these sensors so I am trying energizer ultimate lithiums to try to get the a longest duration of action.
BTW Vera still can’t configure these Aeon Labs sensors. I am moving all but one of these between houses and the one that is still installed is indefinitely “waiting for wakeup to configure”!
How are you guys configuring the node within 10 seconds of inclusion? After I include it, I have to name it and then save it and that takes like 30 seconds +. Getting this simple sensor configured is starting to drive me insane. Any help would be appreciated.
Thanks, Rob
Welcome!
I don’t recall issues getting mine to work. Note that you can triple click the tamper switch quickly to wake up the device (red LED will be on). After you’re done configuring, you triple click it again to put it back to sleep.
The simple way to do this is to take the sensor out off it’s backing, this wakes the sensor.
Go to Vera, click on the node, in the settings tab clicking on Configure node right now.
As you have the sensor with you, click on the sensor, it should then be configured.
Put it back.
Support relative to the AEON single Door Sensor:
I have read this thread and seems that different processes have worked for different people, and some of the process seem to contradict one another. Regardless, none of the process have seemed to work for us.
Can someone provide a link that describes how to exactly configure the AEON?
Here are the steps that we feel are most appropriate, but we are obviously doing something wrong:
Yet, within a few hours we get another message “Waiting for wakeup to configure”
The sensor still gives accurate state, however within a few days teh battery icon will show with “?”
It would be greatly appreciated if someon could provide the correct process for Both AEON and UI4/UI5?
Thanks in advance for your support.
Sean
Thanks in advance for your support.
We have authored/developed a process that seems to be pretty consistent in terms of applying the AEON Door/Window 1 sensor. (See attached PDF)
If the device’s Advanced tab (in VERA) does not show the above parameters you will need to repeat the above process in its entirety.
However, we have noted that in some applications on UI4 and UI5 alike, the sensor eventually gives a “?” inside VERA device interface.
On other VERAs it seems to work fine.
Does anyone know what would cause the Battery to go to “?” on a VERA UI4 or UI5 interface if device added properly? (I can say that the battery icon shows “?” if no activity on sensor for more than a few days)
Thanks in advance for any support on this.
Excerpt from [tt]http://wiki.micasaverde.com/index.php/Release_Notes[/tt]:
35. Add logging for the last time the battery level was reported and show the battery icon as a ? if it's been more than 7 days.
AP15e,
Thanks for this information. If not for your reference, i would have assumed problem with Aeon or Vera.
Sean
Ap15e,
We visited the client site where we are using these AEON D1 door sensors.
We had felt (after weeks of testing here in our lab) we had finally determined how to configure properly.
In this case, we had configured the Sensors as per the PDF we listed, and then as indicated in previous post, the Sensors showed “?” after a number of days of inactivity.
Your comment that the 7 days of no activity will show “?”, and our assumption was that simply opening the door (changing state) would send a state change along with battery state to VERA. but we found this not to be the case. The Door would change state in VERA, but the battery did not update as we had hoped/expected. We found that we had to press the tamper switch to update the battery state on one sensor… And on teh other we had to reconfigure it.
We like the AEON sensor for easy of support and installation and CR2 battery. But it they are not consistent (like HDRS1 or SM103) we are not able to consider them.
I am not sure if anyone else is using these sensors in a production environment where doors can be dormant for weeks at a time, but anyone’s input/experience with these devices is greatly appreciated.
Thanks
Sean
Our configuration is as follows:
Vera = 1.1.362 firmware
AEON Manufacture INFO = 134,2,4
AEON Version Info = 6,2,97,3,1
PS: for this next test we did the following:
[quote=“smilligan, post:19, topic:168875”][…] our assumption was that simply opening the door (changing state) would send a state change along with battery state to VERA. but we found this not to be the case.
[…] production environment where doors can be dormant for weeks at a time,[…][/quote]
My impression is that Vera asks for the battery level every so many hours; so this would be driven by the wake-up interval.
(All my Aeon sensors show battery levels, including my test sensor that essentially ‘does nothing’.)
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules