-
Notifications
You must be signed in to change notification settings - Fork 41
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
Custom Command Service not working properly on lampsmart_pro v3 ? #27
Comments
It seems that only commands that are already supported in code can be used. This feature is useful for sending arbitrary argument values, not arbitrary (unsupported) commands. However, I agree that allowing arbitrary commands could be useful for extending support for additional devices/features. If you feel like adding such a capability via a pull request, that could be great! |
Thanks for the quick reply ! I tried switching to It seems like this service was implemented by @NicoIIT in #17, I'll try and see if a later commit breaks it ! (as a side note, in case it might be interesting to someone else, I was able to find that the RGB command on my device is 0x22 with args 1..3 as red, green and blue) |
Hi guys, I think I broke that in one of the last changes included in #17. Let me check if I repaired it already in my EDIT: it should work with the
|
Merci copain t'es trop fort c: Everything works great, I just had to explicitly add Here's my ESPHome configuration:
And in my
I also found commands to enable (0x1E) and disable (0x1F) a very ugly RGB animation, in case anyone wants to hurt their eyes ! I'll leave this issue open because it still exists on this repo |
Hi there, and thank you immensely for your work !
I have random Amazon ceiling lights that I'm able to control perfectly with this component, and lately I've been looking into adding RGB functionality through the Custom Command Service + a template light (I'll share the commands and args if this ends up working, if you want to add this to the component directly).
Only problem is, whichever parameters I use for the service call, I always get the same error in my node's logs:
[W][ble_adv_controller:116]: Unsupported command received: 3. Aborted.
And here's how my controller is configured:
Do you think this is a bug with the
lampsmart_pro
encoding, or did I miss something obvious ?The text was updated successfully, but these errors were encountered: