Add `config.group` to 2nd-gen Hue motion sensors

[ebaauw]

See Discord: the second-generation Hue motion sensors, SML003 and SML004, support direct binding of the client On/Off clusters to devices and/or groups. They'll send On with Timed Off on detecting motion, with a fixed On Time of 5 minutes. They don't seem to use Accept Only When On, even though they have a light sensor.

This PR adds config.group to these sensors. I'm not quite sure whether that's a good idea though. This will result in a broadcast (groupcast) each time motion is detected, which might be challenging on the Zigbee network. As it is known, the Hue motion sensor family expects a Default Response on the Report Attributes. When it doesn't see any, it will broadcast the Report Attributes as fallback (while blinking red), and I'm seeing these broadcasts in the sniffer. Not sure, but I think the On with Timed Off broadcast might be interfering with the (timing off the) Default Response.

Note the first-generation Hue motion sensors, SML001 and SML002, don't seem to support this. Maybe related to the fact that they carry two endpoints, and the client On/Off cluster is on a different endpoint than the server clusters?

[manup]

Good point, while on one side it seems useful and always nice to have configurable group bindings, it indeed might be troublesome in larger networks if the interval is too small?

[SwoopX]

Erik, I'd recommend to leave the modelID and manufacturer name alone here. Just want to stay on the safe side 🙂

[github-actions[bot]]

Hey @ebaauw, thanks for your pull request!

[!TIP] Modified bundles can be downloaded here.

DDF Bundles changes

Modified

• philips/sml003_motion_sensor.json : Hue motion sensor (2022) :heavy_check_mark:

• philips/sml004_motion_sensor.json : Hue outdoor motion sensor (2022) :heavy_check_mark:

Validation

[!TIP] Everything is fine !

_{:clock230: Updated for commit 7515f375781e065b2e0e34a7bee25b0ba75fe998}