#yellow-archived
1 messages Β· Page 8 of 1
The Supervisor seems to timeout on several tasks. For example if I look for updates.
On a short look at the GitHub issues, it seems to be the same bug as the data disk move one.
Supervisor 2023.4.0 is in beta, so it should be available the next days - if they don't find any major problems.
I hope, they fix the ZHA-Multiprotocol-Automations bug with tomorrow's release. Otherwise I'm tempted to revert to EZSP for the Zigbee radio.
I had the same issue, and running the command from https://github.com/home-assistant/supervisor/issues/4220#issuecomment-1491854498 in the serial console followed by a reboot command resolved the issue for me.
How to use the serial console: https://yellow.home-assistant.io/guides/use-serial-console-windows/
I'm using ZHA for some Aqara devices and that seems to be working well.
Not being able to install add-ons is frustrating as I'm led to believe I need SSH and/or HACS for mnay integrations.
You can try to downgrade your Supervisor ha super up --version 2023.03.2
If I'm right, only Supervisor 2023.03.3 is effected by the bug.
Thank you. Will give that a try.
Just tried it. Unfortunately it doesn't let you downgrade the Supervisor. The CLI documentation implied such option, but it just says :
Error: No supervisor update available - 2023.03.3
π€·
solvedβ¦
the issue came from my old fritz!box. she made a lot of wlan problems the last days.
i moved to the new 7590AX.
all works perfect now
One of the lucky few with the FritzOS 7.50 update. π
When using the Shutdown option in the HA UI, how do you know when it's safe to unplug the PoE please? The yellow and green lights seem to continue intermittently flashing.
When the yellow and green LEDs stop flashing.
π good things come to those who wait π
External antenna arrived today. I have installed it and added the dtparam=ant2 to the /mtn/boot/config.txt using vi, through PuTTY on a PC connected to the Yellow's USB-C port.
How may I check if it's working please?
My Google-Fu was strong and found something.
If you enter the following command in the serial console, it shows the state of the antennas. The hi one should be active, the lo one inactive.
cat /sys/kernel/debug/gpio | grep ant
gpio-507 (ANT1 |ant1 ) out lo
gpio-511 (ANT2 |ant2 ) out hi```
Thought I would see what it's showing under storage today... in the UI it says "Used Space 0.5%" so I was initially excited, thinking perhaps it's managed to complete the switch to the NVMe but...
devices: []
disks: []
Erm... was the dtparam the only thing in the file or was there more in it? Wondering about your filepath /mtn/boot/config.txt - which should be mnt.
Sorry, that might be my typo in Discord.
There was plenty of other stuff in there.
Have a look at the UI for Storage. If it doesn't show a lifetime anymore, chances are high it has been moved. lsblk in the serial console would tell for sure.
Awesome, I think it has worked then...
`-nvme0n1p1 259:1 0 465.8G 0 part /var/log/journal
/var/lib/docker
/mnt/data```
I added the dtparam above the
device_tree=...```
That might make a difference
I can copy mine here. Nothing to hide π€£
Just trying to get back in via PuTTY. I'm getting a > cursor at the moment.
Ooh, Add-Ons installation seems to be working too. SSH & Web Terminal has installed.
@wary pivot I converted your message into a file since it's above 15 lines :+1:
Thanks for all your help. I have to pop out but looking forward to trying later.
Just be aware of my other modifications. Some you might want to comment out - for example the disabled Ethernet LEDs.
Anyone know how to disable the leds on the HA yellow with a cm4 lite?
search and yee shall find <#yellow-archived message> (the ethernet leds are two posts up from your question)
Ok, 4gb cm4 showed up, swapped the cm4 out and now it doesn't see my zwave hat. difference is wifi on the new cm4, old cm4 did not have it.
I'd recommend to use the switch method with an automation to turn the LEDs off on HA start. That way you can see when HA is completely booted - that wouldn't be the case with the config.txt method.
#yellow-archived message
The Ethernet LEDs have to be turned off in the config.txt
That doesn't matter. Mine worked ooB too. Are you sure, you flashed the correct OS? It needs to be the Yellow, not the RPi4 one.
If it shows Raspberry Pi 4 and not Home Assistant Yellow in Settings - System - Hardware, it is the wrong one.
I do have a baseboard with nvme on it I'd like to install ha on, but when I tried the standard image it choked.
Do you mean something like the RPi baseboard for CM4? I have tried that with the Yellow OS image before the Kit arrived. NVMe didn't work for me too. But I haven't tried the regular RPi4 image with it. That one has less hardware specific changes and might work.
Home assistant yellow std-us vs std?
Iβm in the US and ordered the STD version. What is the difference between std and std-us version of home assistant yellow?
@wary pivot this is just a waveshare board with the nvme on the bottom side.
I think it's their B2
use the regular pi4 image for cm4 on non-yellow, i tried both waveshare with nvme socket and pi foundation IO board w/pci-e nvme adapter, apart for potential changes to boot order no need for anything special.
the only regional differences is the power adapter according to past comments on here. <#yellow-archived message>
Thanks!
well, it looks like the usb ports on the waveshare are not working.
heh, disabled by default on the pi4.
Ok, pain is over. had to mount it using rpiboot msd.
update config.txt to enable the usb port after mounting the emmc on a linux box.
getting a little OT, but if you want to mimmic the Yellows usb serial console I used some small panel mounted isolated ch340 boards connected to gpio header and changes to config.txt/cmdline.txt <#hardware-archived message>
Have received my HA Yellow PoE and set-up the hardware as per the PoE 'Getting Started' guidelines, including installation of a Raspberry Pi Compute Module 4, 32GB EMMC, WiFi. Prepared a USB stick with the "Home Assistant OS Installer for Yellow" version of OS. Inserted the USB in the top USB socket on the device and plugged in a PoE enabled Ethernet cable. Lights appeared to flash as per 'Step 10', but I never got to the "only the red LED will be on"bit.
I've attempted to repeat the process of re-flashing a different USB and re-commencing the start-up but now have both yellow and red LEDs steady with the green occasionally flashing.
I've consulted the help pages, and followed the 'Option 1' procedure on the "How to reinstall the operating system" page here: https://yellow.home-assistant.io/guides/reinstall-os/
Result was the same. 'Step 10' on this page https://yellow.home-assistant.io/poe/
begins as described, with the Yellow LED blinking in a heartbeat pattern for a time, and then the Yellow LED remains on constantly. But it never begins blinking again.
I've verified that the Ethernet cable is OK, by plugging it into another PC and verifying that device can see the network and access the Internet - ping & traceroute.
Any hints anyone on the next best step to get this thing running? I am not relishing the prospect of having to "Using the serial console for debugging",
@grave moon at any point did you try rebooting it to see what the results were? Does it get an IP address?
And to reboot you - unplug the PoE and reconnect - or press the red or blue buttons?
I would go ahead and unplug ethernet/PoE
It's not like youre going to corrupt a long running HA install at this point
Unplugging the Ethernet/PoE, removing the USB stick and reconnecting the Ethernet/PoE results in green and red LEDs on constantly, the yellow LED on the Ethernet port flashes (green on the Ethernet port is constant on).
π I just started setting up my new Home Assistant Yellow and migrated my current install (HA Core / Docker) to it. I was going to start installing a few AddOns but when I click on "Install" on any add-on, I basically just see a spinner on the install button and nothing happens. There's not even anything reported in my logs.
Anyone seen this before?
It's a known issue with Supervisor 2023.03.3. Should be fixed soon with Supervisor 2023.04.0.
Thanks. Amusingly enough, the AddOn I was trying to install was SSH to allow me to manually move my data disk because of another bug that should be fixed in that update π
Any idea when 2023.04.0 will be released? I'm kinda blocked continuing the migration until I can install add-ons
It's in beta currently. If they don't find any problems, it is expected to be released the next days. 
Is ity possible to opt-in to the beta, even temporarily so I can continue?
Can use the usb serial console
All of my automations are written in AppDaemon, so this Yellow is not gonna be much use until I can move them over π
Sure. In Settings - System - Updates you can join the beta channel. But I wouldn't call that a recommendation.
Some still reported issues with updating the Supervisor. Those had to restore a backup.
I'd recommend to keep patience and wait for the official release.
And download a backup before updating π
it's a clean install with just a restore fro my other system, so easy to recreate. But... it's been "Installing" the Supervisor update now for 10 minutes, so guess that's not working either π¦
@wary pivot - would you believe it, but 2023.04.0 has just been released and as I did a factory reset on my Yellow, it's picked up the updated Supervisor and AddOns work (and so does moving my data disk)!... the timing!
Out of interest given I cannot get my Yellow PoE to show signs of life beyond the USB boot heartbeat stage, what should the default jumper positions be? I left all jumpers on the board in the same position they came in out of the box, JP1 is in the UART position; JP2 is disconnected; JP5 is in CLs3 position.
those are the default settings
so you now have solid red and green? Wonder if your CM4 needs an eeprom update
Some older CM4s can't be updated automatically it seems
Yep - red and green on constantly after removing the PoE power, removing the USB stick and reapplying PoE power.
So, the serial debugging is actually pretty simple. You connect the Yellow to a Pc using the usb c port on the yellow, and no jumpers need to be changed.
But alternatively you can get the CM4 connecting to your PC so that the emmc can be flashed directly and that requires changing jumpers and installing rpiboot
You would do the same for updating the CM4 firmware/eeprom
What would I be looking for with serial debugging?
not much if HA OS isn't installed
the red and green suggest to me that you would want to first look into updating eeprom, based on previous situations here in discord
Working on that now.
@grave moon most likely this is a networking issue. The system waits for NTP time to synchronize. Either the system can't reach DNS or the NTP server. This can be due to firewall or bad ISPs.
Can I test for access to DNS or NTP time from the command line on a MacBook Pro?
We use cloudflare DNS and time servers, I guess this should do it:
nslookup time.cloudflare.com 1.1.1.1
(assuming nslookup works the same on MacOS as on Linux)
Not sure how you could test NTP.
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
Name: time.cloudflare.com
Address: 162.159.200.123
Name: time.cloudflare.com
Address: 162.159.200.1
Hello !
Where should be listed the coral tpu usb in the yellow hardware panel ? I want to be sure HA yellow is seeing it.
(It's plug in a recommended powered usb hub).
I'm asking this because even after reboot, frigate is not detecting the usb coral (no edge tpu detected...)
I haven't been able to get it running reliably. Even with an powered hub. Frigate is throwing USB communication errors after a few detections and shuts down. Now my Coral is sitting here, waiting for someone to find a solution.
Anyone familiar with what the preferred boot order settings for the HA Yellow Rpi CM4 eeprom should be?
Yeah π¦
I may try to make frigate run in a windows docker desktop, because I could confirm the tpu is detected on my windows
With some USB cables the Coral is detected, but it doesn't stay available. And I have spent too much on USB cables to test it. Several lengths, qualities, USB 3 and 2,...
I can confirm that the usb cable works with the coral and my windows machine
The yellow was aimed for me to use a M2 coral in it, then Google and rpi said no. Then the usb coral is very unreliable.
I might just go with a nuc to replace the yellow. Same price but with a lot more power, and just plug a skyconnect or any other ZigBee dongle.
I can understand that. I was a bit disappointed too, when I tried it without success. The crowdfunding page kind of implied, it would work (at least the USB version). But I haven't found anyone with a working Coral yet (and suggestions, what cables and powered hub to use).
Do you mean the default boot order?
Yes - the preferred default for the HA Yellow board.
The Pi default boot order is 0xf25641. eMMC - USB - NVMe - USB-C - Network - Restart
But to use rpiboot (to execute Option 2 reinstallation of HA OS) you'd need to add a '3' on the end:
BOOT_ORDER=0xf256413
I haven't altered the boot order to rpiboot to my CM4. π€
BOOT_ORDER=0xf25641
Is the default within the boot.conf file in the Rpi usbboot package. So I'll leave it as is.
Seems Raspberrypi.dk have improved on shipping. Order placed 03.04.2023, DHL delivery scheduled for 06.04.2023.
Isn't tomorrow a holiday?
For what it may be worth; after updating the bootloader in the CM4 on my HA Yellow, and then using "Option 2: Reinstall Home Assistant OS using rpiboot" to install the "Home Assistant OS Installer for Yellow" directly onto the eMMC - then, after powering off, setting JP1 back to UART and powering up again, 'Step 10' completed - as did 'Step 11' with only the red LED remaining on.
Fingers crossed HA OS is now installed and the Yellow will fire up as a HA instance.
Are you having it shipped to the US?
Has anyone tried having https://raspberrypi.dk/ ship to the US? Given my CrowdSupply order from February still says it should ship by 3/31 π , I'm tempted to cancel there and just pay for international shipping.
Do they deliver by bobsled?
I haven't, but it does seem to be something that they do, it's pretty expensive to ship though like $60-90
Thx @compact quartz , updating the eeprom bootloader and flashing the HA installer into eeprom directly using usbboot did the trick.
@shut cedar it looks like it wasn't a networking issue after all; or possibly it was as a consequence of an out of date bootloader.
Looks like $30 to $40 to ship to the US in my case.
I was just going by what their site said π
Supervisor upgrade to 2023.04.0 - how long should it take? I started the update about an hour ago and the 'blue spinning circle' is still going. There's also another update running alongside 'Silicon Labs Multiprotocol' also running endlessly. I don't want to reset the Yellow or do anything else drastic in case I lose data. Shall I just let it run overnight?
My Supervisor was updated within a few minutes. Others from the beta channel reported, they needed to wipe the device and to restore a backup.
took about 40-50min here, but download are slow on my end
Hmm... new add-ons.
So am I getting this right?
OpenThread Border Router = Thread only
Silicon Labs Flasher = Zigbee only (just flashing)
Silicon Labs Multiprotocol = both
Anybody have luck using the Matter integration with their HAY? All I get is the infamous "Matter is currently unavailable" message.
-
HA updated to 2023.4.0
-
Matter Server running 4.2.0
-
Using Home Assistant app 2023.3.0-full on Android 13 (Samsung S22 Ultra)
-
Tried removing all Matter integrations, rebooting, re-adding, and rebootingh again
-
Already up-to-date
-
Have not tried wiping entire HA install
EDIT: I also posted this into #matter-archived message
anyone have any idea what may be happening here I tried to move datadisk to my ssd but i keep getting these errors on serial debuger. Initially when i try movedisk it shows my ssd on the drop down but after pressing move datadisk and it reboots it says no suitable storage found. If i power cycle the unit the move datadisk option come back vv
[FAILED] Failed to start Wait Until Kernel Time Synchronized.
See 'systemctl status systemd-time-wait-sync.service' for details.
[ TIME ] Timed out waiting for device ββartlabel/hassos-data-external.
[FAILED] Failed to start Home Assisβ¦t OS data partition migration.
See 'systemctl status hassos-data.service' for details.
so im cleaning up all my stuff and I got yellow. Do I need the philips hue hub for anything?
Yes
I hope this necromancy isn't too severe - I'm trying to do this as well and having trouble. The red and green LEDs are solid, but the yellow LED is never lit. I'm vaguely aware that I may need to update something about the CM4? But I have yet to figure out exactly what or why.
Can you elaborate? So Im using zigbee for my lights (but it is not philips hue) and then I will have 3-4 philips hue lights
Some special functions are proprietary like Entertainment zones and using all capabilities of a Hue Gradient lightstrip. So it depends on the usecase.
Ok, thanks
Got my HA Yellow PoE today. no CM4 so I'm going to give running a Rock CM3 on it ago instead, anyone attempted it yet? I saw makerbymistake on twitter got HA running on it
Neither the hardware nor the software is designed (and tested) for the Rock CM3. Even if the hardware would be compatible - as the Yellow needs a specific device tree, you would be on your own to implement it to your installation.
That includes things like the yellow heartbeat LED, NVMe support and the Zigbee module.
Hello, I received my HA Yellow PoE kit and have trouble installing using the official documentation (I already use HA on a regular RPi).
I supply it with a 12V/2A aftermarket power adapter instead of PoE, the chip is CM4 8gb ram, 16gb eMMC with wifi.
I also installed a 500GB ssd (samsung 970 evo plus)
I prepared the OS in a USB drive and have it plugged in as instructed, I am only getting a red and green leds constantly on (no blinking at all).
What could I be doing wrong/how can I troubleshoot? I only have windows computers to help with troubleshooting.
Can anyone telll me what voltage to set my network switch port to for my POE Home Assitant Yellow? The options on my network switch for the ports are 24 or 48V and I cannot seem to find any documentation that states max input voltage to the board. I dont want to risk frying the board!!
Standard PoE, 48v
Should I take this to https://community.home-assistant.io/ possibly? The existing threads there I've seen have been using mainstream hubs like SmartThings or Google Home, instead of HAY, which is the only thing I have.
@ebon field #matter-archived would be a better place to explore. Keep in mind it is still very early for matter
Fair enough, I'll keep my focus there, thank you! I know it's an early beta, but heck I can't even get the option to enroll a device at all! π
yeah getting a device to enroll at all is apparently part of that challenge. I'll be staying away for at least a year
Paying the early adopter fee π«‘
I got my Nanoleaf Essentials Matter bulbs, looks like I might need to shelf them for now lmao
if you have the option to choose you might not have an 802.3 active poe switch? afaik non of the 802.3 standards use 24v. your switch may not be compatible.
@jaunty ice @rose hull You propably need to update the CM4 bootloader. But I haven't got a step-by-step tutorial at hand for the Yellow.
https://www.raspberrypi.com/documentation/computers/compute-module.html#cm4bootloader
π
@potent shale, I'd be a bit careful here -- as @opaque summit notes, it sounds like your switch might just support static PoE rather than the more standard IEEE 802.3 versions that negotiate voltages. I belive the Yellow is designed to work with 802.3[af/at/bt] gear rather than the non-standard static PoE stuff mainly used for older telecom gear. I'm not 100% sure what happens if you send a static 48V PoE line into 802.3 gear, but it's possible it might damage something.
Yellow documentation at https://yellow.home-assistant.io/documentation/ got updated a bit:
- More docs on Multiprotcol (About/Enable/Disable How-tos)
- New Pinion PCB diagrams for PCB Revision 1.3
- New Schematics for Revision 1.3
Also a new Yellow installer is available from the RPi Imager. It allows to force installation of Home Assistant OS onto the NVMe (by pressing the blue button, documented in the according step https://yellow.home-assistant.io/power-supply-nvme/#connecting-the-power-supply)
Will the getting started guide be updated with the additional 4 screws as well? (presumably for the cm4?)
I guess we should... Probably means new pictures π°
As long as you didn't expect me to need 4 spare screws for the nvme..:P
Have they noted the changes between revisions anywhere?
in the blue button press instructions, there's a broken <br>
Advanced: Forcing installation onto the NVMe SSD when using CM4 with eMMC:< br> Press the blue button while the yellow LED is on constantly (during the 5s window, see next step).
Fiiiinally had the time to migrate to my yellow, absolutely love it so far. My z wave hat works perfectly too!
I just received my yellow. Found a CM4 module on amazon (for a months salary). I followed the instructions for creating the Pi installer, plugged it in, rebooted, etc. All seems good. The device shows up on my network, but is not pulling an IP address. I've installed twice, same result both times. What are my next steps for getting this up and running?
Red and green lights are steady. There is no activity on the yellow light.
Power is via POE, and there is activity on that port.
Np Jp2 ps present.
and pressing the red button within 5 seconds after applying power seems to do nothing. I've held it for up to 1 minute.
Is it a CM4 lite without eMMC?
I believe it does have 32GB eMMC if the description on the website is accurate.
Old CM4s seem to need a manual bootloader EEPROM update. But before you go down that rabbit hole. You can connect the Yellow's serial console to your PC via the USB-C port and observe what it is doing during boot or installation and 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/
thank you. I'll try that this weekend
@shut cedar Another thing for the wishlist. Maybe we can get a tutorial in the documentation what to do, when the steady green and red LED problem occurs. It seems so be a quite common question now.
that's what I have - steady red & green as soon as power is applied. I'm doing this (https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/) right now and I'm getting nowhere.
It doesn't show anything during boot?
nothing at all. Sorry, I need to pick this up later. I have to go to work to pay for this darn CM4 module. π
Hi folks, quick one here. Just got a shiny new Yellow w/ POE. It's running happily, but I cannot get Zigbee2MQTT to start at all, and all of the Reddit/Forum threads i've found are either not useful or tell me i'm a moron for putting HA on a Pi, which is also not Useful. I've attached a picture of my Config.
Or not, as the case may be.
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: "-d -d"
log: false
base_topic: zigbee2mqtt
port: /dev/ttyAMA1
baudrate: 115200
rtscts: false
adapter: ezsp
Those are the socat, mqtt, serial configs respectively.
No logs?
@wild solar I converted your message into a file since it's above 15 lines :+1:
Convenient bot
Have you used the Silicon Labs Multiprotocol or OpenThread Border Router add-on once?
Nope, this is a clean install
Okay. Second question... If you go to Setting - System - Hardware, is it showing Raspberry Pi 4 or Home Assistant Yellow?
Yeah. You have used the wrong OS image. That one doesn't include the device tree to support the Zigbee radio.
problem is, its a vague indicator. In my case it was an SSD that the Yellow decided it didn't want to boot from, even though it recognized it enough to write to it during the install process
If I backup, reinstall, then restore. Will it keep all of my assorted trash?
but it could be other issues
Yes.
also, for me, none of my add-ons would start after i restored my backup, until i did a full power cycle
That's a common issue. A full reboot/power cycle is recommended after backup restore.
yeah, wasnt aware of it til i looked it up
Would be handy to have some usual causes at hand. Unfortunately not everyone gives a feedback, what the cause of the issue and the fix finally was.
So every time I try to install, it just boots the existing HA installation
Is there a way to force it to overwrite the install?
Press and hold both red and blue button on power up. Are you using the USB installer stick?
Yes
Red and blue pressed wipes everything, including the OS.
Red alone just deletes all data, but not the OS.
After the wipe, you can use the USB installer
Those are the two options to reinstall:
https://yellow.home-assistant.io/guides/reinstall-os/
rpiboot has worked, it's up and running and Zigbee2MQTT is recognised and running. Thanks for all your help!
In hindsight... with the RPi4 OS, the button weren't able to work, as they are part of the Yellow OS. π€£ π€¦
lol. Ah well, no harm done. I'll no doubt be back next time I have some irregularity.
I've plugged in my yellow for the first time, and nothing, No LEDs, nothing on the network. How to troubleshoot?
If no leds at all make sure your cm4 is fully seated. You should have heard some snaps when inserting it
Thanks @compact quartz I am in business!
@wild solar One little thing left. It is recommended to use rtscts: true in your Z2M config.
Am I doing something wrong if after assembly the pcb is not held firmly but rather able to rattle ever so slightly around in the case? 5 out of 5 had the same result.
Hello! Is it best to use the cm without wifi/bt?
The design and certification is done without wifi, HA is also very wired ethernet centric - but both wifi and bt works, and you can disable either or both in config.txt for flexibility. I have wifi on all of mine, mostly for the bluetooth, and i use one with https://community.home-assistant.io/t/add-on-create-a-wi-fi-access-point-with-hass-io-access-point/321732 for testing.
tl;dr If you need it in a commercial setting it might be best to go without wifi due to compliance, but for personal use it boils down to preference imho.
If I am already running hassio on a RPi 4 will the yellow provide me anything different?
not much; but nvme, poe and zigbee without usb was the selling points for me.
An integrated Zigbee radio and a NVMe slot. And PoE - with the according kit.
i've been out of the HA loop a bit. has Zigbee won out over Zwave?
they did in my house:d
i'm assuming I could still setup my Zwavestick if I needed
I don't own any zigbee devices. Also from a Storage perspective what is the usecase for having NVMe? Do people use HA as a NVR?
nvme was primarily for reliability over sd cards for me. and yes you can still use your usb zwave (even some zwave hats). but the cm4 that runs the yellow is basically just a rpi4 so there wont be much gains in performance or features beyond having nvme on a pcie slot rather than usb.
I guess that's a good point, if HA is running your security system you likely don't want to deal with a burnt SD card
the cm4 module also offers eMMC storage options so you dont need a nvme drive.
Is the concept of HAHA (High Available Home Assistant) a thing, I know i'm very punny. Running a primary/secondary system in the event one goes down?
The HA Yellow is running a specific HAOS variant, which enables certain hardware features. Running other OSs isn't impossible, but you would have to find your own way to implement the specific device tree.
So: no - HAHA isn't really a thing with HA Yellow. If you want to go that way, other hardware would be much more suitable.
guys, everithing wa workin fne until this morning, all my lighst are ON and my zigbee logs reads
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/zha/init.py", line 122, in async_setup_entry
await zha_gateway.async_initialize()
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 220, in async_initialize
raise exc
i have tried reboot everything but nothin works
Home Assistant itself is starting? You can access it?
Have you been installing the Silabs Multiprotocol add-on or the OpenThread Border Router add-on?
no?
it just stopped working
everything was working just fine
You have a second Zigbee coordinator attached to your Yellow?
I have a ZLZB-06 via wifi on my raspberry pi
everything is on, connected and accessible
just one coordinator
on my router it reads "esp32-483858" instead of ZLZB-06
Erm, no. The Yellow has a coordinator onboard. So you have two coordinators (except, the ZLZB-06 is configured just to be a repeater).
How is the ZLZB-06 integrated in HA?
I have a raspberry pi 4 (not yellow) configured without coordinator
So you are not talking about a HA Yellow at all?
my zha is configured socket://192.168.0.10:6638
no just a regular rapsberry pi 4
oh my bad i thoug this was the gerneral thread
so so sorry
This channel is specific to the HA Yellow. The people in #zigbee-archived might be more helpful with your specific problem
I'm so sorry I thoug this was the zigbee channel
Never mind! Come to the Yellow side - we also have Zigbee. π
One step at the time (If i survive my wife)
Is the HA yellow internal zigbee radio matter ready, or do I need the sky connect usb dongle as well? I have both and now donβt think Iβm entirely sure of the skyconnects use with the yellow
It is Matter ready. There are 3 different firmwares available for both Yellow and SkyConnect. Zigbee only, Thread only and Multiprotocol (both).
With Multiprotocol Zigbee and Thread are using the same Channel. If you prefer to seperate them, you would need a second radio like the SkyConnect.
But the Matter/Thread stuff is still experimental at moment.
Are there drawbacks to multi protocol for a small scale setup of less than 100 devices in your opinion?
Iβll do more research but as for now it sounds like the yellow covers most bases
I cannot give an educated answer to that, as I don't have any Thread devices yet. For that kind of question, the people in #thread-archived might have more insight.
Thank you
Oh yeah, is the thread-only one in a released and usable state now?
Last week, I didn't see an obvious way to make it use that firmware.
I'm actually using a 32GB Optane SSD in my Yellow at the moment, because of endurance. But that's probably overkill.
There is an OpenThread Border Router add-on now, which is installing that firmware automatically.
Usable... not really.
Still experimental.
Hello I received my HA yellow today and had is ready to set up, however Im not able to install HA os on my NVMe Crucial P2 ssd
What Crucial P2 exactly are you using? Some are known to work, some are incompatible.
1TB
What product name exactly? Is it the CT1000P5SSD8?
CT1000P2SSD8
It might be incompatible. Do you have a CM4 with eMMC?
yes
Have you followed the installation guide step by step? And at what point it doesn't work?
I missed the step to hold the blue button to force install on the SSD, but when I ran HA and went to hardware I cant see it
so basicly the OS was intalled on the CM4
So HA is already running from eMMC and the SSD isn't showing for the data move, right?
correct
Has the NVMe been used before?
no
Okay. That looks like an incompatibility. Please report this with as much details as possible to the support at yellow@home-assistant.io .
ok will do thank you
anybody here got any experience with the Yellow and recovering a user? (as there is no screen connectable to the yellow
Do you mean a reset of the password? Use the USB-C serial console for that.
hmm, that is an idea actually, thanks
@wary pivot thanks, i am back in!
it seems though, that my configured settings have been reset too, so have to rebuild my user interface i think
Ah well, as long as i can controll my lights again, i am good
That's strange. Changing the password shouldn't alter other settings. π€
But glad, you are in control again π
it seems like it ignores the SSD right now
but Moving to ssd would probably overwrite the data i guess, so i would like to convince the HA yellow to boot from the SSD
You moved the data disk to SSD before? And it is running now without that data disk and the UI is accessable?
yes, it was running from the SSD, till the power went down today, then after it rebooted, it didn't access the data on the SSD and now it is running from the EMMC on the cm4
I had my SSD go offline, but that could be fixed by a powercycle. But this sounds like a new onboarding has been run - not sure how to fix that without data loss (if possible).
Sounds like a hell of a configuration surgery
worst case i need to reinstall the yellow, which would be annoying, but doable, as i didn't configure too much yet
but it is really weird, before the power outage, everything worked nicely, after that, b0rk3d
but if i start recovery now, i won't sleep tonight
Off-device backups and a UPS are my best friends. 
well, what do you think of this : typing reboot on the serial console made the yellow realize it should boot from the SSD. Now the yellow does boot from the SSD and my old config is completely back
basically it seems like HA needed a kick that wasn't available as a powercycle reboot
Oookay. You should make backups and download them on significant changes - just in case it happens again
yeah, i know, had not gotten around to do that part. Have been busy with a lot lately, but not at home
Fingers crossed it doesn't happen again to you
yeah, i know, but i shouldn't blow up too many more powersupply's in other projects hahahaha (thats why the power went out)
just downloaded a backup to the pc, so for now i have a point to work from if needed
So we aren't getting CM4s, because they need the parts for all those powersupplies you are blowing up? π
hahahaha, was just one, because i made a booboo wiring some LEDstrips, or just because it was a shitty 12V PSU from china, could be either one
but i was not planning on blowing up more of them, now i know what to look for and prevent
anyway, time for bed, and i am glad i tend to read first, try and solve issues later, instead of making it worse by just doing whatever
Hello all, is anyone having trouble with the latest update breaking the "Yellow Multi-PAN" integration? I'm getting the following error in the logs. I have not made changes other than to update the multi pan integration and the HA core.
Couldn't start EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis coordinator (attempt 1 of 3)
What version did you update the multi-PAN addon to?
I believe I had updated to 1.1.0, I do not see any easy way to determine what I was running after a downgrade.
I updated 7 hours ago.
I am now running again on multi-pan 1.1.1 and HA core 2023.3.6
it does appear that upgrading to 2023.4.2 HA Core while on multi-pan 1.1.1 results in this error.
I'm restoring back to 2023.3.6 and 1.0.2 to see if upgrading just HA core causes this issue.
It appears that upgrading to 2023.4.2 while still on multi-pan 1.0.2 causes the issue.
There were no relevant ZHA changes between 2023.4.1 and 2023.4.2. Can you get debug logs for the integration and the addon?
where is the best place for me to post them?
You can DM them to me
do you have a preference for which version of the add on I send logs for?
The more the better. It would be easiest to figure this out if you can send me a combination that works and a combination that doesn't. Just to be 100% sure, do you have "automatic firmware flashing" enabled in the addon config?
I do have automatic flashing enabled.
Is there a way to remove/flash the content on a CM4? I have my HA on a m.2 and I am replacing my CM4, but it already has HA on it. So I though just having an empty CM4 added works best rather than one with HA
https://yellow.home-assistant.io/guides/reinstall-os/
With option 2 you get access to the eMMC.
Thanks!
Is my assumption right btw? If i migrated HA to my m.2 on my HA Yellow. a clean CM4 with the a m.2 with HA will run? My new module has not got a enough space for my HA stuff. That is why i did not go with the start with a fresh install and backup route.
No. Only the data partition was migrated to the m.2.
I would recommend to download a backup, wipe both with the red+blue button method and start with the new CM4.
Ok. but i am pretty sure that if i start my backup on the new CM4, there will not be enough space, so i am not sure how to approach is. I have 2 HA yellows with CM4, but only 1 m.2, and the one that has the m.2 drive and working is the wrong CM4. Do you have a recommended approach?
The M.2 drive has a lot of info on it and then new CM4 has only 8gb of space, which i am pretty sure i have exceeded.
I would do the following:
- make and download backups
- wipe devices with red+blue button method (part of option 1 of the guide above)
- swap CM4
- install HAOS with the installer USB stick
- do the onboarding to create a user
- login and move data disk
- upload and restore backup
If the NVMe isn't shown up for data migration, you might need to delete all its partitions by hand.
Ok thank you!
i Kinda did what you said and when i booted it with the nvme it started the HA that was on it
So i guees i can skip a few steps. i did a restore from backup now just incase the new and old system colide
But it would be nice to have a way to just switch CM4, if it breaks or one upgrade. I understand that it is not top pri.
did you see
Also a new Yellow installer is available from the RPi Imager. It allows to force installation of Home Assistant OS onto the NVMe (by pressing the blue button, documented in the according step https://yellow.home-assistant.io/power-supply-nvme/#connecting-the-power-supply)
#yellow-archived message
just not using the emmmc in the future might be easier.
Yeah forcing the NVM installation was a posability. But what happend automagically was actual ideal. My old system just came back when i plugged in the NVM
Its safer too, since i did not have to delete anything on it.
Hmm it was not completly fixed. I get an interessting error where it switches between the fresh install and the NVMe one on startup
After playing around a little i found this to be the best solution. Thanks. Now i have 1 clean HA Yellow, and my upgrade yellow.
is there a way to access the GPIO pins 1-4 on the yellow board and set one of them to high via a HA integration?
Hey! I just got my yellow delivered today but when I install the "Matter (BETA)" integration I get an error saying "Retrying setup: None". Looking in the logs say the following "Config entry 'Matter' for matter integration not ready yet: None; Retrying in background". Anyone seen something similar?
@charred star #matter-archived is the better channel
Thanks
The HACS Integration Raspberry Pi GPIO (https://github.com/thecode/ha-rpi_gpio) might work. But I haven't tested it with the Yellow yet - so no guarantees.
looks very promising, thank you!
Hello, i've migrated to Yellow now. Most things are looking ok, but the add-ons did not start. Any idea why?
Do a reboot of the host. It's a known issue that add-ons don't start well after restoring a backup.
By the way... Nice video about the Roborock integration, @sacred bloom π
Thank you! The integration is really a progress compared with the Xiaomi.
@sacred bloom , can i see the video? i have a roborock and the xiaomi integratijon is giving me grief
https://www.youtube.com/watch?v=r0TFQo-axRg
This is the video. But it is in German.
The integration is dependant on the Roborock cloud (at moment).
@potent lichen I hope its possible for you to follow the video in german. The integration itself is not so difficult to configure. Map configurations are sometimes a challenge.
i'm using xiaomi, also depends on the cloud, and fails for no reason. Is the roborock one better than the xiaomi one (i'm going to have to revert my robots back to the roborock cloud).
do you have any written notes i can throw in a translator?
I see the notes in the github. thanks so much!
I've bought a Roborock S7 Maxv and hated the fact that I had to use the Roborock App or the previous existing HomeAssistant integration. But not both.
Using the Xiaomi integration there is also a limit to the number of map request which this integration doesn't have
Does somebody has a best practice how to migrate from Conbee II to the internal zigbee radio? I read different things but nothing like a general approach.
The only thing i have in written is my code for the map on my blog
Got it. Youtube CC translations is surprisingly good. I can totally follow along
My yellow is currently sitting in teh box because migrating radios will be a pain (fromo Sonoff 3.0P to Yellow on zigbee2Mqtt)
Are you using ZHA?
no z2m and would like to keep it
Don't know of any migration without repairing with Z2M.
Say, does the Yellow kernel happen to support PCIE AHCI drives? That is, the M.2 card is a SATA host controller, not a SATA drive.
@zealous jay no
This topic contains a solution and it sounds like that re-pairing is not necessary. But i do not fully understand the solution with regards to the performed steps: https://community.home-assistant.io/t/home-assistant-yellow-builtin-zigbee/471604
That's the radio migration with ZHA. The radio migration with Z2M would be this and it sounds like a re-pairing would be necessary:
https://www.zigbee2mqtt.io/guide/faq/#how-do-i-migrate-from-one-adapter-to-another
You are right, i thought the setup from the author before the migration was also z2m but it seems it was another topic.
Specifically, the only thing it would need is to have the "AHCI" module compiled.
I suppose the most thorough way is to just try it. Does HA let you move the data partition back onto the eMMC?
No.
What model SSD is that?
Hi all. Wanted to check because I am pulling my hair out and can't find anything to help me.
Has anyone got the USB Coral to work with their Yellow and Frigate. I have a powered USB hub and high speed extension cable. Frigate will not recognize it, nor HA, as far as I can tell.
you need to pass /dev/bus/usb to the container
In my case Frigate is recognizing it, but it keeps failing with USB communication errors after a short period of time.
try a different usb cable, my coral was quite picky about the cable
I have tried 8 different USB cables (different lengths, brands,...) without success.
The same as others in this forum thread:
https://community.home-assistant.io/t/home-assistant-yellow-coral-usb/483822
This sounds promising. I can't seem to find instructions for this. I am running Frigate as an add on.
I followed this as well. Bought the same hub (EU version worked for someone in EU) and a high speed 10 ft extension. Have tried other extensions as well.
I ordered mine 24-Feb (kit with power supply) from crowdsupply. Still waiting π ...
I waited 13 months for mine. Worth the wait.
Anyone managed to get a HAY Rev 1.3 running CM4 Lite / NVME to boot off USB and install? π€
i used usb-nvme adapter initially, but just tried again with the usb installer. both works. some are report having difficulty updating the bootloader automatically so it could be the install works but it fails to boot after?
does the serial console tell you anything useful during the instal?
(ref serial console under troubleshooting: https://yellow.home-assistant.io/documentation/)
((edit: oh, if your nvme already has an active boot partition cm4 might not make it to the usb installer, if so erase existing boot partition))
Will have to see what a USB to nvme adapter yields. Putty doesn't yield anything, console remains blank and unresponsive.
hm, even if cm4 bootloader doesnt have any uart output the kernel in the installer image should output something i think. What does the LEDs do?
re https://yellow.home-assistant.io/guides/yellow-leds/
constant red and green
you plug in the Ethernet? Can you see from your network/router etc. whether itβs been assigned an IP or transmitted any traffic?
I suppose the bootloader of the CM4 is too old and needs to be updated manually.
I just read a thread suggesting that just now. Didn't see a walk-through on how to achieve that though π
Another alternative is the CM4 isnt properly seated, if updating the bootloader doesnt work.
CM4 is seated correctly. Updating the BL doesn't appear nice for Windows users. Beginning to think I'm too dense to figure this out π
linux subsystem or a virtualbox or other virtual machine?
I'm having an issue connecting to my Yellow. My router is assigning it an IP address, but the connection is refused when I attempt to connect. I'm able to connect to the serial console. That reveals the homeassistant login prompt. I can log in, but when I issue the 'ha' command to connect to the Home Assistant CLI . . . nothing, it just stops there. Red light is illuminated, the green has no discernible cadence, and the yellow seems to be flashing twice. Is it still downloading? I've left it overnight, but it never leaves this state.
Hi .*, Can somebody help me out. I got my yellow PoE version. I hooked up the UART IF and I am checking whats happening in the console. Installing the OS from the USB drive seems to finish OK, when only red light is on (reboot: Power Down in the UART console), I unplug the yellow, plug it back in. Boot process seems to start but then I get this:
MMC read: dev # 0, block # 1214464, count 32 ... 32 blocks read: OK
Error: bad CRC, import failed
gpio: pin GPIO27 (gpio 27) value is 1
gpio: pin GPIO26 (gpio 26) value is 0
UMS: LUN 0, dev mmc 0, hwpart 0, sector 0x0, count 0x3a3e000
and it is stuck here. Both the red and green leds are on, nothing else happens. Any hints what could have gone wrong?
Try reinstalling. i've seen that message in my attempts to get mine working. Hold the red and blue buttons on power up. You'll see "Boot wipe has been pressed, deleting boot files to trigger USB boot...
resetting ...
" in the serial console. Then just let it boot from your usb stick.
Thanks Lhankm the issue is my blue button is broken... It came a bit bent and is not clicking... I guess I will need to do some soldering first...
Good luck. I'm beginning to suspect I have an incompatible ssd.
Fixed. Clearly needed a good nights sleep. What I didn't find from any of the minute tutorials that cover Windows based updates was you needed to use "rpiboot.exe -d recovery". As soon as I did that, bootloader updated perfectly and I now have a working HA Yellow.
As I suspected. A lack of willing brain cells on my part π
Welcome to the yellow side of life! π
Assuming people only need to update and not modify the bootloader linking to https://www.raspberrypi.com/documentation/computers/compute-module.html#flashing-the-bootloader-eeprom-compute-module-4 might cut through some of the noise
edit: or https://yellow.home-assistant.io/guides/flash-cm4-firmware/ which seems to have been written but not included in documentation.html ... and i only found out after trying to write the cm4-bootloader-update guide π
(edit2: they fixed edit1)
Hi Folks, I install HAOS on the yellow, successfully, but then after powering down and powering up, at first boot I get:
MMC read: dev # 0, block # 1214464, count 32 ... 32 blocks read: OK
Error: bad CRC, import failed
gpio: pin GPIO27 (gpio 27) value is 1
gpio: pin GPIO26 (gpio 26) value is 0
UMS: LUN 0, dev mmc 0, hwpart 0, sector 0x0, count 0x3a3e000
So far the only hint what to do with this was from @digital talon to push the red and blue button at once to delete the boot files and trigger USB boot. Now in my case the yellow came with a broken blue button so this is not an option. Any other hint how to get rid of this bad CRC error. What is actually wrong here?
What i managed to figure out I can wipe the eMMC on the CM4 with the following sequence:
- change the JP1 to USB
- connect the USB-C cable
- connect the 12V DC power
- After this my computer will recognise the device as a USB device
- with disk utility I can erease the eMMC
- eject the device after erease
If I do this then I can again install from the USB device, but each time at first boot the same CRC error. Is maybe my CM4 module wrong? Anybody any hints, getting a bit desperate... :S
Tried also with the SSD in place, also without SSD, the same thing always.... π¦
First: your blue button is also broken electronically - it seems to be pressed permanently.
You should contact Nabu Casa at yellow@home-assistant.io for a possible RMA.
Second: for the CRC error (if it isn't caused by the stuck blue button), you could try to reflash the bootloader/OS - but it might also be a hardware failure of the CM4 eMMC.
The blue button, is bent inwards a bit, if you open it up the button is mounted on a metal plate and those upper two plactic pieces what melt throught the metal are not there. There is no clicking feedback or anything. According the documentation that is a power button, so I dont think it is permanently pressed, since then install wont work either... I contacted Nabu Casa, but no answer to my email for over two weeks... π¦
It says GPIO26 value is 0 - meaning blue is pressed.
GPIO27 value is 1 means red button is not pressed.
I also tried to reflash the bootloader, the thing then I see zero activity on the UART, so I just guess it worked. After that I tried to reinstall the HAOS again with the same results... π¦
Well... pressed or shorted out
ahhh great thats good to know...
there is zero clicking feedback so I guess then that button is stuck... Does anybody have some experience how quickly the folks from Nabu Casa get back in case of HW issues?
They usually respond quite quickly.
Ok I might just try to send the same email again..., thanks @wary pivot for your help
Is there any way to get the Thread-only firmware for the integrated radio, and have that be used properly? The GUI only currently offers multiprotocol.
You can use the OpenThread Border Router Add-on. But I wouldn't call it "properly usable" yet. All that stuff is still experimental. The Thread-only firmware is also included in the Github mentioned in the guide for manual flashing.
Basically all of my initial problems boiled down to this
One of the cheapest compatible SSDs is the Silicon Power P34A60. Bonus points because it has an activity LED, so youβll know for sure when itβs working
I wish we knew why other SSDs donβt work, I paired the PNY my Yellow didnβt like to my spare Pi 4 via an Argon One case and itβs working fine
NVMe in the Argon one/Pi4 is using USB isnt it? Afaik the compatibility issue is with CM4/PCIe not the yellow as such.
Do the yellow support the razberry z-wave module?
I can confirm the Aeotec Z-Pi 7 is working. As the Razberry ones are using the same GPIO pins, chances are quite high those are working too.
ah, interesting, then the Yellow might be something to consider getting
Looks like the M.2 AHCI drive (that is, M.2 PCIe, not M.2 SATA) works just fine in Yellow.
Doh, it failed to do the migration properly... it didn't label the new drive hassos-data, or something!
Hello! I have the yellow with power, how can I convert it to be POE ? Is it possible?
Use a POE splitter with 12V output and a 5.5mm OD/2.1mm ID barrel plug.
Nice, so something like this would work SAR 41.98 40οΌ
Off | EWIND POE Splitter 10/100/1000Mbps Ethernet Splitter IEEE802.3af 44-57V To 5V Power Supply for Non-POE Camera or Non-POE Device
https://a.aliexpress.com/_EvajJwT
PoE splitter as suggested is the easy option. But the schematic and board files are on github so nothing stopping you from buying the components and fitting them i guess, but its imho not trivial.
yeah, the 100M only versions are usually a bit cheaper - but that sort of thing.
But it needs to be a 12V output, not a 5V one.
https://www.aliexpress.com/item/1005001309240177.html
^ pick the 12V 2A DC (Gigabit) or 12V 2A DC(100M)
One downside of POE is that, if you need to reboot a switch, all the stuff that's connected to it will likely reboot (without proper shutdown) as well.
I'm powering mine off a POE Injector, so I can reboot my switch at will
Getting a little OT; but how often do you reboot your PoE switches? I wanted my yellow on my (managed) PoE switch so it is possible to use a hard reset if push comes to shove
mine will reboot occasionally when automatic updates are applied (monthly maybe?)
i also have it on a smart switch, which will cut power to it if we lose mains power, to extend UPS time for my router (to which the yellow is connected via the POE injector)
Iβve gotten my HA Yellow kit in the mail finally and now I donβt even need it. Anyone know where I could sell it?
Anyone have a Yellow using NVMe have their install (apparently) wiped and installed to the CM4's EMMc after running a HA OS update?
No. Still on NVMe after update to HAOS 10.
I just did the 10 update and it looks to have installed HA on the EMMc vs the NVMe. It's not s huge deal, I can reinstall I was just getting started, coming over from a Blue but starting from scratch. I'd just like to know how to prevent the issue in the future... π
Ran the update on the install on NVMe, waited, went back and got the onboarding screen
Wait! Very strange, I just rebooted HA and it went back to the NVMe install, but does not look like it ran the 10 update (still prompting for it).
Maybe the NVMe dropped off. Try a powercycle.
Trying the 10 update again, let's see what happens...
You didn't install HAOS to the eMMC and migrated the data disk later?
Might just be boot order?
Maybe, I had a bit of a struggle when first installing, getting it on the NVMe... It kept wanting to install to the EMMc. Maybe I need to wipe the EMMc to prevent a boot attempt to that...
Ok, did the 10 update again and it came back fine... π€·ββοΈ
@craggy venture how did you install to the NVMe?
Maybe the eMMC has a partial installation on it, which confused the OS?
I followed the instructions... IIRC it was holding the blue button down after the yellow light went solid. It took a few tries to get it to finally get it there, kept installing on the EMMc
Wonder if there is a way to wipe the EMMc via SSH...
You need access via the serial console or the debug SSH.
We do a blkdiscard, which really should wipe the complete eMMC:
https://github.com/NabuCasa/yellow-buildroot/commit/a7467b7def985f16c5eff67836e52691b7cac9be#diff-a3a6090b383d2b889d851601bc43b0f63e58b5d982259506a509656a88ab2783R43-R48
But I think I've seen eMMC's which don't work with blkdiscard, hence the dd to be sure π But it really should be wiped when you've used the blue button.
Hm, ok, but that means you really have something flashed on eMMC π
Do you have debug SSH (port 22222) or serial console access?
Not atm but I can get that setup...
Or, I may just reinstall? I wasn't really that far along in the config...
I've go to get to work so I'll have to pick this up later but I appreciate your help. Any tips on doing the reinstall?
I really wonder how this came to be tbh π
Just double checked my test device, the eMMC is really just full of zeros π :
# hexdump -C /dev/mmcblk0
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
3a3e00000
Ok by me, I wonder if we see this again when updating to 10.1 π°
Yeah, 3 reboots later and it's back to the NVMe... Odd...
How do you determine where you are booting from?
System, storage 4Gb vs 500Gb. Also, one is basically a fresh install and the other has some of my config
You don't have a USB flash drive connected do you?
Hm, maybe you are still booting from eMMC always, and you actually have two data disk partitions active
Also, the NVMe did not actually update to 10 and is now showing an "Unsupported AppArmor issue" warning...
No, just double checked, no thumb drive
Maybe, like I said I had some issues getting it to the NVMe during install
So, a regular install should wipe the eMMC... I'll give that a shot later and see where I get.
If you've got a tip on how to insure it's completely nuked, lol...
The installer really should do it. If you want to make sure it is indeed doing what it should, make sure you use the latest version (reflash your USB thumb drive to be sure and/or monitor the serial console for the string "Clearing eMMC to ensure NVMe boot.").
This indicates that HAOS 9.5 gets booted. I wonder now why that happens. Do you plug out the system multiple times?
Wasn't HAOS 10 meant to be have improved Bluetooth performance? My Yellow with BT/WiFi CM4 seems to have worse Bluetooth performance. Frozen Bluetooth after 6h runtime. π
@shut cedar Since the HAOS 10 update I'm getting superblock checksum errors on boot. Do you have any suggestions how I can fix that?
Starting HassOS data resizing...
[ OK ] Finished HassOS data resizing.
Mounting HassOS data partition...
[ OK ] Mounted HassOS data partition.
Starting Grow File System on /mnt/data...
[ 25.669654] EXT4-fs (nvme0n1p1): Invalid checksum for backup superblock 32768
[ 25.677157] EXT4-fs (nvme0n1p1): Invalid checksum for backup superblock 98304
[ 25.684731] EXT4-fs (nvme0n1p1): Invalid checksum for backup superblock 163840
[ 25.692131] EXT4-fs (nvme0n1p1): Invalid checksum for backup superblock 229376
[ 25.699558] EXT4-fs (nvme0n1p1): Invalid checksum for backup superblock 294912
[ 25.706960] EXT4-fs (nvme0n1p1): Invalid checksum for backup superblock 819200
[ 25.714319] EXT4-fs (nvme0n1p1): Invalid checksum for backup superblock 884736
[ 25.721700] EXT4-fs (nvme0n1p1): Invalid checksum for backup superblock 1605632
[ OK ] Finished Grow File System on /mnt/data.```
Hm, systemd starts a fsck on each boot, maybe it marka the fs to get checked and does so on reboot?
Could also indicate a not completely flashed os image I gueaa
First boot after flashing?
I have tried fsck.mode=force fsck.repair=yes in cmdline.txt
No. The first boot after updating was kind of successful. Bluetooth stopped working after 6 hours and the next reboot resulted in crashes.
Sounds like some kind of issue with that NVMe.. π°
Let's see. I'm not too worried - just preferred to fix the error. If the NVMe dies, a spare one is ready and I have nightly backups on a NAS to recover.
Out of curiosity. The HAOS 10 announcement said, zram was replaced by zswap. Even after updating to 10 lsblk is showing 3 zram devices, one mounted to /tmp. Shouldn't the zram have been removed?
With OS 10 there should be 2 zram devices, one for /tmp one for var.
It seem we still initialize 3 by default, but the unused one is 0 bytes, so this shouldn't really matter.
I'd prefer if more would jump on the train during rc phase π
Note that we had more than 1000 people (with opt-in stats enabled) which tested 10.0.rc releases. I've addressed pretty much any issue I've encountered. But we have very diverse set of users, even though we test with 1k test users, there are always some setups which cause troubles out there π’
Updated mine this morning. Seems to have gone fine too. π
Hello, try to setup yellow for the fist time today. I was blocked because I could get my usb zwave stick to be recognized. Lsusd returns empty. What am I missing? Using PoE edition
Have you tried these instructions: https://www.home-assistant.io/integrations/zwave_js/?
Yes, I am migrating from a working system using RPI4
lsusb should always return something, there is a USB hub on Yellow. Can you report that to the support, along with the serial number of your device?
Which console do you run lsusb in?
After downgrade to HAOS 9.5 the filesystem error messages disappeared and my bluetooth is working more reliable (meaning working at all) again.
π
This really sucks. We need to isolate the probelms and report upstream (https://github.com/raspberrypi/linux/)
@celest parrot actually reported that for him NVMe problems got fixed with HAOS 10.0, but I guess that really depends on the model
@wary pivot what NVMe model are you using?
A Samsung 980 1TB (MZ-V8V1T0BW)
π― I think that is what kbx is using, let me check
I guess that is not a storage but a randomness device then π°
The firmware of my 980 hasn't been updated.
So for kbx he had crashes every other week or so on 9.x with that device.
Yeah probably worth a try. I think there are also reports of file system issues on x86 hardware with previous firmware versions.
As for Bluetooth: I am using a CM4 with WiFi/Bluetooth on my test device, it generally worked, but I didn't test it a lot beyond that.
On bootup it also works. But after some time it completely stops and doesn't recover.
It seems we use the very same git hash for the Bluetooth firmware:
HAOS 9
https://github.com/home-assistant/buildroot/blob/2022.02.x-haos/package/brcmfmac_sdio-firmware-rpi/brcmfmac_sdio-firmware-rpi.mk
HAOS 10
https://github.com/home-assistant/buildroot/blob/2023.02.x-haos/package/brcmfmac_sdio-firmware-rpi/brcmfmac_sdio-firmware-rpi.mk
That said, HAOS 10 comes with a newer BlueZ. So maybe this newer BlueZ actually makes thigns worse for RPi π°
Updating the NVMe via an USB adapter doesn't work. And I'm not really keen on disassambling my notebook to get access to its m.2 slot. π
NVMe is updated. Let's hope it was worth the hassle - and that it doesn't die. Don't want to disassemble my notebook again for a spare SSD. π€£
π π
@shut cedar If you need direct access to a system with the Bluetooth problem, I can grant you access via Teamviewer. I'm back on 9.5, but I'm quite optimistic I could reproduce it with enough time.
Cool, yeah I might come back to that in case needed.
There is also a report in the OS issue tracker: https://github.com/home-assistant/operating-system/issues/2485
That's me.
Samsung 980 250GB here... I never had any issue, neither with 9.5 nor 10
Somebody apparently has to be the lucky one π€·ββοΈ ...
have you seen https://tmate.io/ - its kinda teamviewer for the console (i havent tried it on yellow due to lack of wget/fetch in the serial shell)
Yeah, I've seen that. But I assume the devs would prefer to get access to the serial console and the web UI. So the detour via Windows might be the easiest and most practical one.
Hey folks, great work on the yellow.
I have multiprotocol on and after returning from a vacation and updating to HassOS 10, zigbee doesn't work anymore.
in the addons logs I have a loop going on: https://pastebin.com/Wzuz1fZQ
It starts,crashes and tears down the OTBR firewall constantly
What version of the addon are you running?
1.1.1
Any chance you have another Zigbee integration running, like Zigbee2MQTT?
Have you at all changed the ZHA configuration (e.g. to point directly to the radio)?
Yes I am actually running both π I used to work for a while though
I have a conBee2 connected via USB and running Zigbee2MQTT on it for some devices that are have better compatibility with Zigbee2MQTT
Is it running and accessing the same serial port? From the log, the Yellow's Zigbee radio appears unresponsive. Have you tried powering it down completely, unplugging it for 10s, then powering it back up?
I unplugged the conbee 2 stick and shutdown the zigbee2mqtt addon now. I'll restart it now.
no chance, still not working :/
Can you PM me a screenshot of your multi-PAN addon's configuration?
Resolved: manual config changes resulted in both ZHA and the multi-PAN addon fighting over the radio's serial port, causing neither to start up.
Oh I completely forgot: Make sure that JP1 is set to UART. Otherwise USB host mode won't be available.
@shut cedar - Just wanted to update you. I got it reinstalled and all looks good. It's survived a few reboots and shutdown/startup cycles. What I did was I removed the NVMe, defaulted the system by holding both red and blue buttons to clear the eMMC. I then reinstalled the NVMe and did the normal install, holding the blue button once the yellow light went solid.
What's the recommendation on eMMC SSD usage? Do I install everything directly on the SSD and the eMMC is never used? Or can the eMMC be useful for anything else? eMMC only has 8gb btw
Cool, thanks for the update!
Home Assistant OS itself is only ~200MB (and usually there are two versions of it installed, A/B fallback type of installation). So the 8GB is plenty enough for just HAOS. If you use the NVMe SSD as your data disk, everything else (including Home Asssitant Core itself) gets then installed on the NVMe SSD.
You can install everything to the NVMe SSD, but this is somewhat experimental as we have seen booting issue with some NVMe SSDs. For that to work you need to press the blue button in a specific window while the installer is running (see https://yellow.home-assistant.io/power-supply-nvme/#connecting-the-power-supply). Installing HAOS directly on the NVMe SSD has the advantage that everything is installed on the NVMe SSD, so you'll be able to upgrade the CM4 by just replacing it.
Sweet thanks for the detailed reply! I thought 8gb would be enough but I'm getting 1gb left warnings. Maybe I'm doing something wrong. Only about 3-5 extra addons
Being able to install to NVMe storage would've been pretty useful back before I had to replace my 32GB SSD π
Just as a data point for folks trying to get their hands of a HA Yellow PoE kit -- I originally ordered one of these kits from CrowdSupply on 2/26/23. The ship date on that kept getting pushed back. It was originally supposed to ship by 3/3/23. The current estimate is now 6/30/23 (so roughly 120 days after I placed the order, assuming that holds). I got tired of waiting so I ordered one from raspberrypi.dk instead (where they are currently in stock). Placed my order on 4/13. Unit shipped via DHL Express International on 4/14, and it arrived here in Colorado today on 4/20. Total cost was ~$190 including shipping after the exchange rate conversion, so about $30 more than the CrowdSupply all-in cost (~$160 including tax + shipping). But it's a $30 extra I was happy to pay to get a board now, vs maybe in another two months.
My HA Yellow has become really slow over the last month or so. I'm taking some time now to try to identify what the issue is, but really struggling. I've disabled all add-ons, rebuilt the database, but it takes forever to start up with most integrations reporting they are timing out starting. There is nothing obvious in the logs other than timeouts for pretty much everything! Where else can I look?
It doesn't seem too bad once it is up and running, but restarting HA takes over 5 mins.
The file editor add-on which used to load quickly now spins for 5-10 secs before loading, so not sure if it is an I/O issue
I even get timeouts for these?!
Setup of input_button is taking over 10 seconds.
Setup of input_boolean is taking over 10 seconds.
Some integration startup times... Samsung Smart TV 295.60s, HomeKit Controller 196.05s, Mobile App 193.99s, Overkiz 167.60s, Alexa Media Player 113.55s, MQTT 108.07s
Well... MQTT 335.23s, Alexa Media Player 8.09s, Mobile App 1.77s π€·
I've disabled most add-ons and some integrations now but no change
Jorg my MQTT has three entities. Suspect yours will have a lot more π
At moment my MQTT has three entities less than yours. π€£
What are some good ways to debug bootloops of the yellow?
I now had 2 different kinds of bootloop. A few months ago it would start without supervisor, just core and I resetted the yellow multiple times with different backups until it started working again
Now it's different, it just loads, and after a while I loose connectivity
Maybe the database is corrupt or my SSD is?
Connect to your Yellow via the serial console and observe the boot messages for errors.
Finally got it: https://pastebin.com/ygpgyiMH
It starts with [ 176.510555] CIFS: VFS: cifs_mount failed w/return code = -22
and then dies
Is this related to smb shares I use in a lot of my addons?
And now a bunch of those
[ 177.680615] CIFS: VFS: Error connecting to socket. Aborting operation.
[ 177.700971] CIFS: VFS: cifs_mount failed w/return code = -111
[ 177.769240] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
[ 177.769240]
[ 177.841056] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
[ 177.980263] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
I think some of my addons that mount smb drivers might be acting funky, maybe due to HassOS 10
I'll cross post to general, probably not yellow related
After updating to HAOS 10, my yellow is using 26-27% CPU even when doing nothing. Is this happening for anyone else?
Nope. 4% idle right now
Have a look at the OpenThread or Multipan add-on, if you are using one of those. Sometimes their CPU usage spikes up to approx. 25% and doesn't get back down. An add-on restart helps in those cases.
@mild kindle With what method are you mounting the SMB share and what parameters are you using?
Yes! I'm not on a yellow, but I have HAOS on a Proxmox LXC and CPU utilization doubled with v10 and stayed doubled. It's discussed on #devs_os-archived
nilse 7931 With what method are you
Hi I got my Yellow PoE using a CM4 lite, during install the yellow and green led never went off, it was at least 12h constantly blinking.
Removed the power and tried the process again. Now the green en red led are constantly on.
Tried with the rpiboot to recover, same result.
In a serial session I have zero output. Already set in the file boot.conf BOOT_UART=1. Still nothing happening. Anyone idea's?
I've got my Yellow up running. Migrating from a Raspberry Pi 4 with a Conbee and Zigbee2MQTT. I've restored a backup to the Yellow, but I don't see any Zigbee2MQTT and none of my Zigbee devices work. Anyone have a guide or can tell me what I should be aware of in this situation?
Already set in the file boot.conf BOOT_UART=1. Still nothing happening. Anyone idea's?
you ran the update-pieeprom.sh script and ran rpiboot with the custom recovery folder after?
(i.e ref: https://github.com/raspberrypi/usbboot/tree/master/recovery)
I just ran the update-pieeprom.sh script with the https://github.com/raspberrypi/rpi-eeprom/raw/master/firmware/stable/pieeprom-2023-01-11.bin binary as original. Ran rpiboot with -d recovery.
Then rebooted with USB drive in it. And it boots. Serial output is now the following.
Welcome to Buildroot
yellow-installer login: [ 17.629001] vc4-drm gpu: [drm] Cannot find any crtc or sizes
[ 35.804793] cam-dummy-reg: disabling
Since 10 minutes nothing happened.
No output before Welcome to Buildroot? Should be the bootloader should list storage devices iirc?
I do have output before Buildroot. I omitted it.
the console wont do much more than that while the installer is downloading and installing the latest images.
edit: should also see something like:
[ 23.548885] haos-flash[251]: Getting latest Home Assistant OS version from channel stable...
[ 23.754001] haos-flash[251]: Installing Home Assitant OS 10.0 to nvme0n1.
Could it be that my nvme drive is not found?
idk, that would be in the output you omitted
I went through it, doesn't seem like it is mentioned.
https://pastebin.com/2GTtkhdf
if you dont have a section that looks like https://pastebin.com/pPnCaKtd then your eeprom update didnt work btw. and yes, I can only see the usb drive in your log.
What do you mean the eeprom update didn't work?
i mean if you set boot_uart=1 that didnt work (or the yellow installer over wrote it) the pastebin i posted shows the output from the first bootloader that is enabled by boot_uart=1
yeah, seems the yellow installer will over write your custom eeprom even if its up to date. so that explains the lacking output from the bootloader. you could log in as root and check the storage with lsblk not sure if the mention of nvme0 in your log is just without partitions or not properly supported when i think about it.
I did find it though.
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 7.7G 0 disk
`-sda1 8:1 1 64M 0 part
nvme0n1 259:0 0 238.5G 0 disk
strange nvme0n1 isnt in the bootlog.
I had less issues putting the yellow image (not installer) on the nvme with a usb adapter than using the installer, so if thats an option you can find the image at https://github.com/home-assistant/operating-system/releases/latest
You mean flashing the image on the nvme drive like you would do with sd cards?
yeah, the haos_yellow-10.0.img - not the installer. I'd try that if you have an usb-nvme adapter.
(or you could use rpiboot -d mass-storage-gadget to use the yellow as usb-nvme adapter)
I'll look into it that. Just strange that the installer won't work.
What SSD are you using?
Gigabyte GP-GSM2NE3256GNTD
At least it isn't reported to be incompatible (yet).
I also checked that list.
Did you back up your zigbee network first?
I've just re-arranged my home network to include an IoT VLan and I need to connect my Yellow to it. The Yellow had a fixed IP on the original network and I now can't 'see' it or access its settings, despite it being connected to the router's port which is allocated to the IoT VLan. How can I 'find' the yellow, set it back to DHCP to have it recognised and then re-allocate it a fixed IP? I'm hoping NOT to have to completely reset it to defaults and restore a backup (this would be last resort!). Can I connect direct with ethernet from my PC and get to the UI? I know I'm missing something obvious here! Thanks, Andy
You can connect your Yellow to your PC via the USB-C port and access the serial console.
With
ip a show eth0
you can get your current IP settings.
To change it to DHCP run the command
ha network update eth0 --ipv4-method auto --ipv6-method auto
Thanks, Jorg - always appreciated. I haven't done this before, so I'm falling at the first fence trying to access the serial console. I installed PuTTy, selected 'serial' and the port the Yellow's connected to (Com8), but trying to type just comes out corrupted and meaningless, like I have the wrong keyboard. Any pointers, please?
Have you set the speed in PuTTY to 115200?
Thanks - just did that but no improvement. In PuTTY, is the serial setting Telnet or something else please?
No. Connection type Serial.
ok, but there's a box on the right to select telnet, etc. Leave as-is? I'm still getting unintelligible characters in the com window
can I attach a screenshot?
That box is only active, if you choose Other.
Sometimes un- and replugging the USB cable helps. Or powercycling the Yellow.
ok, I'll try both - thanks
Great - I got to 'homeassistant login:' and it's not accepting my normal credentials
login
I'm assuming I need my login details for the local instance, not the homeassistant.io one?
Just the user root no password
I am trying to reset my HA Yellow.
I have followed the instructions but it does not reset.
Any help?
Thanks in advance!
Jorg - many thanks - with your patient and experienced help I think we got there! I'll now wait to see if the Yellow appears on my network. Thanks again, Andy (Oxford UK)
What kind of reset have you tried?
How have you been installing HAOS? With the USB installer or with a HAOS image (in that case which one)?
My HA Yellow has become really slow over
I assume that is what I would do under Z2M Settings -> Tools -> download z2m backup? If so I did a backup now. What to do with that?
You should be able to restore that to your current zigbee network. That should restore your network.
might need to clear your existing network to a blank state though TBH I've not done it myself only read about the fact you have to back it up to restore it.
Ahh... OK. I'll try that. And then I'll just need to install Z2M again manually, since it was not restored from the backup?
yeah thats the one
OK. I'll give it a try later this week, when the wife permits house downtime. π
After the os update to 10 Bluetooth is having the following issue for me, anyone else resolved this?
Retrying setup:Β hci0 (E4:5F:01:88:04:58): Failed to start Bluetooth: [org.bluez.Error.InProgress] Operation already in progress
Even restarting and delete/adding doesn't resolve it
^ same, but I just disabled the integration and relied on ESPHome bluetooth proxies instead.
It is already reported and under investigation. Let's hope they can fix it soon.
https://github.com/home-assistant/operating-system/issues/2485
Hello All:
I am having issues with my Homeassistant Yellow.
Everything was up and running fine.
HA dropped from the network (unknown reason).
So I decided to just reset and start from scratch.
Noticed that the Factory Reset (Hold red button for 10+ seconds after power-on within 5 seconds.
Now the reset does not work (see Anove)
So now I am stuck.
HA Yellow on power up seems to start normally, Red light-Green flashing then Yellow Heartbeat.
Again nothing shows on network.
Tried several IP scanners Angry IP, Fing and the EERO app from my provider and no HA Shows at all.
You can roll back to HAOS 9.5 with the following command in a terminal:
ha os update --version=9.5
thanks
You can look for error messages in the boot process, if you connect your Yellow to your PC via the serial console and powercycle the Yellow.
Hm, my Yale smart lock said it required a new offline key some time after the update to 10.0, rolling back to 9.5 resolved that issue as well.
I have connected to HA from my Windows PC with Putty.
I can connect and tried "ha supervisor logs" Et al. with nothing...
Any error messages in the boot messages? Are you using a NVMe and if so, does it show up in lsblk in the serial console?
I am unsure how to access that information.
I have a Samsung 970 EVO Plus installed.
https://yellow.home-assistant.io/documentation/ has links to both windows and linux/macos for connecting to the serial console
Use ha to access the Home Assistant CLI.
ha supervisor logs
Error: No such container: hassio_cli
What does docker ps -a say in the serial console?
Are you running any DNS related stuff in your network? (AdGuard Home, PiHole or something like that)?
I can confirm it is not the SSD. I had the uplink for the yellow configured as tagged (trunk) instead of untagged (access). Thank for all the help and you as well @opaque summit.
I ran into this as well, but a full reboot of the board (vs just HA) seems to have resolved it, at least for now.
Indeed, but (in my case at least) it crashes some time later again. HAOS 9.5 hasn't been perfect for Bluetooth, but much more stable.
I have buy a Yellow with cm4 2GB. Now my problem if with all the integration i have running is there about 800 MB free of Memory. Every time i running esphome firmware build or upgrade af esphome firmware HA if running out of memory. If that normally at esphome if using sΓ₯ match memory? Can i do something that it uses less ram?
You can stop add-ons.
Anyone need a 8GB wifi CM4 (no eMMC)? New never used. USA based.
OK, I give up.
Can someone just help me to FACTORY RESET this thing... π
Not that I know of (DNS) related
docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
all my zigbee stuff stopped working and i could not for the life of me figure out what it was
i thought the chip in my yellow had failed
turns out i sat a USB 3.0 hard drive dock a little too close to it
I WANT TO WRITE BIG LETTERS TOO
I DON'T KNOW WHAT WE'RE YELLOWING ABOUT
pulled apart an old imac to extract the hdd and replace the dead psu, then accidentally dropped a bunch of wet soil in there from a pot plant sitting on the shelf above it...
That was always the goal, right. To make the old imac a pot plant.
vertical garden
it's been a doorstop for a couple of years now, so a plant pot would be a promotion really
Hi I just got my poe yellow. I am now trying to install home assistant OS on my sad drive. But it already hangs for 15 min. Yellow LED is blinking in the heartbeat mode.
I tried to debug. But the log just ends with yellow-installer-login:
My hardware: home assistant yellow, cm4 4gb lite, Intel nvme pcie SSD
I kinda broke my HA Yellow π₯΄ I thought it failed on an update. It was probably just taking a longer time than I had patiences for. I hard rebooted, then couldn't get it to boot, then reloaded HA from a USB thumb drive, now it will only boot from USB. π€
Does the Yellow have an internet connection during the installation process?
So you mean, you cut Yellow's power to reboot it?
I did π
then it wouldn't start up so I figured I botched the update in the middle so I'd have to do a whole fresh install.
And you wiped the old installation before?
I got it to boot from a USB stick, but now it only boots from a USB stick. If it take it out... no go.
no. I was just doing an HA update, but it seemed to be hung up.
And you tried to reinstall HA with the Installer USB method, right?
Yes it has connection
In that case, I'd go with method 2.
https://yellow.home-assistant.io/guides/reinstall-os/
Looks like the installer is not working with the cm4 lite
Have all previously existing partitions on the SSD been removed before and what exact SSD are you using?
I now downloaded the yellow image flashed it with a USB adapter to the SSD now it's booting
You need to update the eeprom. I have a CM4 Lite, updating it enabled me to do a USB -> SSD install just like the official instructions
Some people have run into issues with device functionality doing this, ymmv
are we sure those people arent putting the installer image on their ssd instead of the yellow image, or that the underlaying issue is needing to update the eeprom to boot from nvme?
The installer image on SSD would work too (at least for the CM4 lite). In fact it is one method mentioned in the documentation.
hm, i think that was one of the things i had fail when just playing with using the rpiboot -d mass-storage-gadget instead of usb nvme adapter.
just kept booting back into the installer iirc
I had the installer flashed to the eMMC. That was replaced by HAOS as expected.
But CM4 lites seem to have their own mind π
Best result was putting rpi4 image on it - seemed to be totally non-responsive (will not comment on that being a deliberate test or not:)
I hope the Bluetooth problem in HAOS 10.x will be identified soon.
is there a way to get 2 HOA yellow's to sync? like if i put one on one side of the house and one on the other. just for redundancy and coverage; mostly for redundancy.
You could try externally hosting a mariaDB or running cephfs, but TBH its overkill and probably more trouble than its worth, or constantly run rsync.
How to update the eeprom
I canβt find any about reset HA Yellow to Factory Default with installed SSD.
The problem is, I canβt reset Yellow to Factory Default with installed SSD.
I use this process:
Can I factory reset the system?
Yes: Remove power from your system, reapply power, press and hold the red button within 5 seconds. Keep the red button pressed until the yellow led starts to flash.
The Yellow now clears the data partition, which includes Home Assistant Core, the Supervisor, and any installed add-ons. Make sure that Internet connection is present at this point - the Home Assistant Operating System needs to download the Home Assistant Supervisor and Core after the data partition has been cleared. Due to the downloads, it can take a while until Home Assistant becomes accessible again.
But every time I go through these steps, HA Yellow starts with all the data and not from scratch.
I hope someone can help me
Hello everyone, I'm hoping someone can help me, I have the home assistant hello POE version but am unable to make progress because I cannot find a Raspberry Pi Compute Module 4. To complete the kit. Please can someone help with finding the right board for this. I would prefer it to have WiFi but accept that beggars can't be choosers...
I don't really know what board to get either, storage and memory etc
honestly I would hold out for the real thing, supplies should pick up soon(tm). digikey have in february and april shipped the last of my backordered CM4s so I'm inclined to believe the pi foundation saying https://www.raspberrypi.com/news/supply-chain-update-its-good-news/
(or go for a non-yellow solution on any old available single board computer, thin client etc)
@opaque summit There are issues: step 2 install the yellow installer on the emmc. But the cm4 lite doesn't have. And is this available for an Mac? Doesn't have a windows pc
Open the procedure How to re-install the operating system.
Follow steps 1β7 of the section Reinstall Home Assistant OS using rpiboot.
That just talks about setting the jumper to enable rpiboot working - no mention of installing anything to emmc or otherwise. There is also a link to getting rpiboot "from source code"
On the otherhand I dont think the cm4 firmware is the issue because the installer is booting fine from the usb stick. But not starting the installation or not?
https://github.com/raspberrypi/usbboot has the instuctions for getting rpiboot and https://github.com/raspberrypi/usbboot/tree/master/recovery has the instructions for running the command
Thanks, I'll keep an eye out and wait.
also the leds don't indicates a eeprom issue
I didnt follow the diagnostics, just assumed they meant to update to enable nvme booting; the page is a bit missleading with respect to updates but the steps are the same for restoring a bad eeprom or updating it
What I have not tested now, if the ssd has the correct partition shematic, maybe then it is working
because if I install it via usb on the ssd it is working. so the cm4 module support booting from ssd
i would set up rpiboot, update the eeprom, then again use rpiboot -d mass-storage-gadget followed by using the pi imager to write the yellow image directly to the nvme drive (rules out partitioning, and if pi imager cant find the nvme its probably not supported).
grab haos_yellow-n.n.img.xz from
https://github.com/home-assistant/operating-system/releases/latest
huh, if its working whats the issue?
Aiyahhh said above that my installation method could cause issues.
and I want to report that the method which is discribed in the official documentation is not working with the POE and CM4 LITE
some have trouble with the installer not updating the eeprom automatically as inteded afaik, but if it works it works
If itβs working for you, then just stick with it. However, updating the eeprom is still worth doing to prevent future headaches. The main issue Iβve seen people have when installing the way you did is the radios not behaving properly
The classic? Using the RPi4 image? 
Oh. They kind of took my template switches for Yellow's LEDs and put them in the HA 2023.5 release π
Maybe you should do one for the internal temp sensor so they can add that as well:P
Processor temperature is already added via the Systemmonitor integration. But they could add the visualization to the System menu. π
Looking for some help with installing OS for my Yellow. I installed the installer to a USB drive with the pi imager. When I have it plugged into the Yellow the yellow & green LEDs never stop flashing. At http://homeassistant.local:8123/ I can see the "Preparing Home Assistant" screen but that never goes away. Any ideas?
If you get the "Preparing Home Assistant" screen, the OS is already installed and the USB stick isn't needed anymore.
Yeah, it's unplugged and I power cycled the device
It's been on the "preparing" screen for like a day
hmm
[supervisor.jobs] 'Updater.fetch_data' blocked from execution, no supervisor internet connection
22-03-11 02:39:53 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
strange bc I see ethernet lights
Do you have any special network configuration? DNS or the like?
I don't think so. It's plugged into a router which is acting as an access point to another router, but I don't think that's the issue
For most who run routers plugged into other routers, that is often an issue
hmm okay, let me try plugging it in elsewhere
Unrelated to the ongoing 10.0/10.1 bluetooth issues, has anyone tried switching their CM4 in the Yellow to use the external antenna connector for Bluetooth? Generally that is done by setting dtparam=ant2 in /boot/config.txt, but I'm, not sure if I can edit that file in HA OS without it getting blown away. Anyone know if I can just follow the normal directions (https://www.jeffgeerling.com/blog/2022/enable-external-antenna-connector-on-raspberry-pi-compute-module-4) for enabling the external antenna on the CM4 or if HA requires a different approach?
simplest might be the serial console, but mind you the file is under /mnt/boot/ and you probably have to edit it with vi /mnt/boot/config.txt.
Yeah, editing it isn't an issue -- I have serial access access. More, I wasn't sure if edits made to /mnt/boot persist, or if they get overwritten on updates, etc.
I would think its persistent; updates so far havent touched my config.txt - caveat is that its also not included in backups afaik.
Even the update with Homematic HAT overlay removal hasn't changed the config.txt and removed those options.
I guess there is no way to query a running yellow as of the state of JP1 - it only affects the usb mux?
How do I edit DNS servers for the OS? I tried ha dns options --servers dns://8.8.8.8 --servers dns://8.8.4.4 + ha dns restart but ha network info still shows the old server which I don't want
My OS is connected to the internet but not HA supervisor
@dusky hollow I converted your message into a file since it's above 15 lines :+1:
# ping google.com
google.com is alive!
It seems like the supervisor should have internet access:
# docker exec -it hassio_supervisor bash
bash-5.1# ping google.com
PING google.com (142.251.16.138): 56 data bytes
64 bytes from 142.251.16.138: seq=0 ttl=104 time=29.898 ms
# curl --insecure https://version.home-assistant.io/online.txt
NetworkManager is online
# docker exec -it hassio_supervisor bash
bash-5.1# curl --insecure https://version.home-assistant.io/online.txt
NetworkManager is online
still supervisor_internet: false
Maybe ha dns options --servers dns://8.8.8.8 --servers dns://8.8.4.4 --fallback false helps
nothing. I also have tried changing DNS on the host itself using ha network update which seems to not work. I gave it new DNS servers to use but the result is always []. I edited using nmcli let me see what rebooting does
The option --fallback false should remove the fallback DNS setting
network time sync failed again which isn't a great sign I guess
okay the nameserver got updated but same issue with eth0 connected: true but supervisor_internet: false
Weired
Just a heads up for anyone waiting for an order from CrowdSupply: I ordered 24-Feb (est. ship date mid-March), and when I recently logged in to CrowdSupply to look at the status of my order, it turns out they had secretly cancelled the order and placed a new order with an estimated ship date of 30-Jun (!).
Check your order status if you are waiting on CrowdSupply!
I finally have supervisor_internet: true after setting my router to force time.google.com as NTP server
So it was literally a matter of time 
Any fix for "Failed to start Bluetooth: [org.bluez.Error.InProgress] Operation already in progress" on the yellow? I can fix it temporarily, but the problem returns after a reboot.
Known issue in HAOS 10 and 10.1.
https://github.com/home-assistant/operating-system/issues/2485
HAOS 9.5 seems to work more reliable with host's Bluetooth.
You can downgrade the OS with the following command in a terminal:
ha os update --version 9.5
Heya. Is there any way to connect to the Yellow Installer to see what it's doing? Installing for the first time (fresh CM4) on the PoE kit, and the LED patterns don't reflect anything in the online guide.
The yellow LED is blinking about twice a second, like the installer is booting, but the green one still flashes once every two seconds, red is solid. I'm pretty sure it's booted into the installer at least, as it's gotten an IP with DHCP, and the router gave it a hostname yellow-installer.
I'm a doofus, I plugged it into a restricted IoT port that didn't have Internet access
You can connect your Yellow to your PC via the serial console and get the output:
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
Oooh, that'll be super helpful if I have another hiccup. Thank you!
@hallow sigil yeah same issue I reported earlier. I installed hassos with the piimager directly on the SSD. The installer is not working unfortunately
@vestal quarry The installer seems fine in my case - my issue was that the installer couldn't reach the internet (due firewall config). Fixed firewall rules to allow that port through and it installed
For some reason even the haos image (not the installer) need internet access on first boot. Feels a bit counter intuitive
it downloads lots of packages
i get that its downloading packages (or containers), I just dont get why they're not part of the image. then again its not every day I deploy that image several times on the worlds slowest internet connection, just bugged me that one day.
I don't know how it's decided what's initially included vs. what's downloaded later as integrations are loaded
ideally packages are downloaded that meet requirement specifications, providing some flexibility
but it's also less than a minute for me on my i5 SFF machine
I seem to be having an issue with my HA Yellow where it periodically reboots to the wrong boot slot, and thus loads 10.0 instead of 10.1. Anyone seen that before? Or maybe this isn't #yellow-archived specific (in which case I can take this to #general-archived).
Hi I have a problem with my yellow, which I posted in the matter channel. Does anybody have a solution to this? #matter-archived message
I suppose, I have to swap my NVMe.
If I put in a new empty NVMe, will that trigger a new onboarding on the eMMC and I can move the data disk later, do I have to do a factory reset (red button) or even a wipe with a new OS installation (red+blue button) ?
@wary pivot you were using "move data"?
If so, when you remove the NVMe, it's as though you have deleted the config directory, and should then get new onboarding via eMMC
If the hassos-data partition disappears, we wait for 90s or so (it could appear later, e.g. slow USB disk), if it doesn't appear we drop into an emergency console
I don't think that the red+blue button or any other recovery mode gets you into on-boarding mode
But we could add that π€
The problem is, we need to detect which sistuation you are in, and be careful to not end up with two data disks π°
Sorry: red+blue clears the boot flow, so you'll have to use the Yellow Installer again. That will work π
Just red won't work, as it tries to clear the hassos-data partition, which isn't around.
Ok. So I have to kill it with fire. π€£
My Yellow is crashing way too often due to filesystem/drive issues. So my quick and dirty fix will be to replace the NVMe - just to be safe.
So it no longer falls back to eMMC?
On boot level it does. But the problem is once HAOS booted, it won't find the data disk (since presumably that was on the NVMe).
@shut cedar Another NVMe related question. Would a NVMe with internal DRAM Cache (like the Samsung 970 Evo Plus) have a reliability advantage (especially concerning my filesystem error issue) over one without internal DRAM Cache, but using Host Memory Buffer (like the Samsung 980)?
I factory reset my Home Assistant Yellow, but now it won't log into Nabu Casa. I've set a static IP on IPv4 and disabled IPv6, and it's still not working. When I try to log into Nabu Casa I get the error message "Unable to reach the Home Assistant cloud". According to the troubleshooting I could find on Nabu Casa, the solution is to disable IPv6 and reboot (not restart). Which I've done.
Is your router correctly set as gateway in your static IPv4 configuration? And isn't the static IP used by any other device?
The static IP isn't used by anything else. When I try to add anything to the IPv4 settings (like DNS), it just says "failed to save, check logs", but there's nothing in the logs. I'm rebooting right now, when it's back up, I will check to confirm that the router is set as my gateway.
@wary pivot I think you got it! I removed the default and put in my router IP as my gateway, and I'm able (at the moment, fingers crossed) able to download some integrations and add ons and log into Nabu Casa π Thank you!
I'm at my wits end with home assistant....my cpu since update sits at 30 percent cpu load and goes down. To 8 percent when i disable the Alexa media player integration
I'm using home assistant yellow and before this new update everything worked fine
I will litteraly do anything to have it work lol .
Have you checked the breaking changes?
https://www.home-assistant.io/blog/2023/05/03/release-20235/#breaking-changes
I have nothing mentioned high CPU usage or Alexa media player
Unfortunately I don't own a Yellow yet so I don't have any insight into your issue...
I think a lot of ppl on here are asleep atm, you might have better luck asking again in several hours...
@dusky hollow just a thought, have you checked your memory and storage?
I have no high CPU usage, even with Alexa Media Player. The only culprits for high CPU usage in my setup are the add-ons for Multiprotocol or OpenThread. Those tend to spike to high CPU usages and don't drop back down.
Oh hey, my CPU usage is also high and the green LED is blinking a damn lot.
30ish% CPU for doing relatively little.
mdnsd is going haywire.
hey all, I just got my yellow (rev1.2) and CM4 (4GB RAM 32GB eMMC) last night, ran through the steps outlined here: https://yellow.home-assistant.io/power-supply/#connecting-the-ethernet-cable
but never got past the boot heartbeat pattern so I tried wiping and running through option 2 here: https://yellow.home-assistant.io/guides/reinstall-os/
All those steps worked like described, went back to the first guide (skipping the USB drive steps) and I still stuck on the heartbeat pattern. Anything I'm missing?
I have a similar problem with the yellow rev 1.2 and CM4 (8GB Ram, 32GB eMMC). I am also stucked at the boot heart beat pattern. The uart showed βvc4-drm gpu: [drm] Cannot find any crtc or sizesβ and shot time later βcam-dummy-reg: disablingβ
for this pastbin yes
but i also tried flashing the installer directly to the emmc, which was the same result
what image did you choose to flash
home assistant os installer for yellow from the imager
making sure it wasn't rpi4 because it looks like hardware errors there
i also tried haos_yellow-10.1.img.xz, haos_yellow-9.4.img.xz, haos_yellow-8.5.img.xz but it didn't work in the end for all trys
did you possibly choose the wrong one when flashing directly?
I don't think so. I have now deleted the emmc with the raspberry pi imager, then i reinstalled the raspberry pi eeprom using rpiboot.exe -d recovery, installed the "home assistant os installer" to the emmc. And this is the result: https://pastebin.com/a9wQHnPn
And then i also installed haos_yellow-10.1.img.xz from https://github.com/home-assistant/operating-system/releases and this is the result: https://pastebin.com/ZjdWFZth this time i can login but there is a network issue ... eth0 is unavailable
i can connect the wifi with this installation method but eth0 doesnt work
nmcli dev status
DEVICE TYPE STATE CONNECTION
wlan0 wifi connected maja
p2p-dev-wlan0 wifi-p2p disconnected --
eth0 ethernet unavailable --
docker0 bridge unmanaged --
hassio bridge unmanaged --
veth471469c ethernet unmanaged --
veth48c8ec0 ethernet unmanaged --
veth4ecda7c ethernet unmanaged --
veth8f15c63 ethernet unmanaged --
vethd94a0b7 ethernet unmanaged --
vethe000f65 ethernet unmanaged --
lo loopback unmanaged --
id:browse
so instead of flashing Home Assistant OS Installer for Yellow, I just used Home Assistant OS 10.1 which does appear to be running. Will something not work correctly with this setup?
It depends on the HAOS image you used. If you used the RPi4 image, Zigbee won't be working for example. If you used the HAOS for Yellow, you are fine.
If in Settings-System-Hardware Home Assistant Yellow isn't explicitly stated - it was the wrong one.
hmm yeah that's what I was afraid of, just can't seem to get yellow to spin up
Try this image: And then i also installed haos_yellow-10.1.img.xz from https://github.com/home-assistant/operating-system/releases and this is the result: https://pastebin.com/ZjdWFZth this time i can login but there is a network issue ... eth0 is unavailable
This one works for me except the ethernet problem.
Is the network port of your router/switch active or has it been disabled? Have you tried another Ethernet cable?
I have tried different cables an even a different router but the led on the yellow doesnβt blink. I also dis and remounted the cm4 but nothing helped.
The only thing in havenβt tried is a crossover cable
sweet @hollow ginkgo installing the image directly above appears to be working for me. ty!
also ty @wary pivot can confirm the Hardware is showing HA yellow
All these people having to direct installs is pretty concerning, I wonder why itβs been so inconsistent
I think for me the installer doesnβt work because it needs the internet connection and eth0 doesnβt work.
Have you tried a usb Ethernet adapter?
No I would have to buy one for that test. Since thereβs one on the board I expected it to work. And with direkt install i can connect wifi and it runs at least.
In my opinion the installer should have some sort of backup for cases where the internet connection doesnβt work. Updates can be loaded afterwards if the connection is there.
@hollow ginkgo If the onboard ethernet port seems to be defective, contact the support at yellow@home-assistant.io
(I just posted this in #developersm sorry to cross-post, it didn't occur to me to post here)
FYI I updated to the latest core, it killed my Home Assistant Yellow. One time I rebooted it and got into Safe Mode, tried to recover a partial backup, it just sat broken for hours, I just got a reinstall going, I'm setting it back up. Just thought I'd tell someone.
Did you reboot by software or did you powercycle it? If a NVMe goes offline due to errors, it only reappears after a powercycle.
powercycle as it was non responsive on the network.
I've since re-installed and reset it up
I'm finally setting up my Yellow. last night I got it going and did "Restore Backup" and it never came back up -- at least not on port 8123. I just reinstalled, logged in, moved data disk to the NVMe, and now I'm trying a restore backup again. the backup file is over 1GB so I'll give it at least an hour. this time I have USB serial console going so I can get more info
argh.. unrelated to my issue, but I just realized this CM4 only has 2GB RAM. that's not ideal
oh hey it's up this time. guess I didn't need help after all π hope everyone is having a great day!
Restoring a big backup with many add-ons needs a lot of time.
the first time around I gave it 8 hours and it still wasn't responding -- but I forgot to migrate to the NVMe, so maybe it was taking forever to restore onto the eMMC
Hello, does anyone know how to turn off poe? All my ports come with poe and I don't want to use it.
You have to turn it off on your switch/router. But if you plug in a power supply in the Yellow it takes that instead of the PoE.
Peace on Earth. Purity of Essence. Power over Ethernet.
Pajamas on Elephants
And now there is an elephant in the room - well done cogneato
it takes that instead of the PoE
What a slut
Hello, does anyone know where I can buy Home Assistant Yellow in the US? I am checking online here: https://www.crowdsupply.com/nabu-casa/home-assistant-yellow#products and it seems they only have hte kits that require me to install raspberry pi. I just want an out of the box solution. any tips?
The US distributor is CrowdSupply. The EU distributor raspberrypi.dk is more reliable, but I suppose it would be more expensive to buy there.
yes but crowdsupply doesnt offer the full home assistant yellow. it only has the kits available where I have to provide the CM4
The version with CM4 isn't available at moment - still a CM4 shortage
ahh i see ty. happen to know what general time range for them to be available?
No idea. I was lucky to get a CM4 myself.
guess i gotta be patient
Best bet is to order a Yellow Kit from raspberrypi.dk (assuming they still have them in stock) and then hunt for a CM4 separately. Crowdsupply's latest estimate was end of June before they even have the kits available again, let alone anything with a CM4. You can follow https://rpilocator.com/ for info on CM4 availability -- they have them come up every few days right now, although they generally sell out in under an hour each time.
this was very helpful ty
Using Bluetooth on the CM4 in my Yellow. Just recently it's started throwing these errors and all Bluetooth devices become unavailable in the front end. Would appreciate any advice on fixing it please?
`Logger: bluetooth_auto_recovery.recover
Source: components/bluetooth/util.py:78
First occurred: 09:07:07 (2284 occurrences)
Last logged: 18:38:09
Bluetooth adapter hci0 [mac-address] could not be reset due to timeout after 5 seconds`
@shy saffron I converted your message into a file since it's above 15 lines :+1:
I tried to enable the Bluetooth signal strength entity on a Switchbot thermometer. After seeing the error I disabled the entity again. A restart clears the issue for a while.
I suppose it is related to this issue:
https://github.com/home-assistant/operating-system/issues/2485
The "fix" for me was the transition to a M5Stack Atom Lite (not the S3) as ESPHome BT proxy.
Hi Folks, can I install and configure my new Yellow in a local network (LAN) that already has a production HA-Server running, without any interference or unexpected - or perhaps even worse; Fighting over who's is control of what?
At first the mDNS name homeassistant.local will make problems/won't work. You have to use the IP address and rename one instance in Settings - System - Network - Hostname. After that you are good to go.
hello im trying to setup zigbee2mqtt, and i keep getting Error: {"sequence":-1} any advice ? this is also my current config https://imgur.com/mVuDStG
rtscts should be true.
Is ZHA disabled or ignored?
There is no setting named Hostname in there - only two URL's; Internet and Local Network (IP)
Nope - this is what mine looks like:
https://i.imgur.com/IIr1tkg.png
In that case I'd recommend to reboot the host
By 'The Host' - do you mean HA restart ? or rebooting the machine where HA is hosted (along with several other VM's and containers) ?
You aren't talking about the Yellow? If you are talking about a VM, reboot the HA VM (not just a restart) - if you are running HAOS in a VM.
Correct, my Yellow is still in the box (hasn't even been opened yet) so I'm not talking about Yellow, but my currently running HA production server which runs in a docker container (not HAOS).
Mybe I should rephrase my OP: I plan to unwrap my new Yellow and begin playing with it. Can I safely hook it up to my exiting LAN without causing havok for my production server?
I'm not familiar with a Docker HA Core installation and how the host name management is handled there.
Everything depending on the DNS resolution of homeassistent.local might have problems. (2 instances with the same name)
But I'd not expect havok. I have used a second instance for testing stuff without problems. I just renamed one to be able to use domain names.
Well, as far as I know there is no DNS service running anywhere in my LAN (which most common for LANs). Only NetBIOS names are used. And since there's no place to name or change the host in HA - the I think we're on a wrong track.
My understanding is that there are quite a few thousand Yellows shipped by now, so I can't possibly be the first one hesitating to blindly throwing a new HA server online. (It could end up like locking two cats into the same room - they might end up killing each other) π€£
Strange that NabuCase never mentioned any such precautions in their setup guide (?) I guess most people moving to Yellow is moving away from something already running. To mee, my concern seems logical.
Yeah. I suppose, they expect the new users to have shut down the old instance and to spin the Yellow up afterwards to restore a backup π€·
Settings -> System -> Network for changing the host name. You don't need a service running for mDNS (usually .local).
For HAOS of course. You probably need to do it on the host system, outside HA, for anything else
In case anyone was wondering about NVME heatsinks fitting in the case, I just slapped one on because I couldnβt figure out how to disable the LED on my SSD lol https://i.imgur.com/s1uuJVU.jpg
Thereβs juuuuust enough clearance under the heat sink that the z-wave module doesnβt touch, but Iβm tempted to find something even more low profile
Ping homeassistant.local just gives an error, so clearly that hostname doesn't exist in my LAN.
Hi all - received my kit yesterday and assembled it with my SSD. Unfortunately I was sent the wrong ssd disk and need to buy a new one.
Anyone know if this model will work with the latest revision of the kit? https://www.webhallen.com/se/product/327389-Seagate-Barracuda-Q5-QLC-SSD-500GB-NVMe (Seagate Barracuda Q5 QLC SSD 500GB NVMe
M.2 2280 / 500 GB / PCI Express 3.0 x4 (NVMe) / 2300 ) Iβm using a CM4 lite
We haven't got any reports about Seagate Barracuda NVMes here. Neither reported working, nor not working.
Ok, thanks!
Follow up question, heard anything regarding this one? Kingston NV2 M.2 500GB
M.2 2280 / 500 GB / PCI Express 4.0 x4 (NVMe) / 3500
Some planned to buy one. But no feedback yet, if they have been successful.
I bought this one and it is working Crucial P3 1TB PCIe Gen3 3D NAND NVMe M.2 SSD, up to 3500MB/s - CT1000P3SSD8
The cheapest one Iβve seen (and successfully tested) is the Silicon Power P34A60 512GB
M5 stack PoESP32 with antenna is by far the best performer I've tried for bluetooth_proxy:
I was looking into that too. But for me the WiFi version was a better fit.
I bought the "Kingston NV2 M.2 500GB M.2 2280 / 500 GB / PCI Express 4.0 x4 (NVMe) / 3500" and can verify that it works π
I would like ethernet rather than WiFi but PoE (inc. injectors) is impractical where I am looking to locate the ESP. Do any of the M5 ESP32s support ethernet and PSU?
getting a little OT here, but I cant see why you cant use the PoESP32 and feed it 5v to the 4-pin HY 2.00mm header, other than that Im not very familiar with the m5 stuff
edit: oh, they have a dedicated barrel jack to hy2.0 dc/dc converter!
Apologies. Just read about the HY2.0-4P interface 5V DC power supply option. Thank you.
I finally got my hands on a CM4 for getting started with the Yellow and just clicked restore back-up on the onboarding screen. However, even after a bit of time (10 minutes) the Yellow just sits there blinking (hearbeat yellow led, rapid blinking green led). And is no longer responding on the network. Is this expected behaviour?
Edit: 15:05 It has now been 30 minutes of non-availability.
Edit: 15:07 And, it is online. 30 minutes is a normal time it appears.
Just bought a Yellow with a cm 4 lite, with a 256GB m.2 ssd. I flashed a usb with OS according to instructions. Followed the instructions when starting up. The red is on and the green flashes as indicated activity, the yellow flashes with heartbeats for approx. 30 sec then solid yellow for 3 sec. but then it stops. Nothing happens
Can somebody help me in the right direction to solve this?
I signed up to like 5 stock notification lists for an 8GB one since the 2GB is very, very paltry
Does it start without the USB stick now?
No, with the USB in the green flashes every second and solid red light, but the LAN port indicates traffic (green fixed and flickering yellow). Without the USB the green and red is fixed. The JP1 jumper (USB - URAT is in UART), both lights on the ssd is fixed.... The LAN yellow indicates traffic (flickering)............
Are you sure the drive is sat correctly?
Presumably you saw https://yellow.home-assistant.io/guides/yellow-leds/
The green flashes might be an error code
Yes, but the green is. fixed, no flash
and the UI doesn't come up?
The messages on the serial console might give a hint.
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
No... It gets and ip adress, and on the router I can see yellow-installer
Will have a go Thanks
Sounds like incompatible SSD. This basically describes my initial experience, down to the installer getting an IP address
What I have is a 128 and 250 GB Intenso m.2 SSD TOP . came up as a suggestion when I bought the Yellow at Raspberrypi.dk....
All Intenso SSDs at raspberrypi.dk are SATA m.2 SSDs - and those aren't compatible with Yellow. You need to use a NVMe SSD.
Thanks! Then the question is why I comes up as a suggestion π£ Found this one in the thread and will test it .. https://shorturl.at/jmSY8
I checked their website. For me they just suggest Samsung 970 EVO Plus NVMes with the Yellow. They offer that Intenso SSD and a MicroSD with HA preinstalled. But I suspect those to be for RPi4 and x86 hosts.
Saw that to, maybe a mishap. I ordered what they suggested - I am quite incompetent on this area ....
A Samsung 970 EVO Plus is a safe call. Crucial ones might work, but some have been reported to be incompatible.
Thanks!! ordered a Samsung. delivered tomorrow.
Samsungs are complete overkill lol but enjoy
You couldβve spent β¬20 or less on a Silicon Power SSD π€·π»ββοΈ
Hi all, first time poster, anyone can help me with the yellow install? i'm stuck at the heartbeat D6 led and no activity is going on
i did get caught out by the SATA from raspberrypi.dk but i swapped it out for and NVMe one, but after that i still can't get the install going, is it maybe because i have a CM4 lite (no emmc)? i tried to install directly to the SSD but the D6 led never got to solid so i can't press the blue button to bypass the emmc.
On a CM4 lite the eMMC does not need to be bypassed.
that's the first thing i did, not bypass it, but it didn't do anything so thought i'd try it anyway lol
Some older CM4 lites need their EEPROM to be updated manually π€
https://yellow.home-assistant.io/guides/flash-cm4-firmware/
I just bought it but it wonβt hurt trying it too, Iβll do that when I get home, thanks for your help Jorg
i did get caught out by the SATA from raspberrypi.dk
@warped palm I didn't realize that was happening.
Did you download and flash the Yellow image to the new SSD from https://github.com/home-assistant/operating-system/releases/tag/10.1 ?
@compact quartz I havenβt tried that, any guide on how to flash directly to the ssd?
Using etcher and an adapter for instance with another PC altogether. Not likely to have an nvme adapter, I realize
haha yeah sorry i don't have an nvme adapter :/
So the LED keeps heartbeating? That likely points to a Internet issue, no connectivity/no DNS
it's not an internet issue, i've swapped the cable through all my LAN ports on the router and it's the same issue each time, but the other things on the other LAN ports are working fine... maybe i should try another ethernet cable instead of the one that came with it lol
I just bought one on amazon, it'll be here tomorrow so hopefully I'll be able to do that then π
you can try rpiboot -d mass-storage-gadget and use the yellow as nvme adapter, then image it with rpi imager
(edit: do steps 1-7 from https://yellow.home-assistant.io/guides/reinstall-os/#install-os-rpiboot first)
edit: and use haos_yellow-n.n.img.xz from
https://github.com/home-assistant/operating-system/releases/latest when flashing.
thanks for the tip, i'll try that when i get home
Another cable is unlikely to help. The LED turn solid as soon as the bootup completed, which happens once NetworkManager deems the system online. The installer uses DHCP DNS by default, and Cloudflare 1.1.1.1 as fallback. For some reason, it seems that the NetworkManager can't connect to the Internet, hence doesn't deem the system fully up.
It could be a firewall or the ISP blocking certain requests, not sure
You can see what the system is doing on the serial console, see:
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
It would be interessting for me to know what exact issue the Yellow Installer has in your environment. As we have 100s of successful installs, but every now and then some weird environment appears which seems to trip the system.
It worked perfectly, Thanks!
I tried to get it from putty on windows and homebrew on mac, but neither are giving me a port to connect to on putty and logs for booting
my terminal doesn't recognize rpiboot even though i installed it earlier, i tried to connect the yellow directly to as a USB, but the laptop still doesn't recognize it π¦
Hm, is JP2 set to UART?
i tried both UART and USB
doesnt recognize the command or just stuck at Waiting for BCM2835/6/7/2711... ?
says 'command not found: rpiboot"
okay, thats just a path issue then, you need to navigate to wheverever you installed it
i just ran the rpiboot again on a windows laptop , did all the steps perfectly but the green light that should be on is still not on, despite the device manager recognizing my BCM2711 as a USB device, so at least the driver is correct
the yellow presented the nvme drive as a mass storage driver that pri imager was able to write haos_yellow-n.n.img.xz from
https://github.com/home-assistant/operating-system/releases/latest ?
if so you either have a boot or network issue, connecting to the serial console after writing the image could be useful.
(https://yellow.home-assistant.io/documentation/ has links for the serial console on different client os)
has to be boot issue, i can't even get to the serial console, maybe a dud cm4 lite? ever happened?
if rpiboot conencts and works its at least partially working; double check its seated properly?
also jumpers need to be returned for serial to work in case you forgot that?
yep, checked the jp1 (no jp2 on mine), i'm getting tired, it's getting late here and i have an early start and haven't had dinner yet, maybe i should have just kept my HA on my laptop and gotten the yellow lol
sorry for the language but FUCK ME!! I couldn't get to sleep so i went back and tried a few things and then just to make sure and be thorough, i took the heat sink off to make sure the CM4 was properly in place and despite having screwed all 4 screws into place, i still heard a click... meant it wasn't all in!! please don't be mad, i'm already mad enough at myself for all of us. I'm usually quite good at physical tech but i should slap myself in the face a few more times for this stupid oversight!! I wanted to thank you all but especially @opaque summit and @shut cedar for the time you took to try and troubleshoot me.
Those things can happen. I'm glad you got it working in the end.
thanks Jorg π
The CM4 requires a concerning degree of force to click it into place correctly
I was worried it was going to break, or Iβd snap the yellow board.
That's all hardware in my experience
"carefully insert the RAM"
leans on it with full body weight until it CLICKs
If the force is applied directly above the connectors it isn't too bad. The problem is that the Yellow PCB bends, so I recommend taking it in your hands:
https://yellow.home-assistant.io/power-supply/#installing-the-cm4
glad i wasn't the only one worried about that π
I did take the board with my hands to ensure it went in properly and i put in the screws as well thinking that would ensure the CM4 was properly installed... boy was I wrong lol i guess i missed the full click
I wasn't able to fully insert CM4 module upon my first attempt, I guess the guide can be revised to warning first time users. Your CM4 should make direct contact with screw bases instead of floating above it. It is easy to miss because official guide only asked you to install heatsink for CM4 not screws.
I was trying to move my POE yellow to a different location than current one to avoid signal interference however the new location doesn't provide UPS to POE devices, I wonder if it would be possible to install 18650 batteries power management board to Yellow in order to use it as backup? If it is, how can I achieve it? Any guidance appreciated.
I'm also trying to give it cellular backup with a native Raspberry Pi solution if possible, preferred SixFab 4G/LTE because there seemed to be cheap used ones for sale everywhere, currently mine relying on dual WAN setup on parent router, better than nothing.
That one seems to need too many GPIO pins
so I recommend taking it in your hands
Be gentle, it's my first time
Hi I just got a new yellow pcb and installed my cm4 but when I power it up with a flash drive having the boot os the yellow light never turns on. Only the red remains constant and the green blinks erratically. I am trying to diagnose what my issue could be? Is it a problem with my cm4?
Any help or guidance here is deeply appreciated
I have 4 hue gu10 lights that are on a regular switch, when i go though the really annoying pain to reset them and add them back to Z2M they work fine, but a day after that i cant access 3 of the 4 lights within z2m, any ideas ?
Hi I just got a new yellow pcb and
Dumb question which I'm sure he been answered before. It's there any point to me using a sky connect on a yellow? I bought a bundle that came with both not thinking anything of it and then after reading more saw that the sky connect may have been redundant. I can repurpose it at a different location if thats the case.
Well... it depends. The radio of both can serve Zigbee and Thread simultanously. If I remember correctly, it uses the same channel for both. When Yellow and SkyConnect are both used, each radio can specifically serve Zigbee or Thread and use seperate channels. I'm not sure, if seperate radios would increase the capacities of each network.
hi
Hi everyone I need help with installation π
I'm following instructions here: https://yellow.home-assistant.io/power-supply
I have done the following already:
- mounted a CM4 on the yellow
- put the HA installer on a USB from Pi Imager
- sticked the USB in the yellow
- plugged ethernet cable
- plugged power
I am now expecting the yellow LED to flash in a heartbeat pattern but it's not turning on π’ Only the green and red LEDs turn and stay on...
(this is step 10)
Does anyone know what's wrong?
What CM4 model are you using and are you using a SSD. If yes, which one?
@wary pivot I'm not really sure where to see which model it is. And no I'm not using a SSD
The CM4 packaging has a sticker with the model number (e.g. CM4108032)
@wary pivot CM4002016
What kind of USB flash drive is it? Not using the USB C port, right?
@humble magnet
When you mounted the CM4 in the sockets, has it been noticeably clicking?
It was stable enough for me to think it was correctly mounted. Also the first time I mounted it, none of the LEDs turned ON. So when I read that it might have been because of the CM4 not being correctly mounted, I re-did that step and that's when I got the green end red LEDs to turn ON, so since then I assumed it was mounted correctly? @wary pivot
If you connect your Yellow to your PC via serial console, does it show error messages during booting from the USB stick?
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
I just connected my yellow to my mac and did the screen to its port with the USB stick in it. When I connected to power to boot the yellow, nothing appears and my terminal just remains black with the cursor in the top left corner @wary pivot
Okay. If you put the USB stick in your PC, is there anything on it?
Yes it's the HA installer files that pi imager put on it @wary pivot
The CM4 is new and hasn't been used before, right?
Well, the last one with a similar issue hadn't had the CM4 correctly seated. Any other ideas, @compact quartz ?
I assume it was new, this is where I found it: https://www.ebay.co.uk/itm/144978510300
@humble magnet jumpers are in default positions? You might try flashing the emmc directly using option 2 as described here: https://yellow.home-assistant.io/guides/reinstall-os/
additional info for use with MacOS https://www.jeffgeerling.com/blog/2020/flashing-raspberry-pi-compute-module-on-macos-usbboot
Very simply what will that do? @compact quartz ?
You would be connecting the board to your Mac and flash it directly (the emmc) with the pi imager instead of using the usb