Setting current_heating_setpoint is not correct or not changing at all (v2)

[TheDukeSr]

Hi,

EDIT: 2 Hours after this post it suddenly has the correct temp. and 1 hour later the difference is back again, but now a 0,5c difference ?!

Sorry if i don't understand this ticket system correctly. This ticket is closed, but i do not see the problem solved?

Today I did a re-install, and same problem is still here.

Zigbee Model: TS0601 Zigbee Manufacturer: _TZE200_ckud7u2l

  - platform: ai_thermostat
    name: betterwoonkamer
    unique_id: thermo_wnk 
    thermostat: climate.radiator_woonkamer
    temperature_sensor: sensor.atc_temp_woonkamer
    window_sensors: group.trv_open_raamdeurbgg

Taken from Zigbee2Mqtt: "current_heating_setpoint": 17 Hass: climate.radiator_woonkamer: 17 Hass: climate.betterwoonkamer: 18

Picture showing difference in temps

Originally posted by @TheDukeSr in https://github.com/KartoffelToby/better_thermostat/issues/246#issuecomment-1029931973

[kukachik]

Can you check local_temperature_calibration ? In my case, it was -1. It must be 0.

[KartoffelToby]

@RubenKelevra We should make sure that the local_temperature_calibration is set to 0 if we use setpoint_override

[RubenKelevra]

@RubenKelevra We should make sure that the local_temperature_calibration is set to 0 if we use setpoint_override

Nope I don't think so.

I used local temperature calibrations on my valves. Better Thermostat should just ignore them on the setpoint override. I don't think people will adjust them at all manually and if we don't touch them it won't affect our operations.

The issue is, that 0.9.x and everything on 1.0 up to b2 won't work properly on the TS0601.

[TheDukeSr]

The issue is, that 0.9.x and everything on 1.0 up to b2 won't work properly on the TS0601.

Tested... local_temperature_calibration setting has no impact on this problem.

[RubenKelevra]

@TheDukeSr thanks!

Does the 1.0b3 work for you?

[TheDukeSr]

@TheDukeSr thanks!

Does the 1.0b3 work for you?

Will test it. But need a few days . Busy busy...

[RubenKelevra]

@TheDukeSr there are still several pesky bugs around in the current beta. I recommend testing the first RC version as soon it's ready, as I got the same hardware, and it should work then.

Until then you don't need to invest time. :)

[RubenKelevra]

Please report back if this bug still exists in 1.0beta10

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity.