-
Notifications
You must be signed in to change notification settings - Fork 70
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
Help Needed! How to convert Lightbulb setHue payload? #65
Comments
Hi, i made white color and rgb in separate groups |
identify is just a little helper to identify an accessory when adding it in the home app. For e.g. a lamp it makes sense to let it blink a few times, so you know which lamp you are currently adding. About converting RGB to HSL - there is a little bit of math necessary, see e.g. https://stackoverflow.com/questions/39118528/rgb-to-hsl-conversion |
Hmm could you try to explain further what you mean with "enable current brightness payload and others like color payload"? You can already configure separate topics for Brightness, Hue, Saturation. You can also set factors to convert them to other value ranges. |
hey @hjltu thank you for providing the script, but I am totally a noob here, so how to run this? I am running homekit2mqtt inside a docker container, does it means I need to go inside the container and install python stuff to run this script? |
Hi @hobbyquaker, let me try to explain(as a noob of view) However homekit2mqtt is expecting seperated topic for those info(does it?) So in this case, I have to find a way to seperate the topic and make homekit2mqtt happy(understandable), because I think it can't understand So, I use node-red to get the mqtt topic from lightbulb and seperate those info and then re-publish as several new topics(each topic contains a single payload such as So, I would like to request a feature that homekit2mqtt can at least understand a single topic with json objects, or maybe somehow, I don't know how, can read RRGGBBWW value(FF9D30FF) from json object. or, let and so sorry for the noob-kind-of-explain. I hope you understand what I trying to get. Thanks! |
Yes, that's right.
Until now this is a needed workaround...
|
Will close this issue now, you can follow the above mentioned issues to keep an eye on the progress. |
I Implemented RGB topics for LightBulb in v0.9.3 |
Hi, I have an ailight smart lightbulb already setup and working, however the ailight is using tasmota and the color for mqtt payload is set to RRGGBBWW(string)
{"POWER":"ON","Dimmer":100,"Color":"FF9D30FF"
So how to convert this
FF9D30FF
string to let homekit2mqtt setHue topic to understand the current color?Also could u please explain what exactly does the
identify
topic does? What do I need to put which topic to this one? Does it means just a device identify or a device with health info?Also could u please enable current brightness payload and others like color paylaod? Right now it always go to topic, I have to "convert" the topic somehow using node-red to create a complete new topic with current brightness level payload.
Thanks man, again very awesome job!
Shane
The text was updated successfully, but these errors were encountered: