#SSD Swap an Raspberry Pi 4

1 messages · Page 1 of 1 (latest)

sacred flare
#

Hey, I want to switch to a bigger SSD. First I installed HA on the new SSD and restored a backup. But then i learned i have to pair all my zigbee devices again because i dont have the key (no coordinator backup jason becaus of old installation). During that i also learned that my old ssd only runs on the usb 2.0 port and the newer one on the usb 3.0 port.

So because of the zigbee issue i decided to clone all the partitions on the new ssd. turns out: i dont get it running. it never appears in my router, i cant connect to it. i dont have an idea how to solve this. but maybe you?

muted dome
#

Can you connect a keyboard and monitor and check what you see?
What stops you from starting the old install again and creating a new backup?

sacred flare
#

not at the moment, dont have any micro hdmi cable or adapter.

muted dome
#

You need this to properly debug a pi.

sacred flare
#

yeah i know but so far i dont have it.

#

the fact that i have to setup my whole zigbee network again stops me

muted dome
#

You really shouldn't need to of you have a full backup.

sacred flare
#

i could not control a single device. i found out, that i need the coordinator_backup.json with the key. but i dont have it

#

i still habe the old installation. it is no problem to get it running again. but what data do i need of it

muted dome
#

Try find / -type f -name "*backup.json" via the SSH addon on the old install.
Generally a full backup is all you need.

sacred flare
#

i already did that

#

i flashed ha and restored a fresh full backup.

turns out: cant controll devices.

muted dome
#

Cloning the disk should also work if done properly. I'd recommend dd.

#

Make sure to reboot after restoring a backup.

sacred flare
#

i did it with dd

#

i rebootet a lot of times 😦

muted dome
#

I assume you use Z2M? What did it say in the log? Please also share the result of the command above.

sacred flare
#

but: i had to switch usb ports between zigbee dongle and new usb.

#

i cant tell you right now because i have the cloned disk which i cannot reach atm

muted dome
#

The port shouldn't really matter if you use a proper by-id path.

sacred flare
#

at the moment i am running the cloned thing which i cant connect to

muted dome
#

I can't really help troubleshoot why without you being able to run commands.

sacred flare
#

i only have this error out z2m (yeah you was right) saved: z2m: Publish 'set' 'state' to 'Arbeitszimmerlicht' failed:
'Error: ZCL command 0xd0cf5efffee6e6e7/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (8) Error: waiting for response TIMEOUT)'

sacred flare
muted dome
#

You need to see something to know why the cloned disk fails to boot.

#

The command above you should run on the running system with the old SSD.

#

i found out, that i need the coordinator_backup.json with the key
What made you think that? It looks like your Z2M is running.

sacred flare
sacred flare
muted dome
sacred flare
sacred flare
muted dome
#

You use a extension cable, right?

sacred flare
#

no in that case it was usb 2.0

muted dome
sacred flare
muted dome
#

Your Z2m would not be starting without a proper config. Please check interference first. If you want to find the file run the command above.

#

Or just grep -sR "network_key" /.

sacred flare
#

typo in first command, "jason"..

muted dome
#

Weird. Try ls -lah /config/zigbee2mqtt/.

sacred flare
muted dome
#

Well there is your Z2M data.

sacred flare
#

but the network key is not in that config

#

so no idea how that data should help me

muted dome
#

But Z2M is running right now, yes?

sacred flare
muted dome
#

Then go to Settings > Tools > Request Z2m backup in its GUI.

#

I'd also like to take a look at that configuration.yaml.

#

cat /config/zigbee2mqtt/configuration.yaml.

sacred flare
#

in between there is a big pile of devices..

muted dome
#

Maybe it's set in your addon settings instead.

sacred flare
#

you mean this?

muted dome
#

Yes. Weird.

sacred flare
#

chatgpt says that network key is only findable in newer versions. i dont know. i think i use z2m since early 2023 oder early 2022

muted dome
#

My memory isn't that good to remember things like that but ChatGPT likes to hallucinate.

maiden hamletBOT
#

ChatGPT and other "AI" systems do a fantastic job of generating well structured, convincing looking answers... that are either totally garbage or, if you're lucky, have subtle flaws. Don't use them to "help" others, and don't use them yourself.

sacred flare
#

but so far it is well hidden.

#

so but you say: i dont need that key. it should be in the full backup anyway, right?

muted dome
sacred flare
#

i have no clue what i am looking at 😄

muted dome
#

Basically you're not just restoring but also upgrading a very old installation in the process.

muted dome
sacred flare
#

so it was and it is not anymore?

muted dome
#

Please try

grep -i "key" /config/zigbee2mqtt/configuration.yaml

Censor what you need to.

sacred flare
muted dome
#

I don't understand. Does stat /config/zigbee2mqtt/configuration.yaml show that the file was recently used?

sacred flare
muted dome
#

I really cannot remember it ever being optional.

sacred flare
#

but when there is a default key, why should i have to put it in the "new" config of the new system? would expext that it would work anyways with defult key

muted dome
#

Maybe the new version's migration tool didn't account for a empty one. I cannot tell you. What does it say exactly?

sacred flare
#

and i would not exclude the idea of interferencen. cause like i said: the old ssd and zigbee config use different ports than the new ssd

#

What does it say exactly?
what dou you mean?

muted dome
#

It's very finicky as you saw in the video. An inch can make all the difference.

sacred flare
muted dome
#

i have to put it in the "new" config of the new system?
Where? What prompts you to do that?

sacred flare
#

right here: "network_key:"...

image.png
#

but maybe i am on the wrong path and its just hallucination

#

what would yo do? stick to the cloned version and buy an adapter or flash ha on the ssd, restore the backup and try something with a cable extension or something like that?

muted dome
#

I'd probably attempt the clone again and try to make it boot. Alternatively try to upgrade your current old system and then do the backup and restore.

#

But if you just want to test then go to the frontend and see if you can find the network key in the settings there.

sacred flare
#

oh i think i cloned it three or four times so far

sacred flare
#

yeah thank you so far. i have to sleep now and will try tomorrow some things. thanks for your help man!

#

if i reach something ill let you know

sacred flare
#

Update: After updaten my whole HA system i finally found the keys file. but turns out: i do not need it. zigbee works with the restored backup. But you were also right. interference with usb 3.0 has been the problem here…

#

i now have a problem with my pi case :D…but it is solvable. thanks a lot for your help @muted dome

#

and: i am tidying out my flat at the moment and i found a micro hdmi to hdmi adapter xD. i never used it; i did not buy it. i got it from work years ago and i just dit not remember..

turbid stag
#

Esphome