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

Device support: ROBB Smarrt insert dimmer #1834

Closed
Klumper opened this issue Sep 8, 2019 · 5 comments
Closed

Device support: ROBB Smarrt insert dimmer #1834

Klumper opened this issue Sep 8, 2019 · 5 comments
Labels

Comments

@Klumper
Copy link

Klumper commented Sep 8, 2019

ROBB Smarrt Dimmer

I've tried to connect my new zigbee dimmer to deCONZ and integrate it within HomeAssistant, which looks alot like the iCasa ICZB-IW11D. The connected dimmer does not show up within the Phoscon App but is visible with vnc.

It seems like my other sensors are connected to this dimmer and not directly to the Conbee II stick I use, which is why they don't work properly. The '/lights' api endpoint also returns an empty object.

According to the manual, the device supports the following:
Input Clusters

  • 0x0000: Basic
  • 0x0003: Identify
  • 0x0004: Groups
  • 0x0005: Scenes
  • 0x0006: On/off
  • 0x0008: Level Control
  • 0x0b05: Diagnostics

Output Clusters

  • 0x0019: OTA

Device information

Name: HUE insert dimmer Zigbee ROBB Smarrt
SKU: ROB_200-004-0
EAN: 7439647744702
Bought here
English manual
Dutch manual

Cluster Info

ROBB Smarrt insert dimmer - Cluster Info

Node Info

ROBB Smarrt insert dimmer - Node Info

@ebaauw
Copy link
Collaborator

ebaauw commented Sep 8, 2019

deCONZ hasn't read the descriptors. Try to select Read Node Descriptor and Read Simple Descriptor(s) from the dropdown menu. The second dropdown menu should appear, with the endpoints and clusters.

Next, open the network from the old web app, or search for devices from Phoscon. Then in the Node Info panel, read the Basic cluster attributes. That should trigger the creation of the /lights resource.

@Smanar
Copy link
Collaborator

Smanar commented Sep 8, 2019

Next, open the network from the old web app, or search for devices from Phoscon. Then in the Node Info panel, read the Basic cluster attributes. That should trigger the creation of the /lights resource.

BTW, was an old question I have.
If I want to test the inclusion in the API, without de-paring/re-pairing a device. I can just delete it from the API, and use this trick to re-create them ? So I can test code change in the API, without take out my device (realy hard to include) ?

@Klumper
Copy link
Author

Klumper commented Sep 8, 2019

@ebaauw Thanks for the quick reply! Looks like the Read Node Descriptor remains checked but the Read Simple Descriptor(s) option unchecks instantly. I've tried searching for new devices after selecting the Read Node Descriptor option within the old web app without result.

@ebaauw
Copy link
Collaborator

ebaauw commented Sep 8, 2019

@Klumper
You might need to toggle the squares a couple of times, a few seconds apart. Did the second dropdown appear? You need to read the Basic cluster attributes to trigger the creation of the resource.

@Smanar
Yes. Sometimes not all resources are deleted, though. In that case, I typically remove them from the database using sqlitebrowser. Make sure to close deCONZ and make a backup before hacking the database.

@stale
Copy link

stale bot commented Jan 6, 2020

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.

@stale stale bot added the stale label Jan 6, 2020
@stale stale bot closed this as completed Jan 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants