[Matter] Error setting up node, '>' not supported between instances of 'NoneType' and 'int'
Describe the issue you are experiencing
Matter device (Pergola controller) and it's endpoints are recognized correctl.
Clusters on Endpoint 3 Device Type(s): Color Temperature Light
No entity is created for the endpoint (RGB Light)
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Matter Server
What is the version of the add-on?
8.1.1
Steps to reproduce the issue
- Error after every start. RGB Light of the device is not recognized correctly.
...
System Health information
System Information
| version | core-2025.11.1 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| container_arch | amd64 |
| user | root |
| virtualenv | false |
| python_version | 3.13.9 |
| os_name | Linux |
| os_version | 6.12.51-haos |
| arch | x86_64 |
| timezone | Europe/Berlin |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| HACS Data | ok |
| GitHub API Calls Remaining | 4987 |
| Installed Version | 2.0.5 |
| Stage | running |
| Available Repositories | 2434 |
| Downloaded Repositories | 19 |
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 | Home Assistant OS 16.3 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2025.11.2 |
| agent_version | 1.7.2 |
| docker_version | 28.3.3 |
| disk_total | 30.8 GB |
| disk_used | 16.5 GB |
| nameservers | fd00:2a2a:2b2b:2c2c:2a2a:2b2b:2c2c:2a2a, 192.168.6.2 |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | kvm |
| board | ova |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Terminal & SSH (9.20.1), Zigbee2MQTT (2.6.3-1), Mosquitto broker (6.5.2), File editor (5.8.0), OpenThread Border Router (2.15.1), Matter Server (8.1.1), ESPHome Device Builder (2025.10.5) |
Dashboards
| dashboards | 3 |
|---|---|
| resources | 3 |
| views | 5 |
| mode | storage |
Network Configuration
xxx
Recorder
| oldest_recorder_run | 26. Oktober 2025 um 12:14 |
|---|---|
| current_recorder_run | 12. November 2025 um 18:44 |
| estimated_db_size | 730.83 MiB |
| database_engine | sqlite |
| database_version | 3.49.2 |
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Logger: homeassistant.components.matter
Quelle: components/matter/adapter.py:142
Integration: Matter (Dokumentation, Probleme)
Erstmals aufgetreten: 18:44:41 (1 Vorkommnis)
Zuletzt protokolliert: 18:44:41
Error setting up node 1: '>' not supported between instances of 'NoneType' and 'int'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/matter/adapter.py", line 142, in _setup_node
self._setup_endpoint(endpoint)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/matter/adapter.py", line 251, in _setup_endpoint
new_entity = entity_info.entity_class(
self.matter_client, endpoint, entity_info
)
File "/usr/src/homeassistant/homeassistant/components/matter/entity.py", line 136, in __init__
self._update_from_device()
~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/components/matter/light.py", line 382, in _update_from_device
if min_mireds > 0:
^^^^^^^^^^^^^^
TypeError: '>' not supported between instances of 'NoneType' and 'int'
Additional information
No response
Please attach your diagnostic file
https://www.home-assistant.io/blog/2024/02/07/release-20242/#matter-diagnostics-and-actions
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.
Update / Solution:
I have successfully resolved the "unsupported color mode xy" issue for my Pergolux controller with a custom patch.
The Problem: The Pergolux Matter implementation sends state updates in XY mode but doesn't report XY as a supported capability. Since HA 2025.3, this triggers a strict validation warning and can cause the light entity to malfunction or disappear.
The Fix: I’ve updated my Gist with a multi-layered approach:
Capability Injection: Manually adds XY to the supported color modes during entity discovery.
Mode Fallback: If Home Assistant still rejects XY for the specific entity, the patch dynamically reports the state as HS (Hue/Saturation). Since the values are converted correctly, the UI stays functional and the validation warning in the logs is silenced.
Stability: Added None checks for color/temperature attributes to prevent crashes.
How to apply:
Copy the official matter integration to /config/custom_components/matter/.
Replace light.py and manifest.json with the files from this Gist: https://gist.github.com/tchristian1103/9a3eb414a3a98343fc0b755ba8a8d6f8
Restart Home Assistant.
I've tested this on the latest 2025.12.3 release, and the "unsupported color mode" errors are completely gone.