#okay I started with `zigpy radio ezsp

1 messages · Page 1 of 1 (latest)

lyric summit
#

Traceback (most recent call last):
File "/home/wendelin/.local/pipx/venvs/zigpy-cli/lib/python3.11/site-packages/bellows/uart.py", line 268, in reset
return await self._reset_future
^^^^^^^^^^^^^^^^^^^^^^^^
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/home/wendelin/.local/bin/zigpy", line 8, in <module>
sys.exit(cli())
^^^^^

tepid mist
#

if not on coordinator fw it will error

#

also you may need to add --baudrate 115200 in there

lyric summit
#

I did flash it before back to coordinator. Ok I will try with baudrate thanks 🙂

tepid mist
#

after radio

#

zigpy radio --baudrate 115200 ezsp

lyric summit
#

ok now it looks better. Another error but zigpy.exceptions.NetworkNotFormed: Node is not part of a network

#

so I run form now

#

let's see 🙂

#

works 💪

tepid mist
#

now backup

#

edit the ieee and restore.

lyric summit
#

just some random hex numbers?

tepid mist
#

yeah jus tmake sure it doesn't match anyting else, likely can just change 1 or 2 at the end of what it is now

lyric summit
#

worked, now I flash back to router 😄

#

So now I integrate it again into my zigbe network? And the existing device is actually the sky connect?

tepid mist
#

yes

lyric summit
#

It is found by zha but it automatically uses the same device again 🤷‍♂️

tepid mist
#

hmmm. out out of ideas. for now. if anything pops up to me I'll chime in, hopefully someone else may have thoughts.

lyric summit
#

what about migrate radio -> reconfigure current radio and restore backup from before I added the sonoff router?

tepid mist
#

I think you'd be better served by restoring an HA backup from before the router was added

#

the devices are not really kept in the coordinator backup

lyric summit
#

I don´t think there is one. I was thinking about this

tepid mist
#

they exist in HA and the zigbee.db

lyric summit
#

I have a backup form tonight. But there was the sonoff coordinator. As far as I know it is not possible to migrate when the old stick is not found. right?

tepid mist
#

your sky-connect has the same network settings the sonoff did at the time of the migration

#

so you'd just need to restore, and then do a re-configure current radio, change the path and leave the network alone and you should be okay

#

(don't form new, or restore backup)

lyric summit
#

I'll try thank you

lyric summit
#

oh man 🙈 the whole afternoon 💩 I was now doing the backup restore multiple times. Always some unexpected errors. At the end it just works without errors. I have no idea what happens.

#

And now I did everything as you said. And sonoff is again overwriting my coordinator

#

😠 😢

#

I thank you so much for your help and patience, but it was not possible

cold quail
#

What are you using? cc2538-bsl.py?

#

If so, just add --ieee-address some:new:random:ieee:address when flashing and it'll write a new one

#

Your network will experience glitches if you have two devices with the same IEEE address, especially when one is the coordinator

lyric summit
#

I used zigpy-cli and used the method to restore a backup where I set the ieee

#

then I checked it with zigpy cli info and it did showed a different address

cold quail
#

That only takes effect if you're running coordinator firmware

#

Once you switch to the router firmware, the address written with zigpy-cli won't matter

tepid mist
#

its a sonoff-e

cold quail
#

Oh, I thought it was the -P 🤦‍♂️. Ignore me...