-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Temperatuur changes without manual change #1532
Comments
Without more information, we cannot analyze your issue. debug log |
Hi, i have the same issues happening again and again. Will try to catch logs. |
For some reasomn I get an error while downloading the txt log. So I needed the debug logging line to the manifest.json. Then I get the following in the main log file: 2024-12-27 19:16:14.802 DEBUG (MainThread) [custom_components.better_thermostat.climate] better_thermostat Daikin_Better: HA set target temperature to 20.0 & None |
It does not recognize a daikin: 2024-12-27 19:14:35.174 INFO (MainThread) [custom_components.better_thermostat.adapters.delegate] better_thermostat None: integration: daikin isn't native supported, feel free to open an issue, fallback adapter generic |
I have the same bug on one of my TRVs. (others work fine).
At some random time during noon, my target temperature drops to somwhere around 12°C. No manual intervention done. This is what's in my logs for this event.
This is the event of me changing the target temp back to 21°C
This is BT changing it back again. But I cant'see why. Again, no manual intervention.
This is an error I can find repeatedly in my log, maybe it helps.
|
That's ok and just means the "default" adapter mode is used, no specific configuration / adaption exists for your TRV (which is not even needed in most cases). |
Diagnosis data download is broken (#1469), PR for bugfixx is pending with maintainers
We need full logs - Your BT setpoint is 20°, so everything working normal, there's no change to a new BT target temperature as described in the bug report. |
This looks like multiple events are fired for BT changing the TRV 3min before, either because the TRV is sending changes/updates late and mutliple times now (trigger_trv_change), or something is going wrong in BT and the update event is handled multiple times. There's nothing in between 13:36:38 and 13:39:16 in the logs? Will probably extend debug messages, to rly figure out what's going wrong, but don't have time to check potential causes in the source rn. As a temporary workaround, you can enable child lock in BT for the affected TRV(s), or disable target temperature calibration (calibration mode "no calibration").
Diagnosis data download is broken (#1469), PR #1526 for bugfix is pending with maintainers (this is unrelated, and why you have to use debug mode for getting any data out atm). |
But you do see the gui change to a higher value and when I check with the Daikin app it does set the temperature to this high value. |
This is working as designed for the given compensation mode you activated in BT, this issue is about the BT target temparture changing, not the TRV/HVAC. If you want BT to just set your HVAC target temperature to what you set in BT, you have to enable "no calibration" mode in the BT config of your TRV / HVAC, that's all. |
@mueller-esch "Diagnostic data" download is broken in v1.6.1 and v1.7.0b1, and also wouldn't provide enough information to analyze the issue. Please follow the instructions here on how to get proper debug logs:
Please create a new issue and follow the other directions there, i.e. provide the stated version numbers, TRV hardware, etc., and statistics graphs of your BT entity and the associated TRV entities during that time, or at least a proper description of what exactly happened when (and when what issue occured), since we don't have any information about your specific issue. Further, if this is about the TRV target temperature changing, and not the target temperature in/of BT, then please read my previous comment - This is not a bug, and can be disabled as described. |
More information/data needed (like in #1552 for example), or we will have to close this issue. When providing debug logs, please make sure to provide a full log, including the full timeframe as well as before/after the problem occured. Working around TRV "changing on it's own" issues means, we need to fully understand what's happening / why the TRV might be reporting an unexpected change. So far I can just recommend to enable the "ignore TRV settings like child lock" setting as a workaround. diagnostic data debug log |
Prerequisites
Description
Steps to Reproduce
After setting the temperature to 20 degrees is suddenly changes it to 31 without manual change
Versions
HA 2024.12.1
BT 1.6.1
Additional Information
The text was updated successfully, but these errors were encountered: