thermostat card not powering on the device

StefanW86 commented 1 month ago

The problem

Describe the issue you are experiencing I have configured a climate device through my knx integration. All service calls works like expected. If i want to power on my climate device through the thermostat card i click on "cool", because there is no extra "on" button. HA sends a cool command to the knx bus but the climate device ignores it. It needs a "on" command. So after clicking multiple times on cool, at same time HA sends a on command and the climate devices powers on.

Describe the behavior you expected If clicking the cool button, HA should first send a on command if the deviced is powered off and then a cool command.

Steps to reproduce the issue Clicking on cool in thermostat card

What version of Home Assistant Core has the issue? 2024.8.2 and all others below

What was the last working version of Home Assistant Core? No response

In which browser are you experiencing the issue with? No response

Which operating system are you using to run this browser? No response

State of relevant entities No response

Problem-relevant frontend configuration No response

Javascript errors shown in your browser console/inspector No response

Additional information

i opend the issue in the frontent part, but the told me, it could be a core / knx issue. The issue in frontend is here: https://github.com/home-assistant/frontend/issues/21596

What version of Home Assistant Core has the issue?

2024.8.2

What was the last working version of Home Assistant Core?

-

What type of installation are you running?

Home Assistant OS

Integration causing the issue

knx

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

StefanW86 commented 1 month ago

whats that? an exe file? Malware?

home-assistant[bot] commented 1 month 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!

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)}}

farmio commented 1 month ago

Hi 👋! Please share your entity configuration, maybe an annotated screenshot of the group monitor and some infos about your actuator /config so we can better see where the problem is.

StefanW86 commented 1 month ago

Hi, here is my knx config for the climate device.

` climate:

name: "Klima Wohnen" on_off_address: "4/1/80" on_off_state_address: "4/1/81" controller_mode_address: "4/1/82" controller_mode_state_address: "4/1/83" target_temperature_address: "4/1/84" target_temperature_state_address: "4/1/85" temperature_address: "4/1/86"`

knx bus

attached a screenshot from the knx bus.

At 15:26:48 i clicked the first time on cooling, at 15:26:56 the second time and after clicking at 15:27:03 the third time on cooling, then the climate device is powered on.

If i use my alexa box and say "Start climate device with cooling" it starts immediately.

Alexa sends the command to home assistant and ha turns on the climate device.

The issue in the gui is reproducable

farmio commented 1 month ago

Awkward. As you can see in your group monitor, HA sends the same 2 telegrams all 3 times. One for the mode and one for ON. Your actuator even responds with correct status all 3 times. Only for the first 2 it sets its status to OFF ~0,3 seconds later.

So unless there are any telegrams filtered out, it seems like an actuator issue, rather than a HA issue.

StefanW86 commented 1 month ago

Awkward. As you can see in your group monitor, HA sends the same 2 telegrams all 3 times. One for the mode and one for ON. Your actuator even responds with correct status all 3 times. Only for the first 2 it sets its status to OFF ~0,3 seconds later.

So unless there are any telegrams filtered out, it seems like an actuator issue, rather than a HA issue.

If I power on the device through KNX ets software, it works every time. If I turn it on through Alexa (through HA) it works every time.

Turning it on through HA climate card, it needs 2 to 5 attempts. I attached a video.

https://github.com/user-attachments/assets/8ff95d42-e957-4159-8ded-6351c457b6e1

farmio commented 1 month ago

🤷 it seems to send the correct telegrams. The Knx bus can't know how you triggered that. As you see on the group monitor (and in your video) it was ON for a fraction of a second. So with the information I have, I can not help you any further, sorry.

StefanW86 commented 1 month ago

Hi, here is photo from the knx bus while sending the start command through alexa. alexa

Only the on command will send from HA to the device and it starts immediatly.

Perhaps a problem, that HA sends first the cooling telegram and then the on command? Or perhaps is the pause between cooling mode and on telegram to short?

Can we do some tests to change the order of the telegrams or do some wait between the commands?

farmio commented 1 month ago

Or perhaps is the pause between cooling mode and on telegram to short?

Since the device responds with the new status immediately - for both telegram - it has obviously processed both. There may, of course just be some kind of internal bug in the device firmware or something like that. Did you contact the manufacturers support about that issue?

Can we do some tests to change the order of the telegrams or do some wait between the commands?

You can use ETS to send telegrams, but I don't know if you can send multiple in any fast enough way. Other than that, you can try to create a HA script and use knx.send and delay for testing purposes. https://www.home-assistant.io/docs/scripts/ For more detailed tests, some Python knowledge would be required.

StefanW86 commented 1 month ago

A problem with missing delay can be ruled out. I created this HA script to set the cooling mode and then instant power it on.

`alias: Test Klima An sequence:

action: knx.send metadata: {} data: response: false address: 4/2/72 payload: 3
action: knx.send metadata: {} data: response: false address: 4/2/70 payload: 1 description: ""`

The ets bus knx

The climate device instant power on and start.

Minimal python knowledge is available.

farmio commented 1 month ago

action: knx.send
metadata: {}
data:
response: false
address: 4/2/72
payload: [3]

Since this is not DPT 1/2/3 you'd need to send a list of raw values to produce the same telegram.

For the on/off telegram it is correct to use payload: 1.

StefanW86 commented 1 month ago

sorry, i dont understand right. It makes no difference if i use

alias: Test Klima An
sequence:
  - action: knx.send
    metadata: {}
    data:
      response: false
      address: 4/2/72
      payload: [3]
  - action: knx.send
    metadata: {}
    data:
      response: false
      address: 4/2/70
      payload: 1
description: ""

or

alias: Test Klima An
sequence:
  - action: knx.send
    metadata: {}
    data:
      response: false
      address: 4/2/72
      payload:
         - 3
  - action: knx.send
    metadata: {}
    data:
      response: false
      address: 4/2/70
      payload: 1
description: ""

or my first try

alias: Test Klima An
sequence:
  - action: knx.send
    metadata: {}
    data:
      response: false
      address: 4/2/72
      payload: 3
  - action: knx.send
    metadata: {}
    data:
      response: false
      address: 4/2/70
      payload: 1
description: ""

farmio commented 1 month ago

First or second example are ok (same), third is different (wrong for DPT 20.x). It may not be visible in ETS, I don't know, but it may be processed differently by the devices firmware.

StefanW86 commented 1 month ago

Do you have any other ideas on how we can narrow down or identify the problem?

At the moment we can exclude a timing problem or missing telegrams or telegrams with wrong order. The issue only happens with the use of the climate card. What happens in the code of the climate card if someone clicks on "cooling" ? Can we reproduce the steps with a HA script?

farmio commented 1 month ago

I don't know what the frontend does there exactly. You can probably look at HAs event bus to find out. https://my.home-assistant.io/redirect/developer_events/

Other than that, I still strongly recommend to contact the device manufacturer or your installer. Send an ETS log and ask why the device is behaving that way. They should know. Everything else is guesswork.

home-assistant / core