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

Support for Orvibo Contact Sensor - Model no SM11 #4403

Closed
ashar38 opened this issue Feb 11, 2021 · 2 comments · Fixed by #4465
Closed

Support for Orvibo Contact Sensor - Model no SM11 #4403

ashar38 opened this issue Feb 11, 2021 · 2 comments · Fixed by #4465

Comments

@ashar38
Copy link

ashar38 commented Feb 11, 2021

Hello team,

Going through the old issues I noticed there was a thread open to add support for Orvibo door/window sensors, but looks like that thread went cold. Hence, I am starting a new issue hoping that support could be added for this device in one of the future firmwares.
I have tried to add as much info as possible from what I see through Deconz. But please let me know if I can add some more.

Device

  • Product name: LivingWise / Orvibo Contact Sensor
  • Manufacturer: ORVIBO
  • Model identifier: e70f96b3773a4c9283c6862dbafb6a99
  • Device type : Sensor

Screenshots

Required screenshots:
Node Info.
image

Clusters:
Basic:
image

Identity:
image

IAS Zone:
image

IAZ Zone: cont'd
image

Power Config:
image

@SwoopX
Copy link
Collaborator

SwoopX commented Feb 22, 2021

When support has been added, you need to enter sensor search in Phoscon and pair the device. However, you also need to keep an eye on deconz GUI for the device to show up, as the manufacturer name and model ID are not read automatically. When it appears in deconz GUI, you need to read the basic cluster's attributes while sensor search is still running (which is the case even when Phoscon already issued the greenish success message) for the sensor resource to be created.

@ashar38
Copy link
Author

ashar38 commented Mar 1, 2021

When support has been added, you need to enter sensor search in Phoscon and pair the device. However, you also need to keep an eye on deconz GUI for the device to show up, as the manufacturer name and model ID are not read automatically. When it appears in deconz GUI, you need to read the basic cluster's attributes while sensor search is still running (which is the case even when Phoscon already issued the greenish success message) for the sensor resource to be created.

Thank you. Much appreciated. I will wait for the next release and confirm if everything works well.

@SwoopX SwoopX linked a pull request Mar 3, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants