I have had frustrating and unpredictable behaviour with all three drivers, I am back with frient 1.5 driver and it is creating history very infrequently if at all. It’s as if a reset is not fully resetting the sensor.
1 Like
That’s weird but I think I’ve seen that before on a different device.
When I have the physical device I can do some investigation. Looks like I have to turn off the reportable change completely:
Behavior: The device’s technical manual specifies that the Reportable Change should be disabled (0xFFFF), and reporting should be based solely on a time interval (max reporting interval every 10 minutes).
Can’t do much without logs.
Just received the device, installed my driver, added the device, set the max reporting interval to 30 seconds, then 60 seconds and… it works as expected:
aroedl@hydra ~ $ grep -i "event.*illu" frient_log1
2025-11-03T11:29:21.082213160Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":37}}
2025-11-03T11:29:51.112795872Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":62}}
2025-11-03T11:30:21.132094792Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":58}}
2025-11-03T11:30:23.650670626Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":61}}
2025-11-03T11:31:24.148546187Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":61}}
2025-11-03T11:32:24.181413111Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":63}}
2025-11-03T11:33:24.232267576Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":62}}
2025-11-03T11:34:06.199050539Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":4}}
2025-11-03T11:35:06.296906351Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":5}}
2025-11-03T11:36:06.336834983Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":5}}
2025-11-03T11:37:06.376582574Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":5}}
Another test with max reporting interval of 120 seconds and the device reports every two minutes:
2025-11-03T11:44:40.361491608Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":5}}
2025-11-03T11:46:40.784030580Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":5}}
2025-11-03T11:48:40.872307344Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":5}}
2025-11-03T11:50:40.935017983Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":5}}
2025-11-03T11:52:41.525657213Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":5}}
Testing the lowest maximum reporting interval of 10 seconds:
2025-11-03T12:02:01.371962312Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":3}}
2025-11-03T12:02:11.373886771Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":3}}
2025-11-03T12:02:21.408954272Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":3}}
2025-11-03T12:02:31.350717065Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":4}}
2025-11-03T12:02:41.462326775Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":5}}
2025-11-03T12:02:51.452403776Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":3}}
2025-11-03T12:03:01.462368641Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":3}}
2025-11-03T12:03:11.496727767Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":3}}
2025-11-03T12:03:21.596118060Z INFO Frient Motion Sensor (AR) <ZigbeeDevice: 2181cd2e-f31f-4f55-9b74-cf08f6e6c8c2 [0x750E] (frient Motion Sensor Pro)> emitting event: {"attribute_id":"illuminance","capability_id":"illuminanceMeasurement","component_id":"main","state":{"value":3}}
Seems to be the case. It stops reporting after a while when there’s no motion and starts reporting again at the set max interval as soon as there’s motion.
@languageservicesco : solution: replace this sensor with an Aqara FP2.
1 Like
I now know what the German is for Illuminance. I might need that one day!
I prefer to at least make companies recognise that their products are rubbish, so I still go back to my original post, which was trying to find a contact possibility for Frient. I thought Aqara needed its own hub, or has Matter solved that? I really cannot be bothered with yet another hub. I see Ikea has a very simple movement sensor out for £7 (or maybe it was dollars). It looks like it would possibly do the job, better than the Frient sensor anyway. I will then try and find a role for the Frient that relies less on the actual illuminance and just run automations based on night and day times, for example. I also have a Frient smoke alarm, and this whole thing makes me wonder whether I should just chuck it away.
1 Like
The Aqara P2 motion sensor is Matter over Thread so as long as you can add Thread devices to SmartThings you’re good to go.
It has illuminance sensor independent of the motion, or that’s what Aqara announces, I’ve not tested it.
Recent firmware updates enable the hold time and sensitivity, but SmartThings cannot update it and the drivers do not support those features.
Edit: And the FP2 has a local integration with SmartThings, even if it’s not Matter. No Aqara hub required either.
1 Like
I’ve quite liked the look of Aqara in the post, so if it works directly with Smartthings, I might give it a go. So, what can be set for the P2, does anyone know? For it to work for me, I need to be able to set the illuminance level quite low for triggering the automation (it was at 7 for the Frient). I need it to switch off 1 minute after the last movement detection. The trigger requires frequent checking of the illuminance, preferably around 2 minutes maximum. Is there anywhere I can check that?
You can’t set anything in SmartThings so either the defaults work for you or not. The default time is 1 minute so that will be fine. I don’t know about the illuminance and didn’t find any data. Matter devices are expected to be smart and report when it makes sense instead of just reporting every fixed interval, but that depends on the implementation of the device.
The Aqara FP2 reports illuminance independently from the other sensors at a high rate - several times per minute.
You can’t set anything in SmartThings so either the defaults work for you or not. The default time is 1 minute so that will be fine. I don’t know about the illuminance and didn’t find any data. Matter devices are expected to be smart and report when it makes sense instead of just reporting every fixed interval, but that depends on the implementation of the device.
That’s pointless then. Thanks for the information. I’ve been burned by Frient’s poor implementation, I shan’t do that again.
Don’t tell anyone else but I got a reply from info@frient.com
Thanks Andrew. I will report back if I get an answer too.