-
-
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
[amazonechocontrol] Support QuantityType Color Temperature command #17919
Conversation
Signed-off-by: Andrew Fiddian-Green <[email protected]>
Signed-off-by: Andrew Fiddian-Green <[email protected]>
Signed-off-by: Andrew Fiddian-Green <[email protected]>
This pull request has been mentioned on openHAB Community. There might be relevant details there: |
This comment was marked as resolved.
This comment was marked as resolved.
Changed to draft to prevent unwanted merge. Please revert when mqtt channels are fixed. |
@ccutrer do you think anything needs to be done in the MQTT bindings in order for them to accept QuantityType inputs. AFAICT they do already accept such inputs and a) if the Channel has a ‘unit’ field then UoM conversions are applied, or b) if the Channel has no ‘unit’ field then it takes the raw decimal value of the given QuantityType (without conversion). |
To answer here: the handleCommand and downstream calls are all set up to handle K or mirek in MQTT, but due to another issue core was only sending decimal commands. PRs are open (openhab/openhab-core#4507 and #17929) to fix that. |
No problem. I will split it. |
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.
LGTM, thank you
It will only take about 30 minutes to do the split |
Signed-off-by: Andrew Fiddian-Green <[email protected]>
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.
LGTM, thank you
Can you please adjust the content of your first message ? |
If I get the context right, what is left here in this PR is a fix for a regression introduced by #17754 - and likewise for all the others (i.e. #17942 fixes #17777 etc.). So I think all the PR's should be backported to 4.3.x. Given a clean commit history (one commit per binding) we could have merged just one PR without squash-merging the commits. We used that approach here: #17725 (comment) But I like this split approach as well, since there is a clean 1:1 relation for each PR to a PR that introduced the issue - and also all bindings will be mentioned in the release notes. 👍 |
To be backported in branch 4.3.x. |
I will do the different backporting, I am just searching again the proper git commands... to not make a mistake! |
…penhab#17919) * [various] process color temperature quantity type commands Signed-off-by: Andrew Fiddian-Green <[email protected]>
For reference: #15329 (comment) |
The 5 PRs are now backported to branch 4.3.x. |
…penhab#17919) * [various] process color temperature quantity type commands Signed-off-by: Andrew Fiddian-Green <[email protected]> Signed-off-by: Ciprian Pascu <[email protected]>
Resolves #17917
Signed-off-by: Andrew Fiddian-Green [email protected]