#yellow-archived
1 messages Ā· Page 10 of 1
I got my first yellow in late February after a long wait, I ordered a Yellow Kit with Universal Power Supply recently and I don't really need it until September so hopefully I'll get it by then. I already got the nvme drive and cm4008032
Overall experience so far is very good with the yellow I have, good enough to order another one š
Any thoughts on whether the new Core3566, which bills itself as CM4 compatible, would work with the Yellow/Home Assistant? I'm willing to take a chance if there's no news one way or the other, but I thought I'd check first: https://www.waveshare.com/product/core3566.htm
Is there a quick guide on what it takes to get a file onto the hostās file system so that when I attach a USB TV tuner, it knows where to find this .fw file itās looking for in the logs? Or is that the wrong approach?
Neither is the hardware tested to be compatible with the Yellow, nor is the speciallized OS optimized for that board. So most likely it will not work as a 1-to-1 replacement for the CM4.
You can access the host OS via the serial console or the debug SSH. But how to get the TV tuner working might be a question for #hardware-archived
I'm willing to hack a bit... I think I'll give it a shot as it's 1/2 the price of a CM4 right now. It'll be interesting š
bought a Yellow today. however, has a working nuc installation but is curious and wants to support NabuCasa
as I was poking around with a privileged docker container I noticed a broken symlink on the hostās filesystem /lib/firmware/updates/ -> /mnt/data/supervisor/firmware/. Iām 90% sure I didnāt create that. But that got me curious so I created a firmware/ folder inside the supervisor containerās /data/ folder and stuck my missing .fw file in there. I checked the symlink and it was no longer broken, and when I hotplugged my device it picked it up
alas, now Iām on to fighting how to get an addonās container to be able to access the device. i confirmed what i want shows up in /dev/ but any attempts to access it give permission denied š¦
Does someone also have the issue, that the clock is not correct any more? I have today a deviation of 4 minutes. Don't know how to fix this
Mine doesn't deviate. But it has the ability to contact NTP servers
Mine also but it looks like it does not synchronize
Hello,
I got my yellow way back last year, but only today I was able to grab a CM4 to boot it.
I'm facing a very peculiar problem, on every reboot I lose username password access.
I even tried a very dumb passwd, just to make sure it was not some special character encoding.
I'm on my 3rd red button wipe, managed to do zero real progress with it.
When I create my account (onboarding) I can use the UI just fine, added zigbee switches, all looks good, until it doesn't anymore.
Any suggestions?
Are you using a SSD?
no, just CM4 internal memory
Hello everyone, I have some trouble installing Home assistant on yellow. Maybe someone experienced the same troubleshooting and can help me. I followed exactly the step of the installation.
The software seems to dowloaded well ( yellow light steady blink) then after few minute stop.
The red should remain the only light on, but the green still blink. I waited 10 minutes, but still YELLOW = off / GREEN one short blink every 1 second /RED on.
When I disconnect the Yellow and reconnect again, red and green stay ON, the device seems loop rebooting . I have reset and reinstalled home assistant 3 times, still the same issue. Anybody has an idea?
Thank you very much for your help
A few common troubleshooting tipps:
a) check, if CM4 is fully seated in its sockets
b) install without installed SSD
c) use serial console to watch for errors
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
d) flash installer to the eMMC instead to a USB stick
https://yellow.home-assistant.io/guides/reinstall-os/ (option 2)
e) reinstall CM4 firmware and flash installer afterwards as described in d
https://yellow.home-assistant.io/guides/flash-cm4-firmware/
Thank you Jorg, I will try to do those step, have a nice day/night!
In that case i would try to reinstall the complete OS (not just the red button reset)
https://yellow.home-assistant.io/guides/reinstall-os/
Just curious, does having the serial USB in effect any of the functionality? For example, if im watching the serial would that change the effects of pretty the red or blue buttons?
no it would not
@digital reef The two times I've seen this it was because the CM4 was not fully seated
can take a good push to get it to seat properly
Jorg this list was a great guide- does anyone have any other suggestions to maybe get more detailed logs? After exhausting this list I am still seeing the same thing over serial- and I canāt see anything strange in my logs, it just kinda stops itās boot process. If thereās a way to get more detailed logs during boot I might find a new lead- but right now Iām clueless on my next steps.
What are the last outputs in the serial console when the boot process stops? And have you mounted a SSD, an if so: which one?
I donāt have a SSD- https://pastebin.com/RAN4WB3L here is my log, but the last few lines are
āāā
Welcome to Buildroot
yellow-installer login: [ 17.629016] vc4-drm gpu: [drm] Cannot find any crtc or sizes
[ 35.804813] cam-dummy-reg: disabling
āāā
Are you using a USB installer stick or have you written the installer to the eMMC?
And is your Yellow connected to Ethernet and does it have internet access?
By roaming over the logs, it seems the Ethernet connection is down
bcmgenet fd580000.ethernet eth0: Link is Down
A not correctly seated CM4 might cause this or a network issue.
This is a great lead Jorg! Iāll do some digging. It was working, until I did a backup- thatās when it bricked. I have tried using the usb and usbc / rsppi boot to write to the eMMC, as well as flashing the firmware.
No errors or strange logs anywhere in the eMMC flashing process- worked just as the instructions said it would.
I have not really checked the CM4 as it was workin to flawlessly until I did the rollback, and I have it screwed into the yellow- but Iāll reseat it next I think.
I'd try another Ethernet cable - just to be sure.
Are you using Windows? If so and you have storage access with rpiboot, you can use the Windows disk management to remove all partitions on the CM4 before flashing the installer to it with the Raspberry Pi Imager.
Thanks @wary pivot , this has given me lots more threads to pull on š
I have one zigbee connector built in (HA yellow) and a zwave/zigbee USB connector. Is there a way to force HA to select the built in coordinator? Right now when HA reboots, it shows up as zigbee unconfigured and I have to select and setup the on board coordinator with current settings... Every... Stinkin... Time
When you are saying backup, rollback and bricked. Keep in mind, that a restore from backup can take quite a long time - espeacially on a Pi based system. It isn't necessarily bricked.
Have you selected the USB coordinator to be used with ZHA?
I do every time it boots up. If I remove the USB zwave/zigbee dongle, no issues. But I'd like to keep using the zwave portion of the dongle. Any ideas?
Is there another place to "select" the coordinator other than "configure"?
When the USB Zigbee coordinator shows up, it needs to be ignored (3-dot-button beside the configure button).
It doesn't show me other coordinator except when I start configure
Where might I find the USB coordinator to setup an ignore?
Configure what? The USB coordinator or the onboard /dev/ttyAMA1 coordinator?
Please use imgur or other image sharing web sites, and share the link here.
Image posting is blocked in most channels to discourage people from sharing text as images. Sharing text as images assumes that everybody sees the world as you do, which isn't the case. Some people are colour blind, or have visual impairment that means they can't make sense of an image of text.
On reboot: ZHA fails to setup https://imgur.com/32V0yAH
All of these show up as options - I select yellow https://imgur.com/Gge0TKg
Ideally it doesn't fail to setup every time I lose power or reboot
it makes sense I should be able to disable the usb zigbee or pick the onboard zigbee coordinator as a default... but I don't see where I can do that
or that the configuration would stay until I tell ZHA to migrate to a new coordinator
You need to migrate the radio to the /dev/ttyAMA1. And if there is a prompt later (new device discovered - your USB), do not configure it or you break ZHA again. Select ignore in the three dot menu instead
Hmm- itās possible! I did a reload of a backup created from inside HA, it rebooted. Since then itās been stuck- although I have left it on overnight. Since then however I have been hacking at it with all the reinstall processes , so Iām not sure what is left of my original HA install.
interesting, so I usually select /dev/tty/AMA1 - Yellow... on this screen https://imgur.com/Gge0TKg
Propably nothing
and then I select "Keep radio network settings" and it's good to go
...until the HA reboots or loses power
What exacly happens then? You get a notification "new devices found" and see a new ZHA discovery in Integrations, which likes to be configured?
all of my "Unavailable" devices now show status
should I "Migrate to a new radio" instead of "Re-configure the current radio"?
I usually select re-configure the current radio
I don't remember "new devices found"
Migrate
I should probably download a backup first, right?
Backups are always a good idea
I wasn't sure about migrate because the instructions I followed to migrate to the yellow onboard coordinator and then unplug the zigbee/zwave usb
but I don't want to unplug the usb because I still need the zwave functionality
but then I cannot use the zwave. I'd have to buy a new dongle that's just zwave
I am fairly certain I unplug the zigbee/zwave usb and it works fine
it wouldn't have another zigbee choice and so it should go to the yellow onboard coordinator
but then my $30-40 usb is not usable and I need to buy another $30-50 zwave only usb
For now it just needs to be unplugged temporarily for the ZHA repair. If there are no incompatibilities it can be added again later
I don't think there were any incompatibilities. I ran it without the zigbee/zwave usb and it worked great
but I said "you know, I want those zwave device to work again too"
And what did I say?
options: 1. buy a new zwave only usb dongle or 2. plug in my zigbee/zwave dongle
TEMPORARILY
š
remove the usb temporarily and do what differently to bring the combined zigbee/zwave usb dongle back?
I don't see it resolving itself with time -- "forgetting about its years with the combined usb dongle"
When ZHA is successfully migrated, the USB can be added again (might need a host reboot). And if something ZHA related appears (new discovery on the Integrations page) select ignore instead of configure
ah, I understand now. Now that I configured the yellow zigbee coordinator, I will remove the usb and plug it back in
and see if anything pops up in ZHA
Do not replug immediately, give HA a restart first, plug it in and reboot the host, if needed.
If that still doesn't work, the people in #zigbee-archived might have further ideas.
thank you! I'll try it
Hello Jorg. I hope you're doing well. I have try so far 3 time each step, with no improvement. After the installation the OS boot over and over in loop.
There is the log file :
https://justpaste.it/bedps
thanks for your help!
And there is the log of the installation : https://justpaste.it/c9hwe
https://yellow.home-assistant.io/guides/reinstall-os/
Follow the guide option 2 until step 8. Remove all existing partitions (e.g. with Windows' disk manager or a Linux partition program), but do not create new ones. After that continue with the guide and flash the installer directly to the eMMC
Thank you, unfortunatly there are still the same issue .
[ 415.347964] haos-flash[241]: Getting latest Home Assistant OS version from ch annel stable...
[ 415.610540] haos-flash[241]: Installing Home Assitant OS 10.3 to mmcblk0.
[ 430.548854] audit: type=1334 audit(1690536006.964:11): prog-id=0 op=UNLOAD
[ 430.555851] audit: type=1334 audit(1690536006.964:12): prog-id=0 op=UNLOAD
[ 430.562827] audit: type=1334 audit(1690536006.964:13): prog-id=0 op=UNLOAD
[ 1024.299363] haos-flash[247]: curl: (18) transfer closed with 249326648 bytes remaining to read
[ 1024.311105] haos-flash[248]: unxz: (stdin): Unexpected end of input
[ 1024.450101] Alternate GPT is invalid, using primary GPT.
[ 1024.455734] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8
[ 1024.444702] haos-flash[249]: 0+10394 records in
[ 1024.445132] haos-flash[249]: 0+10394 records out
[ 1024.449725] haos-flash[241]: Error during Home Assistant OS installation.
One last hacky idea... you can flash HAOS to the eMMC. Start over with the guide option 2 until step 8 (rpiboot). Then use the program Balena Etcher (instead of the Raspberry Pi Imager) and flash the following image https://github.com/home-assistant/operating-system/releases/download/10.3/haos_yellow-10.3.img.xz (needs to be downloaded before) to the eMMC. Shortly after reboot the onboarding screen should be accessible via http://homeassistant.local:8123 . If that also fails, please contact the support at yellow@home-assistant.io
Has anyone had an issue with time not syncing on the yellow? On the ssh & terminal addon, it shows that the time is 10 minutes ahead, and because of that, tuya integrations can't sync and are unavailable. Is there a way to force time update with ntp? The terminal doesn't know what "sudo" is. So no luck there
Have you blocked NTP on your network?
I don't think so. No. But I am having some troubles with my router, yeah. Didn't thought of that
Thank you very much, it does the trick! Os working now. One last question, I don't have currently a router at home, can I connect directly from a PC (LAN) ? or I need a router with DHCP to assign IP to the Yellow?
Have a nice day š
In standard configuration it uses DHCP. HA can be configured to use a static IP.
But I have never tried to connect it via a crossover cable directly to a PC. A patch cable might not work (don't know if the Yellow supports auto-crossover). I'd recommend to use at least a switch.
just about any network card made in the last decade should do auto mdi/mdx, and all gigabit cards should
A CM4 also should be able to use a m.2 Coral TPU - if there wasn't a hardware bug. I'm just a bit cautious about things I haven't tried myself. But on paper a Pi should be able, as you said.
well in theory only one end of the connection needs to support it š
Hi there - Can someone point me to a comparison of installing the OS on eMMC and storage on NVMe vs installing everything on the NVMe?
eMMC is easy and fast. Some/most people have issues booting from the nvme. If you have a CM4 lite this is not an issue.
Hi guys, I believe anyone here with network skills will help me with setup. I have a yellow with CM4 lite, using DuckDNS for external connection and Lets Encrypt for SSL certificate. Problem is, that while I am connected to my local network (LAN/WAN) I cannot connect to HA at all. Port forwarding on router is set for 443 and also 8123. I also added this to configuration.yaml file.
homeassistant:
external_url: https://xxx.duckdns.org
internal_url: http://192.168.0.142:8123
I managed to connect to https://192.168.0.142:8123, when I confirmed that it is not secured, but my phone is impossible to run, while connected to wifi. It must be just some tricky simple solution, but I cant get to it.
Your SSL certificate isn't valid for the internal access. You can either remove the local access settings in your app and use the remote access permanently, take care of DNS rewrites or you use a reverse proxy.
https://companion.home-assistant.io/docs/troubleshooting/networking/
will try that, thanks a lot
if you use dnsmasq you can make it work also
Seeking installation guidance as I the yellow LED will NOT turn on when I work through step 10 in https://yellow.home-assistant.io/power-supply/.
Troubleshooting Steps:
- Validated the CM4 is seated properly. I've taken it off and put it back on a few times and it is definitely locked in, parallel with the board, and aligns with the white outline on the board.
- Tried two separate USB flash drives to install Home Assistant with no dice.
- Tried three separate ethernet cables to validate that is not the issue.
Other notes:
I've got the CM4 w/8GB RAM, 32GB eMMC, without WiFi (CM4008032).
Red and Green LED are on and solid (no blinking)
Are you using a SSD and if so, which one?
No - thought the eMMC on the CM4 made an SSD not a requirement.
It isn't, but incompatible ones can cause issues.
You can connect your Yellow's serial console via the USB-C port and look for errors.
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
You can also try to flash the installer to the eMMC directly, following option 2 of this guide:
https://yellow.home-assistant.io/guides/reinstall-os/
If that fails, you can also try to flash the OS to the eMMC, following the same guide, but instead of using the Raspberry Pi Imager, use the Balena Etcher and flash the following image to the eMMC:
https://github.com/home-assistant/operating-system/releases/download/10.3/haos_yellow-10.3.img.xz
What would be the best way to get a yellow to it's final destination. I'm building one for my parents place in Florida, doing all the cloud stuff now cuz that's all I can do. Should I just put it back in the box when the time comes and ship it there?

Any thoughts on why neither Windows or MacOS would recognize Yellow after trying reinstall-os and then going to Balena Etcher?
You have used the rpiboot program?
Yes
Afterwards the Yellow should appear as mass storage
Interesting - the storage won't show after running rpiboot program. It will only show once I follow USB-C recovery step. Doing that enables me to flash from balena. Currently flashing. Will update.
Rpiboot is part of the USB-C recovery procedure in the guide - as I said. Just Balena instead of the RPi Imager
I'm an idiot š
Is it working now?
Appears to be - yellow light came on and is going through the motions
does anyone have the exact dimentions of the home assistant yellow POE verson? im trying to make a costom server rack mount for it before i receve my preorder
Dimensions are listed
oh i didnt see them there thanks
Good evening everyone, hoping to get some assistance with my newly arrived Home Assistant Yellow PoE. I canāt seem to get it powered on. Iāve tried reseating the CM4, different switches (UniFi Pro 24 PoE and Enterprise 24 PoE), different cables⦠everything but another CM4 or Yellow because of course I only have one of each. My searches have found similar issues but no solution I saw. Plz halp
Used a fresh install per the guide on a usb, my pi is a CM4104016, I have a 1TB Samsung 990 Pro I was planning to transfer the OS to if possible and a Zooz 800LR Z-wave GPIO module as well. Really bummed this isnāt powering on as Iāve been waiting to do my whole zigbee and z-wave deployment once I had it up and running. The yellow was the last thing I was waiting for.
The Samsung 980 Pro is incompatible, so chances are the 990 Pro is incompatible too. Are the PoE switches configured to provide passive PoE (not compatible)? You can try to power the Yellow with a 12V 2A 5.5 mm barrel plug.
Thanks @wary pivot . I saw that about the 980 pro after scrolling up a bit last night. Guess itāll just slide into my desktop now lol. My switches are both active PoE that currently power my wireless APās and surveillance cameras. Iāll have to look around for a charger thatāll work. Itās very odd that itās not getting any power, makes me feel like a jumper is on the wrong pins or something.
Jumper JP5 is the one to select the PoE classes
Is your switch set to provide PoE or PoE+?
Iāve tried both PoE+ and PoE++ ports and I have plenty of room in my available PoE budget (each switch provides 400w of which I use maybe 50w)
Okay JP5 is currently jumpered in the Cls3 position
You can try the 990 Pro, just be aware it might not work (make a backup first and download it). If you try that SSD, let us know the outcome, please.
Will do for sure, I thought it was a great deal for $70 at Microcenter. Once I get this powered up and running Iāll give the ssd a shot.
Just to be sure... PoE is activated in the Unifi software?
Just verified, I donāt have PoE disabled for any port. š«
Usually I plug in a PoE powered device and I start getting blinky lights right away on my switch. With this, nothing for a few seconds and then just the āconnectedā light comes on not the PoE light
And the Yellow doesn't start to show its LEDs, I assume.
If it keeps failing to start with PoE, you might consider to contact the support at yellow@home-assistant.io
They can look at the QA logs and assist with a possible hardware failure.
Yeah no LEDs. I took a short video and a picture but I guess canāt upload them to this chat.
Please use imgur or other image sharing web sites, and share the link here.
Image posting is blocked in most channels to discourage people from sharing text as images. Sharing text as images assumes that everybody sees the world as you do, which isn't the case. Some people are colour blind, or have visual impairment that means they can't make sense of an image of text.
But keep in mind that today is release day - so the team might need a bit to respond
Thanks @wary pivot , Iām sending an email now.
doing my first install of a yellow, how long should I expect to wait before I can hit the home page?
its flashing with network and pi activity
I am probably being impatient
I was
Got my Yellow in today and attempting to install HA onto WD Green SSD. Looks like I'm running into an issue not seeing the SSD. Console says from the yellow-installer:
[ 21.941305] haos-flash[236]: Installing Home Assitant OS 10.3 to nowhere.
[ 21.941874] haos-flash[236]: No storage media found, exiting.
Thoughts?
It might be the SSD, plenty of WD black don't work. A WD blue was reported working. Also, is it a nvme or sata SSD?
Hi All, I just got my HA yellow POE with CM4 (w/ EMMC). I have an existing HA installed on a raspberrypi with the OS and DATA on an M.2 stick.
Is it possible for me to just transfer the m.2 stick and have it auto boot without having to do anymore changes?
The Yellow has a custom HAOS image. The one for Raspberry Pi will lack some features like the internal Zigbee coordinator.
Best practise is to install HAOS for Yellow and recover a backup.
Thank you for noting on the custom image. Noted and will do a restoration from backup
If you want to reuse the m.2 in your Yellow, make sure it is a NVMe and not a SATA SSD, it is not listed as incompatible (https://yellow.home-assistant.io/faq/#which-ssds-are-not-supported) and wipe all partitions on it before.
noted.
Hope im not stepping out of line giving advice here, but I just set mine up last night and had exactly the same issue.. turned out i didn't fully seat the CM4 onto the PoE yellow.
Started up just fine after a proper re-seat.
I'm having a nightmare experience with my Yellow. Yesterday my install became unhealthy after I did a shutdown via the UI so I could move it into another room. No matter what I tried from various guides, I could not repair the supervisor so I opted to do a clean install and restore from a backup (i wonder if I disconnected the power too soon and something got corrupted?). I have a backup that's 2 days old, and multiple others from the last couple weeks. So far none of them work, the restore process never seems to complete. What could be happening here?
The restore needs quite some time on the Yellow, maybe it is still in the restoring process.
It is possible that it needs longer than an hour.
i swear it wasnt like this the first time i migrated to the Yellow.. but I'll give it a go i guess
You can still connect to the serial console and look for errors. But you usually don't see anything but the login until the restore is almost completed and it reboots.
currently doing a second clean install, then ill attempt to restore again.. but i have seen that being unable to restore seems to be an issue across various devices
what is extra frustrating is i set up HASS at a different location and migrated devices just last week with no issue, but my HASS yellow at home is just refusing to do the exact thing I accomplished earler :/
What hardware have you been using at that other location?
i migrated from an old pi3 to a CM4 with a carrier board (not a yellow)
this current yellow, i migrated from a pi4 in April, and it was working spectacularly until yesterday
doing the restore now, but it's looking a lot like before. My SSD has an activity LED on it that was blinking like crazy during the initial install, but right now after hitting restore, it blinks maybe once every 8 seconds or so, which indicates not a whole lot is going on here...
@honest rover what are the supervisor logs showing?
you can kind of monitor the restore by observing them
i'll have to set connect to the console, one sec..
are you restoring at onboarding?
yes
I would skip that
i have also tried after onboarding..
but i will try again
currently in the console, i have not quit the current restore attempt yet
23-08-03 13:58:33 INFO (MainThread) [supervisor.backups.manager] Successfully imported fa9966c3
23-08-03 13:59:57 INFO (MainThread) [supervisor.backups.manager] Partial-Restore fa9966c3 start
23-08-03 13:59:58 INFO (MainThread) [supervisor.backups.manager] Restoring fa9966c3 Docker config
23-08-03 13:59:58 INFO (MainThread) [supervisor.backups.manager] Restoring fa9966c3 folders
23-08-03 13:59:58 INFO (SyncWorker_2) [supervisor.backups.backup] Restore folder addons/local
23-08-03 13:59:58 INFO (SyncWorker_2) [supervisor.backups.backup] Restore folder addons/local done
23-08-03 13:59:58 INFO (MainThread) [supervisor.backups.manager] Restoring fa9966c3 Home Assistant Core
23-08-03 13:59:58 INFO (SyncWorker_1) [supervisor.docker.interface] Stopping homeassistant application
#
and thats where it ends.
@compact quartz any idea why it just stops?
How big is your eMMC? I suppose you haven't moved the storage to the NVMe after the new install yet. Don't know if that would happen, if it runs out of space š¤
i dont have emmc
its a 512gb ssd with a CM4 lite that worked just fine for months :/
because core is being restored, the one which is running needs to stop
this is the same when you update HA core. You expect it to stop, you have no access for some length of time, then it comes back
Itās been quite a while.. but ok
so at that point, yes you would lose access
no more logs, but at least you got to see the restore of add-ons and folders prior to that
Currently trying to restore just home assistant, no add-ons etc. maybe Iāll have more luck doing things granularly
yeah, so whatever it might be choking on, if it is doing so, is related to HA core and config directory
do you have a large db?
ok so that sounds good
I could try a known working backup from like April⦠I saved the one I used to migrate
how long has it been?
It backs up every 2 days but I only kept the latest 4ā¦
I mean since it went down and waiting for it to come back
Oh like 45 mins
did you restore any http config which requires you to use https instead of http?
Nope
ok so no duckdns, your own domain, no reverse proxy
Only thing that could go wrong as far as I can tell is my backup password. But I set it to same as my login password
Nope, no fancy networking done. I run adguard but no dhcp server or anything
it wouldn't have extracted if the backup password was wrong
Iām gonna try this backup file on my spare pi4
or just pull power and then power it back up, see what happens
Whenever I do that I go back to the onboarding screen
Nothing has moved or changed but I can try
Itās actually screwed down lol
Could I have a bad SSD?
I'm not for CM4 Lite or booting anything pi related from SSD. Too many caveats. You could try clearing/cleaning the SSD to be sure
Every time I do a clean install I delete all the ssd partitions first using a usb adapter
do you ever notice if anything (data partition and data) has been written to it when connecting it to another pc?
after the restore I mean
Hmm I can check that, wouldnāt I need a Linux install to be able to see those partitions?
yup
but if you have a spare pi4 you probably have that? or the potential to have that
Yeah the pi4 has Manjaro on it currently
it's ext4 so should be good
Iāll investigate.
With a CM4 Lite and the onboarding showing there must at least be something from the basic installation on the SSD (data and partition wise)
you would think heh
Are there any alternatives? Like is it possible to manually restore yaml files from a password protected backup?
Something is definitely there lol. No usb installer connected or anything
Yes, but you would need to decrypt the backup manually and extract the needed stuff from the tar file afterwards.
Would 7zip show me a password prompt or something?
Plus if your config is extracted to the SSD you could copy it off without needing password
Hoo boy, wasnāt expecting to be running python stuff today lol. This was meant to be a simple all-gui restore š š
My fingers are still crossed
Iām gonna stop and chill and have lunch lol, this is just annoying me so much right now
before i do this whole process over, im trying one thing - individual restores. I just sucessfully restored one add-on lol, lets see how far I can get before it just stops
the LED flash patterns are definitely different than before
So yeah apparently, I didn't know how to seat the CM4 properly. There's a definite "click" for both sides, wasn't what I thought I was feeling at first. I'm getting some lights at least now lol
Nevermind! Every solved problem is a good one
unless the solved problem creates more problems
which I find to be the case lately for me
Well now Iām thinking that with my troubleshooting to get it on, I must have some corrupted installation files or something on the cm4. Is there a way to wipe/reset it so I can try a fresh install with the 990 Pro?
It definitely started installing and then lost power a few times
If HA itself is starting, you can wipe it by pressing and holding the red and blue buttons simultanously on powerup. Or you go the rpiboot path of the reinstall guide (option 2) and remove the partition on the eMMC with a partitioning tool before the OS flashing step.
something is seriously wrong with my backups.. or with the current version of Home Assistant with restores, because I just set up HASS on a spare Raspberry Pi and tried to restore and it too is doing absolutely nothing
Some seem to claim, that it's just taking (way too) long. š¤
I would try to restore and let it run overnight. And maybe raise that question in #installation-archived - just in case someone else has an idea.
If someone on a i3 NUC needs 4 hours...
weird, but i guess that checks out
that said, i just did this on a different CM4 very recently and it was the simplest thing ever
If your system draws too much power (maybe due to that SSD), you can change to a PoE++ port and change the JP5 jumper to Cls4.
thanks for your help today @jorg, still having issues restoring but I think i'm tapped out for the day lol.
ok i lied, i tried one last thing, i checked the core logs. This is weird, so in the supervisor logs when it gets to this point and stops:
23-08-03 18:18:49 INFO (SyncWorker_2) [supervisor.backups.backup] Restore folder share
this happens in the core logs this happened about 1 second prior:
2023-08-03 18:17:42.574 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /backups/6ffdff03/info - Backup does not exist
Thanks, I think I might go option 2. It looks like it's trying to do something but then the ethernet LED's both go off for a few seconds and just the red and green lights stay on/flash. I've waited for the yellow to come on constantly so I could try pressing the blue button to force the install on the SSD but it's never gone solid that I've seen, just flashing after the ethernet lights come back on. Also, I couldn't find the "reinstall" guide on the yellow.home-assistant.io site. Could you link me if you have it handy?
aaaaand just like that because I typed it I've been able to progress haha
The yellow seems to have no issues with the 990 pro. It reads it as storage but I will have to verify tomorrow if it installed the OS on the SSD or eMMC.
@wary pivot I canāt believe it. After almost 6 hours the process finished. Wtf
6 hours for 250mb jfc
That's a lot of coffee 
I almost unplugged it out of spite. Glad I listened to you lol. I didnāt even know it worked til I ran my Goodnight scene in HomeKit and my z-wave lock responded lol
Hello all. Got a new 980 EVO Plus drive -- installed it, now I can't get past solid green & red lights and console access doesn't appear to be working. I removed the drive and still have the same issues. Held the blue and red buttons to and put the USB drive in to reflash but have the same situation. Any suggestions?
There is no Samsung 980 Evo Plus NVMe. Either a Samsung 970 Evo Plus, a Samsung 980 or a Samsung 980 Pro.
Yes, 970 EVO Plus...
Usual steps to troubleshoot are:
a) check if CM4 is fully seated in its sockets (makes a satisfying click on install)
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 Yellow's storage by following option 2 of the following guide
https://yellow.home-assistant.io/guides/reinstall-os/
Should I even see something on the console if there's no OS?
You should see the boot process of the installer USB stick you have plugged in on powerup
I'm not even seeing that now. I did yesterday.
When you connect to the serial console you just get the messages from that time on. It's not entirely like a monitor.
If it is connected on powerup/reboot, the boot process should be observable. You have used an installer USB as mentioned in the startup guide, right?
If the green LED is starting to flash 3 or 4 times, you might have to reinstall the CM4 firmware.
Yesterday I was able to see the whole boot sequence. Today, I'm not seeing the boot sequence even after removing the drive. I even reinstall the WD drive to replicate what I had yesterday - but that failed too.
Many WD drives are incompatible
I'm also using CM4 lite, no eMMC.
Ah. The painful path.
I think something else is wrong because I'm not even seeing console output now - even without the drive installed.
Does reflashing the installer require eMMC?
The most common culprit is a not correctly installed CM4
Maybe
Some older CM4 Lites need the firmware to be updated, before they are working
I'd go with the CM4 firmware update guide
If that fails, reseat the CM4
Do you have a m.2-to-USB adapter at hand?
Believe it or not, it needed to be reseated. I'm now seeing console output.
Thank you, @wary pivot.
This looks much better:
[ 22.918829] haos-flash[240]: Installing Home Assitant OS 10.4 to nvme0n1.
Just in case you are going to recover a backup after installing: the recovery process takes extremely long at moment and it looks as if it is doing nothing anymore. Be patient and take several pots of coffee and let it do it's magic š
Do you mean a restore?
Sorry. Yes, I meant a backup restore š
The tar backup is 4GB, so good to know it will take a while. Honestly, the HA install itself was pretty quick.
Oh dear. 4GB will take a heck of a time, I suppose
I still have console access. Is there a way to check the status of the restore?
Not really
Well, you could login and look at the supervisor logs, but they don't provide a progress estimation.
it takes me several pots of coffee reading thru the discord alone š
im making coffee as I type this
I dunno why I decided to update the OS on this PI
but it's making me want to curse
thankfully I'm not actually waiting on it for anything
Just do what I did and wait 6 hours
It worked. Itās ridiculous, but it worked
Grr. Looks like my backup can't be restored because the version of the supervisior I have loaded is a lower version. Says I need to update supervsior first - however, when I run the update from the CLI, it says I have the latest version. I'm assuming I need to indicate that I want beta version someplace.
You are restoring a beta backup?
Yeah
Okay... if you cannot do it in the UI, you login to the serial console (user: root) and run ha supervisor options --channel beta
OK, then I'm doing the "ha backups restore [slug]", yes?
Afterwards a ha supervisor reload
Opps, yes, then the restore.
I suppose a ha supervisor update might be needed first
GPIO layout
TXD = GPIO14, RXD = GPIO15, SCL = GPIO3, SDA = GPIO2
rm4
Hi. Got my yellow POI this week, but it doesn't seem to be able to install the OS. Have tried both USB stick and from other computer. Green and red leds steady on, no yellow. Any suggestions/ideas?
Check if the CM4 is fully seated in its sockets. It makes a satisfying click when inserted. That's the usual cause of that issue.
Checked and appears OK.
Or checked as well as I could without removing cooling fin - afraid of breaking plastic tabs.
You can give it a slight push on the heatsink as described here:
CM4 is down to the same level on all sides, and toucing the screw mounts. I did the heatsink push.
You can connect the Yellow to your PC via the USB-C port, connect to the serial console and look for error messages after poweron
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
Serial console doesn't seem to work (I am on linux)
Aug 5 15:30:58 nuc ModemManager[2030]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3.2': not supported by any plugin
Aug 5 15:30:58 nuc brltty[1442]: USB configuration set error 16: Device or resource busy
Aug 5 15:30:58 nuc brltty[1442]: USB interface in use: 0 (cp210x)
Aug 5 15:30:58 nuc brltty[1442]: USB control transfer error 32: Broken pipe
Same result on bith desktop PC and laptop
Is it powered when using screen?
No, wanted to try to at least get a /dev/ttyUSBx first
But /dev/ttyUSB0 appears and disappears right away
If you run screen /dev/ttyUSB0 115200 and power on the Yellow, does it show anything?
screen complains that there is no /dev/ttyUSB0. /dev/ttyUSB0 disappears as soon as it appears.
Is there any way to attach a log file in discord?
Please use a code share site to share code or logs, for example:
- https://dpaste.org/ (select YAML for the language, and consider picking a longer expiry)
- http://pastie.org/ (select YAML for the language)
- https://paste.debian.net/ (you guessed it, select YAML as the language)
Please don't use Pastebin, since it can randomly add spaces to the main view. Please also don't share text as images since it makes it harder for people to help you. Remember that others may have colour blindness, impaired vision, etc.
Same applies to logs
Thanks!
Have vou tried to reboot you PC with the Yellow attached?
No, that is a good suggestion. Will try. I assume Yellow should not be powered?
I'd let it powered, just to be sure it can be detected
You said you tried to install "from other computer" - is jumper JP1 by any chance still in setting USB? It needs to be in setting UART
It is set to UART
Well, it has detected the CP2102N at one point š¤
Maybe trying another USB cable?
Same result with other cable. I might boot the laptop into windows, but now I can't find the instructions for doing terminal connection in windows (I am not a windows user)
Ah, yes. Who ever reads the backlog? š
No worries
In windows, CP210N shows up, but under "Other devices" and no COM port attached
trying to update driver
No driver found
Even if you power off and power on the Yellow?
yes
No SSD
You have connected to the Yellow with the rpiboot method to install something to it?
Yes, after USB stick method didn't work
Just to rule out the firmware of the CM4, you could try to reinstall that
https://yellow.home-assistant.io/guides/flash-cm4-firmware/
If there is still no output afterwards, you should contact the support at yellow@home-assistant.io
Will do! Thanks!
That helped! I was able to write installer to drive, now I have it running! Many thanks!
That's great! The serial console is also working?
yes
I probably need a m.2 SSD - any ones to avoid (or any specifically recommended)?
Those are reported not to be working:
https://yellow.home-assistant.io/faq/#which-ssds-are-not-supported
Samsung 970 Evo Plus are great. I have some doubts about the 980 (without Pro - the Pro is incompatible).
But there are also some cheaper SSDs other users are happy with
A "small" one like 250GB should be enough for most usecases.
Thanks!
As reference: the HA Blue (the limited edition of the Odroid N2+) came with 128GB eMMC storage
If you have a special need for more storage - the sky is the limit š¤£
ugh trying to setup my yelow now that i have a cm4 available ... and just getting a red light.... is ther ea magic reset im missing? my cm4 came from another device
nm found the pinned post
hmm still not workin will play more in the morning
Has anyone been able to successfully run a Coral USB with their yellow? Mine is connected, but when I enable it in frigate, frigate continually crashes and says it cannot find the Coral
I haven't been able to and I know nobody, who was reliably able to.
Im not using a yellow, but I updated Home Assistant core last night, and now Frigate wont run due to errors with the Coral. Did you update recently? Is this a new install?
I've been trying to get it to work for the last few weeks
What's your config look like for the coral / what are the logs saying?
The issue is not update related. The Yellow has problems to keep a stable USB connection to the Coral, even with a powered hub. If it starts working, it crashes a few detections later.
Interesting. Just a coincidence I guess. Mine has been running fairly flawlessly for a few weeks now. Didnt give me issues until I updated.
Good afternoon all, I just used a USB and Pi OS Manager to install HA Yellow on my Home Assistant Yellow. Install went precisely as documentation described, up until removing the USB/Rebooting. Wherein I am now getting a Solid Green and Solid Red light, but no activity light and no sign of the device on the network (despite flashing lights on the Ethernet and Switch ports). I have re-seated the CM4, and have attempted a factory reset, but nothing happens.
Usual causes are a not correctly/fully seated CM4
https://yellow.home-assistant.io/faq/#my-home-assistant-yellow-appears-broken-no-led-is-lighting-up-what-can-i-do
or a CM4 firmware issue.
https://yellow.home-assistant.io/guides/flash-cm4-firmware/
If you are using a SSD, make sure it is a NVMe and not a m.2 SATA and that it is not listed as incompatible.
There is also the option to flash the installer directly to eMMC with option 2 of this guide:
https://yellow.home-assistant.io/guides/reinstall-os/
And to look for error messages, you can connect the Yellow to your PC and use the serial console
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
I removed the SSD as a test.
It seems to be booting now.
It is a Mushkin (CORRECTION: MICRON, not Mushkin). 7450 MAX 800GB
Did I miss some kind of preparation of the NVMe SSD?
formatting or something the like?
Home Assistant should partition it itself, but I would remove existing partitions just to be safe.
Fully remove everything? or should I wipe and set to EXT4?
I have just removed all partitions.
But: Another user had problems with a Micron 7450 - it might be incompatible
ah poo.
okay, well I donāt NEED the NVMe, I did grab the 32GB CM4.
Iāll have to see what other NVMeās I have kicking around. I might be able to swap the Micron for a Samsung 970 EVO. Not on the INCOMPATIBLE list, do you know if one of those has worked for people?
The 970 Evo Plus is working, so I expect the 970 Evo to work too.
Excellent! well thank you very much for your assistance @wary pivot ššš
I do like that they planned for different sized drives, cause I took the one I pulled from my steam deck to put in the yellow.
Hello, currently i'm using raspberry 4b and i'm completely satisfy with it except one thing: it does not start automatically after UPS is discharged completely and power is restored. It has solid red led at this situation. I'm using ArgonOne case, which is setup to start board on power plug and this feature works fine when i unplug/plug original raspberry's power adapter to UPS (CyberPower, if really matter) or directly to wall-socket. Recently i've discovered that my router (mikrotik hap ac) has 'Wake on LAN' tool for such situation, but raspberry doesn't support it. As i see yellow board is based on raspberry as well , and it has external lan interface, so, does it support WoL?
oh, and i'm using the NUT community addon for UPS integration to HA. There was an shutdown_host option which was always enabled, i've disabled just now to verify that rasberry does not turn on automatically because of it was shutdowned softly. Does it make sense? just could not check by myself since don't have physical access
A WoL after a shutdown? Never tried it. After a graceful shutdown, the Yellow also shows a red LED and doesn't power off like a PC. I'm using a Shelly Plug to trigger a powercycle, if the UPS commands a shutdown and doesn't drain completely.
But a nice thing to try. Shutting down and sending a WoL packet (I don't expect it to work) 
Nope. Not waking up from shutdown.
I thought about a smart plug, but didn't figured out how HA will turn on back a plug after it has been disabled?
In my case it doesn't do it itself. But HA notifies me (via NUT integration) on a power outage and shuts down when commanded by NUT. I can VPN into my router when the power is expected to be back up, connect to the Shelly's web portal and turn it off and on.
Not perfect, but better than having to be on site to restart it.
yeah, but it's what i'm trying to avoid ) Seems that it's time for mini PC with WOL, strong CPU, and forget about decode issue on plex)
N100's are recommended often (except you have the need for much more processing power)
#hardware-archived can help, if you need help choosing a good mini PC
can anyone recommend a good document for reinstalling my Yellow? i followed option 2 here - https://yellow.home-assistant.io/guides/reinstall-os/. it boots and i see a "yellow-installer login" on the console, but it never installs (it has never worked properly. it had trouble connecting to my network and after debugging, i decided it was time to start over)
It is supposed that the first start after option 2 is the installer. When finished HAOS should be installed. If that fails, you can install HAOS directly. Follow the same guide, but use Balena Etcher, download the current version of HAOS from GitHub (Warning! Use the image for Yellow, not the one for RPi4!) and flash that to the eMMC
it is strange. i get a "yellow-installer login" login prompt, so it is running the installer image, but the install does not auto launch. is there a way to trigger the installation to run manually?
It does automatically (at least it should, if nothing goes wrong). The status is shown by the LEDs
the yellow light stays in the heartbeat blinking mode for hours
Does the Yellow have full internet access?
There has been a hacky way to abort everything and start it manually - but no guarantees.
And I don't think the script not running is the problem
after i did the reinstall, it does have internet access. i connected to the console, logged in, and i am able to ping public servers
Good Morning - i just got my Yellow and am facing an odd issue:
When trying to configure the "Yellow Zigbee Home Automation" i“m getting a message "Unknown error occured".
I don“t really know where to get any logs for it and what the issue really is.
I first thought it could be something related to the Matter Server/Beta i was using so i uninstalled the Add-On and Integration. But the Issue still persists.
I also thought "lets try to use that Multi Protocol Thingy" - but i was unable to install that one either. Zigbee2MQTT is not working either.
Do you guys have any clue on how to fix this? Thread Integration is also not in use at all.
Overview of all integrations: https://imgur.com/C4vBsfu
Overview of all Add-Ons: https://imgur.com/vT1EmBr
Issue when trying to install Yellow Zigbee: https://imgur.com/XLQyStk
You propably messed up the radio firmware. Deinstall all Multiprotocol or OpenThread add-ons and Zigbee2MQTT. Remove all ZHA and Thread integrations. Restart HA and install the "Silicon Labs Flasher" add-on, configure it to use /dev/ttyAMA1 and run it. When it completed successfully (look at its log section), deinstall the add-on and restart HA. ZHA should be autodiscovered and be able to be configured.
i get that log output and don“t know if it has been successful or not: https://dpaste.org/Nok3h
(And don“t know how to access the Container logs thought)
It has been successful
Issue with configuring ZHA still persists - getting unknown error
Did a full restart of the Yellow
Check if the CM4 is correctly seated.
Ye that was it - argh i read that seating thing before and thought i did it fine - that force there feels odd to apply thought š
Thank you for your help š
Is there any way in ZHA to see the current radio firmware version? I don't see it anywhere...
Also is my yellow Zigbee radio properly detected by ZHA? It says HUSBZB-1, but, isn't that the old Nortek stick that also has Z-Wave?
Download the network backup and it will be in the JSON
As for the displayed name, it's cosmetic and will be fixed in a future release. The Yellow is detected fine.
Awesome, thanks!
Hey, I'm having issues with my HA Yellow. I have a CM4 in it w/ eMMC, and I've flashed my USB drive (multiple times to be sure), and it never gets past the yellow heartbeat. I can see the device on my network (shown in my Unifi administration panel), and I have tried clearing eMMC multiple times by holding in the blue/red buttons for 15+ seconds (with no USB plugged in) during boot.
I have tried about 15 times in the last 2 weeks, and it never gets past the heartbeat... even left it for over 24 hours.
Any ideas what I can do?
Usual steps to troubleshoot are:
a) check if CM4 is fully seated in its sockets (makes a satisfying click on install - this is very often the main problem)
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.4/haos_yellow-10.4.img.xz) and flash it to the eMMC by using the program Balena Etcher for example.
a) yes (have done this three times to be sure, also tried alternate CM4 eMMC)
b) yes
I will get to work with the next steps, thanks.
And if you use a m.2 SSD, check if you really have a NVMe in use and not a SATA and if it is known as imcompatible.
Not using m.2 right now (was planning to add later)
yellow-installer login: root
[ 35.804795] cam-dummy-reg: disabling
[ 49.172928] audit: type=1334 audit(1646984057.903:11): prog-id=0 op=UNLOAD
[ 49.179889] audit: type=1334 audit(1646984057.903:12): prog-id=0 op=UNLOAD
[ 49.186821] audit: type=1334 audit(1646984057.903:13): prog-id=0 op=UNLOAD
never goes to shell, seems frozen (not responding to additional ENTER presses)
Is there somewhere I can paste the full boot log?
You might be in the shell. New messages will be showed like that. It's not like a monitor.
Please use a code share site to share code or logs, for example:
- https://dpaste.org/ (select YAML for the language, and consider picking a longer expiry)
- http://pastie.org/ (select YAML for the language)
- https://paste.debian.net/ (you guessed it, select YAML as the language)
Please don't use Pastebin, since it can randomly add spaces to the main view. Please also don't share text as images since it makes it harder for people to help you. Remember that others may have colour blindness, impaired vision, etc.
Same applies for logs.
I'd try the firmware reinstall
Yeah so looking at that, I only see Windows instructions (I'm on macOS). https://yellow.home-assistant.io/guides/flash-cm4-firmware/
Here you can find the way to get rpiboot for macOS
https://github.com/raspberrypi/usbboot/blob/master/Readme.md#macos
Sounds good, looking now
@steady beacon I converted your message into a file since it's above 15 lines :+1:
Still didn't work.
@steady beacon I converted your message into a file since it's above 15 lines :+1:
First bootcode.bin is always successful, but then fails successively
But it runs through it all fine if i have rpiboot waiting ahead of power on with JP2 shorted
Green light stays blinking.
"On Compute Module 4 EMMC-DISABLE / nRPIBOOT (GPIO 40) must be fitted to switch the ROM to usbboot mode. Otherwise, the SPI EEPROM bootloader image will be loaded instead." is this something to consider?
Yeah, now back in UART mode, and seeing same stuff from yellow-installer
I'm going to flash to eMMC now
Using https://github.com/home-assistant/operating-system/releases/download/10.4/haos_yellow-10.4.img.xz to flash, I should decompress this first right?
No. Just download it and use Balena Etcher to flash that compressed image
So far so good.
Flashing finally done. Moving back to UART and booting up (without USB drive of course since installer is now on eMMC). Seeing progress so far.
Seems to be delaying on Network Time Synchronization... ok, it finally passed.
Alright, at Preparing Home Assistant screen. Looking good.
Thanks for the help @wary pivot . To summarize, what worked for me:
- flash rpi firmware (using rpiboot via USB)
- flash eMMC with release (using balenaEtcher via USB)
Well, you didn't flash the Installer, but HAOS itself. A shortcut
Oh, oops, yeah, the release.
Glad it worked
Me too! Can finally move forward again š
All working great.
What is the Home Assistant Green? An upgrade of the HA Yellow or something entirely new?
This is Home Assistant Green. The system with the lowest electrical power consumption on the market.
wow! can I earn CO2 credits with this? Patent it!!!
Sure! You can also collect bonus miles
sorry, I want airmiles...
It is wireless, they also count as airmiles
Is anyone running into issues with audio since the 2023.8.2 update?
Im getting either 0 audio devices, or if i try to reload im getting error 500
[core-ssh ~]$ ha audio reload
Command completed successfully.
[core-ssh ~]$ ha audio info
ERRO[0000] Unexpected server response. Status code: 500
Unexpected server response. Status code: 500
I get the same output with ha audio info . When I'm back home from work, I'll try if there is still audio output with the VLC add-on (there the built-in stereo is still selectable as output).
how hot do your yellows get? and how hot they can be without getting hurt
Normalt ligger min runot 45-50 C och nƤr jag gƶr tex en bakup sƄ rusar den upp runt
Sorry, Normally, mine is around 45-50 C and when I do, for example, a backup, it rushes up to about 62 degrees C
Mine is running at 50.6 °C CPU temperature with 10% load. The CM4 operating temperature range is up to 85 °C
Tnx
Audio output by the VLC add-on is working despite those error messages when running `ha audio info'
I bought a yellow pre assembled, my unit is a 1.2 revision. I don't get past the red power light, any advice?
Hello All, my yellow's USB's have died for all but USB storage devices. None of my z-wave or zigbee dongles work in it anymore even with a powered USB hub but work in my other Intel NUC's and PC's. Any Advice? Device is less than 6 months old
Check if the CM4 is fully placed in its sockets like shown in the following guide. If that doesn't work contact support at yellow@home-assistant.io
https://yellow.home-assistant.io/faq/#my-home-assistant-yellow-appears-broken-no-led-is-lighting-up-what-can-i-do
Hi, I'm trying to get zigbee2mqtt/ZHA to work on the Yellow, but the publish commands keep getting timed out although interviewing worked. I tried different firmwares also with/without the multiprotocol addon, but I keep keep getting the same problem. Any idea what this might be?
You got the radio to work with ZHA/Z2M (it is starting without errors)? If so, #zigbee-archived might be able to help
Well I can't read/write any states unfortunately. The interviewing process is working
When you say Z2M/ZHA, are you trying to run both at the same time?
No, I tried them both seperately
Sounds like your Yellow is positioned in a spot with a lot of interference. Is it in a networking cabinet or near any WiFi routers, SSDs, or other computers?
It is as I'm debugging why it isn't working. I'll try to move it, I hope that's it to be honest.
Zigbee2MQTT:error 2023-08-15 19:49:58: Failed to configure '0x842e14fffe3665f3', attempt 2 (Error: Bind 0x842e14fffe3665f3/1 genOnOff from 'x/1' failed ({"address":58469,"clusterId":32801,"sequence":8} after 10000ms)
at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)) it's giving the same error unfortunately
Are you using the multi-pan firmware? I had a lot of zigbee problems with it and realized I don't really need to use it so I switched to the latest Zigbee only firmware using the Sillicon Labs Flashing addon and it is working beautifully now...
If you do this, make sure you set the Baudrate to 115200.
Add thread devices
I tried the 7.3.1 version the addon is flashing and this one as well https://github.com/NabuCasa/silabs-firmware/blob/main/EmberZNet/NabuCasa_Yellow_EZSP_v6.10.3.0_PA32_ncp-uart-hw_115200.gbl it's giving the same time outs
Hey all, I'm having trouble getting the installer to run on my new HA Yellow with POE. I'm using a CM4 with no MMC, and 1GB of memory. It's all I could get my hands on for now, but I plan to get one with more memory when I can. I have a Samsung 970 EVO Plus 2TB Internal SSD PCIe Gen 3 x4 NVMe installed. When I plug in the network cable, the red LED lights up and the green LED blinks once, then both the red and green LEDs stay constantly lit. I've tried all the obvious things I could think of like ensuring the CM4 is totally seated, ensuring the nvme is totally seated, and I've tried 2 different flash drives. Any ideas on what the problem could be?
Hi all, any recommendation for a gsm module that works with HA Yellow? Thanks
You could try to reflash the CM4 firmware.
Thank you! I'll give it a try.
YES, That was the ticket, thanks so much for the direction
I donāt but is interested as well. If you find any, please share
@wary pivot I plan to adjust the LED blinking patterns in the Yellow Installer (Installer only): Use steady blinking during bootup and fast blinking during flashing. This way it should be easy to identify if the OS is running or the Installer ... Thoughts?
Sounds like a good idea
When we are at LEDs. Would it be possible to react to error codes of the OS or the installer by changing the red led to a blinking pattern? @shut cedar
I'm having trouble getting my OpenThread Border Router working. I ended up removing the integration as it was repeatedly failing to start, and when I add it back it is asking for the URL for the OTBR REST API. From my reading it seems that the API should be provided from the silabs-multiprotocol addon, which is currently running as v2.3.1, but a docker ps in terminal doesn't show any ports exposed for silabs-multiprotocol and I additionally don't see anywhere that 8123 is exposed, which leads me to believe there is some sort of ingress. I'm unsure what host or port to specify for the API URL and I don't know how to find it.
well, I can't find anywhere that specifies it, but I happened upon the correct URL in a screenshot for debugging interference here: https://yellow.home-assistant.io/guides/about-multiprotocol/
I'm not sure how you are supposed to figure that out otherwise.
The OTBR integration will autodetect the add-on. Just remove all Thread related stuff from integrations (including disabled or ignored stuff) and restart HA. If the add-on is working properly, those integrations will be configured automatically
Yeah I was considering such patterns, especially for the installer. But its a bit a pain to implement, the installer is currently just a shell script š
Maybe something for the next color š
Can someone point me to yellow POE kit documentation? Trying to determine if I can temporarily power the yellow through the usb-c port?
You cannot. You can power it either via PoE or via the barrel plug. If power is provided to both, the Yellow uses the barrel plug. The USB-C is for serial console (UART) and CM4 device access (storage/firmware) only
Hello everyone, I have the HA Yellow Rev 1.3 and an Intenso M.2 SSD 512GB. Unfortunately, I can't get the SSD to work. Anyone an idea. Thanks
Which one exactly of Intenso's SSDs are you trying to use?
Intenso Interne M.2 SSD SATA III Top, 512GB, 550MB/Sekunde 1
ASIN: B0776YFLWL
SATA drives are not compatible. The Yellow only supports NVMe drives (but be aware of the list of known not working ones)
Where can I find the list of SSDs that work?
You can also search for a SSD model in this channel to look for some user feedback for it (if someone wrote something about it)
I find only the samsung 970 evo plus mz-v7s500bw should run?
The 970 evo plus is fine, but there are also others (cheaper).
I'm a bit suspicious about the Samsung 980 (non-pro) but that's not based on evidence yet.
okay thanks then I'll order the 970. I'm currently running HA on a Pi4 and said Intenso 500GB. Hope that's my 6GB backup then I can import it on Yellow?
That should work. But a 6GB backup will take a ton of time to recreate. It will look like it has crashed.
Yes, that will definitely take time. Thanks for your help
Hello! Not really sure if this is the appropriate place to ask, but what is the average delivery time for yellow? I ordered mine in April this year, but still see shipment details as "Label Created" only.
Depends on the distributor. Raspberrypi.dk is known to be quite quick, crowdsupply is... existant and with Seeed I haven't had any experience yet.
Gotcha, I am from Canada, so did CrowdSupply..
maybe here -> https://www.crowdsupply.com/contact/status-pre-shipment
I am in canada and ordered one from CrowdSupply 2 weeks ago, it came within the same week. If your delivery is taking so long I would follow up.
Wow! Thanks for the info! I sent them an email yesterday, waiting for the response
cm4 finally arrived, got it installed and working but then looked at the m2 slot and one of the pins is bent š¦ off to support i go .. but before I do that, is there anything to use the m2 slot for other than ssd? if i have emmc on cm4 (i do) it doesnt seem too important
It is intended for a NVMe SSD. Haven't heard about anyone using it for anything else. If the pin has been bent on delivery, you should contact the support at yellow@home-assistant.io or the distributor.
yeah what i figure,, so far as i know its been since, just trying to get it up for the first time heh since cm4s have been hard to come by... but working now, managed to get 2g 16 emmc ... woulda preferred more ram of course
A short circuit might damage your CM4, so I wouldn't recommend using it.
Depending on the contact condition
true didnt notice till buttoning it up so its already running but good point since it is wired direct to it
Is there anyway to airplay to my HAY and have it output to the audio jack?
only if it's in the middle of the barn
I ordered my yellow from SEEED and received it in less than a week. I am in the US
Did you have any issues with customs?
they have a us warehouse, but seed even from china is very very fast
Good to know. Thanks for sharing!
Hi folks, just received my yellow, I made a backup from my VM (~280 MB tar file), my yellow having been restoring for now 3+ hours, I got an ECONNRESET on the URL, do you know why it takes so much time?
In the backup there is a 1 GB MariaDB database, but I don't think it would take so much time to copy 1 GB file
I have the lite one with an NVMe
Yeah, it needs a lot of time.
remember a shutdown can take 5 minutes š
it's also not just 'copying files'
Apparently it finished during night
@ashen dagger I converted your message into a file since it's above 15 lines :+1:
@ashen dagger I converted your message into a file since it's above 15 lines :+1:
I'm starting to think that it could be a hw issue, any idea on what could be happening?
What exact SSD model are you using?
it's a FORESEE E2M2 064G, but the rpiboot error happens with the SSD disconnected
actually, if I boot from the install USB, the process seems to complete correctly, it's when rebooting right after that I get the red&green solid lights
I wonder if those errors line up with a CM4 that is not fully seated
Did you add it yourself? And heard some good clicks when it was inserted?
yes to both š I can try and re-seat it. Didn't think it was the culprit due the install process working fine (I can see yellow-installer asking for an IP on my DHCP server when the install runs) but never hurts to be double-sure
The SSD is one salvaged from a Steamdeck, right?
yep
had a Samsung EVO already lined up for this, but it was a nice coincidence that the deck left me with one laying around
As far as I see, the 64G module from a Steamdeck is an eMMC and not a NVMe
hum, that's right, didn't realize that the 64GB model is the only one using eMMC
should I try using the EVO then? would it make sense that the rpiboot failed due to the eMMC disk connected during install?
I've just reseated the CM4 with two very audible clicks
going to try rpiboot again
same exact output. Just noticed that on dmesg I get USB disconnect, device number 36 at the exact same time as Successful read 4 bytes on the rpiboot logs
Sometimes it helps ro reflash the CM4 firmware
things are happening, green light is blinking on a steady short blinks pattern...
gotta wait for a minute now, but this is very promising!
I would leave heatsink off during setup/installation and only attach it once everything is up and running, and after a successful reboot
ah, no luck I'm afraid, the install process works as expected, and then it reboots back to solid red&green
Which install process have you been using? And where did you try to install it to?
I've been using this guide: https://yellow.home-assistant.io/power-supply-nvme/
as per the where, my understanding is that if the installer detects the SSD, it uses it, and it uses the CM4 internal memory if there is no disk, right?
mistery solved, it was the SSD
although I don't fully understand how, as I tried to install the system to the CM4 directly and didn't work either, just swapping the eMMC module with the NVMe one and reinstalling did the trick
No. It installs to the eMMC by default. If no eMMC is detected (for CM4 lite models), it installs to the NVMe (if present).
For CM4s with eMMC, the installer has to be forced to install to the NVMe (it's an option, but not recommended)
ah, I see... wonder if the install now installed it directly in the CM4 or the NVMe... I'll check as soon as the web interface gives me access
If it behaves weired, you might have to wipe the OS and reinstall it from scratch.
hope not, that's what I just did š
on the storage section of the config, I'm only seeing one disk, not two
so it could be that the CM4's internal storage is missbehaving, and that plus the invalid SSD could explain the whole thing
running mount on the new install only shows mounts related to the SSD, it doesn't seem that the CM4s internal memory is being used
well, in any case, I have the yellow up and running even if it's just on the NVMe directly, which is way further than I was an hour ago. Thanks a ton for all the help! š
Does it show something like lifetime in the storage section or just the used space?
just used space
Then it's not using the eMMC (at least for the data part)
yep, I think there is something not going well with the CM4's eMMC
If you connect your Yellow to your PC via the USB-C port, you could login to the serial console and use lsblk to check, if the eMMC (if it is not a lite model) is detected by the OS.
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
https://yellow.home-assistant.io/guides/use-serial-console-windows/
They sent from China to Europe (Netherlands) in 4 days
Hello all. I have bought a yellow. But the USB ports are not providing power. If i put a device in the USB-A port, no 5V is applied to the device. Anyone knows how to resolve this ?
I design and produce electronics, so i have a full skillset to debug. But this one seems very weird
Basic power supply should be present on the USB-A ports. But it is quite limited. For power hungry devices, a powered USB hub is needed
I put in a zigbee dongle. When i put the board into a USB-A in the PC, the red led comes on (directly to 5V). and when i put this into the yellow, no led lights up
So i don't think it's loading the 5V supply too much, it's just not present
The CM4 module is powered and online, so U16 on the schematic will work
U9 is a chip that needs a USB power enable signal
This comes from U7
Could it be that U7 has issues ? Or does the command to U7 does not get asserted to enable the USB power ? If the muxes are not set correctly, this might be an explenation ?
According to the schematics U16 provides 5V for the USB ports
U16 is the general 5V for the CM4 and the USB
But on page 3, you can see there is a power switch handling the over current in coordination with the hub
But this needs to be enabled by the hub
The hub being U7
If you suspect an issue, you should contact the support at yellow@home-assistant.io
Okay, thanks. I will try this
How can I check the version of the zigbee firmware on my Yellow? And how can this be updated?
I tried https://github.com/NabuCasa/silabs-firmware/wiki/Flash-Silicon-Labs-radio-firmware-manually, but didn't work
nevermind š¦ asked too soon
Disable ZHA (temporarily), install, configure and run the Silicon Labs Flasher Add-on (can be deinstalled after running) and reenable ZHA
ah didn't know about the Add-on, so I still learned something new š
That will install the latest EZSP firmware for ZHA (without Thread). If you want Thread only, the Open Thread Border Router Add-on will install the according firmware, the Multiprotocol Add-on the firmware for the combined function.
For each one: the radio must not be in use by any other Add-on or integration.
Thanks a lot š
any other suggestions to investigate zigbee slowness? Like if an automation triggers it takes several seconds before lights turn on
and one more question about the flasher add-on.. There is one add-on that performs all the flashing right? or..?
Silicon Labs Flasher = Zigbee only firmware
Silicon Labs Multiprotocol = Zigbee and Thread firmware
OpenThread Border Router = Thread only firmware
(if "Automatically flash firmware" is sctivated)
gotit
Zigbee slowness can be caused by interference (Wifi nearby, USB3 ports nearby,...)
I think it started when I added a new zigbee plug outside (IP44/45 or whatever rated) I thought it was because of the bad reception there, but I wonder if that's really the case.
How many devices should be supported?
Or too few Zigbee routing devices / too big distance to the device
but would that slow down other devices that are close / had good reception before?
Don't think so. But the people in #zigbee-archived might be able to help troubleshooting your network
I have a RaZberry 7 in my Yellow as a Z-Wave controller, and I need to upgrade its firmware. Unfortunately the manufacturer only provides a closed-source binary updating tool which is compiled for arm 32-bit.
Is it possible to install compatibility libraries on the Yellow so I can run the updater binary?
Repost from #installation-archived message I setup home assistant on a yellow, no issues with install but as soon as I had it up and running my Nest WiFi stared to have all sorts of issues, mesh points going offline, etc. I unplugged the yellow and the wifi stabilized. I did not enable any nest wifi (or other nest/google) integrations. Has anyone seen this behavior before?
Hey! Has anyone had to update the Zigbee radio firmware to avoid issues with the network? I'm having trouble with some devices on Yellow & zigbee2mqtt that previously worked on my Rpi4+CC2652RB setup. I've seen some people having trouble after upgrading the firmware, so I'm not rushing to trying it out just yet
(for context, this is the issue, why I'm asking: https://github.com/Koenkk/zigbee2mqtt/issues/18759)
#zigbee-archived can help with firmware specific questions
Thanks, posted there too. But I actually wanted to specifically ask this of Yellow users
I just did that too.. I got the PoE already, but I'm still waiting for that eMMC module from China... haha. have you got it working?
Thereās a z-way add-on for HA that allows you to update the firmware on the Razberry 7.
Thereās a z way add on for HA that
tweakers.net (dutch) just released a review of the HA yellow, for those who are interested: https://tweakers.net/reviews/11390/kant-en-klaar-smarthome-in-een-doosje-home-assistant-yellow.html
Howdy there. Have there been any updates regarding the supply of CM4 modules to the project so those of us with "whole package" orders can update their expctations of getting their units? The estimated date for those was in two days and I presume things haven't really improved.
No. The reseller's support might tell.
Or do you mean, when Nabu Casa will be able to restock the resellers with those?
Iām not doing through a reseller. I have an order in ādirectlyā from HA via CrowdSupply. However they function similarly to kickstarter insofar as they donāt really do support at a project level and itās on the project creators to handle that.
Hey, my yellow just has a solid red and green light. I've tried connecting to the serial port but I just have a solid cursor. I'm not sure what to try next
Iām in the same boat as you. Iām planning to email them Sept 4th if thereās no update by then.
Keep me in the loop if you would. What email are you planning on hitting up?
@spark gull CrowdSupply is also a reseller since the crowdfunding phase is over - and a quite intransparent one regarding their shipping. They accept more orders than they can fulfil immediately. The best you could do, is contacting their support for updates.
https://www.crowdsupply.com/contact/status-pre-shipment
Maybe someone from NC is reading this and can give an update about the supply situation for CrowdSupply.
Looks like that's the best place to start. Thanks for the link!
Thank you for the clarification, I'll raise the matter with them shortly.
@raven raptor @spark gull @wary pivot Nabu Casa is about to send 1.350 devices to Crowd Supply for further distribution pretty much right now
Didn't want to ping you for that. š
Well, in general
CrowdSupply is also a reseller since the crowdfunding phase is over ...
also sums it up very well.
@ashen dagger I converted your message into a file since it's above 15 lines :+1:
above message is a reply to this āļø
Are you sure you have got a CM4 with eMMC? Which model ID do you have (should look like CM4108032)?
i have a question for a first hardware to start really domotic.
i can buy a yellow to have something easy and independant (200-250 buckets ?)
but as i should buy a new NAS when enough money, i see that i could use TrueNAS and install HA on it and then need only the usb zigbee dongle => some good savings i think)
Any experiences or advices between the 2 cases (or others ?)
The Yellow is not suitable for Domoticz. It is specifically designed for Home Assistant with a custom OS to enable some hardware features.
Depending on the NAS hardware, that solution will likely be faster (the Yellow is basically still a Raspberry Pi 4 with extra features and better looking - what is more a taste thing than a hard fact š ).
ok then better to wait have more money and regroup NAS and HA install in one pack... but not the same budget
which would be the best dongle ? conbee II
i could even start with a docker on my linux PC then, until i have the future NAS
The people in #zigbee-archived can give you suggestions for Zigbee coordinators. There are many options (from USB to Ethernet) depending on what Zigbee integration you want to use. The freedom and burden of choice. š
Not saying the Yellow is bad. But it has its limitations and isn't suitable for everyone.
the pi4 is surely lacking a lot when you look only at price/performance. The value is in the easy to use software and big community
but HA doesn't require a lot unless you run something like frigate
And for Frigate the Yellow isn't a good choice - I haven't heard about anyone who has successfully and reliably been using a Coral with it.
Yeah i've read the github issues, it's a hardware problem. I run HA on my synology, coral works fine. Unfortunately DSM7 removed support for most basic USB device support, so im stuck on DSM6...
The m.2 problem is known since the crowdfunding phase. But even the USB version is unreliable - and would be limited to USB2 performance nevertheless
wow too many thing i even don't know what they are š
Ordered a Yellow in Nov 2022 - estimated shipping was in March 2023 and then pushed back to August 2023. The order is still āpendingā and the last update on the Crowdsupply page was in February. I assume the continued delay related to CM4 availability. Is there any other news on shipping estimates?
@fiery sluice
Hey all I just got a yellow, trying to figure out the best way to migrate from a vm based home assisant. I tried doing a back up of the old HA and restored to the yellow, it seems to work. I currently have no Zigbee devices but am planning on getting a few to try. Do I just need to install the Zigbee integration from here. https://www.home-assistant.io/integrations/zha
what's the issue with the m.2?
oh I see the PCIe/USB Coral TPU.
As long as the correct OS image has been used (the installer image or the specific HA Yellow OS image), the onboard radio should be autodiscovered and already be configured as ZHA integration.
Or at least be proposed for configuration.
I ended up installing zha. I didnāt see it in the proposed list. It did find the yellow zigbee module so I guess Iām ok but Iāll have to get a zigbee device before I can confirm.
@vestal quarry I converted your message into a file since it's above 15 lines :+1:
ZHA does not work for me on latest beta:
@vestal quarry I converted your message into a file since it's above 15 lines :+1:
Does the Yellow ship with M2 mounting hardware?
@vestal token there's a stand-off, yes
Thanks. the images and product information doesn't make that clear. Does it include the screw?
I ordered a Yellow with a CM4 that includes Wi-Fi and BT. Will those devices work with integrations?
yes. in fact the standoff blocks the nvme in place, and the screw is to fix the standoff
Yeah, I finally figured it out. Unlike the typical M2 hold-down on a mobo where you use screw to fasten the M2 to the standoff from the front, with this goofy M2 hold-down you position the standoff into the slot then fasten post to the PCB with the screw from the back
Report that in the #beta channel. Here it doesn't help
Anyone using Matter with their Yellow?
Please create an issue in the HA Core repo and provide all logs you have. This looks like an issue related to a recent bellows change
I'm struggling to get the Matter integration working on my Yellow. I'm getting the following, which doesn't provide much information.
2023-09-03 18:13:54.599 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_matter_server/start request
2023-09-03 18:13:54.607 ERROR (MainThread) [homeassistant.components.matter] Failed to start the Matter Server add-on:
#matter-archived might be able to help
Is it possible to set up a yellow that suppports bluetooh and-zwave?
Yes, but...
If you have a CM4 with bluetooth, you could use that. Otherwise a compatible BT stick would be needed. ESPHome BT proxies are likely a better choice, as they are more reliable.
ZWave is possible, if you have a ZWave stick or a Pi compatible HAT like the Aeotec ZPi 7.
I have a CM4 with Wifi/Bluetooth on order. I'd like to use a Z-wave board like the Aeotec ZPi 7 but have read that it shares the UART with Bluetooth on a Pi. Not sure if that is also true on the CM4
I have a yellow on order with a CM4 that has Wi-Fi/Bluetooth and want to add Z-wave capability but I'm not sure how to proceed. I prefer using an internal Z-wave board on the Yellow header if it's compatible with CM Bluetooth. I that doesn't work I'll go to a USB Z-Wave stick. Or I'll disable the CM4 BT and use an internal Z-wave and use a BT USB dongle. Has anyone explored these options and have a recommendation on a preferred reliable and non-fiddly option?
The Yellow's OS allows to use both. The ZPi 7 can be used with the onboard GPIO pins without the need to disable BT.
The Raspberry Pi tutorials don't apply here
Thanks .... that's perfect. A lot of information is not specific enough.
Hi, does anyone know where I can buy replacement thumbscrews for the Home Assistant Yellow case?
On a yellow if move data to SSD what, if anything, is left on the eMMC? Is the eMMC written to after move?
The OS itself stays an the eMMC and is mostly read only. The boot files might me altered and an OS update would write to it. But it shouldn't cause relevant wear.
Where is the swap file after the move?
Would I be better off reinstalling to SSD?
The swapfile is in /mnt/data, which will be on the NVMe after transfer
perfect
/tmp is a ramdisk
is there anythign I need top do to optimize for 8GB RAM
No. As long as you don't know why and what to do on the OS or boot part, you should just let it do its thing.
OK .. just wanted to to know if I needed do something to optimize use of RAM for caching etc... Thanks for your help . I'm a HA noob and there's a lot to learn
Hi everyone, does anyone know when the yellow will be delivered? I've order mine in January. But still nothing?š¤·š»āāļø Is it cancelled or?š«¤
Ps. I've ordered it in crowdsupply.
I just ordered one from Seeed. It was here in 6 days
Anyone that also ordered on crowdsupply? Very strange that I is still not delivered.š«¤š
You might want to contact CrowdSupply's customer support. They don't have a great reputation here.
https://www.crowdsupply.com/contact/status-pre-shipment
Oke, why? Is it a scam or?š±š«¤
Not a scam. They are just accepting more orders than they can fulfil immediately.
And their shipping is highly intransparent. Sometimes people are ordering later, but get it earlier.
Not a great customer experience
No that's not fair indeed. I've send a message to the support team. Hope they answer soon. It's an order from the 17th of January ššš
Did you order one with CM4 included or a kit variant?
Indeed, with cm4... There where trouble's with the delivery of that item, not?(sorry for the bad writtened English, I actually speak dutch so šš)
A CM4 is indeed a limiting factor.
If you are from NL, you might consider cancelling your order at CrowdSupply and place it at raspberrypi.dk - there you can only order when it is in stock and they are reliable (my past experience)
And should you be able to get a decent CM4 yourself - the kit variants might be the better choice
Unfortunately those are still hard to get
We try to get the specs of the screws - please stay patient
I ordered a kit from Seed with CM4 but HAOS was not installed.
Yeah. Some sell Yellow with CM4 (without OS) and some sell the Standard variant (which is the 2GB RAM/16GB eMMC preinstalled one)
If I was waiting as long as some of you, I'd cancel crowd supply and order from someone else
For example: at raspberrypi.dk the Standard (with OS) is not in stock, but you could order a kit variant with CM4 (they have a 4GB/32GB CM4 in stock - but without OS
232.10 EUR + shipping for Yellow Standard (preinstalled OS - 2GB/16GB)
237.42 EUR + shipping for Yellow Kit Power Supply + CM4 (not preinstalled - 4GB/32GB)
You could guess my suggestion, if you want to go with the Yellow š
Yellow (nonPOE) with power supply and 8GB/32GB/Wifi/BT was $219 + $24 Fedex to US. Delivered in 6 days from Seeed
They are custom, so can't be bought of the shelf š¢ You can use regular machine screw, gives it s steampunk look š
@eternal jacinth the base screws are thumb screws: M3, 8mm dia./10mm
oh I didn't see falstaff reply till now š
I myself would have preferred normal screws recessed so rubber feet could be put in the recess .The thumbscrews provide no practical value. Thumbscrews are usually ony used when they will be removed frequently
OK I've tried three time to install HAOS on the yellow and force to the install to be on the SSD. It keeps ending up on the eMMC. I've followed the instructions to clear the eMMC between installations and followed the instructions to force install on the SSD by pressing blue button to during the boot when yellow is on steady. Has anybody got this to work?
I'd used it as a data drive myself. Booting from external drive on RPi is too finicky
I sure hope mine is about to be shipped. I asked Crowd Supply about a week ago and they said they did not know when they would be shipped. They offered to refund my money or sell me one without the CM4. I decided to hold out.
I'm quite sure your device is amongst those! We don't have full insights and that's why I need to make sure to not let it sound like a promise (!) but at least as far as we know at this point of time we fully covered all open orders with the shipment we sent out
Uwe, while you're around, did that shipment of 1350 CM4 units get shipped? I'm speaking with CS regarding potential timelines and they don't seem to know anything about it.
Normally I'm not an idiot I promise...
However I just set up a home assistant yellow, but I'm trying to install some custom intregrations on my appliance. How the heck do you ssh into this thing?
The port isn't open, I installed the ssh/terminal addon and it looked like it would do it, and I can't seem to ssh into it still.
Someone please correct me here, but I was unable to find any specific documentation reguarding the yellow device on how to do it
EDIT: The longer of the two buttons on the back is a power button. Press and hold for 5 seconds, wait for the yellow and green lights to stop flickering.
How can I safely power off my HA Yellow?
I couldn't get it to install the OS to the SSD, so I removed the SSD and got it running from MMC... and now I want to shut it down and install the SSD.
You could try the "brute force method".
a) Follow steps 1-8 of option 2 of this guide and delete everything on the eMMC:
https://yellow.home-assistant.io/guides/reinstall-os/
b) Power off the Yellow
c) Follow this guide to reinstall the CM4 firmware (just to be sure).
https://yellow.home-assistant.io/guides/reinstall-os/#install-os-rpiboot
d) Power off the Yellow
e) Follow steps 1-8 of option 2 of the guide mentioned in a). Use the program Balena Etcher and flash the following OS image directly to the NVMe (Don't select the eMMC as target. You could also use a USB-m.2-adapter and install the NVMe after flashing)
https://github.com/home-assistant/operating-system/releases/download/10.5/haos_yellow-10.5.img.xz
f) Power off the Yellow and ensure jumper JP1 is set to UART
g) Power on the Yellow - HAOS should start completely from NVMe now
And make sure your SSD is really a NVMe (not known as incompatible) and not a SATA.
You could hold the blue button for 5 seconds. Or in the UI you could go to Settings and click on the
menu. Select Restart Home Assistant, followed by Advanced options - Shut down system. When the Yellow shows a steady red light only, it is shut down gracefully.
What SSD exactly are you trying to use?
You can install a Terminal & SSH add-on (or the advanced one). But you have to configure it, like setting a password or SSH key. That way you can SSH to that add-on and get limited access to your Yellow.
For full OS access (not recommended unless you really know what you are doing there) you would need to use Yellow's serial terminal (the USB-C port) or to enable the debug SSH access.
That's kind of stupid. It's pretty darn hard to install custom integrations without that. Or at least time consuming to make a git repo and go through that..
Also I tried the plugin but ssh remains unavailable after configuring it per its linked documentation and common sense.
In that case you should head to #add-ons-archived to get that running.
Thanks for the tip about the shutdown menu.
I got a 512gb SSD with the Seeed Studio package deal. It shows up as a "Foresee XP1000F512G."
The move seems to have been successful.
If they are not aware, that must be internal communication!
Devices are underway - but depending on how they are shipped it can take a good while.
@zenith haven this isn't specifc to the Yellow but is how it works on any HA OS install. You don't need ssh access to the host system for custom integrations or to install HACs. I suspect you may not have the port enabled for the SSH add-on? But you could also use the web terminal it provides.
Yeah, using the regular terminal add on it didn't work try as I might. But I got the advanced one and it effectively does the same thing but does open the port as I needed.
Yeah I could use the web terminal, but personally I will argue that is less secure. Giving software that is assessable to the one port and service (the webserver) direct access to modify the files is less secure than keeping it local only. SSH/SCP/SFTP is the standard for modifying files for literally everything else. I greatly prefer to use it over a built in web gui.
Also, while I do admit I didn't do my research enough before purchasing the yellow device, there are far more ZWave devices on the market than Zigbee. Often for cheaper as well.
Pretty disappointing I have to still go by another adapter when litterally every other smart home hub these days support both.
@zenith haven You're making assumptions. You're using docker. HA is in a container. The SSH add-on (another container) has limited access to the directories that are needed for you to configure home assistant. This is not your desktop
The directories are mapped from the host to be accessible to the containers.
I understand how docker works. It isn't difficult to add the access to the volume or filesystem it needs to support ssh.
The part about more Z-Wave devices than zigbee... That's the opposite of what I've seen over the last 6 years
Yeah if you include the bunch of no name and generic products.
But hey may be wrong. I'd still like to see both.
Almost every z-wave device is $50
They aren't the same license wise
Yeah everyone would like to see both.
You also need different types of Z-Wave for different regions of the world
Espectially on the suposed "best hardware" for home assistant. I know it isn't easy, but I would gladly have paid more for it.
Well you can gladly pay more and add it. What if you didn't want it at all because you didn't plan on using Z-Wave?
Then you're talking about adding it as an option at checkout time
It's an RPI. Tons of ways of adding it.
I get it.
for the core ssh add-on, you have to enter 22 here in the configuration.
for the advanced ssh add-on, you don't
I wouldn't recommend to update HA Yellows to Core 2023.9.0.
In my case ZHA stopped working completely. (Onboard radio with EZSP firmware)
A fix should be in Core 2023.9.1, so better wait for that one.
Dang, my two test devices are on Multiprotocol and Thread currently š¢
Do you happen to have a link to the PR fixing it?
Hm, I see that is related to the version. This probably slipped because it got tested with a newer Zigbee (EmberZNet) firmware version.
A new firmware version has been pushed?
On the one hand, I'm tempted to try updating the firmware and the core afterwards. But on the other hand, a rollback takes so painfully long.
@shut cedar You were right. Running the Silicon Labs Flasher add-on and updating the firmware seems to work.
The newest one I know is the 1.3 revision with screws for the CM4 and SW3 instead of JP2
Officially the regulatory approval does not cover the WiFi/BT variants.
Personally I wouldn't care, if I'm able to get one at all.
But I wouldn't specifically look for it. WiFi isn't needed and for BT the ESPHome BT proxies are more reliable IMO.
@charred canopy Usual steps to troubleshoot are:
a) check if CM4 is fully seated in its sockets (makes a satisfying click on install - this is very often the main problem)
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.
Usually A is the main problem.
Anybody having an issue with their HAY where the Thread network keeps crapping itself, and you keep having to restart the Silicon Labs Multiprotocol add-on periodically?
- Silicon Labs Multiprotocol 2.3.2
- Home Assistant 2023.9.0
- Supervisor 2023.08.3
- Operating System 10.5
- Frontend 20230906.1 - latest
Man I can't even upload logs due to non-Nitro limits
@ebon field I converted your message into a file since it's above 15 lines :+1:
#thread-archived can help with OTBR specific problems
Hi Jorg , much appreciated for the quick reply, a im pretty sure is correct , b i know is fine , ill check the rest tomorrom
My guess would be a not correctly seated CM4, the CM4 firmware or an incompatible NVMe
How do I perform an orderly shutdown of Yellow?
in the Settings menu. There you can select to restart HA. In the following menu select the advanced options and power off.
Holding the blue button 5 seconds should trigger that too.
OK .. thanks
It is safe to remove the power, when only the red LED is shining and the yellow and green one are constantly off
It didn't occur to me that an orderly shutdown was an "advanced" option 
It makes sense from a certain point of view - if you poweroff a Pi based host by accident, you would need access to the power supply to restart it.
I'm a HA noob so tryin' to get my HA zen calibrated
Hello everyone, finally i got the CM4 and i was finally able to mount it on my Yellow. As the CM memory is just 8GB i would like to install the OS in a nvme drive. Reading the docs it is stated that if you press the blue button while the orange led is steady it should start to install in the ssd, i have tried multiple times but it keeps install in the CM disk, i have tried to clean both memory but still when i launch the usb installation it keeps installing in the CM. i am pretty sure the disk does work because after the installation i can move the data to the ssd, but i would like to install everything inside the nvme drive. Does someone have some suggestions? Thanks
That failed for me (3x) as well AFAIC it doesn't work
ok, maybe i did it, will update you shortly
yes, it woks!! i took the yellow os image from github, flashed the image into the nvme, it booted and it seems working š (https://github.com/home-assistant/operating-system/releases)
@wary pivot So i have gone through your steps again for checking:
a) Ive taken it apart again and reassembled it. making sure it is seated properly. I think it was anyway
b)It has internet as I uplugged the ethernet cable out my printer
c)Connecting the Yellwo to pc with usb cable ( different cables and two computers) - This is where the trouble starts. Following the instructions I should see the device appear/disappear in Device manager - but nothing changes. The jumper JP1 is set to UART
d)Follow the instruction for reinstall option 2 . Get to 7 and run rpiboot. rpiboot opens and displays" RPIBOOT: buid-date Dec 16 2022 version 202212......... Waiting for BMC2835/6/7/2711...
Your Windows machine might need the Windows UART driver:
https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers?tab=downloads
@wary pivot Not sure if this will help, but I tried another usb to serial converter ( that I use for programming security systems) and that appears to the Ports in device manager
š what is the SSD exactly used for? is it to get better performance out of CM4 & the Yellow Card or?
It is used to provide more storage or storage at all (in case of a CM4 Lite).
ahh they are fixed size, i haven't looked much at CM cards š
so an SSD upgrade later on, would require reinstall i guess?
ahh. so a 8GB / 16GB eMMC CM4 with wifi, would fit just fine as a base.
and then expand with a compatible m.2 for data ?
and when we talk data, then it's integrations etc ?
Basically everything except the base OS and the boot partition
gotcha.
it all makes sense now š
I wish it all would work with Risc-V boards, they seem to get a lot of traction out there. with hardware available too
Not enough traction yet
it will come, especially now with the new boards by Milk-V they look really really interesting
š¤

Installing HA on HA Yellow SSD with no eMMC CM4
Am I able to use NUT on a Yellow with UPS USB cable connected to the Yellow? Is using NUT for one UPS connected directly to the yellow overkill and is there simpler method to monitor and respond to a UPS shutdown ?
You can. I'm doing this with my Eaton UPS.
Hi there. I have a Yellow v1.3 where I have gone through all the steps to get it started. I only get a red steady light afte a quick green light blink. When I check the network port there is no connection to the switch. I have tried all the ports and 3 different cables that work on other devices. Tried to connect via the USB cable from Windows and Mac with no connection established, just the Waiting for BMC2835/6/7/2711... Running out of options and ides so if anyone have any further suggestions I am very open to them. Otherwise I start to suspect defect hardware with the network port
Most likely the CM4 is not fully/correctly seated in its sockets.
https://yellow.home-assistant.io/faq/#my-home-assistant-yellow-appears-broken-no-led-is-lighting-up-what-can-i-do
I have reseated it several times and made sure I got the proper "snap" each time, that is 6+ times, so I do not think that is the problem. The FAQ page states no LED and I get a brief green flash and the steady red light. No lights on the LAN port neither on the yellow nor the switch
Make sure you hear some good clicks. You could even try squeezing or applying pressure and watch the Ethernet port lights for activity
I have heard the good clicks and then still no Ethernet port activity š¦
Do you attach the heat sink each time? Or leave it off?
I have tried with it on and off with the same result
Have you tried using the usc c serial connection to flash yellow HAOS image directly to emmc?
I have tried that also with no result. Does not want to connect via the USB from neither Windows or Mac
You say brief green flash - not more than one flash?
I stand corrected. It is a brief blue light on the other side of the board. Neither of the lights near the red lights makes any indication
The blue one is the radio
That is the only light that blinks briefly when powered on
I have just reseated the CM4 again with good snap. Connect it with the blue light flash, steady red light and no port lights on at all.
Are you using a 12V 2A/3A power supply?
I am using the supplied power supply with the kit, so that should be the proper one
I will get my vold meter out to ensure that the voltage is correct
Steady 12v supplied by the power supply, so the correct power to the unit
I will bring another computer tomorrow and then try to connect via the USB to see if I can read any error messages then
Your board is the version with the SW3 button at the m.2 connector, right?
So it is a button and no jumper. And is JP1 (near USB-C) in position UART or USB?
It is a push button labeled USB-C Rcvry and the JP1 is in position UART
And no m.2 SSD is installed?
I have a m2 SSD installed but I tried without also before. Be happy to remove it again to get it started
Will call it an evening. Time to take the dogs out. Might have to call in sick to work tomorrow so that I can fix this as it is really bugging me now
Thanks for the help Jorg, very much appreciated
If it's not the SSD (what specific model are you using?), I'm running out of ideas.
Let's assume, the CM4 is correctly seated - power supply is correct, jumpers are set correctly,...
Maybe Cogneato has some ideas I'm missing
That one has been reported to be incompatible
Ah. Will try something else then
Is there any list of compatible 1TB m.2 SSD so I can get that ?
When I try to boot from USB without the m.2 SSD installed it is unfortunately still the same result. Red LED and no Ethernet port activity or lights š¦
Will be back at it tomorrow again
Unfortunately not. But Samsung 970 Evo Plus are a safe call.
I'd always set up Yellow and HA OS without SSD first. Unless using cm4 lite
Has anyone used RTL_433 on a Yellow?
What SDR dongle or device did you use?
Does the Yellow have enough processing power to handle all the RF traffic and filter the desired messages?
how hard am I supposed to press for the CM4 to get seated properly, and how hard is it to pull it out again?
Medium? š Make sure to orient it correctly and align. Best is to hold it with both hands like shown here:
https://yellow.home-assistant.io/power-supply/#installing-the-cm4
ah, there we go, I was pressing it against the table, and was afrait to push too hard
Yeah in that case the lower PCB bends, which is not ideal
any update on bluetooth issues with the yellow and HA? broke a few releases ago iirc.
Alright, so, I screwed up the setup of my boot partition it seems (missing fs drivers in initrd?). how do I get the HA yellow back to booting from USB while the NVME is connected?
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=E4:5F:01:E2:F4:B3 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 console=ttyAMA2,115200n8 console=tty1 root=PARTUUID=61e2f9f0-c8d8-344e-9722-4f8b59263c4d rootfstype=btrfs fsck.repair=yes rootwait
...
[ 3.320992] VFS: Cannot open root device "PARTUUID=61e2f9f0-c8d8-344e-9722-4f8b59263c4d" or unknown-block(259,2): error -19
...
[ 3.445509] (driver?)
[ 3.451757] 103:00000 1000204632 nvme0n1
[ 3.451770] (driver?)
[ 3.458173] 103:00001 1048576 nvme0n1p1 c99728a3-bf3c-d34a-99e0-6d8a68a8bf74
[ 3.458187]
[ 3.467190] 103:00002 996147200 nvme0n1p2 61e2f9f0-c8d8-344e-9722-4f8b59263c4d
[ 3.467204]
[ 3.476227] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(259,2)
This is a snippet from my boot log, if anyone are interested in seeing how badly I screwed up :P
What NVMe are you using?
XPG SX8200 PRO 1TB
it's loading the bootfs and kernel fine from it, so that shouldn't be the problem, and I was able to interact fine with the drive to copy over my filesystem while booted from USB SDcard reader
(I'm migrating over from a Pi4B USB SSD setup)
What did you copy over?
I did, however naively copy over the boot files from the new install on the USB drive, but the root fs from my existing install, so probably messed up kernel modules or some such
is there any way to get it prioritizing USB boot over the NVME? (without first disconnecting said NVME)
Yes, that's propably not going to work.
Yellow needs is special OS version.
After installing that, you can migrate by importing a backup and restoring that.
You will need option 2
was able to boot fine from the USB stick with vanilla pi os, following this; https://community.home-assistant.io/t/pi-os-instead-of-ha-os-on-yellow/473695/10#copy-drivers-edit-boot-and-run-in-docker-2
is rpiboot relevant for the CM4 lite?
not supported as in Nabu Casa won't help, or not supported as in won't work?
Not supported as in it might work, but might break or have unknown sideeffects
I think the odds of it working just fine is quite high, and I don't feel like going with the HA managed OS and re-doing everything
A Docker install is a common thing. You will not get add-ons, but have to set up software in Docker.
I'm aware, been running it this way since before the OS was a thing
usbboot/mass-storage-gadget$ sudo ../rpiboot -d . gave me direct access to the nvme block device on my laptop, so booting from USB wasn't required
After copying over the correct boot files, and some fiddling with the uuid stuff both on boot args and fstab (btrfs really didn't like PARTUUID, had to change over to UUID), and fighting some with dhcp lease holding to the old mac, I'm now fully back online, including ZigBee via the external adaptor
Thank you so much for the help ā¤ļø
would've never tried rpiboot without your nudge, as all the documentation only mentioned it in connection to the on-module flash
There should be a also a device tree file for the LEDs, so you could utilize the yellow LED
CM4 Lites are sometimes a pain in the bottom š
device_tree=bcm2711-rpi-cm4-ha-yellow.dtb should be loaded
Oh, I'm pretty sure a non-lite would've been equal pain in this particular situation, as I managed to desync the boot and root filesystems completely
I didn't have the required initramfs loaded
only took me all night to get back up and running, so now I'm gonna go get a little sleep š
Again, thank's for the help!
The LEDs might be in that file too - didn't dig too deep.
Edit: looked at my boot directory - there is no additional file
I'm using this one to monitor 2 gas meters on my yellow and it works great, https://www.amazon.com/gp/product/B008S7AVTC/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
New to HA and noticed that seedstudio has these listed. Is there a CM4 module that is better than others to select? Any other hardware I should pick up?
Lite models cause more headache than models with eMMC. Other than that it's personal preference - I'd go with a 4GB or 8GB RAM model.
Great, thank you Jorg
Thanks !
Question about HA Yellow and swapping out the CM4: right now I have a Lite 2GB, which is... not a lot. I can get an 8GB RAM one but it also has 8GB of eMMC. If I swap it out, will HA still start from NVMe, or will I need to do anything?
In that case HA will run as before
Great, thanks
But creating and downloading a backup before changing the CM4 is recommended,.
Makes sense. It shouldn't have WLAN/BT, right?
The WiFi version isn't covered by the regulatory approval, but it doesn't really matter in real life
Ah, I thought it would interfere with the zigbee module
As long as you don't use Wifi, it is fine
Looks like the only two in stock anywhere near me are 8GB RAM/8GB/no Wireless, for the same price as the 8GB RAM/16GB/Wireless+BT.
Speaking of Wifi...
@shut cedar dtoverlay=disable-wifi and dtoverlay=disable-bt in the config.txt are not working anymore.
Do you know an alternative method to deactivate the CM4 onboard radios?
oh for... this website is only selling them to "club members" (membership free but not available in this country)
dumb
Ah. Berrybase
Welectron has it too (8/8/no wireless) but for ā¬15 shipping.
Non-EU country? Iām a Swedish resident and just ordered from them
Austria, which has its own subsidiary
but not the club
And I'm loath to order from germany and pay extra shipping for the one I don't even want
How do you disable bt and WiFi? Sorry if itās a stupid question.
It was possible to disable them by editing the config.txt via the serial console. But since one of the OS updates, that doesn't seem to work anymore.
You still can disable the Bluetooth integration and keep the wlan0 network disabled in the HAOS network settings.
using silicon labs 700 series z-wave controller and its not working. i flashed to 7.19.2 which is zone agnostic but im seeing RF EUR in the logs, it should be US
anyone know why it's defaulting to EUR?
i was able to change it to US but it still doesn't pick up devices unfortunately. not getting anoy more hints from the logs
#zwave-archived might be able to help troubleshoot
Hi everyone,
Just heard of Home Assistant through a Verge article about Home Assistant Green. I'm a newbie in smarthome, so I'd like to know if a Home Assistang Yellow could easily replace gateways and bridges (like Ikea TRĆ DFRI and Philipps Hue Bridge, which I currently use) ?
Thx
The Yellow has a Zigbee module built in, so it could replace those bridges. But it is quite hard to get a decent Raspberry Pi Compute Module 4 for it (needed for the kits without that CM4).
The Green would need a Zigbee stick, like the SkyConnect, to replace those bridges.
If you're going to be a HA power user get the HA Yellow with a CM4 module that includes Bluetooth and get a Zooz Z-Wave plug-in board and you'll be able to connect to just about anything
No problems getting a CM4 module, it's if you want to get it at the MSRP. Lots of scalpers have lots of stock at twice the price. I went with a CM4 "Lite" module (has no eMMc memory) and paid the nVME SSD price to get it working. More expensive, but significantly faster for any process that uses local storage. 1TB also gives me space to store IP camera footage.
@vestal token That's exactly what I'd done. CM4 Lite model CM4104000 - 4GB RAM, BlueTooth, WiFi, 0 storage along with the Home Assistant Yellow PoE edition and added the ZAC93 LR GPIO module. Ignore the instructions, you absolutely do NOT need to disable the BlueTooth, works great with no boot configuration changes.
Confirmed. Z-Wave worked right out of the box. I have multiple Bluetooth and Z-Wave devices all working and the Z-Wave background RSSI is -105 dBm or better and no dropped messages and only 1 collision. that's stellar RF performance. Z-Wave running at 908 MHZ is away from the 2.4 GHz RF storm
I use certified Z-Wave devices for my critical sensors and controls and cheaper Zigbee for the non-critical stuff
Cool part is I've both a large installation of Z-Wave and also Zigbee 3.0 devices. I found a number of Sonoff devices I can hid behind switches as well as longer battery life on the Aqara contact sensors. Can confirm all three working without trouble.
The Zigbee devices are much more likely to go AWOL than the Z-Wave. Since Zigbee devices don't have you pass actual standards compliance certification there can be good ones and bad ones
In former life I was involved with development of low power FCC ISM devices and eventually we learned 900 was better than 300 or 400 MHz
Hi, just want to vent a bit if that's okay with you.
So, I bought a yellow + CM4108032 from seeed a couple of weeks ago (+ ā¬60 import costs š¦ ). Upon arrival I installed the pi on the board, connected a usb stick with Hass, ethernet, power... nothing. No LEDs or anything. So, after a lot of trial and error and noticing a weaker power supply did make the board light up, I tried again with the main power supply, but that still wouldn't work. Out of desperation I tried yet another power supply and suddenly the board caught flame and I knew that was it. I asked for a return of just the Yellow, hoping I could get my money back and buy the board from Denmark (without import costs), while keeping the pi cm4 which looked fine. Well this was a mistake since Seeed only returns money for unused products :(, so after a large FedEx adventure I finally got a new Yellow, connected my Pi cm4 and.... nothing. No LED whatsoever. No Serial, no usb+rpiboot, just the pi getting hot.
I suspect the pi also broke during the shorting of the previous board. So... Anything else I can try before I attempt another return/repair adventure with FedEx?
I wouldn't recommend to use that CM4. In a worst case scenario it might damage the new Yellow board.
And about the power supply, double check if it has the right voltage (and polarity) before plugging it in.
I used the power supply that was delivered by the board, so the voltage and amperage is definitely correct. I'll likely send both the yellow and the cm4 back, just in case it damaged this yellow too
Got my Yellow today and immediately lost the standoff for the NVMe drive. Having trouble finding any replacements that are similar. Anyone know where I can buy standoffs like that?
I'm afraid that they are custom made, like the thumb screws.
You could send a mail to the support ( yellow@home-assistant.io ) - maybe they have spare parts or a suggestion for a compatible replacement.
That is surprisingly DIY unfriendly for a product designed for Home Assistant.

Thanks for the info though, I can stop searching increasingly sketchy websites for this style of standoff š
If they aren't lurking here right now, the support should be able to give you a hint, when you email them.
I just sent in my e-mail, fingers crossed support can help me out once the week starts.
Why custom made parts for things like that? Very silly when standard OTS parts would work fine š¤
Again... 
Looks like the designer has very little real-world useability experience
I think you could use a standard NVMe standoff.
Standard standoffs have a threaded male end that's meant to screw into the main board, don't they? I'm not sure if there is clearance to add a small nut on the underside.
You can use screw from the backside
That would need a standoff that has two female ends, are those a thing?
(I've been away from hardware for too long, I'm only used to working on imaginary computers these days š )
or a nut if that's what it takes
or drill the hole out and press in the broaching nut, or epoxy the standoff to the PCB
They don't have to hold with very much force thus the tiny screws on conventional NVMe standoffs
Can you link me a good cheap OTS part? I searched hours, the ones I found were solder on (which was a no-go since we want to support different length). I think I found one off-the-shelf solution with a ridiclous price (like a dollar or something for a single screw!).
Btw, if there is a OTS part, it is very likely going to fit. The hight distance is quite standardized (since the M.2 connector is). The hole size could be different.
Afaik, there is no "standard standoff" (at least I didn't found anything defined/written in the M.2 standards).
Amazon had a lot of options but you're going to have to measure carefully to get the correct height and make sure the screw diameter isn't too large to fit to the notch in the end of the card. I'd contact Nabu Casa and ask them for a replacement first. They created this mess with their one-off design
Disclaimer: I work for Nabu Casa and took the decision to let the stand-offs produce on our own.
The standoff which appear on Amazon are the typical screw type. You can't use those without a washer + nut (and onther screw ontop).
The design we ended up going with has
a) as few parts as possible (two)
b) as many off the shelf as possible (the screw is off-the shelf)
c) can be used for any NVMe length
d) can be used with a simple hole in the PCB
There are always design trade-offs... š¤·āāļø
Then you choose to be a supplier for replacement one-off parts so ... supply
Yeah supply those is not a problem. Distributing is... š°
As in, Distributors for Yellow would not stock it.
Yeah ... cost more to distribute than a whole box of them.
Where are you located?

