Closed bussnet closed 9 months ago
Hey there @julius2342, @farmio, @marvin-w, mind taking a look at this issue as it has been labeled with an integration (knx
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
knx documentation knx source (message by IssueLinks)
Hi 👋! Right, only the presets modes are interpreted, the rest is ignored for that DPT. See https://github.com/XKNX/xknx/blob/4ecee64b805dec2ac32ba130b7b855aaf15a2337/xknx/dpt/dpt_hvac_mode.py#L112
Help needed: The values of this type were retrieved by reverse engineering. Any notes on the correct implementation of this type are highly appreciated.
So, I think this helps: (part of the KNX Spec for this Type) 03_07_02 Datapoint Types v01.08.02 AS.pdf
Anything else needed? I can help to test also (I'm an IT guy, but not familiar with python)
Oh, thank you very much. I didn't mean to refer to that note 😬 (this seems to linger there since >6 years), but to the code / class that would have to be changed to add support for this.
If you don't want to do it yourself, you may open a feature request at https://github.com/XKNX/xknx/issues Please be aware that this DPT is quite rarely used so I wouldn't expect it being picked up next.
Oh, thank you very much. I didn't mean to refer to that note 😬 (this seems to linger there since >6 years), but to the code / class that would have to be changed to add support for this.
😁 Ah, OK.. I was wondering why an official open spec was not used.
If you don't want to do it yourself, you may open a feature request at https://github.com/XKNX/xknx/issues Please be aware that this DPT is quite rarely used so I wouldn't expect it being picked up next.
I tried several hours to get xknx local running, get the tests working and tried to understand the concept there.
I don't think it make sense that I try do change this concept, because the controller status in xknx could only has a single state, but multiple states in KNX, so this needs to change... or the HEAT/COOL bit should affect the controller_mode?
I add a FeatureRequest in the XKNX project: https://github.com/XKNX/xknx/issues/1348
Great 👍 Im going to close this one in favor of the new issue.
The problem
As defined in the KNX Standard Appendix A (defined here as
KNX AN 097/07 rev 3
) contains the heat/cool status in the b5 bit, but is not interpreted.I tested the Comfort b0-b3 bit (comfort, standby, night and frost protection), they worked as expected, but the b5 does not change the
hvac_modes
attribute fromheat
tocool
if the bit is 0 -hvac_modes
stay always toheat
.Same behaviour without the operation_mode_address.
Don't know if it works before, don't use it this way before.
Find a log from the moment I changed the heat/cool flag in the KNX device externally.
What version of Home Assistant Core has the issue?
core-2023.10.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
knx
Link to integration documentation on our website
https://www.home-assistant.io/integrations/knx
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response