Jump to content

Aeotec Door/Window Sensor 6 not showing the barrier node


jec6613

Recommended Posts

Posted

Background: I have three Aeotec Door/Window sensor 6, and the first one included and set up just fine so I picked up the other two.  These are for doors where I really don't have other good options to get a sensor on, as they're exterior sliding doors with shades right in front of them.

The first one worked great, but the subsequent ones do not show the barrier node, only the binary sensor, which by default does nothing, though I have configured it to send on/off at least now.  I've opened and closed these, tried resychronizing, and nothing.

I have a Z stick on the way for a possible firmware update, but it seems this should work on all firmware versions.  Anybody have any ideas?

 

Posted

What's your Firmware/UI? If you aren't on the latest isy firmware, I would upgrade. Also if the firmware and UI don't match, clear your java cache.

It's possible the nodes haven't shown up yet. You can always remove and then add them back in. Be close to the isy while doing so to ensure proper commination during the join process

Posted
1 hour ago, lilyoyo1 said:

What's your Firmware/UI? If you aren't on the latest isy firmware, I would upgrade. Also if the firmware and UI don't match, clear your java cache.

It's possible the nodes haven't shown up yet. You can always remove and then add them back in. Be close to the isy while doing so to ensure proper commination during the join process

5.0.16C for both firmware and UI.

I've excluded and re-included them twice (so 3x joins total) with no change.  When joining, they're about six feet from the ISY.

Posted
35 minutes ago, jec6613 said:

It's possible the nodes haven't shown up yet.

I've experienced a few cases that the nodes can take up to a few hours to populate the AC.

Posted
58 minutes ago, jec6613 said:

5.0.16C for both firmware and UI.

I've excluded and re-included them twice (so 3x joins total) with no change.  When joining, they're about six feet from the ISY.

Try rebooting your isy. Maybe there's something hung up

Posted
17 minutes ago, lilyoyo1 said:

Try rebooting your isy. Maybe there's something hung up

Also tried that yesterday morning before the last re-enroll. :)

Posted
39 minutes ago, dbuss said:

I've experienced a few cases that the nodes can take up to a few hours to populate the AC.

This has been days, unfortunately.

Posted

I did get this sorted: there's a bug in 1.02 firmware, which those two had.  The third had 1.01.  I updated them all to 1.03, and they work great.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...