HUE Motion SML001 missing occupancy_timeout

[tore1980]

The problem

Z2M has implemented occupancy_timeout settings / configuration of HUE Motion SML001.
Occupancy_timeout is missing in ZHA

Z2M:

ZHA:

What version of Home Assistant Core has the issue?

2023.10.3

What was the last working version of Home Assistant Core?

2023.10.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[TheJulianJES]

Yeah, for now, you can change it through the clusters UI:
Open the device page -> click the three dots on the left -> Manage Zigbee device -> Cluster tab -> select PhilipsOccupancySensing cluster -> select pir_o_to_u_delay, then enter whatever value you want in the first field (default is 0, but defaults to 10 second timeout IIRC). Leave the lower field empty (always!).
Then, press "write attribute". The sensor should now have the new timeout.

I probably still have a branch where I added this as a config entity, but at the time, there was an issue where the sensors reports this attribute as an "unsupported attribute" initially. zigpy wasn't able to handle this in earlier versions, but it can now. (when an unsupported attribute becomes supported)
The initialization for the attribute might still have to be worked around (could be set to the default value of 0 using the quirk, but that's not ideal).
But yeah, this should be added eventually.

[tore1980]

Thank you for great answer. I hope this going to be added some day.