How do we pass "i_understand_i_can_update_eui64_only_once_and_i_still_want_to_do_it" option

[pipiche38]

To restore an EZSP radio coordinator, how do we pass the option i_understand_i_can_update_eui64_only_once_and_i_still_want_to_do_it = true from the zigpy-cli command ?

[pipiche38]

When looking to the previous bellows cli, the command line was

sudo bellows -d /dev/ttyUSBX restore --i-understand-i-can-update-eui64-only-once-and-i-still-want-to-do-it -B backup.txt

is it the same approach for zigpy-cli ?

sudo zigpy radio znp /dev/ttyUSB1 restore --i-understand-i-can-update-eui64-only-once-and-i-still-want-to-do-it deconz-backup.json

[puddly]

You can pass it in the JSON via ezsp.stack_specific.i_understand_i_can_update_eui64_only_once_and_i_still_want_to_do_it. I would avoid passing it, however: just upgrade the adapter firmware to something more recent that supports writing the EUI64 to an NV3 token. Bellows will do this automatically and will throw an error if it isn't possible.

[Hedda]

I would avoid passing it, however: just upgrade the adapter firmware to something more recent that supports writing the EUI64 to an NV3 token.

FYI, the "Universal Silicon Labs Flasher" from Nabu Casa (written by puddly) can write IEEE address to firmware of Silabs adapters:

• https://github.com/NabuCasa/universal-silabs-flasher

  • https://github.com/NabuCasa/universal-silabs-flasher/blob/dev/README.md#writing-ieee-address

Note that the EUI64 address can only be written if the adapter already have a flashed Silabs EmberZNet Zigbee firmware on it.

Quote from universal-silabs-flasher README.md file:

Writing IEEE address

Ensure a target device running EmberZNet firmware has the correct node IEEE address:

$ universal-silabs-flasher \
    --device /dev/cu.SLAB_USBtoUART \
    write-ieee \
    --ieee 00:3c:84:ff:fe:92:bb:2c

The IEEE address can also be specified without colons: --ieee 003c84fffe92bb2c.

If the current device's IEEE address already matches the provided one, the command will not write it unnecessarily.
Depending on firmware version, writing the IEEE address can be a permanent operation. If this is the case,
you will need to upgrade the firmware on your adapter to a more recent release of EmberZNet or perform the one-time
write with --force.