Philips motion sensors stopped reporting "Occupancy"

[vikdb]

What happened?

I have multiple Philips motion sensors both indoor 9290030675 and outdoor 9290030674. But after the 2.6.2 2 devices stoped reporting the occupancy while all other attributes work fine.. Also i havo other 9290030674/9290030675 sensors in the home and they still work.

Is there some kind of threshold on LQI for motion? Because they are a bit further in the house. (LQI less then 70)

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.6.2

Adapter firmware version

20230507

Adapter

ZZH!

Setup

Home assistant Add On

Device database.db entry

No response

Debug log

No response

[vikdb]

I tested my LQI theory and indeed when i move the sensor closer it also starts to report motion ( apart from temperaturen / lux which always works).

So is there a new thing were they stop reporting stuff when LQI is to low?

[Zarn-Smith]

Possibly helpful but possibly not...

I am also running an Outdoor (9290030674). LQI averages under 40 and am not suffering the problem you are facing. (Still reporting occupancy without issue).

Zigbee2MQTT version is the same: 2.6.2, but I am using a zstack adapter.

[vikdb]

Ahah good to know!

I do have a ZZH! adapater, it usses the ZStack3x0 coordinator firmware. Which is a bit outdated though..

[chris-1243]

@vikdb If you need to move your device closer to your coordinator to have it to work correctly, it means the link is to weak. You should run a network map and check to which router / coordinator your device is connected to. Add a router in between to relay the signal. Check the documentation or the whole section on network range and stability.

LQI shown on Z2M dashboard is a good start but it depends on the coordinator firmware and how those values are interpreted. You may run the exact same network, one based on zstack and a second based on ember and you would be surprised by the the LQI difference shown just due to the implementation in the firmware. Some deconz firmware always show really high LQI due to a bug... A network map is more accurate and will provide you more information.

[vikdb]

Thnx @chris-1243 I'll have a look at the documentation you've provided.

My main problem with this theory is that it has always worked before the update and now all of the sudden 2 motion devices partly fail. not completely but just the motion attribute.

If i got some more time i'll update my coordinator.

[chris-1243]

Well, It might be related to interference as well. New Z2M versions seem more impacted by this phenomenon. Wifi and Zigbee are on the same 2.4 GHz band. You may have a look at this also.

This update might have revealed a small failure in your network.

If i got some more time i'll update my coordinator.

20230507 is using a broken SDK. TI had some issues with the SDK used in this firmware. It took time to Koenkk, lot of effort and feedback from the community to get rid of this problem. I would suggest to update...

Do one change and then wait to see the result. It is then easier to debug if anything does not go well.

[cd861]

I have the same problem with 2x SLM004 aka 9290030674 with fw 2.53.6 - 20210830 after upgrading to 2.6.2.

What I tried so far which didn't help:

• Reverting back to 2.6.1
• Using different coordinator fw : both Zstack 3x0, 20230507 and 20240710 with a SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P (CC2652P based)
• Removing/repairing device
• Bringing device close to the coordinator

What somewhat works is to set motion sensitivity to "high". But for me this is not useable as it now triggers way too often.

Im currently trying to work around this by setting motion sensitive to "really low" in the HUE app and then repairing in Z2M afterwards and not touching any configuration option.

[lennvilardi]

I can confirm the same issue, but with a different Hue model.

I’m using Philips Hue SML003 (9290030675), firmware 2.53.6 – 20210830, and since upgrading to Zigbee2MQTT 2.6.2/2.6.3, motion detection only works if I set the sensitivity to High. On Medium or Low, motion is never detected.

Additional information:

• Model: SML003 – Signify Netherlands B.V.
• Firmware: 2.53.6 (20210830)
• Zigbee2MQTT: 2.6.3
• Zigbee-herdsman-converters: 25.59.0
• zigbee-herdsman: 6.3.2
• Coordinator: ZStack3x0 – 20240716 (Sonoff ZBDongle-P, CC2652P)
• LQI is good (~136)
• Temperature and illuminance update correctly
• Re-pairing, coordinator FW changes, distance to coordinator, etc. did not fix it

So like others reported: Only “High” motion sensitivity works after this update. Medium and Low don’t trigger any motion at all.

Thanks for looking into it.

[mckochan]

Just to help others troubleshoot: My outdoor hue sensor required repairing to get it to work after the update. For a time it was totally unresponsive and could not remove it from z2mqtt, then I pressed the setup button for 10 sec and then again to repair, it came back but was stuck on occupied, but other values could update. I could then remove it and add it back and it works again (motion on medium works).

[esguo]

Same motion sensor model as @lennvilardi, on a different Sonoff model dongle... also confirming the same.

Updated to the latest Zigbee2MQTT. Using EmberZNet coordinator, on Medium or Low, motion is never detected. Remove and re-pair did not change anything.

Model: SML003 – Signify Netherlands B.V. (9290030675) Firmware: 2.77.35 (20240618) Zigbee2MQTT: 2.7.1 Zigbee-herdsman-converters: 25.83.1 zigbee-herdsman: 7.0.4 Coordinator: EmberZNet – 8.0.2 (Sonoff ZBDongle-E) LQI is good (~152) Temperature and illuminance update correctly

[vandenberghev]

I'm having the same issue with several SML004: no occupancy reporting unless sensitivity >= high [EDIT]or sensitivity is empty; after re-pairing it works as long as sentitivity is empty - once set to low/medium, it stops reporting again[/EDIT]. Re-interviewing, re-configuring, re-pairing, etc. don't resolve the issue. Nothing seems to have changed in the device's converter since early 2025, so I'm guessing the issue is probably device firmware related?

I have a single SML004 that is still on firmware 2.53.6 (20210830) that DOES report occupancy on low, while the others that stopped reporting are on 2.77.35 (20240618); I very recently upgraded Z2M from 2.0 to 2.7.2 so only just got the OTA capability for these devices... But the firmware difference might be a coincidence; the 2 'broken' devices were already in use for 1-2 years, and the 'working' one (with the older firmware) was a spare I just started using.