OTA Updates config?

Configuration Zigbee
1

Since HA 2024.2 or 2024.3 ZHA is able to update devices via the GUI and I read about some way to add a custom URL via the config like this:

z2m_remote_index: "https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/index.json"

I saw it in this pull request: OTA v2: provider and metadata rewrite by puddly · Pull Request #1340 · zigpy/zigpy · GitHub

So my question about that is: Do I still need a manual OTA config or do I need to make changes? Because with the z2m_remote_index there would be an option to finally update Hue devices, right?

My zha config still looks like this:

zha:
  enable_quirks: true
  custom_quirks_path: /config/zha/custom_zha_quirks
  zigpy_config:
    ota:
      otau_directory: /config/zha/zigpy_ota
      ikea_provider: true
      inovelli_provider: true
      ledvance_provider: true
      salus_provider: true
      sonoff_provider: true
      thirdreality_provider: true

All that got me a bit confused, because iirc with Z2M you are able to update Hue devices, why not with ZHA and a custom config.

2

To add the koenkk reository of firmwares you mention, you need to add this under ota:

      z2m_remote_index: https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/index.json

You should keep the rest too.

1 Like
3

Thanks, that worked :slight_smile:
I got updates for my Hue devices around 1-2 hours later.

About the ikea_provider: true and the other ones: are those to get OTA updates in general or only to have them installed automatically?

4

OK, how to change it for new providers & config in HA (in Log in old way you can see warning) ?
I used:

zha:
  zigpy_config:
    ota:
      extra_providers:
        - type: ikea
        - type: hue
        - type: z2m
          index: https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/index.json

But whole ZHA integration stopped working …

5

The issue was caused by using type: hue. Some sources also mention that using url or index is no longer supported, and that the Koenkk URL has become the default for the z2m provider.

My question is: how should the configuration be set up now? Is specifying z2m alone sufficient?