Skip to content

OTA update in ZHA #7

@pvvx

Description

@pvvx

OTA update in ZHA.

Zigpy OTA-Configuration

The "configuration.yaml" file must have a directory assigned to the OTA files and the "ZHA Toolkit" installed.

For example, the directory name will be: “/zigbee_ota”

zha:
  zigpy_config:
    ota:
      enabled: true
      path: /mnt/nvme/pvvx/zigpy_ota
      extra_providers:
        - type: z2m
          url: https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/index.json
        - type: z2m_local
          index_file: /zigpy_ota/index.json
        - type: advanced
          path: /zigpy_ota
          warning: I understand I can *destroy* my devices by enabling OTA updates from
            files. Some OTA updates can be mistakenly applied to the wrong
            device, breaking it. I am consciously using this at my own risk.  

Place the new FW version files "*.zigbee" or "index.json" from bin into this directory ("./zigbee_ota"). To download OTA files from Github, use the raw link!

Restart ZHA (preferably the entire Home Assistant).

Update in new versions of Home Assistant:

image

image


To create an index for the Zigbee update file for any device, use the ZigbeeTLc Index Configurator for Zigbee OTA utility. File uploads support local files and links. To download OTA files from Github, use the raw link!


To restore to BLE, use the Zigbee OTA file with the same number device from: https://github.com/pvvx/ATC_MiThermometer/tree/master/zigbee_ota

After running Zigbee OTA, be sure to delete this file or files from the update directories for Zigbee OTA and completely restart z2m/zha. Otherwise, with the new Zigbee firmware, this update in BLE will work again.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions