Not setting temperature of "real" TRV

[gavyb]

I have configured the virtual TRV and also created a group to cover the windows, but having set the "virtual" TRV to a different value from the "real" TRV, it is not changing the temperature of the "real" TRV.
TRV model is TS0601_thermostat.

[KartoffelToby]

@gavyb Can you update to 0.2.0 and check if this bug is solved?
If not pls add the HA Developer status output of your TS0601_thermostat like i did in #1

Thanks!

[gavyb]

Thanks - I have updated and it still fails to update the "real" TRV target temperature. I now get the following error:
"Failed to call service climate/set_temperature. 'NoneType' object is not subscriptable"

[gavyb]

additional log details:

2021-11-18 15:23:50 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/ai_thermostat/climate.py", line 361, in _async_sensor_changed
await self._async_control_heating()
File "/config/custom_components/ai_thermostat/climate.py", line 432, in _async_control_heating
max_forcast_temp = int(round(float(forcast[0]['temperature']) + float(forcast[1]['temperature']) / 2))
TypeError: 'NoneType' object is not subscriptable

[gavyb]

and the following in the zigbee2mgtt log file:

error 2021-11-18 15:44:54: No converter available for 'get' 'local_temperature_calibration' ()

[KartoffelToby]

@gavyb You're a winner, i'm sure you got all current bugs :D
i feel very sorry,

additional log details:

2021-11-18 15:23:50 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/config/custom_components/ai_thermostat/climate.py", line 361, in _async_sensor_changed await self._async_control_heating() File "/config/custom_components/ai_thermostat/climate.py", line 432, in _async_control_heating max_forcast_temp = int(round(float(forcast[0]['temperature']) + float(forcast[1]['temperature']) / 2)) TypeError: 'NoneType' object is not subscriptable

Its a problem with the weather data, what kind of service do you use? In Version 0.4.0 it not longer crash if no data was found and the temp should be setted anyway, just a log warning appears with "no weather data found."

in 0.4.0 the weather entity is also optional and if the issue #10 is closed there will be an alternative outdoor sensor option.

and the following in the zigbee2mgtt log file:

error 2021-11-18 15:44:54: No converter available for 'get' 'local_temperature_calibration' ()

This was a other bug, i figured out that only the SPZB0001(so far) must be forced to get the local_temperature_calibration.

in 0.4.0 this will be fixed, so only if the model matches the SPZB0001 this function is triggered.

As soon as 0.4.0 is published i would like you to check it out, if the bug persists feel free to reopen this issue

[gavyb]

@KartoffelToby to answer your question, I am using AccuWeatherand seems to be returning current temperature, last change 5 hours ago...
I also have UK Met Office and OpenWeather, so I could try one of those ? Interesting that those other 2 were last updated several hours ago, but that's probably another issue elsewhere!

[gavyb]

ok, I have updated to latest version (0.4.0) and am no longer getting these error messages, but the virtual TRV is set to off and does not change the temperature of the real TRV or switch it on. However, when I change the temperature or switch the mode to Heat, this is reflected in the virtual TRV.

[gavyb]

am getting some positive results, will continue to test and provide an update tomorrow...

[gavyb]

I have an automation that turns the "real" TRV to 20 and this is not reflected in the "virtual" TRV - see lscreenshot:

I also am getting some error messages in the main log:

2021-11-19 10:05:27 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/ai_thermostat/climate.py", line 373, in _async_sensor_changed
await self._async_control_heating()
File "/config/custom_components/ai_thermostat/climate.py", line 497, in _async_control_heating
remappedstates = convert_outbound_states(self,converted_hvac_mode)
File "/config/custom_components/ai_thermostat/models/models.py", line 29, in convert_outbound_states
if self.hass.states.get(self.heater_entity_id).attributes.get('device').get('model') is not None:
AttributeError: 'NoneType' object has no attribute 'get'

and finally - getting a pop up as follows:

when I try to set the temperature in the "virtual" TRV

[KartoffelToby]

@gavyb
Oh boy, first thanks for your patient. I need to complete reproduce your environment, for that i need a couple of informations.

TRV Model:
Z2M Version:
HA Version:

HA Dev-Tools output of your Devices:

Z2M Log of the time the problem appears:

I will try to final fix it this weekend.

[upais]

I had the error above and solved it when I changed the 'name' in the virtual thermostat because with the domain 'climate.' it matched the value from 'thermostat'.
Example:
name: tvr_bedroom
thermostat: climate.tvr_bedroom

[KartoffelToby]

@gavyb can you check that first? i'm confused that HA allowing this. Its a circular dependency so yeah thats a error pool.

[gavyb]

@IvanUpa I don't believe I have that problem:

• platform: ai_thermostat
  name: bedroom_thermostat
  thermostat: climate.master_bedroom_trv
  temperature_sensor: sensor.ble_temperature_master_bedroom
  window_sensors: group.bedroom_windows
  weather: weather.home
  off_temperature: 20

[gavyb]

Apologies for the poor formatting above, I am using my mobile...

[KartoffelToby]

@gavyb can you checkout 0.5.0, it has a better error log, and what kind of TRV do you use? has it a local_calibration option in Z2M?

[gavyb]

I am using a TS0601 TRV and will now try 0.5.0, but am getting issues with controlling my TRV now, so may need to remove this integration

[KartoffelToby]

@gavyb
Yes the TS0601 is the problem, i must use a special method to calibrate it, you can take a look at #15 and #34 #38
If you haven't a head to test it longer, i'll understand you. I'll release the 1.0 version if all these problems are fixed under the new name better_thermostat. So you can wait for this.

[gavyb]

it looks like I am getting similar errors, so I think I will wait for 1.0 to be released before using it further. Many thanks for your work on this.