Error while setting up homematic platform for cover after HA Restart

Configuration
1

Hi,

I constantly get this error message after restarting HA.

Error while setting up homematic platform for cover

Then the state of the HMIP-BROLL window covers is unavailable. However this does not effect my HMIP-PSM plugs, which keep on working as desired.

I am running Home Assistant Supervised on Debian 10 and Debmatic on the same host.
The only way to get the covers working in HA again is to restart Debmatic AND then restart HA again. (Alternatively restarting the entire Host does the same)
But as soon as I restart HA afterwards (e.g. due to changes in configuration.yaml) the error message is back and the covers are unavailable.

Full log error message:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 192, in _async_setup_platform
    await asyncio.gather(*pending)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 301, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 397, in _async_add_entity
    supported_features=entity.supported_features,
  File "/usr/src/homeassistant/homeassistant/components/cover/__init__.py", line 219, in supported_features
    if self.current_cover_position is not None:
  File "/usr/src/homeassistant/homeassistant/components/homematic/cover.py", line 45, in current_cover_position
    return int(self._hm_get_state() * 100)
ValueError: invalid literal for int() with base 10: ''

I assume this has nothing to do with the common issue of loosing the connection between CCU and HA after rebooting CCU - since 1. this happens on HA reboot and 2. the HMIP-PSM keep on working.

any ideas?

Best
Pete

2

Looks like your cover is reporting an empty position state instead of a number.

Is the position determined by a template?

Does your cover actually support a position?

3

These covers report either 100 for fully open or 0 for everything else.

In the past I used templates for this state attribute but since I migrated my HA installation I removed these templates and that’s when the error appears.
So now I added the templates back to my configuration and interestingly after HA restart the same error happens again and the covers are unavailable BESIDES the cover “cover.xxxxxxxxxxxxxx3” (wohnzimmer_links) which is available and working.

But I don’t see any difference in the configuration of cover 3 in comparison to the others.

sensors.yaml:

- platform: template
  sensors:
    arbeitszimmer_cover_position:
      value_template: '{{ state_attr("cover.xxxxxxxxxxxxxx1", "current_position") | int }}'
      unit_of_measurement: '%'
      friendly_name: 'Schlafzimmer - Cover Position'
    schlafzimmer_cover_position:
      value_template: '{{ state_attr("cover.xxxxxxxxxxxxxx2", "current_position") | int }}'
      unit_of_measurement: '%'
      friendly_name: 'Schlafzimmer - Cover Position'
    wohnzimmer_links_cover_position:
      value_template: '{{ state_attr("cover.xxxxxxxxxxxxxx3", "current_position") | int }}'
      unit_of_measurement: '%'
      friendly_name: 'Wohnzimmer links - Cover Position'
    wohnzimmer_rechts_cover_position:
      value_template: '{{ state_attr("cover.xxxxxxxxxxxxxx4", "current_position") | int }}'
      unit_of_measurement: '%'
      friendly_name: 'Wohnzimmer rechts - Cover Position'
4

Ok. I was thinking that perhaps you had used the states.cover.object_id.attrributes.position format instead of the states('cover.object_id', 'position') form for the templates - that can have issues at start up. That is not the case.

5

The thing is that I can easily reproduce this faulty behavior:

  1. I restart debmatic
  2. I restart HA
    Result: all four covers are available
  3. I restart HA again
    Result: only 1 of 4 covers are still available

troubleshooting options:

  • Devices in Debmatic CCU: all covers are still usable via CCU directly
  • Connection between CCU and HU: 1 cover and all switches are still available
  • Templates in HA: no difference between templates of the available cover in comparison to the others. Furthermore, even without using any templates this error occurs.
  • Entities in HA: I removed all covers from CCU and deleted the entities in HA. Re-added them to CCU and HA.

nothing changd this faulty behavior.

I ran out of ideas.

6

Looks like you should raise an issue about this.

7

Do you mean on github?
If so, which category does this belong to? core, supervisor, add-on or even debmatic?

8

I’d try core ( homematic is a core integration) but they may tell you to take it up with Debmatic.

9

Hello, i can confirm the problem.

I’m running HA on a raspberry as Docker container.

It appeared with version 0.115 and exists also in my current version 0.116.2.