-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"homeassistant: null" makes z2m fail to start #12340
Comments
Zigbee2mqtt configuration - Save, click OK and restart the add-in to return to normal. |
Thanks, but this won't make z2m 1.25.1 recognize |
Tried to replace 'null' with '{}' (an empty object) for the devices I do not want discovered in HA. This clears the error but the devices are discovered in HA. |
Can you provide your complete |
I made a simple example test installation. |
Hi, same problem here. I have fixed changing: Complete device configuration after fix, like follows: '0x00123c0001234d5f': Hope it helps anyone. |
Unfortunately this isn't the same. |
But at least it solves the problem, Zigbetomqtt starts, and everything works again. |
That is indeed what I stated in the next sentence. It is a workaround to get Z2M to start. I could also have commented the line. The effect would be the same. |
The issue is in the devices.yaml file as I think you have understood. Just to be sure.
|
Fixed now. Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
Thank you! |
Fixed for me too ! |
What happened?
After updating from z2m 1.25 to 1.25.1 it fails to start:
The offending setting is
homeassistant: null
as described here: https://www.zigbee2mqtt.io/guide/configuration/devices-groups.htmlSet homeassistant: null to skip discovery for this device
This no longer works.
What did you expect to happen?
"homeassistant: null" should continue to work.
How to reproduce it (minimal and precise)
Stop z2m.
Add
homeassistant: null
to a device.Start z2m.
Zigbee2MQTT version
1.25.1
Adapter firmware version
20220219
Adapter
Slaesh
Debug log
No response
The text was updated successfully, but these errors were encountered: