python-matter-server: Window Covering commissioning breaks the server

I’ve seen that Window Covering has been added recently (https://github.com/home-assistant-libs/python-matter-server/issues/24 was moved from in progress to Done in https://github.com/orgs/home-assistant-libs/projects/1 and also was closed).

I’m developing a device which has multiple endpoints, and one of them is a Window Covering endpoint, so to test window covering I modified esp-matter example with this patch. I tried to commissioning the esp32 flashed with this firmware, but suddenly the process stops ("no more logs in esp32 console, neither in Matter Server logs), an my android phone the Google service for commisioning a matter device only says “A error occurred” and lastly, at the integrations page, the Matter integration says “Retrying configuration: Matter client not ready”.

Here there are the logs from the matter server: core_matter_server.log And here is the error log shown in Home Assistant Core which I think that is the reason why the Matter server is restarting constantly.

Home Assistant Core Error log

Logger: homeassistant.components.matter
Source: components/matter/__init__.py:127
Integration: Matter (BETA) (documentation, issues)
First occurred: 23:05:42 (9 occurrences)
Last logged: 23:14:30

Unexpected exception: Value {'TLVValue': 31, 'Reason': None} of type <class 'dict'> is invalid for type, expected value of type <enum 'Type'>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/matter/__init__.py", line 127, in _client_listen
    await matter_client.start_listening(init_ready)
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/client.py", line 289, in start_listening
    self._handle_incoming_message(msg)
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/client.py", line 328, in _handle_incoming_message
    self._handle_event_message(msg)
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/client.py", line 346, in _handle_event_message
    node = MatterNode(node_data)
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/models/node.py", line 212, in __init__
    self.update(node_data)
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/models/node.py", line 299, in update
    self.endpoints[endpoint_id] = MatterEndpoint(
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/models/node.py", line 57, in __init__
    self.update(attributes_data)
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/models/node.py", line 186, in update
    self.set_attribute_value(attribute_path, attribute_value)
  File "/usr/local/lib/python3.10/site-packages/matter_server/client/models/node.py", line 177, in set_attribute_value
    attribute_value = parse_value(
  File "/usr/local/lib/python3.10/site-packages/matter_server/common/helpers/util.py", line 223, in parse_value
    raise TypeError(
TypeError: Value {'TLVValue': 31, 'Reason': None} of type <class 'dict'> is invalid for type, expected value of type <enum 'Type'>

I even tried to commissioning the device first to Google Home and later share the device from the app to Home Assistant, but same problem happens.

Although that error, later after reinstalling home assistant to ensure is a clean install, I was able to commissioning the light example without any problem.

About this issue

Original URL
State: closed
Created a year ago
Comments: 24 (10 by maintainers)

Most upvoted comments

I can help with that if you need it!

Diegorro98 on Apr 24, 2023

I was just about to tell you that. That is exactly what we need, thanks!

marcelveldt on Apr 24, 2023