Skip to content
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

Closed
dsantos21 opened this issue Feb 3, 2021 · 10 comments
Closed

Comments

@dsantos21
Copy link
Contributor

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)

@dsantos21
Copy link
Contributor Author

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.

@kirovilya
Copy link
Contributor

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.

@dsantos21
Copy link
Contributor Author

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 :).

@dsantos21
Copy link
Contributor Author

I really don't know GIT nor how to do those fix, but on the weekend I can try!

@kirovilya
Copy link
Contributor

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.
if your events come, then just replace fz.ZB003X_occupancy with fz.ias_occupancy_alarm_1 in device.js

@dsantos21
Copy link
Contributor Author

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.

@kirovilya
Copy link
Contributor

I used USB power. No motion reported :(

@dsantos21
Copy link
Contributor Author

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.
if your events come, then just replace fz.ZB003X_occupancy with fz.ias_occupancy_alarm_1 in device.js

Yes, it did work too. 😄

@dsantos21
Copy link
Contributor Author

Also, I just noticed that the illuminance exposed value are not calibrated. For example:

"illuminance": 3010 (raw value)
"illuminance_lux": 2 (calibrated value)

The calibrated value is 2. But the value reported back to home assistant is 3010.

@dsantos21
Copy link
Contributor Author

Pull request: #2331

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants