-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fantem MultiSensor ZB003-X occupancy not working (follow up to issue #2071) #2195
Comments
I'm really new to this, not sure if that is the right way to do. Please, let me know if this should be canceled. |
I, too, this sensor did not send an occupation, so I had to do it as it is now. I will check your solution later. |
Also, if you would like to include the tamper detection, it would be something like this (bit 3 of zone status): tamper: (zoneStatus & 4) > 0, I just tested it with an online expression tester, with the zoneStatus values I got in debug. Tried a few combinations, worked as expected (for me, at least :). |
I really don't know GIT nor how to do those fix, but on the weekend I can try! |
I think my sensor is broken ... I have never received an occupancy event, but the tamper was received. therefore, I considered that they are confused here. |
Are you using some battery? Try using USB power. One of my sensors was erratic too, but it was caused by bad batteries. Motion was not reported or reported without real motion. |
I used USB power. No motion reported :( |
Yes, it did work too. 😄 |
Also, I just noticed that the illuminance exposed value are not calibrated. For example: "illuminance": 3010 (raw value) The calibrated value is 2. But the value reported back to home assistant is 3010. |
Pull request: #2331 |
Hi! I've just updated the issue #2071 with some comments about occupancy not working. After some debug I changed my local instance and now it's working (without the bitwase operator):
occupancy: (zoneStatus & 1) > 0,
Originally posted by @dsantos21 in #2072 (comment)
The text was updated successfully, but these errors were encountered: