-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[hue] Add support for TransitionTime #4660
Conversation
It's fixing eclipse-archived/smarthome#1722. |
The PR-openHAB2-Addons Jenkins build failed. |
Thanks for this PR! (I have re-run the PR build, now it is green) It lgtm, my only concern is the new fade time channel: I do not think that we should add channels for adjusting configurations. This looks like a very ugly workaround and imho we should not create a precedence. I'd therefore prefer to remove it and rather discuss how we could make it possible through rules to change channel configurations, which would be the proper solution to the problem. |
I can understand your concerns. But I really would like a dynamic way of controlling the fade time. The channel implementation was of course a workaround. My favorite solution would be to have control over the fade time with each light command send to the light. I’m just not familiar enough with the code-base to know a better solution to accomplish this. The usage of a channel seemed like an easy solution. Maybe your suggestion about the rules could be a way. Can you tell me more about that approach? |
This discussion would also be relevant for the ZigBee binding (cc @cdjackson) . |
I tried a new approach with ThingActions instead of the Channel solution. |
No, I don't think so. The new potential feature of changing channel configurations through rules is not specific to any binding, but would be applicable to all - so this would be a framework feature and nothing to be added to each and every binding. |
But I actually don't want to change the configuration. I want to send a Light command with a specific fadetime and just ignore the configuration for that one command. |
Ok, yes, for parametrized commands, the ThingActions are the way to go. |
Ok cool. |
Thanks, looks good to me! Just one last request: Could you please also add the new features to the README.md? |
Sure thing. Will do it tomorrow. |
The README.md is updated in the new PR. |
The PR-openHAB2-Addons Jenkins build failed again. Doesn't look like an issue with my changes. |
Thanks! The only thing you forgot is to also add the transitionTime configuration parameter to the README :-) |
Implemented fade time config for light things. Implemented ThingAction fadingLightCommand for Hue lights Updated README.md Bug: openhab#1722 Signed-off-by: Jochen [email protected]
You are right. Sorry about that. Added the configuration parameter documentation with the newest PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect, now it looks good & complete 👍
Many thanks!
Thank you for the fast feedback comments. :-) |
Implemented fade time config for light things. Implemented ThingAction fadingLightCommand for Hue lights Updated README.md Bug: openhab#1722 Signed-off-by: Jochen [email protected] Signed-off-by: Pshatsillo <[email protected]>
Implemented fade time config for light things. Implemented ThingAction fadingLightCommand for Hue lights Updated README.md Bug: openhab#1722 Signed-off-by: Jochen [email protected] Signed-off-by: Maximilian Hess <[email protected]>
Implemented fade time config for light things.
Implemented fade time channel for dynamically changing the fade times of light things.
Bug: #1722
Signed-off-by: Jochen [email protected]