Feature Request: support deconz

[capstan1]

Would be great to have this support deconz to have something polished replacing your blueprint ;-)

[RubenKelevra]

Hey @capstan1 you mean my blueprint? :)

And yes, deconz will be supported, as we dropped the z2m dependencies already. So try out the newest beta and report back :)

[capstan1]

using one of KartoffelToby I found in the community, haven't seen another one from you. Sorry :(

Great to hear that better thermostat doesn't need z2m any more. Didn't see it in the description. Definitely gonna try it out these days!

[RubenKelevra]

@capstan1 that's my approach: https://github.com/RubenKelevra/Tuya-thermostatic-valve

[RubenKelevra]

@capstan1: Can you report back if this is working for you? :)

[capstan1]

@capstan1: Can you report back if this is working for you? :)

Still in the process of installing it manually after I found out that what I downloaded via HACS is still the old named integration, although it's pointing to this repo. ;-)

[capstan1]

Getting this error: 2022-03-08 23:04:49 DEBUG (MainThread) [custom_components.better_thermostat.models.models] better_thermostat wohnzimmer: found device: 2022-03-08 23:04:49 DEBUG (MainThread) [custom_components.better_thermostat.models.models] DeviceEntry(area_id=None, config_entries={'9afc452328fd10371bcb8dd4ac0d38a3'}, configuration_url=None, connections={('zigbee', 'cc:86:ec:ff:fe:a8:3d:eb')}, disabled_by=None, entry_type=None, id='4886507f831b2ba7083f81c2cfa941e6', identifiers={('deconz', 'cc:86:ec:ff:fe:a8:3d:eb')}, manufacturer='_TZE200_yw7cahqs', model='TS0601', name_by_user=None, name='Thermostat 72', suggested_area=None, sw_version='', hw_version=None, via_device_id='b96f712c8b00db335b5c7f890da81757', is_new=False) 2022-03-08 23:04:49 ERROR (MainThread) [custom_components.better_thermostat.models.models] better_thermostat wohnzimmer: could not find device config for your TVR. Make sure this device exists in Home Assistant.

It's a Hama branded tuya thermostat. Shouldn't it be supported as its TS0601?

[capstan1]

my other trv (moes) also throws out these errors: 2022-03-09 08:21:49 DEBUG (MainThread) [custom_components.better_thermostat.models.models] better_thermostat bad: found device: 2022-03-09 08:21:49 DEBUG (MainThread) [custom_components.better_thermostat.models.models] DeviceEntry(area_id=None, config_entries={'9afc452328fd10371bcb8dd4ac0d38a3'}, configuration_url=None, connections={('zigbee', '80:4b:50:ff:fe:f3:17:90')}, disabled_by=None, entry_type=None, id='3be1916a31e9b1fd0b826938b42c65a5', identifiers={('deconz', '80:4b:50:ff:fe:f3:17:90')}, manufacturer='_TZE200_cwnjrr72', model='TS0601', name_by_user=None, name='Thermostat 81', suggested_area=None, sw_version='', hw_version=None, via_device_id='b96f712c8b00db335b5c7f890da81757', is_new=False) 2022-03-09 08:21:49 ERROR (MainThread) [custom_components.better_thermostat.models.models] better_thermostat bad: could not find device config for your TVR. Make sure this device exists in Home Assistant.

[capstan1]

Still, Better thermostat gave me 2 new entities. Window sensor seems to be influencing the thermostats. But I'm unsure how the external sensor calibration works. It's displayed in the new entity but not reftected in the original one. Offset also doesn't change.

Also, everytime I change the temperature of the better_thermostat via your lovelace card, I get: Fehler beim Aufrufen des Diensts climate/set_temperature. 'NoneType' object has no attribute 'lower'

[jeroen85]

But I'm unsure how the external sensor calibration works. It's displayed in the new entity but not reftected in the original one. Offset also doesn't change.

I also do not understand (yet). Deconz TRV-devices do not have a local_temperature_calibration attribute. They call it offset. As far as I know, the only way to change this offset value via HA is by use of the deconz.configure service.

For example:

service: deconz.configure
data:
  entity: climate.trv_living
  field: /config
  data:
    offset: -300

How is this implemented now?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

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