Aeon Labs Recessed Door Sensor 5th gen


(Brooke) #1

I’ve been struggling to keep my new Aeon labs recessed door sensor working. I have tried multiple device types (including standard zwave open closed, community device types specifically for the recessed sensor, and still having some trouble. The sensor worked fine for about a day when I went back to the defaults and let it pick a device type. Then it stopped reporting anything.

Now I have tried readding it to my hub, and get the following error in my log:

fc5ba14d-b2eb-4acb-979a-f354da4717c9 7:30:45 PM: debug parsed ‘Err 106: ZW secure inclusion failed’ to [descriptionText:This sensor failed to complete the network security key exchange. If you are unable to control it via SmartThings, you must remove it from your network and add it again., eventType:ALERT, name:secureInclusion, value:failed, isStateChange:true, displayed:true, linkText:Contact Sensor]
fc5ba14d-b2eb-4acb-979a-f354da4717c9 7:30:32 PM: error java.lang.NullPointerException: Cannot invoke method leftShift() on null object @ line 208
fc5ba14d-b2eb-4acb-979a-f354da4717c9 7:30:32 PM: debug parsed 'zw device: 09, command: 7205, payload: 00 86 01 02 00 59 ’ to [[descriptionText:Z-Wave Door/Window Sensor MSR: 0086-0102-0059, isStateChange:false, displayed:false, linkText:Z-Wave Door/Window Sensor], 9881008002]
fc5ba14d-b2eb-4acb-979a-f354da4717c9 7:30:32 PM: debug msr: 0086-0102-0059
fc5ba14d-b2eb-4acb-979a-f354da4717c9 7:30:30 PM: debug parsed ‘updated’ to null

I have tried re-adding it several times and keep getting the same thing. I had this trouble initially but it resolved itself when I moved the sensor closer to my hub. No luck with this on the reinstall.

Any ideas? Do I have a bad sensor?


#2

The GEN five sensor is now an officially supported device, so you should be able to get help from support@smartthings.com

One of the things that’s different about this device is that it’s Zwave plus and it’s using security. That means when you pair it, it must be very close to the hub, sometimes even within about 4 inches, or the security Key will not be exchanged.

So, yeah, probably the first thing support is going to tell you is to try to pair it again at a very close distance.


(Brooke) #3

Thanks. I’ll try that again!


(Brooke) #4

Still no luck. Have sent a support ticket in. Anything else I can try? I tried adding it to my hub with the sensor sitting right on top of my hub…same error.


(Tim Slagle) #5

Try doing a “general device exlusion” through the app. It may have been added to a network before and not properly excluded.


(Brooke) #6

Tried that but still no luck. Here is the log which is showing an error: error java.lang.NullPointerException: Cannot invoke method leftShift() on null object @ line 208

8bfbcf71-7b54-4763-9169-532cd981b666 6:12:28 PM: debug parsed ‘Err 106: ZW secure inclusion failed’ to [descriptionText:This sensor failed to complete the network security key exchange. If you are unable to control it via SmartThings, you must remove it from your network and add it again., eventType:ALERT, name:secureInclusion, value:failed, isStateChange:true, displayed:true, linkText:Z-Wave Door/Window Sensor]
8bfbcf71-7b54-4763-9169-532cd981b666 6:12:14 PM: error java.lang.NullPointerException: Cannot invoke method leftShift() on null object @ line 208
8bfbcf71-7b54-4763-9169-532cd981b666 6:12:14 PM: debug parsed 'zw device: 0D, command: 7205, payload: 00 86 01 02 00 59 ’ to [[descriptionText:Z-Wave Door/Window Sensor MSR: 0086-0102-0059, isStateChange:false, displayed:false, linkText:Z-Wave Door/Window Sensor], 9881008002]
8bfbcf71-7b54-4763-9169-532cd981b666 6:12:14 PM: debug msr: 0086-0102-0059
8bfbcf71-7b54-4763-9169-532cd981b666 6:12:13 PM: debug parsed ‘updated’ to null


(Tim Slagle) #7

Did it join but just doesn’t work, or it’s not joining at all?


(Brooke) #8

It does join, but gives the security error and then doesn’t report anything.


(Tim Slagle) #9

What device type did it grab in the IDE?


(Brooke) #10

Z-Wave Door/Window Sensor but I get the same error when using the community device type.


#11

There’s an official device type for this now, that should work. What did support say?


(Tim Slagle) #12

What JD said. Try the official device type


(Brooke) #13

Still waiting to hear back from Support. They are checking on the official integration. Tried the official device type (via the app) and still getting the same error:
This sensor failed to complete the network security key exchange. If you are unable to control it via SmartThings, you must remove it from your network and add it again


(Brooke) #14

Looks like it might be a bad sensor. Let’s hope a new one works!


(David) #15

when will the Gen5 be able to read battery %? I am using the new G5 app


(Joe) #16

unless there is a large batch of bad sensors, there’s some minor incompatibility that causes this. Out of 7 Aeon recessed door sensors gen 5, I’ve sent 3 back for new, with no change in key exchange behavior in smart things. All 10 sensors had an issue with smart things hub, and are unreliable in communication. The one thing I have noticed is that Aeon uses the official US 908.42mhz frequency. Which is supposed to be compatible with the 908.40mhz that smart things and GE/Jasco switches use. The FSK bandwidth is larger than the center frequency difference.


(Mark) #17

I’m having the same problem, it joins but does not function, event log reports:

secure inclusion failed

Anyone have a solution or should I return it?


(Corey) #18

Has there been any resolution on this? I just came across this sensor on Amazon and bought it before searching compatibility issues. I am having the same issue as described above… I am using the original Smartthings hub… does that make a difference?


(Greg) #19

I have several of these. a few of mine had to be paired a few times to work properly. I use this DTH - the only issue I have is the battery reporting is not accurate.