Who is throttling messages from an Aqara FP2 presence detector?
rhuitl opened this issue · comments
Hello, just a quick question, and then you can probably close this issue right away: is there any throttling or scheduling going on when messages from an IP device are received?
I left the polling intervals as they are (30s and 60s), but they're not relevant here.
I see the following debug output when I move from one of the zones to an immediately adjacent zone. The presence messages and the corresponding brightness value changes (due to my light automation) are received with ca. 1 second in between them. I'm wondering if this is the sensor's fault or a problem in homekit-controller.
2023-05-18 20:49:03.986 - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F IP device subscription event received: {"characteristics":[{"aid":1,"iid":2702,"value":0}]}
2023-05-18 20:49:03.987 - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F Set Values to ioBroker: [{"aid":1,"iid":2702,"value":0}]
2023-05-18 20:49:03.991 - debug: homekit-controller.0 (17479) state homekit-controller.0.IP-CF:F8:39:2A:1E:3F.1.sensor-occupancy-2700.occupancy-detected changed: 0 (ack = true)
2023-05-18 20:49:04.977 - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F IP device subscription event received: {"characteristics":[{"aid":1,"iid":2674,"value":17},{"aid":1,"iid":2706,"value":1}]}
2023-05-18 20:49:04.978 - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F Set Values to ioBroker: [{"aid":1,"iid":2674,"value":17},{"aid":1,"iid":2706,"value":1}]
2023-05-18 20:49:04.983 - debug: homekit-controller.0 (17479) state homekit-controller.0.IP-CF:F8:39:2A:1E:3F.1.sensor-light-2672.light-level-current changed: 17 (ack = true)
2023-05-18 20:49:04.985 - debug: homekit-controller.0 (17479) state homekit-controller.0.IP-CF:F8:39:2A:1E:3F.1.sensor-occupancy-2704.occupancy-detected changed: 1 (ack = true)
2023-05-18 20:49:05.975 - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F IP device subscription event received: {"characteristics":[{"aid":1,"iid":2674,"value":5}]}
2023-05-18 20:49:05.976 - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F Set Values to ioBroker: [{"aid":1,"iid":2674,"value":5}]
2023-05-18 20:49:05.982 - debug: homekit-controller.0 (17479) state homekit-controller.0.IP-CF:F8:39:2A:1E:3F.1.sensor-light-2672.light-level-current changed: 5 (ack = true)
2023-05-18 20:49:06.976 - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F IP device subscription event received: {"characteristics":[{"aid":1,"iid":2674,"value":58}]}
2023-05-18 20:49:06.977 - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F Set Values to ioBroker: [{"aid":1,"iid":2674,"value":58}]
2023-05-18 20:49:06.981 - debug: homekit-controller.0 (17479) state homekit-controller.0.IP-CF:F8:39:2A:1E:3F.1.sensor-light-2672.light-level-current changed: 58 (ack = true)
We can only subscribe to data updates ... how often and when they are sent is up to the device. It seems that the device collects changes and sent them then together minimum with 1s pause