Presense sensors go mad after the last update

🛎️ Get Help
1

Recently (I guess after the last Hub update), my zigbee 2 presense sensors (Samsung) started flapping very frequently.

a sample like :

presence present ilker has arrived DEVICE 2022-04-28 21:57:23.037 MSK
presence not present ilker has departed DEVICE 2022-04-28 21:56:43.371 MSK
presence present ilker has arrived DEVICE 2022-04-28 21:47:44.146 MSK
presence not present ilker has departed DEVICE 2022-04-28 21:47:04.459 MSK
presence present ilker has arrived DEVICE 2022-04-28 21:05:48.954 MSK
presence not present ilker has departed DEVICE 2022-04-28 21:04:49.348 MSK

presence present Filiz has arrived DEVICE 2022-04-28 19:41:59.321 MSK
presence not present Filiz has departed DEVICE 2022-04-28 19:41:38.137 MSK
presence present Filiz has arrived DEVICE 2022-04-28 18:01:31.789 MSK
presence not present Filiz has departed DEVICE 2022-04-28 18:01:30.843 MSK
presence present Filiz has arrived DEVICE 2022-04-28 17:57:29.889 MSK
presence not present Filiz has departed DEVICE 2022-04-28 17:57:29.052 MSK
presence present Filiz has arrived DEVICE 2022-04-28 14:49:41.545 MSK
presence not present Filiz has departed DEVICE 2022-04-28 14:49:20.464 MSK

These 2 sensors are usually in my bag an my wife's bag and the bags are just about 5-6 meters range from the Hub. They do not move much.

is there a problem with Zigbee range ?
What can I do to prevent these flaps ?

2

Is it possible the batteries are low/dying? Swapping them out to see if helps might be a good step to try, regardless (it is often recommended to not trust battery readings as reported by devices).

3 Likes
3

that was the first thing I thought. So I changed the batteries although it shows 90%
But the flap continues

4

any ideas on this ?
(today I put the sensors closer to the hub, but the problem continues)

5

Factory reset and repair (don't delete from Hubitat; since they are Zigbee, they'll be recognized as the same device) and/or just run "Configure"?

2 Likes
6

factory reset what ? HUb ? (I don't want to restore all of my devices just for 2 presence sensors, especially if I don't know the root cause)

just "configure" ?
how's that done ?

7

The sensors. Then pair them back to the hub.

On the device page for each sensor.

And pay careful heed to this advice.

3 Likes
8

factory resetting and "configure" did not help much.
I just changed the timeout value from 2 minutes to 5 minutes. I'll see if it fixes.
But I really don't understand; why it started losing. What did the new Hub update cause ?

9

Which specific update do you think might be related? There wasn't much in the last update related to zigbee... in fact the last couple have been minor bug fixes to address specific issues. I'm not an HE engineer by any chance but I'll go out on a limb and suggest it isn't likely to be the update itself that caused the issue. Have there been any other changes to your hub? Location? New wifi router? Added/channged/removed zigbee devices?

3 Likes
10

But you did play one on TV in the amazing series "Zigbee 911 Emergency Automation."
:wink:

Got to agree with Brad's comments, we've heard a number of times there's been very little done in Zigbee recently.

2 Likes
11

If you really think it's the update (but I don't recall any Zigbee changes recently), use the Diagnostic Tool from Settings > Diagnostic Tool to downgrade to a previous hub platform version, verify that the problem doesn't exist, then verify that it re-appears if upgraded.

2 Likes
12

There have been no zigbee changes for a long time. The timing with a platform update is just coincidental. A better question to ask is, which of your zigbee repeaters/routers are misbehaving?

1 Like
13

No changes on my hub or location recently.
Same wifi router and mesh devices for the past 8 months.
No new zigbee devices.
It started with software update 2.3

14

How do you know that all the zigbee routers/repeaters in your mesh are still functional?

15

I don't.
But I don't need the zigbee mesh for these presence sensors.
I had put them near my hub for the last 4 days. They should be directly connected.

Anyway, yesterday I changed the timeout for these sensors to 5 minutes (from 2)
After that, they did not become "not present"

Weird ?

16

You don't know that. Zigbee end-devices tend to stick to a "favored" router.

Can you post the output from:

http://your_hubitat_ip/hub/zigbee/getChildAndRouteInfo

17

Just to confirm... 2.3 has been out since November of last year. You mentioned "recently" so I just want to make sure this has been going on for 5 months...?

1 Like
18

I mean recently and november means recently to me. I did not have time to deal with this at the beginning so I am just looking at it for the past 3-4 weeks.

1 Like
19

I am adding it below. I don't see the presence sensors here:

Parent child parameters
EzspGetParentChildParametersResponse [childCount=0, parentEui64=0000000000000000, parentNodeId=65535]

Child Data

Neighbor Table Entry
[Ventilator, 14D8], LQI:219, age:7, inCost:5, outCost:0
[Gas Detector, 19E9], LQI:254, age:3, inCost:1, outCost:1
[Living Room Spot One, 2C25], LQI:122, age:5, inCost:7, outCost:1
[3D Printer, 343A], LQI:252, age:3, inCost:3, outCost:1
[Extension Cable, 6921], LQI:254, age:3, inCost:1, outCost:1
[Living Room Spot Two, 6A9D], LQI:249, age:3, inCost:3, outCost:1
[Bedroom Outlet 2, 7130], LQI:205, age:3, inCost:5, outCost:3
[Bathroom Light, 8E69], LQI:254, age:3, inCost:1, outCost:1
[Water Machine, 9B61], LQI:83, age:7, inCost:7, outCost:0
[Balcony Cable, CEDF], LQI:162, age:5, inCost:7, outCost:7
[Kitchen Outlet, F45C], LQI:255, age:3, inCost:1, outCost:1
[Building Door, FBC9], LQI:235, age:3, inCost:5, outCost:1
[Bedroom Outlet 1, FE76], LQI:226, age:3, inCost:5, outCost:1

Route Table Entry
status:Unused
status:Unused
status:Unused
status:Unused
status:Active, age:64, routeRecordState:0, concentratorType:None, [Living Room Spot One, 2C25] via [Extension Cable, 6921]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Extension Cable, 6921] via [Bathroom Light, 8E69]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Bedroom Sensor A, 62B5] via [Gas Detector, 19E9]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Bathroom Sensor, FE98] via [Kitchen Outlet, F45C]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Kid Room Door, 999A] via [Kitchen Outlet, F45C]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Kid Room Motion, A1D2] via [Kitchen Outlet, F45C]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Building Door, FBC9] via [Kitchen Outlet, F45C]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Living Room Sensor 2, 42A2] via [Extension Cable, 6921]
status:Active, age:64, routeRecordState:0, concentratorType:None, [3D Printer, 343A] via [3D Printer, 343A]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Water Machine, 9B61] via [Extension Cable, 6921]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Bedroom Sensor B, 0340] via [Extension Cable, 6921]
status:Unused

20

Because they are not under the "Child Data" section, this means they are not connected directly to your Hubitat, but go through a zigbee repeater. In my experience, device event updates are spotty and can be missed when a repeater malfunctions.

In my opinion, this data confirms my suspicion that you have a malfunctioning repeater that the presence sensors are connected to.

Also tagging @Tony for his more informed opinion.