KNX Climate - Time comfort mode
xPudda opened this issue · 3 comments
The problem
Hi!
I have just integrated some KNX devices for the first time and they works well!
I noticed bad behavior for climates: time comfort mode (or time manual mode as the Vimar app call it).
It is a comfort mode but just for a few hours and then it set back to auto mode.
Additionally, in this case if the climate is in auto mode and i set a greater target point the device decline the command.
To make it works I need to put it on comfort mode before set the target point.
Other modes work like a charm (auto, eco, comfort, building protection).
This is the value received on the bus
Vimar app:
What version of Home Assistant Core has the issue?
core-2024.10.3
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/#climate
Diagnostics information
home-assistant_knx_2024-10-25T21-47-21.326Z.log
Example YAML snippet
climate:
- name: "Bagno Giorno"
temperature_address: "1/4/116"
target_temperature_address: "1/4/108"
target_temperature_state_address: "1/4/109"
active_state_address: "1/4/129"
operation_mode_address: "1/4/106"
operation_mode_state_address: "1/4/107"
min_temp: 4.0
max_temp: 40.0
Anything in the logs that might be useful for us?
2024-10-25 23:39:30.528 WARNING (MainThread) [xknx.log] Can not process <Telegram direction="Incoming" source_address="1.0.12" destination_address="1/4/107" payload="<GroupValueWrite value="<DPTArray value="[0x5]" />" />" /> for Bagno Giorno Mode - Operation mode: <ConversionError description="Payload not supported for DPTHVACMode" raw="(5,)"/>
Additional information
No response
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!
Code owner commands
Code owners of knx
can trigger bot actions by commenting:
@home-assistant close
Closes the issue.@home-assistant rename Awesome new title
Renames the issue.@home-assistant reopen
Reopen the issue.@home-assistant unassign knx
Removes the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-information
Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-information
Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
knx documentation
knx source
(message by IssueLinks)
Hi 👋!
This seems to be a proprietary mode specific to your actuator (/manufacturer) as it isn't defined in the Knx specifications.
You could use a select
entity for that mode. These can be configured in a generic way.