I am using 12 Aeon Door/Window Sensor DSB04100-ZWUS, and 3 Aeon Labs Aeotec Door/Window Sensor, 2nd Edition DSB29-ZWUS with my Vera Lite running on version UI5.
About a month ago I was forced to upgrade to version UI7 in order to continue having my home automation work in the way I intended to.
My 3 Aeon 2nd Edition DSB29-ZWUS work fine under the new version.
Out of the 12 DSB04100-ZWUS
1 Fail to configure, even if it adjacent to the Vera Lite Box.
4 Fail to configure, unless it is adjacent to the Vera Lite Box
Manual routing does not work.
Heal does not work
Update Routing does not work
All of these sensors worked under UI5 up until the day I upgraded to UI7
I have wasted 5-6 new batteries trying to get them to work.
Any suggestions? ???
Hey Jimmy,
I just got one DSB04100-ZWUS with my Veralite UI7. Included just fine, but becomes disconnected from the system after some time passes. It never fails to send a contact change status, but is annoying that it indicates disconnected from the dashboard. I’m testing this since I need about ten more contact sensors.
Sounds like some quality control issues with this hardware? It is the lowest cost of all the zwave door contact sensors.
I believe it is hardware incompatibility with UI7.
Both my V1s and V2s were working fine for over a year under UI5.
It appears that the older version has issues going over a direct hop to the base under UI7.
Doing heals and manual routing doesn’t seem to help.
Nor does excluding and re-including the sensors.
I heard back from Aeon just before the weekend and I forgot to add the excluding/re-including to to my list of troubleshooting I did before contacting them.
So, of course, that was their solution.
I’ll post here how they will handle my issue if/when they contact me after the weekend.
I might add that I have been using a 3V 800mAh lithium ion CR2 that I found on Amazon in many of my zwave devices with excellent results thus far. At $3 each they are cheaper than many CR2 primary batteries.
I have been using these for nearly 1/2 the price 10 pcs Tenergy Propel CR2 Lithium Battery with PTC Protected
They are 750mAh instead of 800mAh. I don’t know how that balances out in the long run…
As far as Aeon goes. It appears more and more like a UI7 compatibility issue.
They pushed me back to Vera saying that their V1 worked with UI5 and it is not their fault that Vera changed things.
And now that it is over barely over a a year since I purchased them, they refused to do anything about it.
12 unusable door sensors at $40 a pop = effed up customer service.
I will never buy anything ever ever ever from Aeon Labs again.
Let’s hope the good people at Vera can do something about this.
I have 15 Aeon Labs DSB04100-ZWUS. I also recently bit the bullet and upgraded my Vera Lite to UI 7. After the upgrade most of my Aeon Labs sensors appear under “failed devices” either with the error message “can’t detect device” or “waiting for wake-up to configure device”. As I had to replace the batteries in all my sensors (it had been about 3 years and I was getting a low battery alert for some) I used the opportunity to attempt to reconfigure the node for each and poll them by manually waking them up by hitting the tamper button three times.
Although it seemed like the attempt to reconfigure the sensors failed at first (I was still getting errors and the states did not change properly) I let them sit for a day and left them alone. Today, it seems as though all the sensors are actually functioning properly now (state changes properly) even though the Vera dashboard still says each sensor has an error. One thing I did notice today is that even though each sensor received a new battery and almost all registered 100%, now several are down to 80% or even 70%. Is the battery reporting for these sensors reliable in Vera now? I always felt as though the battery reporting for these sensors was unreliable as they all lasted about three years on a single battery before I finally had one give out and report the wrong state. I just want to make sure there isn’t some sort of weird battery drain.
So if we were to open up a support ticket with Vera for these Aeon Labs sensors, would they be able to correct the error messages we get for these sensors? For everyone else having problems your sensors are actually not working vs simply working and still reporting an error as mine are?
Hi Agoodman,
i’m having hte same issue with all 5 of my window sensors. i decided against ordering more until this is fixed with my Veraedge.
I have contacted Vera and opened a support ticket. its been a few days since they have contacted me last, but they suggested two things:
-
You can try to run a z-wave network heal using the request below (from the same network) :
192.168.1.100/port_3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:ZWaveNetwork1&action=HealNetwork&BatteryMinutes=60&Node=&StressCycles=2&Configure=0&StartStage=1
(you need to change the IP / Port to match your controller -
Also, you can try to go to Settings, then Z-wave settings and uncheck the ?Use Vera routing instead of Z-Wave (requires 4.5)
i tried both… the heal will eventually fix the units, but they go back into a ‘disconnected’ state.
Me too.
I have 4 of these with the same issue. Would love to learn how to make them work with UI7.
Me three. I’ve got 2 sensors that will configure fine, and within a few days they go rogue and show disconnected.
If this worked in UI5, I would guess this is a software issue with the Vera unit, hopefully something that can be fixed.
This is the first time I’ve been unable to get a z-wave device working correctly with my system and it’s frustrating as heck. 
Interestingly, I looked at the devices with the “Alternate UI to UI7” that you can find on the forums. I armed the device. Hmm, that got me thinking.
I went back to UI7 and added a notification, then I opened the door. Bingo. I received a notification on my phone. Crazy.
It seems I can arm and disarm through the Alternate UI with no complaints. Can’t say that I fully understand what’s going on, but it’s almost usable.
Sure they technically work but they pose a problem when every time you log in your dashboard is alerting you to x number of devices with issues that may not technically have an issue, COME ON vera/Aeon this is sloppy we pay for your products do us a solid, this is still an issue now I see why they are so cheap on amazon, headache city
We’ll, I finally fixed my aeon windows/door sensors in ui7.
The failed device was driving me nuts and I don’t know how many times I’ve done a exclude reinclude and a heal.
I noticed one of my sensors was working normally. This sensor has a newer model number on it.
The fix:
Go to the device
Go to the advanced button
Go to the variables button
In the capabilities (first one from the top) check the box “switch to input type text” then change the first number from 83 to 82.
I then hit the back button and the save button, however I don’t think you have to do this step.
Problem solved
edit: I forgot that I went back and polled the device, however it was already showing it was “normal” and no error on it.
edit2: I spoke to soon. Just checked and those sensors are back to red. The variable has reverted back to 83. I’ve changed it back to 82 and the alerts go away. Just need to figure out how to stop the device from going back to its original variable of 83 and keep the 82.
@bucket23: what exactly is being changed when you change the 83 to an 82 in capabilities?? I tried it on one of my sensors but it didn’t seem to fix my sensor showing up in red as you noted after your edit. The sensors function… but Vera thinks they’re broken 
Wouldn’t have a clue. My other door sensor (same make but a newer version) doesn’t have the issue with “can’t detect device”. I just changed my sensors to the 82 and I also changed the version info (the manufactuererinfo was the same). Hoepefully that will stop the door sensor going back to it’s default capability.
I’ll know by tomorrow morning and post my results.
Wouldn’t have a clue. My other door sensor (same make but a newer version) doesn’t have the issue with “can’t detect device”. I just changed my sensors to the 82 and I also changed the version info (the manufactuererinfo was the same). Hoepefully that will stop the door sensor going back to it’s default capability.
I’ll know by tomorrow morning and post my results.[/quote]
Well, my sensors keep reverting back to their default capabilities. I also changed it to not automatically configure but that didn’t work either.
I did just change my sensors to “armed” and they are no longer flashing red. I’ll know tomorrow if this worked.
Wouldn’t have a clue. My other door sensor (same make but a newer version) doesn’t have the issue with “can’t detect device”. I just changed my sensors to the 82 and I also changed the version info (the manufactuererinfo was the same). Hoepefully that will stop the door sensor going back to it’s default capability.
I’ll know by tomorrow morning and post my results.[/quote]
Well, my sensors keep reverting back to their default capabilities. I also changed it to not automatically configure but that didn’t work either.
I did just change my sensors to “armed” and they are no longer flashing red. I’ll know tomorrow if this worked.[/quote]
That didn’t work either.
It seems that when you make any change, ping the device, wake the device up to get the ping, then all is good for a while. II still have no idea why one of my devices works fine (it has newer make of model on it) than the other ones.
I wish there was a way to change it’s capaibilities to 82 permenantly as that is the only change that I can see from the ones that don’t work to the one that works.
I am having the same problem also. I have the older models. The DSB04100. I have tried everything. They are not only unstable but stay in alarm. They worked for a couple of days and now they do not. I am getting very frustrated. Help please anyone.
I am using a Vera 3 and a Vera Edge. I updated the V3 when I started having problems with a couple of the new z-plus items I purchased. What a mistake. I have gotten both units to work after hours on the phone with the help center. Both units bricked after I was trying to move everything over to the new system. I have spent thousands on equiping the house with switches and I was very proud of the u15 V3 system. I am fearful that going back now would only cause more problems and would make it even more problematic.
The Door sensors of both types will work right after I exclude and then include them, than they die in a day or so. The new U17 update has not helped with any of these pieces of equipment. In fact the newest update has taken the ability to system heal, or pick the z-wave/vera routing option out of our choices. My door sensors and motion sensors are the two best triggers I have. If I can’t get these working, the system is useless. I won’t even start talking about the haphazzardness of the scheduled events.
Somebody has got to have the ability to make these door sensors work with U17. :-\
I am afraid I hold Vera totally responsable for these problems.
it’s been a month and no new updates and I search through but didn’t see any resolution. Is everyone device still not working? Mine has never worked and I kept on thinking it’s me. Glad I found this thread
When I migrated my system from UI5 to UI7 this summer I had 15 of the Aeon Door/Window sensors. At first, it seemed like a disaster – none of the door/window sensors were indicating the correct state, were responding to state changes…etc. I took each sensor, one by one, woke them up and re-configured them and then polled each sensor. Vera was still stating in the alerts area that the devices couldn’t be detected or that it was waiting for them to wake-up to reconfigure them.
I then gave up, obviously very frustrated.
A few days later though, for no apparent reason, all the sensors appeared to miraculously started working again. Then reported the correct state, changed states correctly and worked in scenes. To this day I still have alerts from Vera for all the sensors not being detected, but they do actually work perfectly fine. I can’t really explain why they just started working days after I tried to configure each one… but they do work and I am on UI7.