Confusing Error

🛎️ Get Help Devices
1

Noticed an error occuring several times in sucession in the logs:

sys:12024-09-25 01:09:12.887 PMerrorThe device join failed and was not added to your network. Make sure the device is compatible before trying to pair the device again.

Had no idea what it meant. Next day discovered a Zigbee contact sensor quit working. Had to reset and repair that device to get it back working.

So I am assuming the error referred to that? But why would it be trying to join on it's own?

Just trying to figure out what it meant.

3

So the device is telling the hub it has had enough and is leaving. So why can’t the error message indicate that rather than it didn’t join?

4

What make/model contact sensor, and using which driver?

1 Like
5

Third Reality. Generic Zigbee Contact Sensor, no temp.

The fact that it dropped off doesn't worry too much, those things happen. Just would like a better explained error message. Or does the device actually try on it's own to reconnect? If that's the case then I guess the error message is correct.

7

IIRC Rick has/uses a bunch of Third Reality stuff. Or am I mis-remembering?
@rlithgow1 ?

8

I have a couple of the zigbee night lights and one of the matter night lights

1 Like
9

Ah, my weak memory, must have been someone else who I was thinking of that was "all-in" on Third Reality stuff.

10

Getting Old Baby Boomer GIF by MOODMAN

1 Like
11

To be honest that's more me than you...

2 Likes
12

I have several Third Reality. A number of contact sensors and motion detection. Also a couple push buttons. Have not had any issues till this one.

13

Possibly the pairing didn't go well overall. I have had some Zigbee devices pair incompletely and only report a subset of capabilities. Remove/Re-pair and connects/reports normally.

14

Been working fine for a couple weeks before taking a vacation.

15

That all you're going to do, confuse us w/facts?! :wink:

If so, then no explanation other than some sort of Zigbee "oops" occurred that caused the device to jump ship, resulting in the error message that really hasn't been fully understood/explained yet, as I read the other topics where this has been discussed. Seems to be a relatively rare event, so this may remain a mystery...

Fat lot of help I am, right? :man_shrugging:

16

I am Soooo confused.... :crazy_face:

17

I also received a blast of 10 of those messages last week.
Just checked and found a Ecolink 4655BCO-R contact sensor had a dead battery.

18

I don't blame you. It is confusing. That error has to do with certain 3.0 devices that can't exchange security keys with the hub and can't join. Some devices may pair, and will work fine, but if for any reason they drop off the network and can't rejoin, you will see that error. Our engineers have been working with Silicon Labs to find a solution, and we hope to have this issue resolved in the near future, though I don't have a time-frame when that may happen.

4 Likes
19

Thanks for the explanation.