#yellow-archived
1 messages · Page 11 of 1
Kirkland has been the one with the missing/lost standoff
I sent some to @compact quartz who is on the same continent. He might be able to send you one.
I don't need any ... @upbeat gale and does. Knowing how rare they are. If I remove the SSD from my Yellow I'll tape the standoff to my forehead so I don't lose it 🤣
Now .. back to the fun ... exploring creating ESP Home devices
can't you 3d print one? as a last resort?
Good idea. I guess it is quite small, which makes it challenging. Using the same 3D file as used for the metal part probably doesn't work due to overhang etc. Would probably need a design which works well for FDM.
A resin printer could probably do it as well
Don't need to 3d print. Just use some plastic square stock and use self-taping screws from bottom and top. Or drill it through and use a small bolt all the way from top to bottom of the PCB. There are a lot of hack to skin that cat
Maybe. But if I can load a model, press print and be done with it I prefer that method 😅
@wary pivot hello, I flash the HAY system according to rpiboot, but after running rpiboot, no green light is displayed, and no disk is ejected from the computer. What is the reason for this?
Here's a video of the operation:https://drive.google.com/file/d/1Eb5oJ6X2YmHOMvAE49_EDJSPqkeeA2gX/view?usp=drive_web
Have you tried another USB-C cable? Some are for power only.
Yes, my USB-C can do data transfers and works well on other devices
You are using a Mac, right? Have you installed libusb and pkg-config with brew?
I really didn't install it. Are these two necessary to identify HAY CM4?
I don't use Mac, but they are mentioned in the install guide. And a missing USB library might explain the lack of communication
https://github.com/raspberrypi/usbboot#macos
you never need brew
especially on your private machine
its more harm than good to macos
Is MacOS good? 😆
yes it is. best regards, a macos user that last reinstalled his macos in 2012
Last Apple product I had was an iPhone 4 (without S).
MacPorts work very well.
while not that bad, its also not really good. I see it like HAOS, you don't touch the system and it runs fine for a veeery long time
Hi everyone
Just got my yellow, cm4 with 32g emmc and kingsman KM660 128gb nvme installed, boot up with usb installer, wait for yellow light up constantly, press the blue btn. After onboarding, everything still install on emmc in cm4, 128G nvmc can only be a data disk. Any idea which step was wrong ?
kingsman KM660 128gb nvme? Not finding it
not finding a more general result with "km660 128GB" either
Sorry, should be km600
I would just go with using it as data disk, to be honest. It's not worth the time spent to get a small advantage booting the whole thing from SSD.
Ok I see it now. Booting from SSD is finicky on Rpi, it could be this SSD
Cause the cm4 will be replace later, so I prefer to boot from ssd
I wasn't successful too with installing on ssd. So I installed to CM an moved it then to the ssd.
You can do this on the GUI
@wary pivot I had the same problem on the mac. I tried to re-update the eeprom, but to no avail
@wary pivot I also flash the HAY system according to rpiboot, after running rpiboot, no green light is displayed, and no disk is ejected from the computer. What else can I do
My other two HAYs worked fine, but one of them didn't recognize my SSD. I also updated the eeprom but it still doesn't recognize my SSD.
By the way, this unrecognized SSD can be used on my third HAY
I'm not using MacOS, so I just can refer to the usbboot documentation for Mac specific problems.
As the Raspberry Pi 5 is announced for October now, I'm curious when they will release a Compute Module 5 with that architecture and if it will still be compatible with the Yellow. The additional processing power would be nice. Time will tell.
That would be nice! And we should get ready for the active cooling mods 😅 i bet it'll warm the box more than the CM4
Yeah. Thermals might become a real issue with a CM5
They still sell the Rpi5 without heat sink by default, so it seems to be working with just air cooling.
But the system will be thermally restricted in term of performance I agree.
But I am pretty sure you get more performance out of the CM5 with the same cooling solution (as in, the new SoC has more performance per Watt dissipated, as the SoC is using a new, smaller process node)
And the Google Coral issue might be solved with the new SoC - at least the m.2 one. I don't expect the USB one to become stable.
Yeah I've seen Jeff's investigation 🤞
Now of course we only need to hope that they actually remain pin compatible 🤞 and no other weird incompatibility issue 😅
And that "someone" makes a new Yellow-5 HAOS image for it. I'm not looking at you 🤣
You could already add that to GitHub - just to get the rumours going 
Do you think the Yellow will be forward compatible with the CM5? the RPi5 was just announced so the CM5 will be coming. If the Yellow is compatible the 2X performance boost will be a perfect upgrade.
That's pure speculation
As long as the specifications for a new CM5 aren't released, nobody outside of the Raspberry Pi Foundation will know
No one knows until there is a CM5. Same as before RPi 5 was announced
As manufacturer, Nabu Casa should have knowledge
Time between RPi 4 and a CM4 was over a year
That's fine ... right now I average 4% CPU
If the CM5 is compatible, the Yellow will have very long life
How would Nabu Casa know? It's a carrier board for a CM4. No one knows what a CM5 would look at this point. There are many other carrier boards for CM4 and basically we can hope it would be compatible, but it's unknown until it exists
Even if not - look how long the CM3/CM3+ is around
The CM is OEM device and Nabu Casa is an OEM
It doesn't exist. Even on paper.
And if Nabu Casa would get involved earlier - there will surely be an NDA until release
Nabu Casa didn't know an RPi 5 was to be released afaik. The relationship isn't that close. CM4s were hard enough to get a hold of as it was 😅
I'll bet it exists in design specs and OEMs should have access to those specs so they can have boards available when the CM5 is released. NDA's 🤣 🤣 🤣 ... leaks happen especially with large eco system like the Pi
Go ask Eben Upton
But back into speculations: chances aren't too bad, the CM5 will be pin compatible. They stuck to the CM3 style for long, so I'd expect the new format to stay for a while.
yeah releasing 32 variants of a cm4, going through a long period where they were almost impossible to obtain (and still are) and then switching it up would be pretty bleak
There is info at the cnx-software blog about the Pi5... they have one. So that will be good sire for information about the Pi5 as they wil be testing it
Many influencers got pre-release Pi 5s
Pi states that the Pi5 will have at least an 11 year production guarantee
To dampen your expectations, Occam: I don't expect Nabu Casa to get a high priority at the Raspberry Pi Foundation. In sales numbers, I'd expect Nabu Casa to be a small player (without insights - so take this with a grain of salt), compared to others like Waveshare. (sorry cogneato and falstaff321
)
This is still a niche market/product
I'm an enthusiastic guy especially about excellent eco systems like HA + Pi
The Pi5 is based on 16nm tech so that should reduce the power/clock ratio so the higher clock won't increase power consumption as much. but an active cooler built into a nice heatsink is a $5 option. The Pi4 is based on 28nm
A lot of the I/O is now offloaded to a custom RP1 chip via 4-lane 16GB/s PCIe buss. The memory bandwidth is 2x the Pi4
hi there, i just received my Yellow Standard Kit from raspberrypi.dk, along with the apporved nvme 1Tb addone. Inserted the nvme ok, powered her on and now waiting. and waiting. and waiting. its been 15 minutes , noting coming up on the IP - I can see on my router the Yellow has been given an IP which is pinging. but IP:8123 is not loading.
Yellow led is flashing, as is Green less frequently . red solid on.
Is it just a waiting game while it downloads its updates?
It is best practice to do the onboarding without NVMe.
flip it. OK, will power it off and remove it and go again.
ok, doing it again now for 9 minutes and counting. no NVMe this time
Okay usual troubleshooting steps are:
a) check if CM4 is fully seated in its sockets (makes a satisfying click on install - this is very often the main problem, but unlikely with Standard versions)
https://yellow.home-assistant.io/faq/#my-home-assistant-yellow-appears-broken-no-led-is-lighting-up-what-can-i-do
b) check if the Yellow really has (unrestricted) internet access
c) connect the Yellow to a PC using the USB-C port and connect to the serial console to look for error messages
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
d) flash the installer directly to Yellow's storage by following option 2 of the following guide
https://yellow.home-assistant.io/guides/reinstall-os/
e) reinstall the CM4 firmware
https://yellow.home-assistant.io/guides/flash-cm4-firmware/
f) install HAOS without the installer by following the guide mentioned in d) up to step 8. Download the HAOS image from GitHub (the Yellow one, not the RPi4 (https://github.com/home-assistant/operating-system/releases/download/10.5/haos_yellow-10.5.img.xz) and flash it to the eMMC by using the program Balena Etcher for example
I don't know why d exists. I'd skip it.
I think that was for/from someone who altered the bootorder of the CM4 some time ago... 🤔
oh hmm
But flashing the OS directly would do the trick too, so you are right
yeah I'd think flashing the image is most direct
As long as they don't use the Pi4 image 🫣
right lol
I will modify it in the script of my book "The Home Assistant Yellow and me - by Austin Powers"

Just to be clear: The Software is not preinstalled, you have to use a USB stick with the HAOS installer. Did you follow https://yellow.home-assistant.io/poe-nvme/?
I hadnt done that, but the device is already getting an IP address, so it must already have some OS installed on it ?
Without OS/installer the yellow LED shouldn't flash, right? Raspberrypi.dk still sells the Standard with preinstalled/preflashed CM4.
i am getting double Yellow flashes, and single green ones. both about every second or so,. and a constant Red
according to their site, the Standard one is preinstalled.
Going to have to get a debug feed to see if logs saying anything.
the switchport its connected to definitley has internet - confirmed with a laptop
and the OS has obviously booted enough to get a DHCP request out.
if i flash a usb with the Yellow image from the Raspberry install creation utility, I can just overwrite the whole thing again. wont do that till i see logs first
The CM4 firmware can boot from network. I guess that is what got an IP.
Yeah if the yellow LED flashes then the OS is running. To get logs best is to hook up the serial console. There are how-to's for this as well: https://yellow.home-assistant.io/documentation/
how do you know?
He read the paper - it was blank
Arrghhhh!. Got serial working, couldnt see much. ping to google worked so he has In ternet connection. couldnt see anything wrong., tried a different browser : worked first time !. I don't know why Edge doesnt load it, but Chrome did.
thanks for the help and @wary pivot
Hi i finaly got a CM4 card yesterday after years of waiting 😦 i can not get Z2M wo work it will not connect to the port what am i doing wrong ?
i tried with and without multi protocol activater and deactivated
cant figure it out, ZHA is not installed or active
By using the Multiprotocol add-on you have installed a firmware, Z2M can't use directly.
so ok thanks 🙂 how do i remove it ? or i need to do an fresh install of HA ?
thanks ill try have a nice day
With the Zigbee only firmware you should be able to use Z2M with
port: /dev/ttyAMA1
baudrate: 115200
rtscts: true
adapter: ezsp```
With Multiprotocol you would need
```serial:
port: 'tcp://core-silabs-multiprotocol:9999'```
so i found Silicon Labs Flashe and installed it now i have yellow multi-pan in the discovered section but cant configure it 😦
do i need to have multi protocol deactivated or activated when trying this ?
Deinstalled
Everything ZHA or Thread removed and the Multiprotocol add-on deinstalled.
After that you can run the Flasher add-on
ill try again in a fresh install 🙂 with the above
so fresh HA install on the Yellow, Thread not installed, ZHA not installed, Multiprotocol not active. installed Silicon Labs Flasher, in the config of the flasher i set /dev/ttyAMA1, 115200, HW flow controll on verbose off and saved, then start it but then what ? nothing pops up anywhere or do i just install Z2M now ?
When the Flasher has finished without errors in the add-on's log, it can be installed and you should be ready to go with Z2M
so when i start it it rund for a couple of minutes then it shuts down
does it flash and turn off when done or does it have to run all the time ?
looks in the log as if it is sucessfull so ill keep it off 🙂
Wuhuu. Success 🙂
now i just have to delete all 40 + devices from the old Z2M and add them again on the yellow 😦
You can use the Multiprotocol add-on in the future, but Z2M would need some adaptions and it is all mostly beta at moment.
Before you Include everything new, you might ask the people in #zigbee-archived - maybe Z2M has a backup/restore method
yea i tried but didnt get it to work also i have a chance now to do the names better so there is more logic to it 🙂
thank you for your help ?

is there a certain CM4 board i need for the yellow purchase (it said it didnt include) so i didnt know what CM4. there is (going on amazon shows differnt CM4s ) so i want to make sure the right one
Preferrably one variant (the CM4, not the CM4 base board) with eMMC (16 or 32GB) and 4 or 8 GB RAM.
You need one with eMMC
Yes, it is a CM4. Yes, it would work. No, it isn't a model I would recommend (it has no eMMC).
cm4 is just a plug-in RPI4, but with some more HW configurations like onboard storage (EMMC)
it's the same chip
Hey, I have a YELLOW and I did buy the Aquara Humidity and Temperature sensor without the Aquara Gateway. I added one sensor with my Zigbee Home Automation.
But the sensor is out of the range of the Yellow's Zigbee signal... How can I fix that? ^^
Would it help to get rid of my Hue Bridge and add all Zigbee bulbs directly to Home Assistant? Can they spread the zigbee signal? ^^
Yes, indeed. Additional Zigbee routers (like most lightbulbs or plugs) create a mesh network and increase the range
Ah, damn... 😄 And thanks!^^
The Hue app is pretty good... Hmmmm ^^
We'll miss the scenes... 😄
Is it expected to see /dev/ttyAMA1 in the list of ls /dev/tty* for the onboard zigbee controller? I only see /dev/ttyAMA0.
I am migrating my existing RPi install using a HA Skyconnect controller to my new yellow.
That usually happens, if the wrong HAOS image has been used. If you used the RPi4 image, the Zigbee module will not show up
Aaah yes! That makes sense. I flashed this a while ago and I'm sure I accidentally used the RPi4 image. Easy enough to resolve that. Thank you very much.
Hi .. What fan did you use on your Yellow? Did you also have to change the heat sink?
Just a cheapy from aliexpress. And no, the new case I printed has the fan sitting above the stock heatsink.
Okay...thanks
Small question, why the order for yellow to Germany is removed (and is it permanelty)?
You might have to ask the distributor
I seem to be having issues restoring back ups on my yellow
it starts the process but seems to go on for way longer than expected ive left it for over 30 minutes and nothing happens
Restoring needs a lot of time sometimes. Just start it and let it do its job.
for how long though
are we talking hours/ days
ive left it over an hour and nothing happens either
Until the UI is responsive again. Depending on the backup size it can also take some hours.
It needs to download containers from the web as well, which can take quite a while at times. The Yellow(/CM4) CPU is not as fast as your typical x86-64 CPU...
And the Python method of decompressing archives seems to be quite slow, if I understood the forum/GitHub issues correctly.
ok thank you ill just have to turn the lights on with a switch for the moment 🙂
Any disadvantages of using Pi4+SkyConnect over Yellow(POE)?
MicroSD card instead of eMMC, a SSD would be connected via USB instead of m.2 NVMe
If I don't need lot of data storage, is there anything that would make the performance any different?
If used with CM4s with eMMC the read/write speeds are better than those of a micro SD card
Once HA is running, does it even make a difference on the day-to-day operation of devices?
In speed likely not - as long as you don't restart HA. In reliability, yes.
In reliability how?
MicroSD cards have a lower lifespan than eMMC
I'm just looking to test out HA and see what I can do. I may upgrade (Yellow/Green) later, in my case will I have any drawbacks? I just don't want any compatibility issues just because I am using a Pi.
There is no compatibility issue. You can create and restore backups between those systems
Awesome, just to clarify. When I do switch to Yellow, backup-restore will be seamless and I wouldn't have to reconnect devices or recreate automations?
If you use ZHA, correct (with Z2M I'm not 100% sure). You would just have to migrate the radio.
if you use Z-Wave, you'd probably need to do an NVM backup/restore at least as well, or re-pair things. not significantly different than migrating the radio in zigbee though
(well, or maybe moving a stick + doing a backup-restore in zwave-js-ui or stuff to keep the names or such)
If the stick or the HAT stays the same, you don't need to migrate the Z-Wave stuff
yeah, realized that after I said the first thing. mostly just saying "make sure you know that z-wave stores information on the dongle", heh
Hello. Need a bit of help here. I had to upgrade my CM4, and now everything is in place, homeassistant has been restored from the backup I did earlier and is install in the CM4 eMMC. However I would like to move it to the NVME. Which is now pretty simple to do from homeassistant directly. However it still holds my previous installation. Do I need to format the NVME first ? If so, how ? Or is homeassistant taking care of that when I select the « move data disk » option ?
You should erase it first. If I remember correctly, the NVMe will not show up for data migration, if an old data partition is present.
Well I can see it in the data migration tool. However I don’t have any other pc or usb adapter to connect the NVME and have it formatted. Tried with the HA terminal tool, but when I do « df » I don’t see it. I guess that’s because it’s not mounted.
If it is shown, you should be good to go
Thank you @wary pivot. Migration started… will see how it goes
That worked apparently !
swhere do i buy the CM4 (im kind of lost of what model) is there a place for current links for the CM4 (I just bought the yellow)
CM4 / eMMC 16 or 32GB and 8GB ram (is there a model number or link for that one)
wow theres so many choices
ha
what is a CM4 this is needed for yellow then
wait are CM4s not in stock
Yes. The model numbers for the variants you mentioned are as follows:
8GB RAM / 32GB eMMC / with WiFi: CM4108032
8GB RAM / 32GB eMMC / no WiFi: CM4008032
8GB RAM / 16GB eMMC / with WiFi: CM4108016
8GB RAM / 16GB eMMC / no WiFi: CM4008016
didnt know this is what is going on so to obtain CM4 hehe
They are hard to get in a decent variant sometimes
wow i thought a raspi was its original $35 hahahaa never even knew about the CMs (been out of the ras world a bit though)
haha crzy crzy
never orderd from germany to US hope its legit (thanks for the link @wary pivot
At what shop did you order?
welectron
Those are legit
Wow CM4's in stock in US. Never thought I'd see it. I waited almost a year for my Yellow pre-order and ended getting one w/ a better spec'd CM4 off Seeed.
Any hope for support for ZGP (Zigbee Green Power) devices in ZHA? It has been requested for more than a year?
Looking forward to any update on this
ZGP is not expected to be implemented soon.
So is the best course of action to just cancel my yellow pre order?
It depends
On?
@cobalt crane if you ordered one with a cm4 I'd wait at least another week or so. Mid October is the expected time for crowd supply to receive more which were sent mid September.
Thank you for quick reply. I will abandon ZHA then and goto z2m instead. I know that works
Hello everyone. is it possible to use the bluetooth that is my cm4 module in yellow? (CM4008032)
In theory yes. But the model you mentioned has no WiFi and Bluetooth
Okay. it would otherwise have it. is there a possibility to see it through HA
If it had one, HA could see it. But the results with an ESPHome BT Proxy are better in my experience
lol.. it's my fault had misread but yes it doesn't have wifi/blue.. is there a good way to get bluetooth
sorry
is not quite so strong in it. esphome which module should I use there?
You could use one of the recommended BT adapters (https://www.home-assistant.io/integrations/bluetooth/#known-working-high-performance-adapters) or ESPHome BT Proxies (https://esphome.io/projects/?type=bluetooth)
The Olimex PoE Module has some performance advantages, the M5Stack Atom Lite is in an enclosure and very small and good to hide
Thanks a lot, I'll look into it. probably believe that esp but just have to see the others
I'm using the M5Stack Atom Lite. Powered by USB-C and included via WiFi
and that's where I was dropped off🤣🤣🤣
If you have more questions, the people in #bluetooth-archived can help with details
thanx
When migrating data to the NVMe drive, is everything moved over, or is boot/OS Data still on the eMMC?
I try this option, but get errors in UART saying that dd is already running
Advanced: Forcing installation onto the NVMe SSD when using CM4 with eMMC:
Press the blue button while the yellow LED is on constantly (during the 5s window, see next step).
The Boot/OS part stays on the eMMC
Is there a trick to getting everything migrated to the NVMe drive?
or a fresh install?
Wiping the eMMC and doing a fresh install to the NVMe. But the installer sometimes fails with the button method, so you might have to do it by hand.
But it would be just a slight advantage, if changing the CM4 is expected.
There wouldn't be much of a speed difference with the OS directly on the NVMe?
No.
That's not so bad then, I may just use the standard install then. What would be the method of installing by hand? Just using the Pi Imager to write HAOS 10.5 RPi 4/400 direct to the NVMe?
If you do that, you would loose the Zigbee module for example.
You would have to flash the HAOS image for Yellow (from GitHub) to the NVMe and to wipe everything from the eMMC.
It would basically be Option 2 of this guide, except of the Raspberry Pi Imager part. You would have to wipe all partitions on the eMMC and to use Belena Etcher (for example) to write the Yellow HAOS image to the NVMe.
https://yellow.home-assistant.io/guides/reinstall-os/
ok, that makes a lot of sense. I may give that a shot in the event I want to migrate to a new CM4 with ease in the future
Just received the Yellow today, so I've got time to get it prepped before I decide to migrate
But in my opinion, it is not worth the hassle
Does the NVMe slot not make full use of the drive speed?
When changing the CM4 you can create and download a backup, start with a fresh install and restore from backup (with some patience - it takes quite some time)
No, it (usually) doesn't. The CM4 provides 1 PCIe lane to the m.2 slot. Some common NVMe can use 4 lanes, for example,
The read/write speeds are faster than eMMC, but they will not use the full drive potential
ok, I was curious about that, I may just go the easy route then 😄
Thank you for all the help!
When you start with a new CM4, you likely should also wipe the NVMe. Old installs can cause problems sometimes. (if you go the backup/restore route)
Good to know, thanks
If you're going to run an NVMe then a small eMMC is OK to host HAOS. Your data will be on the NVMe if you move it. I have an 8GB CM4 and run about 1.5GB in use and I have a lot of add-ons running . I'd get a 4GB if I ordered
now
👍
Oh, @clear prism - would be cool if you could give some feedback about the restoring of an uncompressed backup. I wonder if it is really the decompression method or downloading components and add-ons, what takes so long.
Even the compression was taking a really long time, my old host is a dual Xeon with 400gb RAM, full SSD array, and was still taking 30 minutes to compress a 4gb install down to 1.1gb. I stopped the restore at the 6 hour mark yesterday because I thought it was hung up. Turning off compression made a really big difference
And for the record, downsizing to the HA Yellow performs just as well as before, I ended up going with the full NVMe install method
Thanks for being our test guinea pig for the uncompressed backup restoration! 👍
I should have put that in quotes 😆
No problem, thanks for guiding me in the right direction. I would imagine the gzip would go a lot faster, but it's single threaded, so only one core gets tasked to do the compression
400 GB of RAM!!?? WTH are you running on that?
Home Assistant 😝
Yeah .,.. for the whole city
Thats a lot of movies
Depending on the size of the home 
Own ZIP code? 😆
I ran an office with 75 employees on 10 servers on 96GB RAM stack
I've got a few people that I share my library with, the only solution was to spin up something equivalent to a Netflix server node😂
Dell?
how many VMs?
Moved everything to the Azure cloud with path redundant fiber
Server room is now nothing but routers, switches, patch panels and storage. Even the phone system is virtual except for the headsets
HP, down to 2 VMs now that HA is offloaded onto a dedicated box. Looking to downsize due to electricity costs of running a pile of servers 24/7
Got a rackmount synology that I want to move everything to, and have it run all my docker containers. Rather than having a SAN/compute server setup
electricity cost ... yeah .,,, 30 or 40 AMP service to your server is a bitch
My fully redundant Dell stack had two 30 AMP feeds and couple of big commercial UPS
Wow, I am not at that stage, I never exceeded a 15 amp circuit. Most I will consume in a day is 10kwh
My stuff was old with lot of spinning disks everything was duplexed for redundancy
So much off topic and I didn't get smacked down yet ... good night
Makes sense, a business loses money due to lost time when servers are offline. It would be stupid of me to have a failover cluster of my Plex server though 🤣
haha you as well
If you insist, I can arrange something for you 🤣
You been on a break? 🤣
LOL

weirdly enuff cant access homeassistant.local anymore 😅 I did set a static IP like a week ago but everything still worked fine until today 🤷♂️
Oh shoot actually even IP doesnt work lmao wtf XD
Cloud access still works
Did you set up some SSL stuff?
nope
Omg dont tell me its Edge doing it with its stupid new beta vpn feature... because im using the http:// url
😒 nvm sorry for bothering lol
Glad, you found the issue
Edge ... is like a fungus that just wont go away
I just bought a yellow kit with power supply and put it together. I got up to the point of plugging it in and watching the LEDs. But when I did, none of the LEDs lit up.
Already tried another outlet, reseating the compute module, pressing the blue button and try button.
Anyone have an idea what to do next to troubleshoot the issue?
I have an outlet tester with a look voltage mode and it appears the barrel Jack is receiving power.
If you are sure, the CM4 is fully seated in its sockets (makes some satisfying clicking), it might be a hardware issue.
Contact Nabu Casa's Support at yellow@home-assistant.io in that case.
Ok, thanks. I'll try re-seating one more time before contacting support. I wish there was a led that would confirm the yellow board was receiving power but the CM4 was not.
There is a LED for power on the Yellow board
Should that led light up if the CM4 is not seated?
It depends on the CM4 afaik
Ok. That's what I mean, I wish there was an extra troubleshooting led on the yellow that would always light up even if the CM4 was not installed.
@wary pivot thank you. It wasn't seated after all. I'm certain I heard a click the first time I installed it. But decades of "never touch anything but the corners of a PCB with your bare hands" and "be very delicate with computer components" have betrayed me. I tried again, with a lot more force, and heard the click sound I was supposed to hear. It was definitely louder than the first click I thought I heard. That felt way more violent on the board than I thought I should be.
It's lit up and setting up now.
I'll alter my suggestion then. Maybe instead of another LED what the Yellow could use is a big sticker on the bottom of the PCB (so you know it's safe to touch) and a rectangular piece of cardboard cutout so it form fits to the top of the CM4.
Then it would be much easier to say it's going to take a lot of force.
Also, is that connector a latching type? i.e. Where once it's seated it can't fall out on its own? Because that would be the other thing the documentation should mention if true. Because the connectors look so small I could not imagine the click being something akin to a buckle connecting them together. The connectors looked as if the CM4 would just sit on top of the connectors and be held down by the mounting preasure of the heatsink's pins.
Well, it kind of is, if I understood you right. But the "can't fall out" hasn't totally been the case. Early batches with preinstalled CM4 had issues with "deseating" during shipping. That's why later batches got the screws for the CM4
Hi, trying this install on a cm4 lite with an emmc installed.. how do I see the logs of what its doing?
https://yellow.home-assistant.io/poe-nvme/
My emmc had windows on it before and I wasn't able to erase it.. will it automatically wipe ie for me?
It needs to be an NVMe, not an eMMC in the m.2 slot
An existing OS installation might cause problems
ok. Any easy way to wipe it using the yellow?
You could use usbboot to get access to the drive and delete the existing partitions.
Option 2 leads that way.
That way you also wouldn't need an installer USB-Stick.
The imager should overwrite the old Windows installation
It's very handy to have a M.2 to USB adapter. Then you can use Windows Disk Management to delete all partitions
I just got my home assistant yellow, followed all steps here: https://yellow.home-assistant.io/power-supply-nvme/ and imported a backup from my VM. Everything works great except the very last steps "Select the Move datadisk option". I get "No suitable storage found". Any idea how to start troubleshooting? Hardware wise, everything seems fine. But hassos doesn't seem to recognise the nvme.
There are five possible options i could imagine at moment:
a) the NVMe is incompatible - 
b) the NVMe is not empty (enough) - wipe all pre-existing partitions on it before installing it
c) the NVMe is smaller than the eMMC (not likely) - 
d) you are using a CM4 Lite without eMMC storage. In that case it is already using the NVMe and no need to move datadisk
e) the CM4 is not fully seated in its sockets
seems that my skyconnect is having trouble and I'm out of clues.
I've Multiprotocoll installed and zigbee is running fine, but thread doesnt.
I also cant reconfigure it via "hardware"
I only can read there: "The muliptotocoll support is already installed for a other device" (translated from german)
The Multiprotocol add-on only supports one radio at a time. The Yellow's or the SkyConnect's.
I have only one SkyConnect installed.
And you are using a Home Assistant Yellow, right?
No. I'm using a SkyConnect with a HASS-VM (official image) on an Unraid Server.
Then you are in the wrong channel. This is the #yellow-archived channel. You might want to ask the people in #zigbee-archived or #thread-archived
oh, then excuse me, please. Thank you.
Good morning everyone,
I'm trying to do a clean install of HA on my Yellow to prepare it to sell.
I have a CM4 4GB Wifi Lite and an NVME drive.
When it was brand new, I had quite the time installing and needed help. Apparently the installer needed to be modified to resolve boot order issues. The modified installer provided to me in this chat worked at the time, but it's not working anymore 😦
Neither is the installer published through the raspberry pi flash tool.
I've formatted the drive as ExFat - thinking the installer should identify it and format it. If that's incorrect please correct me.
Can anyone give me direction?
You can use Option 2 of this guide, but do not use the part with the Raspberry Pi Imager:
https://yellow.home-assistant.io/guides/reinstall-os/
Use Balena Etcher for example and flash this image to the NVMe:
https://github.com/home-assistant/operating-system/releases/download/11.0/haos_yellow-11.0.img.xz
If firmware was updated and boot order was correct during previous install, I should be able to skip most of these steps and just install directly to the NVME, no?
What I suggested was basically skipping installer steps and flash the OS directly
That didn't help, looks like. I've given it an hour.
What's interesting is the yellow light flashing pattern was different. Went to rapid double flashes which I haven't seen before - but it's still flashing slowly: yellow yellow green.
Will let it sit a little longer then not sure what to do next.
There are only green signals with USBboot. And on the next start it is the OS with the onboarding screen
Well, there was no USB plugged in - so why yellow/green like USB? I'm so confused 😦
You followed the guide option 2?
Sorry, no I didn't. I understood those steps to be required to update firmware and boot order. Because this CM4 was previosly running HAOS off NVME I thought I could skip. I can try to do those.
Just ignore the part with the RPi Imager and flash the image I linked with Balena Etcher
Or remove the NVMe and flash that image with a m.2 USB adapter
Yes, I flashed the OS directly to NVME from a USB M.2 adapter.
I tried option 1 and it appears to have worked with the standard installer. Weird.
As long as it is working now...
Hello I just got my yellow and im kind of confused how to use it some ppl told me that I can connect it directly to my aqara d1 switch and some other ppl fold me no I need a hub to do so can anyone help me with that please?
Zigbee devices can be paired with the Yellow directly. But some devices need workarounds with ZHA events, as they don't create devices in HA.
So no need for the aqara hub
I got some d1 switches and aubess device
not a consumer of the HW HA equipment, but am curious if anyone knows - what base flavor/distro does HAos run? and does it have a package manager?
and / or does the base OS have an alsa/pulse module loaded?
HAOS is based on Buildroot
hey all! just finally got a CM4 and have a few questions, basically all because I am Being Bad and trying to install onto a USB drive lol
(I know this is not ideal but I got a Lite CM4 and I can't go buy an NVMe drive just yet because I'm sick and don't want to get others sick, but I want to play with Yellow because I'm super bored lol)
basically, the problem I'm having is that the yellow LED never turns on at any point during boot. first I tried flashing the installer image and booting it with and without a secondary USB drive (to act as an install target) with no luck. then, because I figured that maybe the installer was getting confused by there being no eMMC or NVMe storage, I just downloaded a Yellow OS image directly from GitHub releases and flashed that directly to a drive.
based on https://yellow.home-assistant.io/guides/reinstall-os/ I expected this to work, because eMMC boot will fail (there isn't any) and then NVMe boot will fail (there's nothing installed) and then USB boot will proceed as normal, except that it will boot the actual OS instead of the installer. however I still don't get the yellow LED at all.
I would expect it to flash at least a bit even if boot failed - but maybe boot fails so early that the LED stuff hasn't been initialized yet...? like e.g. if the initramfs can't find root to mount because it's expecting a non-USB root or something like that. but I don't know enough about the boot specifics to really diagnose, which is why I'm asking here
note that the problem is NOT CM4 board seating AFAICT, because I consistently get green and red lights.
based on https://yellow.home-assistant.io/guides/yellow-leds/ the system seems to be stuck in bootloader mode, but I'm not sure why. note that I skipped anything involving rpiboot or jumper pins because IIUC that's mostly to override the boot order, but the normal boot order on my board should get to USB boot ok.
while writing out all this I just noticed that I don't need specialized hardware to dump serial console logs, so I'm going to try that now.
clarification on this: it looks to me like the red light and green light turn on at the same time, then the green light turns off briefly and turns back on, and it stays on until power is removed. this pattern is not consistent with any entry in the table at https://www.raspberrypi.com/documentation/computers/configuration.html#led-warning-flash-codes.
Best way to troubleshoot would be the USB-C serial console. Look at the boot messages. CM4 Lites are a pain - at least some models needed a firmware update
oh that's great to know
yeah I'm getting the serial console working right now
took a detour to mess around with strace
literally no serial console logs in screen
I'm going to try a firmware update
hrm. same behavior but now I'm seeing blinking on the Ethernet jack... not sure if that wasn't there before or if I just didn't notice it lol
I'm letting nmap crunch through the network to see if it can detect Home Assistant running
the USB drive is USB 2.0 and probably pretty slow... so maybe it's just taking forever to boot?
hrm. according to my router (which is proprietary garbage that I don't really trust...) I'm seeing 10 broadcast packets outbound from the Yellow
@full field … do a reset all =red+blue button pressed for +15 seconds. NO yellow led will flash. Remove power. Insert USB stick with HA install image. Ensure network cable is inserted and access to internet. Power on again. Now Yellow will read from the USB drive and install HA.
@full field if you are stuck in endless reboot it is most likely because HA doesn’t support your hard drive (https://yellow.home-assistant.io/faq/#which-ssds-are-not-supported for supported SSD nvme).
The attempt (it sounds like) is to boot from a USB drive as there is no NVMe SSD. So if trying to install from USB to USB...not sure that will work.
I’d like to update to HAOS 11 but I still just see Version 10.5 to update to, anyone having the same problem? I’m still on 9.5 because of the Bluetooth bugs.
You can try ha os update --version 11.0 in a terminal
I am not sure if this is yellow specific but none of my addons actually work.
I install them just fine but they never start
i restarted the entire ha yellow and it doesn't change a thing
Without context hard to say. You could do a shot in the blue and try
ha supervisor repair in a terminal and reboot the host after the finished repair
i can't access system from ssh
But the Yellow has a USB-C serial terminal
OK heading to basement
I apprecaite the help @wary pivot
I am not seeing the device
/dev/cu.Bluetooth-Incoming-Port is all I see.
is there no other way to get ssh access
You might have to install the Silicon Labs CP2102N driver
Another way would be the debug SSH access
how do I do that? add on?
No. It has to be enabled in the OS.
do I need to wipe this thing?
I am seeing as well JP1 is set to UART
i am not sure if it is.
https://developers.home-assistant.io/docs/operating-system/debugging/
(not for regular terminal use)
I have had this yellow for little over a year and its such a pain to setup fully, start run into a bunch of issues as I am now and kick the can
but today is the day.
its really odd why they don't pick a lane
either its an euthastist tool or not. If you expect us to do this why not bundle these things in and allow for easy debugging
SSH add-on is the very addon I am trying to enable 😛
looks like I am going to have to wipe this thing 😦
You are not reading, right?
Someone just wants to wipe the device 🤷
Sorry let me get back up stairs I am in a crapped server room
Maybe I didn't read everything properly.
Moving yellow out of this room too.
I linked the guide, how to enable the debug SSH access to the OS
It should also import it by rebooting the device with the USB plugged in
rebooting...
that didn't work
fat32 formatted usb with authorized_keys and my public key in it
And you named the USB stick CONFIG (case sensitive)?
yep exactly. I'm not surprised that doesn't work out of the box... but it's very strange that I can't even get a single character out of the serial console
I already know the steps you're mentioning. as @compact quartz mentioned I do not have an NVMe drive - yes I know this is bad, but I cannot get one right now: #yellow-archived message
@full field is this a USB flash drive or something like a 2.5" in an enclosure? I wouldn't bother with a flash drive
@compact quartz flash drive, why? just the performance or is there something else?
But you could try flashing the drive with the HAOS image for Yellow https://github.com/home-assistant/operating-system/releases/download/11.0/haos_yellow-11.0.img.xz
Yeah a flash drive will be unbearably slow and likely get hot
I did this already
You flashed the image and not the installer?
That says "the installer image" so I wasn't sure
Ok I didn't read far enough. No my mistake
no worries at all
I did forget to mention last night that I confirmed that the EEPROM/bootloader update worked by ordering the "just halt and flash an error" boot method first. then I confirmed that it was booting the drive, for some notion of "booting", by ordering the error boot method immediately after USB boot
to be exact, my BOOT_ORDER (https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER) is now BOOT_ORDER=0xfe54
That will not work with the NVMe later
I know
I wanted to eliminate sources of complexity. I'll reflash EEPROM so it matches the Yellow documentation when I grab an actual drive
When I tried a nice quality samsung flash drive with a pi3b+ just for fun I was surprised by how hot it got
it's definitely not a long term or even medium term solution lol
I tried it again with a pi4 later I think and it was the same thing. Slow, hot. In a short amount of time.
literally as soon as I'm not coughing all over everyone I'm headed to microcenter
progress (maybe): I realized I have a Mycroft Mark II that I could use to see if it was a boot media issue. that's running a regular Pi 4 and not a CM4, but assuming that isn't causing different behavior (which clearly is a big if) it looks like u-boot is boot looping. it goes so quickly it's hard to get a read on what is actually printed but I get a long two-column list of x<some number up to 29>: <16-digit mostly 0s hex code> (I'm guessing these are addresses of some kind because one is labeled (reloc)), followed by:
Code: 54000061 d2800000 d65f03c0 f9400401 (b9400821)
Resetting CPU ...
resetting ...
anyone know if u-boot is expected to output to serial? if not, that could explain why I can't get serial logs.
that was the bit I missed
I got things working though.
things are feeling good.
I will try, thanks
Anyone around that can help troubleshoot my new Yellow not detecting a WD Blue NVME 2280 drive? Is there something I need to do to enable the slot or did I buy a drive that isn't supported?
It depends on the drive. Only one specific WD Blue has been reported working - the WD Blue SN570.
You might also try to remove all existing partitions from the NVMe before installing it.
Hmm oh I didn't think about that. I did previously use it for another RPi project, let me see if I can find a way to wipe it. Thanks
Hi. Just received my new home assistant yellow. I plugged the power and connected the ethernet. Yet, i am unable to connect to it as I am using the default home assistant local address. Also, i tried using the IP address to connect but it's all in vain.. any ideas how to resolve this issue?
First of all: please do not crosspost.
Second: What Yellow variant and what CM4 do you have?
Third: Did you install HAOS (if it isn't the Yellow Standard)?
I have the standard one
Have you been using the full URL http://homeassistant.local:8123 or http://<ip-address>:8123
including the prefix http:// ?
Does the observer say the system is healty? http://<ip-address>:4357
You also can look for error messages using the USB-C serial console
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
i used both with the prefix
the error message i am receiving from the browser is: ERR_CONNECTION_REFUSED
Does the observer page say anything?
it is showing the same error message: ERR_CONNECTION_REFUSED
Try to clear the browser cache with Ctrl + F5
If it is in the same network (IP wise) as the Yellow, it doesn't matter
and perhaps it is useful to say that I was running Hom Assistant VM
Is it running right now?
No, certainly
And you are using the IP address of the Yellow, not the one assigned to the VM
even runing home assisntat app on my android mobile is not working
on VM the IP4 is set to automatic, it is not static
And you are sure about the present IP address of the Yellow?
yes, i got it from my router settings
The Yellow has unrestricted internet access?
If so, you should connect to the serial console of the Yellow, restart it and look for error messages.
Or try to restart the router
i believe it does
i restart the Yellow several times already
restarted my PC also several times
i will restart the router now as you suggested..
I'm back now... same issue!!
you see i ordered this device since january and just received it today
Then go for the serial console
very frustrated
ok. that would take some time now...
BTW, do you think i need to reset the Yellow?
Maybe
it should be fresh already..
even they added a note that this is an upgraded version
If something went wrong in the first startup, it might be possible an OS reinstall is needed
What kind of upgrade?
actually it never started up, i did not see the nabu casa screen at all. it is showing the error message from the first time
I wonder If the OS is preinstalled at all... Does the yellow LED light up in a heartbeat pattern?
two quick yellow beats, then a stop, and then two quck yellow beats again and so on
i sent an email to the support team there.. hopefully they will respond fast
The serial console might show the issue
i will try that one too.. seem will take time
Hi. Not sure what's the time is for you. Just for update: I followed the instructions for the serial console as you suggested. Yet, it seems my PC is not recognizing the device properly. It did not show up under the Ports category, rather under other devices. And there is some error because there is this yellow warning sign next to its name. it is installed in device manager as CP2102N USB to UART bridge controller. And there is no com port indicated
so practically i am unable to configure PUTTY to check the right port
Nevertheless, I tried to run PUTTY, but is not responding. So, obviously, my PC is unable to download the right driver for the port.
any ideas how to find it?
https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers?tab=downloads
The universal Win driver
ok
i will try
the driver installed and worked properly .. COM5
but nothing happens when i start PUTTY
it is making this error bell tone
oh.. God .. this device is cursed
@gloomy quartz it is beeping?
you mean the beep is from windows, right?
when trying to use putty. or chime or whatever
How is the yellow attached to Windows? Your are using a usb c cable and the Yellow is being powered by an adapter, correct?
yes, the beep is from Windows
And I am using USB cable to connect the device to my PC
While still the device is connected to the network via ethernet
yes, the yellow is conntected via power cable to the pwoer outlet
the serial console opens?
no
or it beeps when you click open
@gloomy quartz can you share a screenshot of your putty config and how the device currently appears in device manager?
that is the serial option page. what is showing when you click on session at the top left?
you can leave the serial options as they were by default
and specify them in the session
the defaults were likely COM1 and speed 9600
If you click on "session" at the top, then choose "serial" as the connection type, you can enter the specifics there
I would close this session, disconnect usb, reconnect, and start putty again and a new session if you haven't already
no.. i got: Home assistant login:
since you have a connection, go ahead and enter reboot there. You should then see it restart and see the startup messages fly by
you mean i can use the browser to access HA now?
it will get you back to the "welcome to..." message again in the console
no you probably can't access now if you could not before
I just meant since you have a working serial connection using putty
oh.. i am not familiar with how to setup HA like this..
you aren't setting it up here, you are observing
i have a backup copy and was planning to restore it here
not yet
ah ok
so i will type reboot
that's what happened..
you have an ssd installed?
no
@shut cedar are you around?
@gloomy quartz is this one which had an upgrade to a 32GB CM4?
so, the system is there i see, right?
Yes
yes
@shut cedar we now have a connection over serial console, and the above is appearing (screenshot)
I assume this is first setup?
Hm, corrupt file system. Sounds like smething went wrong during production 😢 Can you DM the serial number?
what do you mean by DM?
direct message here in discord
the serial number on the underside sticker to me or falstaff
Nothing out of the ordinary at production from what I can tell 🤔
is there anything that can be tried through the console?
or should it be reflashed with HA OS image
The factory reset might be good enough here, since it seems to be the data partition only 🤔
But I think better safe and reinstall HAOS
Option 1 from https://yellow.home-assistant.io/guides/reinstall-os/ should work in this case.
BTW, i ordered the device since january..
i only received it yesterday
i was about to cancel the order when i heard about Home Assistant Green
Yes, any Standard versions of Yellow were going to take a long time due to cm4 supply issues
so, i will need to install the OS myself now..
you could try a factory reset first, and see what happens https://yellow.home-assistant.io/guides/factory-reset/
ok
@wary pivot has thoughts I keep waiting to see 😄
oh.. appreciaite it gentlemen.. i took much of your time
Does the factory reset format the data partition or just delete everything on it?
i received a reply from Nabu Casa support a couple of hours earlier.. i explained the siutaiton to them and i shared the link to this conversation so that they can check the great support from you guys
Some of the present people are from the Nabu Casa support. And it's not me 
fantastic
i am lucky then
the one who sent me email is named Ashton
gentlemen, i will clsoe the connection and do a factory reset
will update here just for your infromaiton
perhaps there will similar cases with other customers
I'm optimistic. They have gotten most people on track - sooner or later
yes for sure
guys... IT WORKED!!!!
oh.. finally the great onboarding screen
now i just need to click Restore from Backup
Just be aware: the restore process might take some time. Longer than comfortable.
it's ok... never mind 🙂
i am already late
it was supposed to be working since yesterday
the size of the backup file is about 700MB
i will keep it working and go to bed
Nice. Was that after the factory reset?
yes, after factory reset
thank you Ashton, Jorg, and falstaff321
you really made my day
i will need to work on the restore and setup now
great team indeed
bye bye for now
Thanks, you're welcome, see you!
Reporting in to say I'm seeing the same issues as WW was reporting with their CM4 unit they just got in.
I'll go about reflashing the OS via https://yellow.home-assistant.io/guides/reinstall-os/ and seeing where that gets me.
Also an upgraded model?
Yep.
Interestingly it is reporting the hostname as 'homeassistant' to my router so it's posting at least.
That's strange. But if it is the same problem, reinstalling the OS should fix it
There is also the option 2 with a USB cable and rpiboot
Mac, but it might be fun to try and get that playing along with Parallels.
I'll go dig something out, don't worry.
Another option would be the factory reset with the red button. But I'm not 100% sure that it really fixes the filesystem problem.
Have you tried to look at the serial console output? Just to identify the issue
Would it help you or others if I did? I don't honestly want to be bothered but I can put my big boy shorts on if it'll do some good.
Oh it's just screen and a usb C to C
Hold on.
We are assuming you are experiencing the same problem. But it might also be a network (DNS) issue. Some people have problems with their ISP's DNS.
Negative on that, using Cloudflare/Google iirc.
Cloudflare is the fallback for HAOS
In case you are missing the driver:
https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers?tab=downloads
Is this a USB toy affair or do I need to provide external power?
The docs don't say.
The UART is USB powered, but you need to power the Yellow itself to observe the boot process
Well it's not lighting so that would be the latter.
There don't appear to be any actual linked drivers to download there btw.
I have a 2 year old and a 2 week old. I am extremely tired so bear with me here.
Doesn't appear to be needed.
[FAILED] Failed to mount HassOS data partition.
See 'systemctl status mnt-data.mount' for detai```
🤔
I think I found the issue.
Wait hold on
Huh, it got to the log in propt.
Yeah, seems to be the same filesystem issue
Hiho, off to the USB mines.
The data partition is corrupted, that's why it doesn't really start.
I presume the Red + Blue stuff just triggers a wipe and prompts the unit to watch for USB flashing?
The OS itself is working, so nuking with red and blue should work
Well this has been entertaining. I don't think I've done an actual factual in person serial read in years.
Beats the hell out of Azure/AWS's efforts.
As expected after beating it with a stick and using the R+B + USB install method we appear to be in business.
Quick followup, is the brownfield addition of a NVMe driver something that requires a reinstall or can that be gracefully handled in place?
A NVMe can be added (if compatible - have a look at the Yellow's website before). The data partition can be moved to it without reinstall
Hello again
as you recall, i started the restore process since last night
and it still in progress until now
is this normal?
almost 10 hours so far..
It is slow, but afaik it also doesn't refesh. Try connecting in a separate window to the same device (using http://homeassistant.local:8123 or ip)
ok
shall i close this one?
Anyway, i opened Home Assistant in a new window while keeping the other one as it is. And, yes, it is 100% functional
exactly like my original backup
even my mobile app is working same like before
so, i beleive that does it
Hey friends! I've finally got my HA Yellow and am trying to migrate my previous HA backup to it. Everything goes smoothly but, then, the HA seems to hang indefinitely on the Restore in Progress screen. Opening the instance in a new window displays the Welcome Screen. Refreshing the page whilst on this screen results in termination of the restoration process as it displays the Welcome Screen. Do you have any advice as to the troubleshooting steps here? I am very new to the HA world and your expertise, advice, and ideas are greatly appreciated!
Have you logged in and looked if everything is restored already?
Not yet. I opted to do a basic start and update before restoring but getting a lot of errors
What kind of errors?
Hi, I have a Yellow with a CM4 Lite and a NVMe SSD. I've just powered it up for the first time (using PoE), with the USB stick inserted (which was setup using RPi Imager). Basically, I've followed everything in the guide https://yellow.home-assistant.io/poe-nvme/#gathering-the-required-items and am around step 9/10.
My Yellow is currently in a state where only the red and green LEDs are on, and they are on solid (not blinking), the yellow LED is completely off. It's pretty much been in this state since boot, and that was probably over 10 minutes ago.
Looking at this guide https://yellow.home-assistant.io/guides/yellow-leds/ it says that the green LED should be blinking if something is happening, and the fact that the yellow LED is off indicates that its in boot loader mode or EEPROM firmware (not sure what that means).
It's been long enough that I feel like something should have happened, and as far as I can tell if there was an error I would be getting some kind of flashing LED combination. Anyone got any advice, I presume it's safe to power it off and try again? The installation guide does say that with the LIte it will just automatically install onto the NVMe SSD, but based on the LEDs there's no indication it's got that far.
What NVMe are you using?
WD Blue 250GB SN570 NVMe SSD
A common issue is a not correctly seated CM4.
Some CM4s also need a firmware update. You can find the guide for it here:
https://yellow.home-assistant.io/guides/flash-cm4-firmware/
I assume the NVMe is new and no old data is on it.
If that also fails, a look into the serial console during the boot might give some hints about the problem.
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
If you have a USB to m.2 adapter, you can also flash the NVMe directly. Just to rule out a bad USB stick
I will try a firmware update first
I'm pretty sure everything is seated correctly (although will double check)
The CM4 makes a satisfying click, when it snaps into its sockets
Yes I did get the satisfying click, and the heatsink is warm so the CM4 itself must be getting power at least
Okay new problem, when it says "Set JP1 to USB." what am I actually looking for? Lol
I have basically no proor experience with these kinds of boards
When you open the case there is a jumper at the USB-C port. One jumper setting is marked as UART and one as USB
Thank you. I'm assuming the "USB-C Recvry push button" is the blue button?
Or maybe the red one?
No, it is the small black one besides the m.2 slot
Ohh thanks
Okay weird, it doesn't look like a push button though, on my one there's two pins and what looks like a jumper
And a jumper attached to only one of them?
That's an older board revision. Use the jumper to connect those two pins
Okay cool
My fault for assuming I had a newer board, forgetting that I've had it for month waiting on a CM4 being available lol
I wasn't expecting someone setting one of those up now 😅
Haha
Okay well, now I have a blinking green LED, so seems it flashed the firmware successfully, time to go make a coffee while I "wait for about 1 minutes" lol
Okay so, tried going back to the installation step, but same problem as before, and in fact the yellow LED has never come on, after receiving power only the red and green LEDs came on, they have stayed on solid, yellow LED always off
The missing yellow LED means, the installer isn't running at all
Yeah that tracks, because the activity light on the USB stick basically came on for less than a second and then nothing
My nest steps would be reflashing the USB stick or the NVMe if the USB stick still fails.
And if nothing works - a look at the serial console during boot
Yeah okay, I'll try flashing the USB stick again, what's interesting is that this stick is my "build stick" that I've used many times to build Windows machines in a corproate environment
Okay so I've managed to open a console connection, but I'm not getting any output, just an empty terminal, even after rebooting the Yellow, nothing
The serial console is connected during the reboot?
Yes it seems to be
And if you press Enter, nothing happens
The Putty Window stayed open
Yeah nothing
I just have a solid green cursor which doesn't move
You can try to send a "Special Command - Break" from the menu when pressing the Putty symbol.
And give it some Enter presses
Done, and still nothing
My guess would still be that the CM4 is not fully in its sockets
Okay, here's the event log from Putty, not sure if that helps
2023-10-25 13:58:51 Opening serial device COM3
2023-10-25 13:58:51 Configuring baud rate 115200
2023-10-25 13:58:51 Configuring 8 data bits
2023-10-25 13:58:51 Configuring 1 stop bit
2023-10-25 13:58:51 Configuring no parity
2023-10-25 13:58:51 Configuring XON/XOFF flow control
2023-10-25 14:05:25 Starting serial break at user request
2023-10-25 14:05:26 Finished serial break
Just removed the heat sink to check the CM4, it's definitely in there good, pretty much flush with the board
Going to check the NVMe now, I think I have a cable
Better keep the heatsink off, until the issue has been solved
Stupid question... The Yellow has been detected on COM3 as "Silicon Labs CP210x USB to UART Bridge" in your device manager, right?
Yes, and I had to go and download the driver and add it in driver manager, because windows didn't auto detect it, that guide maybe should have a link to download the driver
You have used the Universal Windows driver, I guess
It has the installer
Is it a problem that I used the universal one, or just the fact that the other one has the installer, as windows was able to find and install it, and the device then did correctly show up in device manager as described in the guide?
I don't know what's wrong with the universal driver, but when I thought I had installed it I had some issue
I quickly went back and took a look at the other a available drivers and didn't have a problem with the other
Okay I've removed the universal one, going to try the other windows driver
Do you remember which one you downloaded?
- CP210x VCP Windows
- CP210x Windows Drivers
- CP210x Windows Drivers with Serial Enumerator
They updated the Universal Driver this summer. I think it had an installer before 🤔
Okay so installed the other driver, connected it, and still no output, although this time I left the SSD disconnected just to see if it would give me something, but got nothing
Thing is, if there was an issue with the SSD, that should only be relevant after the system boots into the installer, right, but it's like it's not even getting that far because no yellow LED
I would remove the CM4 and insert it again. But wait for cogneato's advice
Oh I thought that had already been tried
As I understood, it was just a check of position
Ah
CM4 is pretty tightly in there, any advice on getting it out?
Well, it might be good to visually inspect the insertion tracks
I have used a credit card in the past.
Look at both the underside of the cm4 and the tracks on the yellow. I did come across someone who had a small bit of something in one of the tracks on the yellow
I can't imagine how they saw it without a magnifying glass though
And then when you put it back in, you want to hear significant clicks. Did it come out very easily?
Visual inspection, nothing noticable, there was maybe a tiny fleck on one of the tracks, also used phone camera to help
It was definitely in securly, I got it out by pulling one of the short edges, it had resistance to it but I wouldn't say it was difficult
Ok
Pushing it in with some force, it goes in there but I wouldn't say there was a click, the first time I did it I do remember hearing a click sound, but it's pretty much flush to the board now
Tried a different USB c cord?
No will try a different one, the one I'm using it usually fine, although I can't remember the last time I used it for data
Well, I tried reseating the CM4 and SSD, and tried a different USB stick, and how it's actually working, yellow and green lights are flashing, and I'm getting serial ouptut now
I want to say it was the USB stick, but it's never caused a problem before when building a system and it was able to write successfully, maybe it's finally dying on it
The only difference I can think of is that the other stick I tried is a USB 2.0 stick, but I can't imagine that would be the reason
The status of the installer should now be observable by the LED pattern
When the yellow LED stops and only the red one is on, you can power it off, remove the USB stick and power it back on again. If everything works well, it should show the onboarding page when it is fully started
Okay seems to be online now
Thanks so much for all the help troubleshooting!
Now I just need to move everything over from my current HA
Cool thanks
Use the services page and select hassio.backup_full
And disable the compression option
The backup will be bigger when it is finished, but others have reported the restore process on the Yellow to be shorter
Oh nice thanks
It might be an uncomfortable time amount nevertheless 😅
I'm going to update my current HA to 2023.10 just now anyway, currently on 2023.09
Any tips on moving my Zigbee cluster over, I saw a while back a button added for migrating it in the UI?
You do use ZHA?
You can choose to migrate the radio. And after that do not use the option to create a new network.
But download a ZHA backup from the old instance - just in case
Ah great thanks
When you say, "do not use the option to create a new network", do you mean on the old HA with the ConBee, or going forward on the Yellow?
On the Yellow
The restored instance should have a ZHA integration pointing to the old coordinator, if I'm remembering right
Okay, I'm just thinking going forward with the Yellow, if for some reaosn in the future I needed to create a new network (not that I'm planning to), that wouldn't be a problem, you're tlaking about as part of the migration, right?
You mean a Zigbee network? It is always possible to nuke everything. But usually people don't want to re-pair all of their devices 🤣
Yeah the Zigbee network - I have like 30 lightbulbs paired, so yeah I really don't want to have to nuke it if I can avoid it lol
Okay, just so I understand: on old HA press the Migrate Radio button in ZHA, then on Yellow restore full backup, which then takes over the Zigbee network
No. Backup the old HA and backup the ZHA on the old
Yep got both of those
Restore to the Yellow and press the migrate buttton there when it is back online
Okay cool, well time to make another coffee lol
Yep, still going, almost 30 minutes later
So after migrating my Zigbee network to the Yellow, which appears to be working, I notice in the configuration it still seems to think it's a ConBee USB adapter, the radio type says deconz and the serial port is /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2462407-if00
I mean, technically it works, but now it bothers me lol
The old host is off, the new one is migrated, but still showing the old hardware, right?
That is correct
I'd try a full host reboot
After a restore a reboot is recommended anyway, as add-ons often behave weird without
Not just restarting HA, but a host reboot
Yeah, I'm going to do a full shutdown
Yep, a full system power cycle seems to have fixed it, thank you
now reporting, radio type: ezsp; serial port: /dev/ttyAMA1
Gooooood 
This time I fully shut it down, disconected all power, and waited 10 seconds, I did previoulsy restart it so it could pick up a new DHCP lease, but don't remember if I did a reboot or just a HA restart
👍
Have there been announcements regarding CM5 compability?
There is no CM5 and it hasn't been announced by the Raspberry Pi Foundation yet. The RPi5 has just been released (HA support expected beginning 2024). And I don't expect a CM5 to be announced soon.
For reference: the RPi4 has been announced in June 2019, the CM4 followed in October 2020
Oh, I had my hope set up to early
And compatibility... if the CM5 shares the same connector type and position, the actual compatibility would have to be checked with a real device by Nabu Casa before they would declare it as compatible (they did not get a RPi5 sample before release). And Yellow's HAOS would need to be adapted, like the upcoming RPi5 image.
We have to stick to the CM4 for a while 😆
Hey y'all. Just got my yellow, plugged it in, clicked through setup with default settings intending to wipe it with a backup I have and the supervisor isn't updating and therefore won't let me access the backups/restore page. When trying to manually update the supervisor I get the error [547069151424] Error updating Home Assistant Supervisor: Abort update because of an issue with AppArmor: Can't update AppArmor profile!
any advice? I tried factory resetting by holding th red button during boot up and the yellow light does flash but once it comes back online it seems like no data was deleted and the instance is still exactly the same as before the reboot
#installation-archived might be able to help with the AppArmor error.
If not, I would go with a completely new HAOS installation.
https://yellow.home-assistant.io/guides/reinstall-os/
Hello everyone, what do you use best for HA as a room thermometer with display?
The channel #hardware-archived can help with hardware suggestions
I'm confused about header JP1 UART/USB. Is that jumper not for setting the USB C to host or device? E.g. on UART you can connect it to your pc and connect over serial, on USB you can connect USB C devices (like a speaker or other accessories for example).
Or can it only be used for USB boot?
When the jumper is set to USB I noticed none of my USB A ports work anymore.
Reason for trying to connect a speaker (the Anker PowerConf S330 which is recommended everywhere regarding Voice) is that on USB A I get a popping sound and thought about a hardware issue. If I connect it to my pc (regardless if it's USB A or C) I never experience the issue.
It's not the (assist microphone) add-on (because I tried with another) and not the speaker hardware (because it works on pc). I suspect either the HA Yellow itself or the Home Assistant OS.
USB-C is just for the serial console and for accessing the storage or CM4 firmware updates. It cannot be used as an additional USB port.
But I wouldn't be surprised, if the popping would be caused by the USB-A ports. I wasn't able to get a Google Coral TPU working due to USB communication errors.
I received my HA Yellow earlier in the week and couldn't get it to work. Connected the USB-C today and got the this error:
No filesystem could mount root, tried: squashfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,3)
All I can find on the internet is:
- Refit the CM -> Done. No difference.
- Replace the SD card -> Not possible.
Any tips/tricks?
Something went wrong with the filesystem and you would need to re-install HAOS.
https://yellow.home-assistant.io/guides/reinstall-os/
Propably with option 2
@wary pivot thnx a lot. Worked like a charm. Even on a Mac using https://github.com/raspberrypi/usbboot
@covert panther You reinstalled HA OS to the Yellow?
Is it possible to slow down the rate of the yellow health LED blinking?
I like the idea of the health LED, but at the frantic rate it is by default I opted to turn it off.
Either a 1sec pulse every minute or alternating on/off every 30sec is ok for me.
I see no available trigger pattern for something like that.
I apparently ordered the wrong RPI module - just received it and it doesn't fit on the Yellow. Could someone point me in the right direction?
I ordered this: https://vilros.com/products/raspberry-pi-4-4gb-ram
You need a Compute Module 4, not a Raspberry Pi 4
Something like that.
https://vilros.com/products/raspberry-pi-compute-module-4-4gb-ram?src=raspberrypi
You would have to choose which one (w or w/o WiFi/BT, RAM and storage capacity). I would suggest 4 or 8 GB RAM and a module with 32 GB of storage (the ones without storage - "Lite" - cause more trouble setting them up and you would need an additional NVMe)
I've already got an NVME for it
I got the Yellow with PoE
still need WiFi/BT on the CM4 ?
No. If you want to use Bluetooth, an ESPHome Bluetooth proxy is better.
What's the advantage?
With an ESPHome BT Proxy? More reliability and they can be placed, where BT coverage is needed.
Thanks for the help
I have a Home Assistant Yellow POE which I had been using successfully for a while now. However, the CM4 that I had initially gotten on had 1GB of RAM. So, I got a new CM4 with 8GB of RAM and tried to replace it. I installed the new CM4 and did a fresh install of HA from a RPi Imager created USB drive. The problem is that it doesn't see the NVMe drive, so can't use it. I've spent over a day now trying all sorts of things to fix it, to no avail. I don't think the SSD is the problem since it was working with HA in the same hardware with the older CM4. A couple of weird things that I'm seeing are: 1) My previous system was running the latest HAOS & HA Core 2023.10.5 version. But since 2023.11.0 was released yesterday, all of my new installs are pulling and using that. I don't know of a way to force an earlier version. I doubt that is the problem, but maybe? (Note to self: Don't try to make HA hardware changes on a day when the HA version is updated!) 2) when I do a fresh install on the eMMC, going to Settings | Hardware | All Hardware does NOT list all of the hardware. It only has the ttys, mice, a couple of GPIOs, and a few other items. But no mmcs, no device-mapper, plus LOTS of other items. One problem that I have is the new CM4 only has 8GB of eMMC storage, and it is basically filled when I first do the fresh install. I'm wondering if the install is running out of space and not really installing everything... 3) I've not reinstalled the original CM4 (with 16GB eMMC) and done another fresh install via the USB drive. It installs to the eMMC and boots. It has like 80% free space which would seem to indicate to me that the 8GB on the new CM4 should be enough, too. That's confusing. However, that new install is also not seeing the SSD drive at all. I've ordered a couple more SSDs to try just in case that is somehow the problem. But until those arrive, does anyone have any ideas about other things that I could try?
Yes. Remove all partition on the NVMe (for example with a USB to m.2 adapter or with linux partitioning commands on the serial console). It might not be shown as available device for data migration as long as a previous install is present on it.
I will somewhat disagree with Jorg insofar as depending on your setup simply going for a BT capable CM4 module or just grabbing a HA compatible BT USB dongle may be a "better" way of skinning the cat. I'm personally doing the latter and it's been plug and play for me and works as well as I could hope.
The "better" was is the proxy of course but if you're not doing anything too complex the simple solution might be a better fit.
Yeah I figured I'd go with a BT capable CM4 and get the proxy if necessary afterwards
It might be okay now. We had some nasty onboard BT bugs some time ago.
I'd be interested to see how well onboard does for BT/WiFi given limitations on antenna size but it's worth trying.
Hi All. I have been using HA on an RPI 4 with USB to nvme adapter. I bought a Yellow POE almost a yeat ago but didn't have a CM4. I just got my CM4 8gb, lite, wifi/Bt. Can i take the NVME from my pi4 place it in the Yellow and expect it to boot right up? Of course i will backup the drive first. Any insight would be appreciated.
No
The Yellow needs a specialized version of HAOS
And the NVMe has to be compatible
Wishful thinking that it could be that easy lol. So install the yellow version of HAOS, do a full backup of the PI4 and restore from backup to the yellow? I really don't want to start from scratch if possible. I have almost 200 devices on my home assistant currently. What a pita it would be have to start fresh. Thanx for taking the time to respond.
Do a backup (and download it) before wiping your NVMe 😆
I was going to install a new evo970 plus in the yellow and clone the old drive.
And you should remove all existing partitions on the NVMe if you want to use the install method from the documentation. If you install HAOS for Yellow directly before installing it, it will be fine.
Depending on the firmware version of the CM4 Lite you might run into trouble and need a firmware update.
Can the firmware on the CM4 be upgraded from the Yellow? i don't have another carrier board for the CM4
Thank you very much. Wish me luck. At least this way if I run into issues, I have the PI4 as a complete system.
cm4's with lots of storage were out of stock so I got a small one and stuck 40gb of slc flash on it (yes, I know there's an nvme socket. felt like it). wish me luck 🙂
does home assistant supervised work well on yellow? I notice there're a lot of common commands and libraries missing from home assistant os which will make my previous command line integrations not work, and the simplest way to solve that would be to use a full os?
I suspect running home assistant os inside a virtual machine would break the wireless gateway function that is the system's reason for existing
or, can you do things the other way around and install a virtual machine with standard linux functionality as a guest to home assistant? I know it uses containers internally for lots
No. Home Assistant OS is optimized for the special hardware. If you are not comfortable with messing with device trees, you will likely loose the Zigbee radio for example. And Supervised installs are prone to break.
As the CM4 is basically a special Pi4, the processing power is limited - so virtual machines are not really an option
what's the best option of the available bad options, for getting home assistant able to run debian commands?
Get a small form factor PC, install Debian and run HA with Docker
i'm comfortable stealing the device tree from some other config and slamming it into the os if that helps 😉
boinccmd
command_line:
- switch:
name: "bart_run_mode"
unique_id: "switch.bart_run_mode"
command_on: 'ssh -o UserKnownHostsFile=/config/ssh_known_hosts -i /config/local-ha-rpc-key user@localhost "boinccmd --host 192.168.182.203 --passwd `cat ~/boinc/bart.gui_rpc_auth.cfg` --set_run_mode always"'
command_off: 'ssh -o UserKnownHostsFile=/config/ssh_known_hosts -i /config/local-ha-rpc-key user@localhost "boinccmd --host 192.168.182.203 --passwd `cat ~/boinc/bart.gui_rpc_auth.cfg` --set_run_mode never"'
controlling heating
You want to start and stop BOINC on another machine remotely?
yep
that looks plausible, I think that's the only thing I need linux support for right now, so might be able to get away with home assistant os if that works
container thing on a pc wouldn't give home assistant access to wireless devices i'm adding. unless there's a way to split it across two computers?
rather avoid the extra dependency if possible though
That integration allows you to start and stop BOINC clients
What other dependency are you talking about
the situation of having to run one computer for linux and another for wireless gateways
if that integration works (i'll try shortly) it won't be an issue
If you want to run the BOINC server directly in HAOS, you would have to create an add-on
no need for that, all it needs to do is send the start/stop command like that does. the HAOS computer doesn't generate enough heat to be meaningful anyway (I hope)
although I could see someone running it that way if they have HA on a big server
thanks for finding that.. I started looking at the boinc internal protocol a few years back when I first set this up, but went the easy/quick path instead. worked out somehow I guess.
so, tried the custom integration for the first time, and it didn't work. so I tried to use tcpdump, but tcpdump is linux
that's a bit of a problem\
tcpdump is a networking command and thus doesn't work in a container
I'm thinking really should just install debian and save myself future trouble. the more people use it, the less likely they are to completely disable the option, right?
or maybe I could stick a full linux install to use via chroot into one of the shared folders. that's dirty and supported
going crazy, gonna go to sleep
I think it's actually sending commands end to end, just not the right commands for the way my boinc is set up. will make a local modification of the integration
I'm new here and somewhat new to Home Assistant. Yesterday my CM4 arrived. I've installed it in the H.A. Yellow kit and got everything connected to my UniFi network only to find that the box does not grab an internet connection. Not sure if the box is defective or if there another issue. I know this is vague, but any suggestions will help. I've also emailed Crowd Supply (retailer) for help. Thx, Rob.
Does the Yellow get a local IP address?
No.
If you are using UniFi stuff... is your switch configured to provide sufficient network access on that port?
The most common problem on the Yellow side is a not fully inserted CM4.
It should be. I've looked things over a number of times. I've plugged it into a switch upstairs as well as my PoE+ switch elsewhere, but the green and red LED are solid with no yellow LED activity. I suspected the CM4 not being seated properly and checked it, but I guess I'll check it again. Thanks.
It should make a satisfying click when it clips into its sockets
Thanks. I'm not hearing such a click, but it appears to be connected. That's probably the issue. Thanks. 👍
I got the boinc control working, so now all of my original stuff is working on a yellow, except now with also bluetooth, zigbee, and zwave support, yay
also figured out the tcpdump thing, fwiw. the container the common community ssh plugin runs in has enough privileges to run it seemingly properly, when set unprotected
Going to be moving to a new house soon and am thinking about changing how I host HA with it. Currently I'm running it as a docker container on my Synology, but I'm considering getting a Yellow. I'm pretty sure I would just want to go with the Standard, but I'm curious to get opinions. Also, I'm assuming I can expand it to support/do zwave as well as the built in zigbee?
ZWave can be added with a USB dongle or a Pi HAT like the Aeotec ZPi 7 - that would fit inside the case
Is the Pi that comes with the standard good enough for most things, or should I consider getting a kit and purchasing my own Pi?
I personally would try to get a CM4 with more RAM. 4 or 8 GB
I'll have to see if I can get one. I remember when they used to be cheap.
Just to follow up on yesterday. Is this one you would consider being a good choice? It should be hardlined so doesn't need wifi
https://www.digikey.com/en/products/detail/raspberry-pi/SC0687/13530926
RAM wise it's great. But it is a Lite version without eMMC storage. You would have to add compatible NVMe storage to the m.2 slot. And CM4 Lites are more prone to problems during setup.
Ahh, okay yeah makes sense to try to avoid the light. If I'm using rpilocator.com to find these, does that mean I want to make sure it lists MMC in the description?
It's not an absolute deal-breaker. We just observed less setup trouble with the eMMC ones. In that case I'd look for the 32GB ones - those should be easier to find at moment anyway.
Okay. Also, am I correct that the Yellow kit with POE supports regular power supply as well, it just didn't come with one?
Correct. If both are available and connected, the Yellow will take its power from the power plug.
Cool. I don't believe my current switch supports POE but suspect I may upgrade at some point so I'd rather keep the option than now.
DC 12 V / 2 A (5.5/2.1 mm barrel connector - positive center)
Oh, looks like seeedstudio might sell the yellow kits as well and you can bundle a specific CM4 with it, that's nice.
yeah, and they have some options that are otherwise difficult to get. if I had seen those options available first I might not have ended up with my 40gb emmc version
any recommendations for wall mount? wanting something I can tape to the wall and afterwords socket the yellow in somehow tool-less (for maintenance). currently thinking of modifying https://www.printables.com/model/289956-home-assistant-yellow-wall-mount/files but I could be missing some obvious option
I'm using some L brackets. Not great, but a permanent temporary 
lol
My first plan was some velcro, but it didn't work well
is there a public-able drawing for the stock case and screws? not the end of the world to measure but I figure it's worth asking. saves a good amount of time if I can just import it into cad and draw on it
cool. as long as it's dimensionally compatible, should be fine
thanks
i'm thinking of making something that grabs the screw shaft/head that extends from the back. should be able to be pretty small and not need to reprint the backplate if so
If you want to replace the thumbscrews, the present ones are M3, 8mm dia./10mm
cannot quickly find one with an equivalent profile. might be able to get away with a single outer step screw or spacer + screw
was hoping to use the originals as-is but it might be easier to use a longer one
Any ideas on how to get the Zigbee working on a HA Yellow? I've tried reflashing but get Error: Firmware image was rejected by the device. Ensure this is the correct image for this device. Same result with NabuCasa_Yellow_EZSP_v6.10.3.0_PA32_ncp-uart-hw_115200_ext.gbl and NabuCasa_Yellow_RCP_v4.1.4_rcp-uart-hw-802154_115200.gbl.
How are you flashing the firmware?
I tried both the add-on and CLI, finally got that to work after several attempts and turning things on and off. Now it just won't find any devices (which was the problem before I tried flashing it.) Basically the Zigbee has never worked since I got the unit. Nothing odd in the logs, it is clearly talking to the radio, just never receives anything.
Finally, got it working. The devices (new out of the box, never paired) needed a factory reset.
Looking for any guidance in Migrating to a yellow from a HAOS VM. I have a somewhat large install, but I have created backups of individual sections due to restore not seeming functional on the Yellow, and yes, I know this is a common issue. I have backed up only Home-assistant; the file ended up at 40MB; looking into the backup, the largest file is the db at 1GB. I removed my Mariadb recorder settings to slim down the backup before migration.
Trying to restore just Home-assistant, no addons or extra folders never completes. I put supervisor in debug mode on the cli and its not doing anything with the backup. I left this sit for 5 hours yesterday, and that was way more time than the restore should have taken for a 40M backup file. Is something broken with the restore feature in the latest version? I know the Pi is slow, but it's not that slow that it takes days to restore a 40M backup with basically nothing in it.
Restoring uncompressed backups is quicker
Im currently trying just moving the data from the old disk to the new one. Its only about 2GB in total currently. I thikn something is broken in the restore process, or its -hitting an error and not recovering. Always the chance its a edge case, but I dont see how it could be with the current setup.
I found that the supervisor went unresponsive as well during the restore.
The restore/decompression is painfully indeed. And a Yellow is Pi based - the computing power is limited
The supervisor went unresponsive?
Yeah the entire supervisor stopped accepting connections. It owould give a time out error for any ha cli command. Specifically I was trying to get any info on a job that was running, could not get anything cause supervisor was just deadlocked
That restore was only the homeassistant option, it was setup as a "partial" restore to be the bare minimum to move over. It didnt work, and seemingly things broke
Well the copy /mnt/data over worked, but its not without its challenges. Mainly amd64 -> aarch64 images being wrong in the .json files. Some other little quirks. It is very possible to do it this way, while not elegant it works.
was fighting with the built in restore for 3 days, never worked. This worked in 20 minutes. Idk if there is a scenario where backing up a amd64 host and restoring to the yellow which is aarch64 just doesnt work, but it never did for me.
Backups are architecture independant. They just store the configurations, not the docker images themselves.
The .json files for the supervisor do, but idk if those are included in the backups
They aren't afaik. We observed shorter restore times, when using uncompressed backups. That's my recommendation for a migration. Some add-ons have to be built on system (mostly custom ones, as far as I have seen - those have a "rebuild" button on the add-on's settings page) and slow down everything too.
"user": {
"options": {
"init_commands": [],
"packages": []
},
"version": "5.14.2",
"image": "ghcr.io/hassio-addons/vscode/amd64",```
The backups very much do store the cpu arch they are running on
I have only ever done amd64 -> amd64 restores, I have done quite a few over the years. I have never gone from amd64 -> aarch64 though, so this is my only experience with it
I only see the arch listed in the addon backups btw, the base homeassistant one does not. So there is still an issue with restoring in my case, but Im up and migrated a way that is probably not recommended for most people.
This is my VSCode options.json for comparison from the full backup:
"packages": [],
"init_commands": []
}```
The version is stated in the root backup.json:
``` {
"slug": "a0d7b954_vscode",
"name": "Studio Code Server",
"version": "5.11.0",
"size": 12.05
},```
But nowhere is an arch mentioned. At least in my full backups 
Lemme check a full backup, those are partial backups with just the addons. Maybe there is a difference there?
All of my partial addon backups have a image listed those specifying the arch used too
Yes. The partial add-on backups are way to roll back
tar: Error opening archive: Unrecognized archive format
> tar -zxvf homeassistant.tar.gz
tar: Error opening archive: Unrecognized archive format```
Thats interesting from my full backups...
Encrypted backup with password?
Oh yup, this one is.. I forgor..
Just did a partial one... still arch independant
🤔
Or did you just copy from the host directly?
Nope I used the backup function within HAOS. are you lookg at backup.json or the addon.json within the addon backup itself?
"user": {
"options": {
"init_commands": [],
"packages": []
},
"version": "5.14.2",
"image": "ghcr.io/hassio-addons/vscode/amd64",
"protected": true,```
From a fresh full backup
I'm looking at the root backup.json and the options.json of the add-on tar ball
Its not specifed there in mine either, its drilled down in the addon.json inside the addon itself
@frank prawn I converted your message into a file since it's above 15 lines :+1:
I have no addon.json in my backups.
Well I got migrated, not with the restore function since that never seemed to work regardless of time.
But still mysterious 😅
Nevert had an issue with it until trying to migrate to the the yellow, but could be a whole host of things
Yeah idk enough about how it all works to really dig into anything. lol Python is not my forte
But it is up and fully running now?
Yeah im still fighting with some docker images missing and a couple other clean up things, nothing ground breaking
All stuff I can fix easily.
You shouldn't have to do anything with the docker images - that's what the Supervisor is controlling
I cahnged files under it and it thinks they are already installed...
So it assums everything is there, its not validating it post it being added
Image ghcr.io/esphome/esphome-hassio:2023.10.6 does not exist for addon_5c53de3b_esphome```
You get errors like this
just a simple docker pull fixes it
Erm... that might be a good way to break it
Thats my job as an end user , to break things 🙂 lol
I'd recommend to ask in #installation-archived how to fix it properly
The proper way would be to remove and re-install the addon
