Better thermostat entities not available

[ivanovd]

System Health

version	core-2021.12.10
installation_type	Home Assistant Supervised
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.9.7
os_name	Linux
os_version	5.10.63-v7+
arch	armv7l
timezone	Europe/Sofia

Home Assistant Community Store

GitHub API	ok
Github API Calls Remaining	5000
Installed Version	1.21.0
Stage	running
Available Repositories	966
Downloaded Repositories	13

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Raspbian GNU/Linux 11 (bullseye)
update_channel	stable
supervisor_version	supervisor-2022.01.1
docker_version	20.10.11
disk_total	109.7 GB
disk_used	43.0 GB
healthy	true
supported	failed to load: Unsupported
supervisor_api	ok
version_api	ok
installed_addons	ESPHome (2022.1.3), File editor (5.3.3), Duck DNS (1.14.0), Mosquitto broker (6.0.1), Home Assistant Google Drive Backup (0.105.2), Node-RED (10.4.0), AdGuard Home (4.4.4), Zigbee2mqtt (1.23.0-1)

Lovelace

dashboards	1
resources	6
views	9
mode	storage

Spotify

api_endpoint_reachable	ok

YAML config entry:

- platform: better_thermostat
  name: Living room
  thermostat: climate.living_room_radiator_thermostat
  temperature_sensor: sensor.living_room_temp_temperature
  weather: sensor.openweathermap_temperature
  off_temperature: 15

Card config:

Better thermostat entity:

No errors in the log. The integration version is 1.0.0beta2

Zigbee2MQTT config:

I don't see any errors in the logs, however, the better thermostat entities are unavailable. The regular thermostats are available though.

[ivanovd]

Any assistance would be very much appreciated.

[trevortrevor]

Looks like the manifest changes haven't been implemented in a fulll release yet so will still be loading as the old name ai_thermostat. You should see a line like:

[homeassistant.loader] We found a custom integration ai_thermostat which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

Therefore change you configuration.yaml to the following:

- platform: ai_thermostat
  name: Living room
  thermostat: climate.living_room_radiator_thermostat
  temperature_sensor: sensor.living_room_temp_temperature
  weather: sensor.openweathermap_temperature
  off_temperature: 15

Or use a V1.x beta release

[ivanovd]

Hi @trevortrevor and thank you for your input. I am using v1.0 beta 2, however, as you said I see the above line in the core logs: 2022-02-04 11:47:07 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ai_thermostat which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant after switching the platform to ai_thermostat, it started working

Thank you

[ivanovd]

Now there is another problem and I don't know if I should open a separate thread of wait for the stable 1.0 release. The external temp now shows in the better-thermostat-card, however, the temp adjuster doesn't control the thermostat, it doesn't change the set temperature. The built-in climate card works though.

Better thermostat card with ai_thermostat entity selected:

Standard thermostat card with standard thermostat entity selected:

[DieMetRik]

Добрый день. Сегодня решил перейти с ai_thermostat на better_thermostat.

Переименовал в configuration.yaml ai_thermostat на better_thermostat. Переименовал имя и uid.

После перезагрузки сервера. Пишет так же: Недоступно. Никаких ошибок в логах нет. Версия better_thermostat 1.0.0 beta 3

Обратно вернул ai_thermostat все заработало.

Сейчас сделал 2 термостата. Один AI другой better AI - работает Better - Недоступен Термоголовка: TS0601_thermostat

• platform: ai_thermostat name: kitchen_ai_trv unique_id: kitchen_ait_trv thermostat: climate.hvac_kitchen_trv temperature_sensor: sensor.hvac_kitchen_temperature_bme outdoor_sensor: sensor.street_temp_kitchen off_temperature: 20.0 valve_maintenance: false night_temp: 22 night_start: '00:00' night_end: '7:00'

  • platform: better_thermostat name: kitchen_bt_trv unique_id: kitchen_bt_trv_uid thermostat: climate.hvac_kitchen_trv temperature_sensor: sensor.hvac_kitchen_temperature_bme outdoor_sensor: sensor.street_temp_kitchen off_temperature: 20.0 valve_maintenance: false night_temp: 22 night_start: '00:00' night_end: '7:00'

[DieMetRik]

Нашел решение в дискуссии: https://github.com/KartoffelToby/better_thermostat/discussions/268#discussioncomment-2104233 Надо добавить: window_sensors: input_boolean.better_windows_trv_sensor window_off_delay: 15

[KartoffelToby]

PLEASE use English so we can help everybody.

Can you try Beta 3?

[gymnae]

I just installed this integration with beta 3 and also face the same issue. Are there logfiles I could produce which might help?

[DieMetRik]

After add a fake window_sensors work good

[gymnae]

Not for me, I added an existing binary sensor for window_sensors and it doesn't work. Also, I don't have real window sensors

[DieMetRik]

I add a input_boolean in config with name: better_windows_trv_sensor

then add this in configuration.yaml window_sensors: input_boolean.better_windows_trv_sensor window_off_delay: 15

after restart server better trv change status from unavailable to normal

[gymnae]

I add a input_boolean in config with name: better_windows_trv_sensor

then add this in configuration.yaml window_sensors: input_boolean.better_windows_trv_sensor window_off_delay: 15

after restart server better trv change status from unavailable to normal

Oh yeah, I can second this, adding a fake input_boolean fixes it

[gymnae]

EDIT: While I do see the thermostat entity now, there is no action on the TRV via better_thermostat. No calibration or actuator change is passed on

[gavyb]

Now there is another problem and I don't know if I should open a separate thread of wait for the stable 1.0 release. The external temp now shows in the better-thermostat-card, however, the temp adjuster doesn't control the thermostat, it doesn't change the set temperature. The built-in climate card works though.

Better thermostat card with ai_thermostat entity selected:

Standard thermostat card with standard thermostat entity selected:

I have the same problem. The thermostat card is appearing correctly now, but does not control the trv

[KartoffelToby]

Confirmed bug, will be fixed in Beta 4

A Fake window sensor is not longer needed

[Soukyuu]

I'm running beta14 currently (also tried master) and am still experiencing both the "unavailable" and the "no changes passed to original trv entity" error. In addition, as long as the corresponding better_thermostat entry is active in the config, the original trv entity turns itself off after a while.

It used to work the first time I configured it, but stopped working after a restart. I suspect this has something to do with loading order of zigbee2mqtt vs better_thermostat. Did not try the window_sensor workaround yet, as it's supposedly not necessary?

Sample entry:

# Wohnzimmer
  - platform: better_thermostat
    name: ai_wohnzimmer_nord_thermostat
    thermostat: climate.wohnzimmer_nord_thermostat
    temperature_sensor: sensor.wohnzimmer_temperatur
    valve_maintenance: true
    night_temp: 18.0
    night_start: '22:00'
    night_end: '06:00'
    unique_id: 308
  - platform: better_thermostat
    name: ai_wohnzimmer_ost_thermostat
    thermostat: climate.wohnzimmer_ost_thermostat
    temperature_sensor: sensor.wohnzimmer_temperatur
    valve_maintenance: true
    night_temp: 18.0
    night_start: '22:00'
    night_end: '06:00'
    unique_id: 309
  - platform: climate_group
    name: "Wohnzimmer"
    temperature_unit: c
    entities:
      - climate.ai_wohnzimmer_nord_thermostat
      - climate.ai_wohnzimmer_ost_thermostat

[Soukyuu]

Tried the window_sensors workaround, no dice. Still claims half of the entities are not available, and those that are are "heating" while the underlying ones are getting turned off - bummer.

[stale[bot]]

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