home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.82k stars 30.51k forks source link

homebridge / knx - resetting temp settings in homekit / glastaster from heating to default value of 21 on MDT glastaster after reboot #115182

Closed funx1 closed 1 month ago

funx1 commented 6 months ago

The problem

All room temperature values are reset to 21 degrees within the KNX settings from HA / Homebridge after each reboot.

What version of Home Assistant Core has the issue?

core-2024.4.1

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

homebridge

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

funx1 commented 6 months ago

Anyone experiencing similar changes after reboot on temperature values within homebridge?

funx1 commented 6 months ago

?

funx1 commented 6 months ago

Issue remains still

joostlek commented 6 months ago

What integration is causing the problem? Homebridge isn't an integration

funx1 commented 5 months ago

homekit bridge probably. I'm importing KNX groupaddressess with KNX and after seting up homekit bridge, values get adjusted after a reboot.

funx1 commented 5 months ago

Anything more needed?

funx1 commented 5 months ago

someone any ideas where to look at?

issue-triage-workflows[bot] commented 5 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

funx1 commented 5 months ago

Using the latest version. Just updated and rebooted. The problem persists still. Temperatures are all reset to 21 degrees.

home-assistant[bot] commented 5 months ago

Hey there @jc2k, @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit_controller) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `homekit_controller` 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 homekit_controller` 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)


homekit_controller documentation homekit_controller source (message by IssueLinks)

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

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)

home-assistant[bot] commented 5 months ago

homekit documentation homekit source

farmio commented 5 months ago

@funx1 can you show the configuration of such an entity and a screenshot of an ETS Group monitor session when restarting (filtered for the configured GAs / or just an export)? This is most likely a KNX issue, not a HA issue.

funx1 commented 5 months ago

I found out that only the view in homekit changed. Actually the group values did not change. I thought they changed before also, but after I checked again this time, they stayed the same. The value within homekit changes directly, if I change the value within the homekit app. But before after each reboot the display "heat to" value changes always to 21 degrees, but is set to 19,5 in this example in the group address. Although the group value does not change in KNX, like it is changed in the homekit app.

Screenshot 2024-05-27 at 16 07 16

climate:

funx1 commented 5 months ago
Screenshot 2024-05-27 at 16 15 11
farmio commented 5 months ago

To isolate the source of the issue, please keep HomeKit out of it for now. Only look at HA states here Open your Home Assistant instance and show your state developer tools. and KNX Telegrams.

farmio commented 5 months ago

Btw. I don't think this GA is configured correctly. target_temperature_state_address: "3/4/152" "Stellwert: Status senden" sounds to me like current valve control value, but then again I don't know your actuator... maybe have a look in the manual to check.

issue-triage-workflows[bot] commented 2 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.