Skip to content
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

Integrate netatmo valve #1571

Open
Daximino opened this issue Jan 15, 2025 · 12 comments
Open

Integrate netatmo valve #1571

Daximino opened this issue Jan 15, 2025 · 12 comments
Assignees
Labels
new bug incoming bug issue stale Long time no activity wait for feedback

Comments

@Daximino
Copy link

when i attach into better thermostat a netatmo valve, it command the valve to heat at 30 degrees in random time.

@Daximino Daximino added the new bug incoming bug issue label Jan 15, 2025
@folfy
Copy link
Collaborator

folfy commented Jan 15, 2025

Dear user,

Please follow the mandatory bug reporting template, providing version numbers, configuration information/diagnostic data, debug logs, graphs of your entities showing the behavior, etc.

If you do not provide more information, we will not be able to help you, and your issue will have to be closed.

@Daximino
Copy link
Author

I have two netatmo valve version firmware netatmo 102.
I habe installed last version of better thermostat configured with target temperature based an calibration normal.
Netatmo application has program fixed to 20 degrees more times in few hours the temperature of the valve is modified to 30 degrees

@folfy
Copy link
Collaborator

folfy commented Jan 15, 2025

Maybe your room is 10°C below the TRV temperature, and therefore rly needs to be offset by that much? As said, without actual data from your system we cannot tell you the cause/reason of your problem.

@Daximino
Copy link
Author

Which data do you want? I can attach everything.
The difference between the valve and the temperature sensor is at maximum 4 degrees

@folfy
Copy link
Collaborator

folfy commented Jan 15, 2025

@Daximino As said, current (debug) logs and matching graphs, then I can look into why it still might not be working.

@Daximino
Copy link
Author

Hi,
I have done the debug log of the problem, i have set the Cucina valve to 20 degrees, I have checked and the valve has gone to 30 degrees.
This is the log.
2025-01-17 16:40:06.026 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: TRV climate.salone sends new internal temperature from 21.0 to 20.5
2025-01-17 16:40:06.026 ERROR (MainThread) [custom_components.better_thermostat.utils.helpers] better_thermostat None: climate.salone HVAC mode auto is not supported by this device, is it possible that you forgot to set the heat auto swapped option?
2025-01-17 16:40:06.026 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: trigger_trv_change test / _old_heating_setpoint: 20.5 - _new_heating_setpoint: 20.5 - _last_temperature: 20.5
2025-01-17 16:40:06.026 ERROR (MainThread) [custom_components.better_thermostat.utils.helpers] better_thermostat None: climate.cucina HVAC mode auto is not supported by this device, is it possible that you forgot to set the heat auto swapped option?
2025-01-17 16:40:06.026 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: trigger_trv_change test / _old_heating_setpoint: 20.0 - _new_heating_setpoint: 30.0 - _last_temperature: 20.0
2025-01-17 16:40:06.026 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: TRV climate.cucina decoded TRV target temp changed from 20.0 to 30.0
2025-01-17 16:40:06.027 DEBUG (MainThread) [custom_components.better_thermostat.calibration] better_thermostat None: climate.salone - new setpoint calibration: 20.0 | external_temp: 20.1, target_temp: 20.0, trv_temp: 20.5
2025-01-17 16:40:06.027 DEBUG (MainThread) [custom_components.better_thermostat.utils.controlling] better_thermostat None: TO TRV set_hvac_mode: climate.salone from: auto to: heat
2025-01-17 16:40:06.027 DEBUG (MainThread) [custom_components.better_thermostat.adapters.generic] better_thermostat None: set_hvac_mode heat
2025-01-17 16:40:06.031 DEBUG (MainThread) [custom_components.better_thermostat.calibration] better_thermostat None: climate.cucina - new setpoint calibration: 30.0 | external_temp: 20.4, target_temp: 30.0, trv_temp: 20.5
2025-01-17 16:40:06.031 DEBUG (MainThread) [custom_components.better_thermostat.utils.controlling] better_thermostat None: TO TRV set_hvac_mode: climate.cucina from: auto to: heat
2025-01-17 16:40:06.031 DEBUG (MainThread) [custom_components.better_thermostat.adapters.generic] better_thermostat None: set_hvac_mode heat
2025-01-17 16:40:06.264 DEBUG (MainThread) [custom_components.better_thermostat.utils.controlling] better_thermostat None: TO TRV set_temperature: climate.salone from: 20.5 to: 20.0
2025-01-17 16:40:06.397 DEBUG (MainThread) [custom_components.better_thermostat.utils.controlling] better_thermostat None: climate.salone / check_target_temp / _last: 20.0 - _current: 20.5

@folfy
Copy link
Collaborator

folfy commented Jan 17, 2025

2025-01-17 16:40:06.026 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: TRV climate.cucina decoded TRV target temp changed from 20.0 to 30.0
Your BT target temperature actually changed, not just the valve itself. Your TRV reported an unexpected change from 20 to 30°C, so BT is adjusting to that.

Did you consider the known issues and the proposed workaround?

#1532 - Temperatur changes without manual change (usually an issue with the TRV, try enabling child lock in BT)

@Daximino
Copy link
Author

I have set 'Ignore all inputs on the TRV like a child lock'.
Now i attend

@folfy
Copy link
Collaborator

folfy commented Jan 18, 2025

@KartoffelToby I feel like half our issues are just based around this one single problem, and even putting a warning everywhere won't be enough - I propose to change the default state to locked for the child lock option, and make it something like an "allow changes on TRV (update BT setpoint accordingly - WARNING: Many TRVs send erroneous changes)" flag. What do you think? Or maybe make the warning a secondary (really keep activated / disable ) confirmation after continuing in the config flow, with a more detailed explanation and link.

Edit: That's what I'd propose, in regards tou your #1552 (comment)
Base-issue: #1532

Alternative idea:
See if we can heuristically catch this in any way in BT (probably not reliable, but better than nothing), and at least try to autmatically generate a repair indication, if observed (if the indication is acknowledged once as false-positive "not an issue" by the user, don't prompt again)

@Daximino
Copy link
Author

2025-01-17 16:40:06.026 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: TRV climate.cucina decoded TRV target temp changed from 20.0 to 30.0 Your BT target temperature actually changed, not just the valve itself. Your TRV reported an unexpected change from 20 to 30°C, so BT is adjusting to that.

Did you consider the known issues and the proposed workaround?

#1532 - Temperatur changes without manual change (usually an issue with the TRV, try enabling child lock in BT)

I have enabled child lock' in BT but i continue to have a valve netatmo that set to 30 degrees.

@folfy
Copy link
Collaborator

folfy commented Jan 19, 2025

Logs?

@folfy
Copy link
Collaborator

folfy commented Jan 31, 2025

Unless logs are provided, we'll have to close this issue.

debug log
Depending on how complicated you issue is, it might be necessary to enable debug logging for BT,
reproduce the issue, and then upload this logfile here.
https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging

graphs
For issues in regards to the calibration / control routines, it is very helpful to also
provide statistics graph screenshots from HA for the following entities (from the time you had issues):

  • BT climate entity
  • TRV climate entities controlled by BT
  • (optional) Valve opening states

@folfy folfy added the stale Long time no activity label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new bug incoming bug issue stale Long time no activity wait for feedback
Projects
None yet
Development

No branches or pull requests

3 participants