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

Prolight Smart Remote Control #5551

Closed
jhmgoossens opened this issue Dec 3, 2021 · 5 comments
Closed

Prolight Smart Remote Control #5551

jhmgoossens opened this issue Dec 3, 2021 · 5 comments

Comments

@jhmgoossens
Copy link

Device

  • Product name: Prolight Smart Remote Control
  • Manufacturer: Prolight
  • Model identifier: PROLIGHT REMOTE CONTROL
  • Device type : Remote
  • Link : Prolight Smart Remote Control

Screenshots

Node Info

image

Basic

image

Power Configuration

image

Identify

image

Diagnostics

image

OTAU

image

@github-actions
Copy link

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Dec 25, 2021
@jhmgoossens
Copy link
Author

I tried to have a go at this myself, looking at PR #5067 and its changed files as an example.
I got as far as making and deploying my updated plugin, and seeing my DBG_Printfs in the Debug view--very satisfying. But I couldn't get bindings.cpp checkSensorBindingsForAttributeReporting to recognize the remote as Supported. I guess it's not that easy :-)

Is there a guide to help with implementing device support?

@github-actions github-actions bot removed the stale label Dec 29, 2021
@devilke
Copy link

devilke commented Jan 14, 2022

I think I found the original manufacturer of this device, including the zigbee compliance documentation.
https://zigbeealliance.org/zigbee_products/leedarson_5keys-cct-remote-control/

there might be some useful info in there

@github-actions
Copy link

github-actions bot commented Feb 5, 2022

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Feb 5, 2022
@github-actions
Copy link

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

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

No branches or pull requests

2 participants