-
Notifications
You must be signed in to change notification settings - Fork 506
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
Centralite 3328-G and Motion Sensor-A integration request #1053
Comments
Please provide the info as described in the Wiki |
The Motion Sensor-A is fixed now and will be fully supported with 2.05.57. 3328-G should work too, but needs to be tested. |
Will test them in the next couple of days and report, thank you! |
I successfully tested this with Osram Smart+ Motion Sensor and release 2.05.57. The support is much appreciated. When there is continuous motion in front of the sensor the motion state of the sensor (as reported in phoscon app under sensors) goes back to 'none' after rather exactly 60 seconds, even if motion is still occurring. This happens on both of my devices. Is there any information I can supply to narrow down the problem? |
…resource - Fix two ZHAPresence resources were created instead of one with unqiqueid ...-01-0500 - Delete invalid entry from database Issue #1053
* Prevent 'presence' becomes false on constant motion * Use IAS zone status attribute reporting with interval < config.duration * Use battery voltage for config.battery (battery percentage remaining not supported) Issue #1053
Retested this with 2.05.59. Battery status is now reported correctly (binary). I've also been able to validate the fix for continuous motion. I've noticed that the sensor irregularly falls back to "no motion" despite the presence of motion after 3-5 minutes, but haven't figured out a pattern yet. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I have two Centralite 3328-G sensors connected and can access them via the REST API. However, they don't show up in the webapp. I suspect this might be due to the swversion field containing garbage. Both sensors don't report their swversion correctly. Could we ignore invalid swversion data or make the webapp cope with it? Sensors output from REST API:
|
https://www.amazon.com/gp/product/B0713STYJQ/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1
https://www.amazon.com/gp/product/B01LXPGXQ1/ref=oh_aui_detailpage_o00_s01?ie=UTF8&psc=1
Can connect both to the deCONZ app, and can see temperature readings there, but not recognized in the webapp (and obviously REST API) sensors list.
Can I help adding them to the supported device list?
I have both on hand.
Is there any resources available to start working on them?
Thank you
The text was updated successfully, but these errors were encountered: