Help. I'm in a right mess

Configuration Zigbee
1

I attempted to add a Z2M coordinator as an additional network to ZHA and have lost my Zigbee config and connection to my Home Assistant Connect ZBT-2.

On trying to restart I got this error:

The system cannot restart because the configuration is not valid: Unexpected error calling config validator: 84:2e:14:ff:fe:5d:b6:44

The log shows this:

Logger: homeassistant.helpers.check_config
Source: helpers/check_config.py:217
First occurred: 1:36:33 PM (3 occurrences)
Last logged: 1:38:24 PM

Unexpected error validating config
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/check_config.py", line 217, in async_check_ha_config_file
    await config_validator.async_validate_config(hass, config)
  File "/usr/src/homeassistant/homeassistant/components/automation/config.py", line 328, in async_validate_config
    await _try_async_validate_config_item(hass, p_config)
  File "/usr/src/homeassistant/homeassistant/components/automation/config.py", line 306, in _try_async_validate_config_item
    return await _async_validate_config_item(hass, config, False, True)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/automation/config.py", line 220, in _async_validate_config_item
    automation_config[CONF_TRIGGERS] = await async_validate_trigger_config(
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, validated_config[CONF_TRIGGERS]
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/trigger.py", line 774, in async_validate_trigger_config
    conf = await platform.async_validate_trigger_config(hass, conf)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/device_automation/trigger.py", line 61, in async_validate_trigger_config
    return await async_validate_device_automation_config(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, config, TRIGGER_SCHEMA, DeviceAutomationType.TRIGGER
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/components/device_automation/helpers.py", line 119, in async_validate_device_automation_config
    await getattr(platform, DYNAMIC_VALIDATOR[automation_type])(hass, config),
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/device_trigger.py", line 51, in async_validate_trigger_config
    _, triggers = _get_device_trigger_data(hass, config[CONF_DEVICE_ID])
                  ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/device_trigger.py", line 34, in _get_device_trigger_data
    zha_device = async_get_zha_device_proxy(hass, device_id).device
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/helpers.py", line 1116, in async_get_zha_device_proxy
    return zha_gateway_proxy.device_proxies[ieee]
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
KeyError: 84:2e:14:ff:fe:5d:b6:44

Where do I go from here?

2

First question, why do you want 2 zigbee networks?

Next just restore the backup you made before embarking on such a big change.

3

Range.

I’m downloading last nights partial back up now. I don’t think that’s going to fix the problem.

I need some help tracking it down and making changes.

4

Having 2 networks will not help the range. Having a well designed mesh with well spaced routers will solve the range problems.

Just unplug your new coordinator and restore the backup. If it wont restore then do a fresh install and restore to that.

5

First try to uninstall Z2m. It is likely they are fighting for the same coordinator using different network parameters. Maybe this will allow ZHA to work again after a reboot.

And indeed, as said, two coordinators is 2 meshes = less routers per mesh = worse range.

6

Thanks for the help.

I’ve uninstalled Z2M but still get the error.

I’m not altogether encouraged by the IF in this message:

The backup will be restored. Depending on the size of the backup, this can take up to 45 min. Home Assistant needs to shut down and the restore progress is running in the background. If it succeeds, Home Assistant will automatically start again.

As regards the range, I’ve had to have two zigbee networks before. There is no overlap as the signals are not strong enough, so there’s no impact on speed and I get more coverage.

I’ve yet to find a zigbee router that can connect over the distance. Hence the two networks.

7

Zogbee radio’s, even the new powerful one from Nabu Casa, can’t reach very far due to the fact that Zigbee communication uses weak signals to preserve energy.

If you need long range, z-wave would be the better, but more expensive, protocol and there are other options too.

For Zigbee it is routers, routers or routers. Unless you want to set up a whole new network in a different place. Both networks will be entirely separate, each needing enough routers to reach the further away devices. The second coordinator would be near the new network, using ethernet to link to HA.Having two coordinators within USB distance is of no use.

I sure hope the backup will do, but I’m not confident unless you also backup your ZHA network settings every once in a while. I’m worries Z2M might have overwritten those if your current efforts did not get you furter.

IMG_1197
IMG_11971055×1567 123 KB

8

That’s exactly what I am doing. It’s worked before. I need to get it to work with the new Sonoff Coordinator I have.

Everything was restored in about 20 minutes, which is excellent considering the size of my setup.

Thanks for the help.

1 Like