Error when adding new Danfoss Devolo Home Control Radiator Thermostat

@puzzlewolf wrote:

Hi everyone,

I am a new user of home assistant, so I am starting from a new home-assistant installation.
I am using the current stable docker image, 0.105.5, and a Z-Wave (Sigma Designs) USB stick.
The USB stick seems to work fine, as far as I can tell.

When adding a first z-wave device, a Devolo Home Control Radiator Thermostat, the following errors are logged:

2020-02-20 00:28:55 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 360, in _async_add_entity
    capabilities=entity.capability_attributes,
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 181, in capability_attributes
    self.hass, self.min_temp, self.temperature_unit, self.precision
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 490, in min_temp
    DEFAULT_MIN_TEMP, TEMP_CELSIUS, self.temperature_unit
  File "/usr/src/homeassistant/homeassistant/util/temperature.py", line 31, in convert
    raise ValueError(UNIT_NOT_RECOGNIZED_TEMPLATE.format(to_unit, TEMPERATURE))
ValueError:  is not a recognized temperature unit.

and multiple times:

2020-02-20 00:28:55 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 273, in async_update_ha_state
    f"No entity id specified for entity {self.name}"
homeassistant.exceptions.NoEntitySpecifiedError: No entity id specified for entity Danfoss Devolo Home Control Radiator Thermostat Heating 1

Also, in Z-Wave Control Panel / Z-Wave Node Management for the new node, only the entities
sensor.danfoss_devolo_home_control_radiator_thermostat_battery_level and sensor.danfoss_devolo_home_control_radiator_thermostat_temperature show up.
I tried heal network and heal node a couple of times.

I think a climate.* entity should also be there. There is a github issue (https://github.com/home-assistant/home-assistant/issues/29844) with the same symptom, but it is closed, so something else must be amiss here

FWIW, the configuration.yaml is

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

the included files empty.

Any ideas what’s going on here?

Posts: 1

Participants: 1

Read full topic