You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question regarding Philips Hue Motion Sensor (9290030675). I'm trying to understand how reporting works, but having issues with it.
I'm using Z2M v2.
I have following reporting configuration, which currently should be default:
I enabled Info Logging and inspected the logs. When I put my hand in front of the sensor, there is an immediate topic send, with occupancy set to true. Then there is another, which I assume is the illuminancy, which triggered it. About 5-6 seconds later it spammed my console with 9 topics, but there was no change. And occording to what I understand about the reporting, only occupied could have reported something, due the min values.
To test that, I removed every reporting section but the occupancy. Tried it again and it just worked normal. One topic when I hold my hand in front of the sensor and after about 10 seconds the occupancy: false topic.
I then reconfigured the illuminancy report and it seemed to work at first, but quickly it goes back to the odd behavior.
I reconnected the device (removed it completely and interviewed it again) and suddenly it seemed to work. After changing some settings, like illuminancy calibration, it started acting weird again.
I have a screenshot of this here:
Could someone explain to me how this works (and why) and if this is the expected behavior?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi everyone,
I have a question regarding Philips Hue Motion Sensor (9290030675). I'm trying to understand how reporting works, but having issues with it.
I'm using Z2M v2.
I have following reporting configuration, which currently should be default:
I enabled Info Logging and inspected the logs. When I put my hand in front of the sensor, there is an immediate topic send, with occupancy set to true. Then there is another, which I assume is the illuminancy, which triggered it. About 5-6 seconds later it spammed my console with 9 topics, but there was no change. And occording to what I understand about the reporting, only occupied could have reported something, due the min values.
To test that, I removed every reporting section but the occupancy. Tried it again and it just worked normal. One topic when I hold my hand in front of the sensor and after about 10 seconds the occupancy: false topic.
I then reconfigured the illuminancy report and it seemed to work at first, but quickly it goes back to the odd behavior.
I reconnected the device (removed it completely and interviewed it again) and suddenly it seemed to work. After changing some settings, like illuminancy calibration, it started acting weird again.
I have a screenshot of this here:
Could someone explain to me how this works (and why) and if this is the expected behavior?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions