I have ordered a kit with CM4 and nvme, following the instructions on https://yellow.home-assistant.io/power-supply-nvme/. I did install the CM4 (it did click-in), installed the pads and the heat sing, installed NVMe. Created USB flash drive, plugged in, plugged in the Ethernet cable, power, but it does not install, It gets stuck on the yellow LED hearbeat. I connected the USB cable to my computer and run screen. It seems to stop on Welcome to Buildroot
yellow-installer login:. This is the log. Any idea where is the problem? Thanks!
#yellow-archived
1 messages · Page 9 of 1
What NVMe are you using?
that's a Samsung one if it's from the Danish store
Yes, Europe 🙂
Some CM4 Lites seem to need a manual firmware update:
https://yellow.home-assistant.io/guides/flash-cm4-firmware/
ok, but i do not have windows
This would be a guide for MacOS:
https://www.jeffgeerling.com/blog/2020/flashing-raspberry-pi-compute-module-on-macos-usbboot
From the point rpiboot is installed, the HA guide applies again
What is the USB Slave Port Enable? Shall I move the jumper from UART to USB position?
JP1 jumper has to be in USB position and the SW3 button has to be pressed (or the JP2 jumper to be closed on older hardware revisions). Steps 1 to 7 have to be performed.
https://yellow.home-assistant.io/guides/reinstall-os/#install-os-rpiboot
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode4.bin
Sending bootcode.bin
Successful read 4 bytes
Waiting for BCM2835/6/7/2711...
Loading embedded: bootcode4.bin
Second stage boot server
Cannot open file config.txt
Cannot open file pieeprom.sig
Loading embedded: start4.elf
File read: start4.elf
Cannot open file fixup4.dat
Second stage boot server done```
It cannot open fixup4.dat
Have you pressed the SW3 button on powerup?
Okay. Continue the recovery. As no OS has been installed, those files aren't present on the CM4 (it is a Lite, so the confix.txt will never be on the CM4 🤔 )
Ok, done ./rpiboot -d recovery. What next? I am kind of lost in the instructions - one page refers to another, and they are generic, so most of them do not apply 😦
After a few minutes remove the power, set JP1 to UART and try again to install the OS with the USB installer.
I thought I'd open Raspberry Pi Imager and do it from there. But I do not see the RPi-MSD from there
Ok
If that fails, you can try to use option 2 of this guide:
https://yellow.home-assistant.io/guides/reinstall-os/#install-os-rpiboot
It did not work
I am running the Option 2
Got to point 8. (done it before, it shows Cannot open file fixup4.dat).
After this is finished, red and green LEDs are on
I go to Raspberry Pi imager, but I do not see the RPi-MSD storage
Does it show the NVMe as mass storage in your OS?
Do you have a NVMe to USB adapter? that way, you could flash the installer directly to the NVMe
No, I don't
Probably a dumb question but are you sure the NVMe is seated correctly?
I tried taking it out and put it back in. It is inserted fully and then pushed down and secured with the screw. So I guess it is.
and you put it in at a ~45° angle, then pushed it down?
Yes
And are you sure, it is a Samsung NVMe in your Yellow? 🤔
Ok, I hope you don't think I think you're an idiot or something, just wanted to be 100% sure
tracks with mine
Let me think. I have a Trebleet hub, that has a slot for SSD card. So if put it in there, I shoudl be able to install it from the installer like that. Would that work?
Propably
I'm harping on it but your NVMe doesn't look like it's seated in the lower bit of the screw. I doubt a millimeter would make a difference, though
CM4 Lites are a bit of a pain in the bottom.
It should be seated under the nut, or in the groove in the nut?
In the groove in the nut. The bigger ridge facing down.
I had one stuck with double-sided tape in a different thing for years with no problem
on the other hand, you can just swap them out without having to reinstall anything...
Ok, so I installed the installer for Yellow to the SSD, it boots, but I pretty much get to the same point. It shows Welcome to Buildroot, yellow-installer login: and it is stuck there.
Am I choosing the right image from the RPI Imager?
Other Specific Purpose/Home Assistant and Home Automation/Home Assistant/Home Assistant OS Installer for Yellow
Or shall I get Home Assistant OS 10.1 (RPPi 4/400)?
...on the SDD
No, "for Yellow" is right
The Installer image is the right one. Does the heartbeat LED start to flash?
someone else (unless this is you) has the same problem, but sadly, no replies: https://community.home-assistant.io/t/yellow-installation-fail/568325
No, it is not me
Is the installer using DNS servers it gets from DHCP? My ISP might block some DNS servers - there is nothing I can do about that. So I am thinking if you haven't hard-coded them?
It uses the DHCP DNS and if that fails, it tries 1.1.1.1
have you tried option 1 of reinstalling, with the USB stick?
Yes. And it is now installed on the SSD and it boots fine. It just does not instal. It gets stuck on the login:
also seeing
I had the same problem. What worked for me was to run rpiboot -d secure-boot-msd and then flash the eMMC with HA-yellow
When I type root and enter, it logs me in
does it show up on your router at this point? can you connect to homeassistant.local?
Can I start the instakll from there?
I think the install only starts when you start it from the web UI
Yes, it shows on the router/DHCP server
try going to http://<ip>:8123
Last thing you could try, is to flash HAOS to the NVMe. But it has to be the Yellow version - otherwise Zigbee won't work.
https://github.com/home-assistant/operating-system/releases/download/10.1/haos_yellow-10.1.img.xz
If that doesn't work, you should contact the support at yellow@home-assistant.io
@trail dirge That only works AFTER a successful installation - not with the installer running
the only thing I'm seeing is that the CM4 might be configured to boot off something else
what if you tried an earlier version of the OS?
That doesn't matter, as the OS is not installed yet.
And as the installer is running from NVMe, the boot order isn't the issue
Ok, will install the image directly
Important is to choose the Yellow image, not the RPi4 one.
Sorry, I meant an older installer image. Just to see what happens.
Ok, so installed that one. Now I can go to homeassistant.local:8123 and it show Preparing Home Assistant
Thanks for your help
The state it is right now, is it the same as if I'd get the "standard" option from the shop? Or would it have the installer on it?
As I understand it, the standard one has HA pre-installed
I've signed up for like 7 stock notifications for an 8GB CM4 though, 2GB is not enough to run ESPHome
the first thing would be getting a cm4😂
Raspberry Pi CEO confirms that it's products will be back in stock starting Q3.
unfortunately there will still be backlog to take into account, but hopefully still more to be found regardless
agreed, I'd really like a Pi Zero 2W
I've got a home assistant yellow, but don't have a CM4 yet - is there a recommended minimum model I should be looking to get?
Ah, found the FAQ entry
If possible, get more than 2GB of RAM.
Yeah, 2 is unfortunately paltry
I have an 8GB version though actual running is only around 1.3GB it will actually use closer to 6GB with Caching and Buffers
How can I use the line out (J5) on the Yellow? Things like tts.speak and media_player.play_media want a media player entity, and I don't have a media player entity that could feasibly point at that port.
The VLC add-on and integration can be used as a local media player. But I'm not sure, if TTS will work.
To be sure, you're referring to https://www.home-assistant.io/integrations/vlc correct? Also, when you say not sure if TTS will work, do you mean I'd need to test while monitoring the line out in case VLC wouldn't accept the stream, or do you mean it might not show up as an entity for TTS?
I mean the VLC add-on. When that one is up and running, the integration VLC media player via Telnet can connect HA to that add-on. But according to the documentation only the media type music is supported. The media browser shows TTS, even it should not be supported - but I haven't tried it yet.
The autodetected integration fails to connect, the add-on logs say no password is set, and manually configuring vlc-telnet requires a password. I don't see any way to set a password in the UI and the config section of DOCS.md for the add-on is blank. Any hints, or should I head over to #add-ons-archived ?
I would suggest to give the add-on some time to start, to restart HA and to try the autodiscovered integration again
I had previously tried changing things and restarting HA a couple times to no avail. Restarting the add-on without restarting HA and then configuring it via the new detection (previous detection was already gone from failure) after the logs showed telnet listening and before they started showing muticast info did the trick. Not sure if the multicast stuff the logs showed before restart was relevant to my issue or not, but I have the VLC-telnet entity now. Won't be in a position to test it for a while, but thanks for the help.
Hey, i thought its smooth to activate ZHA and use the Yellow Zigbee Moduel in parallel to my Z2M Integration with a Conbee 2 Stick to migrate one device after the other. But the Integration fails to start. I thought it should be possible as the internal Zigbee and the Conbee 2 are different radio types on different channels?
Sounds like something that might be better addressed in #zigbee-archived, probably not yellow specific.
I didn't test tts.speak, as I don't have a platform enabled for that, but I did test tts.reversotts_say, and it was able to speak using the local VLC-telnet entity.
Quick Q: has anyone repurposed the Yellow as a more general purpose Pi? (I know this defeats the core purpose, but...) If so, can you run Rasp OS Desktop with an external monitor, given there is no HDMI port?
If you solder on a HDMI port... But it wouldn't make much sense to do that, just to run Raspbian on it. With stock Raspbian you wouldn't be able to use the Zigbee radio and more. There are much more suitable hardware solutions for a Desktop.
Maybe use xrdp or vnc to remote into it?
If you’re trying to repurpose your yellow, just sell it and get another board. Guarantee it’ll sell on eBay, or to a community member
You’ll have an easier time with any of the various normal IO boards and probably make someone’s day by selling a hard to get item
What is the best way to get home assistant yellow in the Netherlands?
Graphed the HA Yellow RPi CPU temp with the top cover of the Yellow on vs off. Adding the cover increases the CPU temp by about 10 C. Still within the safe range, but makes me wonder if I should try to add additional vent holes. https://photos.app.goo.gl/FfJKvBrufximsEDt6
Has anybody got yellow and CM4 bundle here from Seeed Studio? https://www.seeedstudio.com/Home-Assistant-Yellow-Kit-with-selectable-CM4-p-5680.html
Hi. My Yellow appears to have stopped working at around 02:30/03:00 this morning. I wasn't able to connect to local or cloudflared URL, or via PuTTY, so I removed the PoE cable and plugged it back in again. Seems to back up again but how may I check what might have occurred? The logs for Core, Supervisor, etc. only seem to include information from after the reboot.
Seeed Studio is official distributor for Yellow in China. But I haven't seen any feedback here yet, if their perfomance is good or bad.
If you watch the boot process via the serial console, does it mention file system errors?
Thanks for the reply. Will give that a try if it does it again.
#NoteToSelf https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
I looked at the price, and Seeed actually offered the 8+32GB version of CM4 at the original price. That's very conscientious! It's a pity that they don't seem to sell CM4 separately, need to buy it together with yellow, it would be nice to know earlier.😂
Which CM4 would be the best for someone who wants to start with their HomeAssistant journey with a HomeAssistant Yellow? Right now I'd just have some Phillips Hue lights and a 3D Printer that I'd like to monitor using HomeAssistant if possible
Eventually I'd want to expand over time, but my wife and I will be doing apartment living for a few years.
if you're planning to use anything esphome, 2GB memory is not enough
What's ESPhome?
Has anyone had issues getting serial to work on a yellow? I'd tried to hook the console up to a raritan serial port with no joy.... have now tried SEVERAL different usb-c-serial "adapters/interfaces" connected to multiple hosts (macos/linux) in an attempt to get some form of a usable tty out of it.... but thus far, no joy.... I'm sure I'm just moronic, and everyone else is having 0 problems with this 🙂
FWIW, I've been a unix admin since the early 90's.... so I'm at least moderately familiar with shells an ttys n other such fun insanity
Isn't the Serial to USB interface baked into the Yellow? You just need a vanilla USB C to C or C to A cable to connect it to the machine of your choice, and then it should show up as a USB serial device.
O_o erm.... lolwut? isn't that kinda like sayin you can just plug your 1/8" headphone jack into an optical data port and it'll magically turn the light data into an analog signal? 🙂 (not saying yer wrong.... I honestly assumed it needed a usb uart to do the conversion as I've NEVER seen 'serial-over-usbc' as a thing before... so I was jus sorta .... leaning towards history)
(this was re: minidisc players of old which ACTUALLY had a dual-purpose fiber/headphone jack)
Basically, there's already a serial to USB chip on the Yellow board. So you just need to connect a normal USB cable with an end of your choosing to that port and you're hooking into the USB to serial chip.
This is pretty typical for modern "serial" ports since they assume no one has their own USB to serial converters anymore.
So the converter is generally baked into the device itself.
sure... I'd tried various SERIAL rj45-usbc adapters (the raritan's serial ports are all rj45) and none of them worked at all... so I'd assumed I needed something else.
never thought to try just plugging it into a usb port on a host tho. that'd be.... too obvious 😉 facepalm ... course, it doesn't solve the console-server problem, but it'd at least be a step towards functional
goes an tries it now coz he's curious
yeah. plug a USB3 -> USB-C cable from a pi4 usb port to the usb-c 'console' port and I get a ttyusb dev.... sigh that..... sigh makes me feel like an utter idiot. I've bought 4 different usb-c -> serial adapters, several other incarnations of adapers.... none of which worked... I'm.... stupid.
thanks for pointing out the obvious @languid pulsar (seriously, I mean that) .... course... now I jus gotta figure out how to get coerce the raritan console to see it as a legit tty... but that at least gives me a functional starting point to go from.
Why can't I set up yellow zigbee integration? I just started to use yellow + cm4, and I'm trying to setup build in zigbee module. But, after I click "setup" button, it said "unknown error occurred", And in log, its said "[aiohttp.server] Error handling request"
ZHA is the one that works for me
Glad it worked! Exposing just the USB side of the serial conversion is pretty standard on modern gear. But you're right that it makes it hard to use stuff designed to accept RS232.
i Finally located the problem: the connection between yellow & cm4 is too loose... reassembling solved that...
Just got my HAY - And I have zigbee problems
iirc; edit cmdline.txt to use console=ttyAMA0,115200 to use the regular uart as the console, then connect to the J11 header (which is a the first 10 pins from the regular pi gpio) but if you can use the usb-c then its a bit easier to leave it at ttyAMA2 (and even documented https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/)
Hello, I have a question. How do I flash directly to the nvme using home assistant yellow? is there any specific instructions?
<#yellow-archived message> does that answer your question?
Yea, saw they announced the official partnership with Home Assistant for reselling Yellow. Should work well and will try to get one there.
@opaque summit I just went through all the steps, but the red and green leds are solid is this correct? also I can't see any logs in the UART console
pretty sure the green led should be flashing; uart output depends on the bootloader. i'd double check the cm4 is properly seated if the rpiboot masstorage presented you with a drive to flash but it fails to boot. if that doesnt help, then maybe the bootloader is too old to boot from nvme and needs updating (which is described in https://yellow.home-assistant.io/guides/flash-cm4-firmware/)
Hey guys, I'm new to Home Assistant Yellow, I'm facing a problem:
- I try to reinstall the OS (I forget the ssh password, so I think this way would help me connect it)
- Using a Raspberry imager to download a
haos_rpi4-64-10.1.img.xz, I plug it in.
untill now, it's still just showing the RED led, even when I flash a new OS for Yellow in Raspberry imager.
If I'm an advanced Pi user, don't need zigbee, and can handle getting my HA OS onto an m.2 or SSD myself, is there any other things I'd be giving up by using a Pi system I already have vs. a Yellow?
@dusky hollow No, you wouldn't give up anything else.
built in rtc, poe and the conveient usbc serial console; but you can replicate that if you want it. (i guess native nvme you'll need to be using a CM4)
Just getting started with HA/Yellow. I’m about to buy the CM4…should I get the model with the wireless?
You could, but don’t use it. Use a wired connection
And ESPHome Bluetooth proxies are more reliable than the wireless' Bluetooth radio.
Here's a possibly dumb question: with a bluetooth proxy, is a bluetooth dongle on the device itself even necessary?
On the Yellow / HA host device? No, it isn't necessary.
Hi, quick question. Can a PoE Yellow be hooked up to a non-PoE port with the DC power adaptor connected?
I was facing network issues (constant yellow led) when installing the HA OS.
Yes, it can. You can even connect it to both. In that case the 12V power adapter takes priority.
yeah. I'd seen that... in my head, because historically to connect to hardware via a serial port, one needs a serial interface on both ends and so naturally adding a host -> (usb->serial) -> Serial-console-device was necessary...
This was just confirmation bias because history... I don't think there's anything wrong with the documentation. I simply assumed wrong ;)....
Thanks 🙏 eventually the network issue was resolved after a factory reset. The yellow manages to stay connected to the network tru a non-PoE port. Not sure what’s the root cause though.
I have a sky connect and a yellow. Is it possible to leave the yellow as zha, and do matter / thread on the sky connect?
Yes. Install the Open Thread add-on and configure it to use the Skyconnect.
The add-on setting "Automatically flash firmware" worked for me too.
Just got my yellow. Restored from backup and everything has been great except remote access. Had to reinstall duckdns and nginx. Duckdns is working but nginx us shutting down snd here is the log. Any help would be appreciated.
@wispy warren I converted your message into a file since it's above 15 lines :+1:
(Reposting since the bot made it awkward to read.) I got a Home Assistant Yellow a couple months back, and out of the box it was working fine, I had it on my network and paired some Zigbee switches. Then one day, it dropped off the network. I tried the usual stuff: factory reset, different router ports, new network cable, reseated the CM4. When I connect to it with screen I notice that the letter "o" is not drawing in all the text, including when I'm typing. Any ideas?
@wispy warren I converted your message into a file since it's above 15 lines :+1:
👋 Is there any official way to bump the gpu memory in the yellow?
With gpu_mem=32 we pretty much went minimum in config.txt since there is no HDMI. What do you use GPU memory for?
You can edit /mnt/boot/config.txt through the OS SSH access (port 22222)
I'm trying to get hw acceleration working in frigate
Are the current values (defaults) shown anywhere? It'd be great if these things can be changed from the UI.
My HA is not really easily reachable and to add the key is a bit of a PITA tbh.
In the meantime I will try to import the key
Yeah true. So far there was not really an use case to adjust those, but we have a way to expose such config.txt in UI today (e.g. the LED settings are exposed that way)
Where do I sign to add the gpu mem to the list? 🙂
I'd say, it only really make sense if Frigate has support using the GPU (and increasing GPU memory acutally makes a difference) 😅
But if that is the case, it would be here: https://community.home-assistant.io/c/feature-requests/13 😄
Totally agreed. Existing evidence seems to suggest that's the case but I will give it a go and report back.
Thank you for your help! 🙇
@harsh relic I assume you are not using a Coral TPU?
Not yet. It is not clear from reading around whether it works with the HA yellow.
I do plan to buy one but that'd be only for detection (and not decoding).
The m.2 is not working with the Yellow. The USB one should be in theory, but I haven't been able to get it working reliably yet.
That's my understanding as well but I've seen people complaining about the USB adapter too
Saying that works for a short bit before failing
I'm interested in running bind9 on my Yellow, and don't mind either running natively or via Docker- will updates to the software on the Yellow break either approach? The goal is to have the Yellow be the only device on in my house overnight. Thanks!
You'd need an add-on, not sure if one exists for bind9. There is dnsmasq, maybe that does the job for your case?
that should work fine- I am curious though- is it feasible to load things on the OS directly and not through HA on the Yellow?
You could try adguard home too
Is there a way to see if the CM4 wifi is enabled inside the yellow from terminal add on?
The OS is rather stateless. It's main root file system is read-only. It is built using Buildroot, there is no package manager etc. So no, not really.
Gotcha I am just wondering if my yellows cm4 has wifi on even while being connected to Ethernet
Or if it shuts off automatically
ha network info should get you a wlan0 interface.
Has anyone seen any issues with the yellow running HAOS not detecting Toshiba M.2 SSD? Did a fresh instal of HAOS yesterday and wiped the SSD tried once formatted as ntfs and one non formatted. I’m trying to move the HAOS install on the CM4 to the SSD. Windows machine sees the drive fine but the yellow doesn’t
Is that Toshiba SSD a SATA m.2 or a NVMe one?
Sata no go
That's an m.2 sata and not nvme
You can think of m.2 as how it fits physically. sata or nvme are the protocol for communication. sata is older for traditional drives. nvme is newer, faster. So your drive fits, but isn't recognized
Dam I was hoping it would be compatible. Easy enough then I didn’t know if I fried something or if I needed to enable something in the yaml configs
There is a list of NVMe SSDs that are known not to work in the yellow FAQ. You might want to check that before purchasing anything. I can add that Micron 7450 also does not work.
Is 32gb on the CM4 enough to run homeassistant if z2m and zwavejs will be running on a separate PI? Or should I just get an M.2 ssd?
Hi guys! Just received my yellow today. And I'm pulling my hairs out after about 3 or 4 hours trying to install HA on it. I just can't get past the darn heartbeat. I've searched all over the web, followed many tips but nothing works. Tried different USBs, rpiboot, nothing works. I ordered a yellow with a CM4 lite with no internal memory, an ssd nvme with 250gb 970 evo Samsung. The Yellow is a PoE, but i'm usint the power adapter for now. And i can't seem to install the darn OS. Anyone had the same issue?
The Heartbeat is usually during bootup, before network connectivity is reached
It seems that there is an issue with network connectivity (cannot reach DNS/NTP).
Optionally, you can flash the OS directly to the NVMe (if you have an USB adapter, the OS image is available at https://github.com/home-assistant/operating-system/releases/tag/10.2)
If that is not an option for you, you can check the serial console to see if you can find hints what is going wrong:
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
I've found something about flashing firmware to a new cm4 module. Testin if that is the issue
I've tried the serial console part, but the com port for the yellow doesn't show up. It doesn't detect my board
Has anyone received a yellow with pi recently? Surprised we haven't gotten an update since February.
I ordered from seeedstudio a couple weeks ago and it arrived in a week: https://www.seeedstudio.com/Home-Assistant-Yellow-Kit-with-selectable-CM4-p-5680.html?queryID=4643f8c830055e4da7a136aa93909134&objectID=5680&indexName=bazaar_retailer_products
The 8gb RAM cm4 is out of stock now though
Does the ssd need to be in a specific format before installing it in the Yellow kit? I'm using a cm4 lite with no emmc memory and i can't install the darn OS
What... How are other retailers getting them faster than nabucasa for crowd supply purchases?
Crowdsupply doesn't say what cm4 came with my order...
I’m planning on moving my HA from a Docker instance to a Yellow. I’m pretty sure I can just backup and restore the configuration to migrate, but does that bring over historical data like energy stats?
Yes, it's in the database
I ordered from seeed as well - took about a week. they ship direct from china
That's kinda frustrating
Ngl
That crowdsupply isn't the first to have inventory and all orders fulfilled
Especially cause you can't cancel it on crowdsupply
You can, unless you are a Crowdfunder.
I do often have bootloop issues. Sometimes they resolve themselves. I think some files might be corrupted on my nvme drive or so.
Is there a guide to troubleshoot bootlooping? What do you guys usually do?
Should I maybe delete the database and start fresh? Would that help>
I do often have bootloop issues
Hi everyone, I need some help with installation.
I followed the instructions in: https://yellow.home-assistant.io/power-supply, in step 10, the yellow LED never turns on, only the green and red LEDs are on.
then I tried to use rpiboot to "flash the Home Assistant OS Installer for Yellow onto the eMMC", and is write successfully but when I repeated step 10 without flash driver, I found the same thing happened to the LEDs, the yellow LED never turn on.
Does anyone know what I should do next? I've been struggling with this for hours.
I found that the green LED will flash at a frequency of 4 long and 5 short after power on, I checked the LED Warning Flash Codes, this status is " Fatal firmware error", Does this mean anything?
It means, the firmware has a fatal error.
You need to flash the firmware manually.
https://yellow.home-assistant.io/guides/flash-cm4-firmware/
Hey, I am planning on migrating my HA instance to a home-assistant Yellow once they are generally available.
Right now I am using a Skyconnect, my plan is to attach the existing Skyconnect dongle to the Yellow (I think yellow already has this hardware onboard but I think the Skyconnect has better placement using an extension cable). Does anyone know if this would work? Is the Skyconnect compatible with the yellow?
It is. Since you have two radios, you can also use one for Thread.
That's good news, thanks!
Thanks! After running cmd, my yellow LED is now on.
So I found out what was my problem. Something related to the ruter. Tried installing in another house with a different router brand and no problem at all.
After a "Start from Scratch" I'm not able to use my Zigbee, it gives this error in the Logfile: ERROR (MainThread) [aiohttp.server] Error handling request
Everything is up to date:
Home Assistant 2023.6.1
Operating System 10.2
Frontend: 20230608.0 - latest
Is there someone who can direct me to the solution?
Has the radio been used in a previous installation with the Multiprotocol or Open Thread Border Router add-on?
@sleek cape what brand/model was the problem router?
Apologies, I forgot to mention it is a Hass Yellow.
Sercomm. Shitty shitty brand that gave me a huge headache with everything. Including personal server, foundryvtt hosting and many many more things. And I can't change it because of my ISP
I just wanted to pop in and say that I ordered a kit from Seeed, but since it didn't come with Yellow installed I needed to follow the instructions. The instructions were easy to find, clear, and the migration was very, very smooth! Thank you to the folks who so quickly answered my questions here! Aside from a few bumps moving my MQTT broker from Docker to the add-on system, the whole process went well. Cheers!
Anyone knows if there is a way to turn of the blue led for the zigbee radio? Is there some si labs firmware version where we can turn it off?
Anyone had yet tried to solder and external zigbee antenna on the board to improve range? Do we know hwo can be the external antenna enabled in the zigbee fw?
You can't.
You could cover it with some (black) electrical tape.
I've tested with external antenna, but the chip antenna performed essentially the same in my environnment (the RSSI read out on far a way devices was essentially the same).
There are some older firmwares around in the silabs-firmware repo, see: https://github.com/NabuCasa/silabs-firmware/tree/main/EmberZNet
Would be interesting if you see significant difference
I started running the VLC add-on to play audio out the line-out port of my Yellow last month on 2023.5.x, and it was working great, but after upgrading to 2023.6.1, I get no sound... I posted this in #add-ons-archived a couple days ago and saw no response, so I'm wondering if it's possibly yellow related and not affecting other devices...
2023.6.2 did not resolve the issue, fwiw
errrm... A reboot fixed it. Restarts didn't, but a reboot did.
I installed a 64GB nvme SSD that came out of my Steam Deck (I upgraded to a larger SSD) into my Home Assistant Yellow. It looks like the nvme is recognized by HA, but it also looks like there are multiple partitions on the drive (assuming since it came straight out of the Steam Deck). First, do I need to format the drive before I move my data disk to it? Second, if I do need to format it, is that something that can be done either directly via the HA interface or via SSH while the drive is installed in the Yellow?
@cyan trail If you use the 'move data' method it would get formatted automatically
Thanks!
are you happy with your yellow? i'm moving to a house soon so i want a really robust setup
Just moved into new house and got my home assistant yellow, setting up everything and was just wondering if there's a guide or suggested installs / addons
@sudden hatch I have checked in Amazon Developers section all seems ok, this is what I was thinking is it a small buggy issue I missed or put the wrong Url in? You videos are great! Best I seen all through me developing! Which is from ZX81 IS it the local url I put in or the one made in Cloudflare as I have bought a Domain from them to make things easier! I also don't have a https:// connection at home only thorugh Cloudflare one I have a https connection. Thanks for getting back to me! I also cannot upload files in Here any reasons why not?
What does this have to do with the HA Yellow?
happy? yes, do I think its robust, sadly not yet, I've had mine lock up completely a few times and had to pull the power on it. Also some weird slow downs before it completely locked up. (POE version) In saying this, its not doing it often, just every now and again. The latest firmwares and OS/HA updates seems to have addressed some zigbee instabilities as well as I had to restart the OS to get the zigbee to work again every so often (haven't done so in a while now). Like most things should get better over time. I'm also using a brand new Samsung NVMe SSD for data and OS. If it can run for 6 months without needing a whole OS reboot I'll consider that robust. YMMV, could also be a bad HACS plugin etc dragging it down. Not had the energy/drive to go looking at journalctl logs yet and nothing telling in HA logs.
@jorg not alot to be honest just no clue on Distro prefered packet news was not as confusing as this! And I tend not to use it that much I normaly fig it myself but on this occasion I cant and was told to post on Ha forum which I thought at the time was! But though Im here Im advice people to stay away from buying a Yellow its no more than a Raspberry pi and does not work at all no yellow light on mine! Taken 3 months to get to me to return it to China now and wait another 3 month for a refund i fI ever get one
I'm very happy with it, no issues whatsoever. I haven't used the builtin Zigbee yet though but installed a ZPI7 and it's been great so far. I have the PoE version btw.
@pastel sonnet Sorry to hear you haven't been happy with your Yellow. The trouble I had was caused by a faulty NVMe - not stability issues after I have changed it. I'm mostly happy with my Yellow. Just the USB Coral for Frigate doesn't want to work with the Yellow, which is bugging me - as it was kind of implied in the crowdfunding updates.
But did you expect a Raspberry Pi powered device to have better performance than a Raspberry Pi?
@wary pivot Its the company Im not happy with! They have not at all been helpful! And Im still trying to get it returned to them though I need it for medical reasons! I'm using a Raspberry pi3 which I dont think is up to Home assistant as everytime I try to get a https it slows down. I have also just lost all my entities too in Home assistant which I think is because the free month plan for Nabu as run out so this is why I have posted in the wrong places as I was asking for help on this from @sudden hatch to see why I connect connect from the Alexa App. I like the way the Yellow is but seems very short only having two usb to it I cannot comment any further as its never booted up from the start. I got the Raspberry Pi Compute Module 4 - 8GB RAM, 32GB eMMC, 2.4/5.0GHz Wi-Fi & Bluetooth 5.0 which you would of thought they just sent out a new one to me to then get this one back to them but no they are doing it the long way! Got it from Seeed so I will not be using these again though they are the only ones doing the 8GB version so no clue what to do now maybe I just get a Rasperry Pi 4 8Gb or wait until its easier to buy and get. Sorry for posting in the wrong place too I still not found the one told to post in either 🙂 HA_Forum
@wary pivot I was expecting a easyier setup getting the Yellow but on getting it found it not at all easier to setup. Will I be able to transfer a full backup from a Raspberry pi3 to Yellow when China get around to it 🤣
@wary pivot I also got a Bill sent me from FEDEX asking for £52 shipping cost which will not be getting paid by me so glad I have no account with FEDEX!
Hey. I'm setting up my Yellow for the first time (new to HA, switching from Hubitat). I have the installer running, but it never gets past the yellow heartbeat. Am I missing something?
@wary pivot is there any way to remove these Heat Sinks to take out the module and see if it boots up doing taht then the company will just need to replace the faulty module if its that. I don't want to attempt if it will break it trying to remove it as I have no clue on how too?
What fans are you talking about? The Yellow is fanless
@wary pivot sorry heat sink 🙂 How can I upload an image so you can see?🙄 https://yellow.home-assistant.io/power-supply-nvme/#placing-the-heat-sink
Yes, the heatsink can be removed. You just have to be a bit careful.
https://yellow.home-assistant.io/guides/remove-cm4/
@wary pivot Brilliant thank you! Whats going to be the best way to know its booting up as on looking at instructions I think I'm suppose to see a yellow liggt flash on it but I have no display to see anything what its up too. I was going to see about a lead from Yellow to a Tablet but with nothing working I see no point yet but would this be the best option or a hdmi to a tv lead Im a noob on this and thank you for your patience!
The Yellow has no HDMI soldered on. It has a serial console which can be accessed via the USB-C port.
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
@wary pivot thank you again! Is the Yellow possible to work without a module in it, or does it need it?
No, the Yellow needs the CM4 to work.
@wary pivot such a shame that it cannot run without it as I could then see if the module was the issue and not the Yellow it self
@pastel sonnet it is safe to power it up without CM4, the power supplies will get on. But you'll have no indication as the LEDs are controlled by the CM4 (which is missing, hence LEDs stay off).
@shut cedar Thanks for this info! I was getting no Yellow light flashing on it first day of getting it so its never booted up from buying it, this is why I'm thinking its the Module at faults here but I'm no expert on this 🙂
Guys I just set up a yellow and I'm having trouble with the zigbee configurations. I'm getting an "unknown error occurrd"
@shut cedar is it possible to debug it or see if it works?
The CM4 is really the heart and brians, so without CM4 Yellow isn't really doing much (on its own)
such a shame so annoyed at Seeed though taken them 3 weeks up to now to give me a free return label! So still waiting! and Can't do much now only keep trying with a Raspberry pi 3
will it over heat without the heat sink on it?
@shut cedar I only get a red and green light never had a yellow light flash on it!
No it will throttle. It's safe to run without heat sink. You just don't get the full speed
@pastel sonnet you followed the instructions at https://yellow.home-assistant.io/? Which ones?
thank you vey helpfull to know, just wondering now where I can buy a 8gb Yellow afetr Seeed refund me as I wont be getting from them again and I see no 8gb ones from Demark or USA so Im a bit loss on what to do. could I do it ok with just a Raspberry Pi4 8gb
@shut cedar I did follow both instructions at the start but took out the NVMe and followed these instructions https://yellow.home-assistant.io/power-supply/
Hm, so the Yellow LED didn't start to blink at that step? https://yellow.home-assistant.io/power-supply/#watching-the-leds
No I have never seen a yellow flash on this system!
Ok, even with the USB flash drive flashed an plugged in then? That is really surprising.
no tried all ways. how long should it take from putting power to it? to see a yellow flash
I see usb flashing a few times then nothing on the yellow at all well apart from red and green lights are on but no flashing yellow apart from Ethernet flashing!
I've even tried both usb sockets on boot up and tried a few different flash on it too with differentmemory to rule that out too. So why I requested a return and I did ask for exchange but due to the way they have taken 3 weeks I requested a refund and got no where with them! I'm in the U.k and it takes them 3 months to get it to me which Im very patience in that but not in 3 weeks to send me a return label!
Yeah that sounds like a rather bad response time, sorry to hear that.
What you still can do is trying to hook up a serial console and see if you see an error message there:
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
@shut cedar thanks for this help will give it a try might be quicker than Seeeds response times 🙂 no good for medical items really! For me to put my trust into them! Love it on here though very helpfull maybe they need to come on here and learn! 🙂 Thanks!
I already have putty installed a sI used it for the Raspberry Pi 3
where is the serial console slot on the Yellow? Do I use the usb slot?
The USB-C plug
and boot from usb or just boot up
@shut cedar ok great I see the Silicon labs in Device manager just going to try putty now
It might work if Windows did pick the same COM port name, I guess 😄
@shut cedar not at all sure on this part I see no console says to hit enter key which I have done on Pc keyboard as no keyboard to the Yellow Black Pi 🙂
As a fellow T1D... HA Yellow is in no means a medical device and should not be used to control insulin pumps or to base therapy decisions on its output.
@wary pivot I do and know my risks lived better off it for the past 4 years and still alive! 🙂 Its a medical device to me! though its nothing at the moment it does not work 🤣 👍🏻
@latent fern I'm trying to work out what you are mentioning
I'm just saying that you tagging people for every single message gets annoying really, really fast
don't tag people like that. it's completely unnecessary and very annoying
ping...ping...ping...ping...ping
alright. it'll get you blocked with most folks
you tagged him in 3 consecutive messages, and it was only you two talking
anyway, carry on
Well, he/she is a mod - so he/she indeed doesn't have anything better to do, than reminding about the netiquette 🤷
Hi everyone. DId any see that error when flashing a brand new Yellow? [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
23-06-19 23:40:32 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-06-19 23:40:32 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not healthy - supervisor
23-06-19 23:40:32 INFO (MainThread) [supervisor.host.services] Updating service information
23-06-19 23:40:32 INFO (MainThread) [supervisor.host.network] Updating local network information
23-06-19 23:40:32 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
23-06-19 23:40:32 INFO (MainThread) [supervisor.host.manager] Host information reload completed
23-06-19 23:46:37 ERROR (SyncWorker_2) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/yellow-homeassistant:2023.6.2: 500 Server Error for http+docker://localhost/v1.42/images/create?tag=2023.6.2&fromImage=ghcr.io%2Fhome-assistant%2Fyellow-homeassistant&platform=linux%2Farm64: Internal Server Error ("Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)")
23-06-19 23:46:37 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
23-06-19 23:47:07 INFO (SyncWorker_1) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/yellow-homeassistant:landingpage to ghcr.io/home-assistant/yellow-homeassistant:2023.6.2
23-06-19 23:47:07 INFO (SyncWorker_1) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/yellow-homeassistant with tag 2023.6.2.
23-05-18 18:34:44 ERROR (SyncWorker_1) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/aarch64-hassio-audio:2023.04.1: 500 Server Error for http+docker://localhost/v1.42/images/create?tag=2023.04.1&fromImage=ghcr.io%2Fhome-assistant%2Faarch64-hassio-audio&platform=linux%2Farm64: Internal Server Error ("Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)")
23-05-18 18:34:44 ERROR (MainThread) [supervisor.plugins.audio] Audio update failed
23-05-18 18:34:44 ERROR (MainThread) [supervisor.plugins.manager] Can't update audio to 2023.04.1, the Supervisor healthy could be compromised!
23-05-18 18:34:44 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.EXECUTE_UPDATE - ContextType.PLUGIN / audio
23-05-18 18:34:44 INFO (MainThread) [supervisor.resolution.module] Create new issue IssueType.UPDATE_FAILED - ContextType.PLUGIN / audio
23-05-18 18:34:44 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
23-05-18 18:34:44 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 0 Home Assistant secrets
23-05-18 18:34:44 INFO (SyncWorker_0) [supervisor.docker.interface] No version found for ghcr.io/home-assistant/yellow-homeassistant
looks like this repo is not available
23-05-18 18:34:44 ERROR (SyncWorker_1) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/aarch64-hassio-audio:2023.04.1: 500 Server Error for http+docker://localhost/v1.42/images/create?tag=2023.04.1&fromImage=ghcr.io%2Fhome-assistant%2Faarch64-hassio-audio&platform=linux%2Farm64: Internal Server Error ("Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)")
23-05-18 18:34:44 ERROR (MainThread) [supervisor.plugins.audio] Audio update failed
23-05-18 18:34:44 ERROR (MainThread) [supervisor.plugins.manager] Can't update audio to 2023.04.1, the Supervisor healthy could be compromised!
23-05-18 18:34:44 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.EXECUTE_UPDATE - ContextType.PLUGIN / audio
23-05-18 18:34:44 INFO (MainThread) [supervisor.resolution.module] Create new issue IssueType.UPDATE_FAILED - ContextType.PLUGIN / audio
23-05-18 18:34:44 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
Have you been using DNS software like AdGuard Home, which isn't running now?
Or some DNS blocking firewall rules
Zero restrictions. Tried with two different ISPs
The last update is from April. Hope to see this issue addressed in the next version. Looks like repository from https://ghcr.io/v2/ have restricted access
looks like a typical DNS or IPv6 issue
Rob here I thought I was the only person doing IPoAC in 2023
having issues with the zigbee module, I activated multi protocol support and since it didn't work with zigbee2mqtt I tried to reflash my controller... now I'm really stuck I'm not sure how to fix it, the documentation is less than helpful and pretty much all wrong or outdated
first of all I would like to understand if there is a way to know which firmware is currently installed
because I'm not sure I was able to flash to EZSP
that will allow me to understand at least where I'm at and start debugging
is there a way to see if the yellow zigbee controller is in a good state and what's the firmware on it etc...?
the universal silabs flasher doesnt' seem to have a command for that
The easiest way to install EZSP again would be the Silabs Flasher Add-on. Just be sure, ZHA, Z2M and other Zigbee-Add-ons are inactive.
The Add-on will try to install EZSP and the protocol should show the detected Firmware
ok I'll try that
the documentation doesn't say that though
doing it now
ok I started the add on and looks like it's having issues
I'm getting this
[13:27:39] INFO: Detected Home Assistant Yellow
[13:27:39] INFO: Starting universal-silabs-flasher with /dev/ttyAMA1 (bootloader baudrate 115200)
2023-06-20 13:27:42 core-silabs-flasher universal_silabs_flasher.flash[159] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.2.2', ezsp_version='7.2.2.0', ot_rcp_version=None, fw_type=<FirmwareImageType.NCP_UART_HW: 'ncp-uart-hw'>, baudrate=None)
2023-06-20 13:27:42 core-silabs-flasher universal_silabs_flasher.flasher[159] INFO Triggering Yellow bootloader
2023-06-20 13:27:42 core-silabs-flasher universal_silabs_flasher.flasher[159] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2023-06-20 13:27:44 core-silabs-flasher universal_silabs_flasher.flasher[159] INFO Probing ApplicationType.EZSP at 115200 baud
2023-06-20 13:27:49 core-silabs-flasher universal_silabs_flasher.flasher[159] INFO Probing ApplicationType.CPC at 460800 baud
2023-06-20 13:27:49 core-silabs-flasher universal_silabs_flasher.cpc[159] WARNING Failed to parse buffer bytearray(b'\xf8'): ValueError('Invalid flag')
2023-06-20 13:27:49 core-silabs-flasher universal_silabs_flasher.cpc[159] WARNING Failed to parse buffer bytearray(b'x'): ValueError('Invalid flag')
2023-06-20 13:27:49 core-silabs-flasher universal_silabs_flasher.cpc[159] WARNING Failed to parse buffer bytearray(b'\x00'): ValueError('Invalid flag')
2023-06-20 13:27:49 core-silabs-flasher universal_silabs_flasher.cpc[159] WARNING Failed to parse buffer bytearray(b'\x80'): ValueError('Invalid flag')
2023-06-20 13:27:49 core-silabs-flasher universal_silabs_flasher.cpc[159] WARNING Failed to parse buffer
and after a bunch of that I get
2023-06-20 13:28:02 core-silabs-flasher universal_silabs_flasher.flasher[159] INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type
[13:28:07] INFO: universal-silabs-flasher-up script exited with code 1
s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Are you 100% positive no Zigbee integrations or addons are running? No Z2M? Zigbee Home Automation? Silicon Labs Multiprotocol?
let me check again
If you're not following it already, check out the documentation on how to disable multiprotocol: https://yellow.home-assistant.io/guides/disable-multiprotocol/
I did see that but it doesn't help cause I'm not using ZHA
z2m is not running and as far as I can see ZHA is not either
And the Multiprotocol addon?
The Thread integrations sometimes restart the multiprotocol add-on. Are those removed too?
let me get rid of it
The only way for the flasher to fail like this is if something else is talking to the radio at the same time. Try a full reboot.
ok looks like the reboot let the flasher go through, it didn't actually do anything but now I know I'm on version 7.2.2.0
[15:43:24] INFO: Detected Home Assistant Yellow
[15:43:24] INFO: Starting universal-silabs-flasher with /dev/ttyAMA1 (bootloader baudrate 115200)
2023-06-20 15:43:27 core-silabs-flasher universal_silabs_flasher.flash[158] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.2.2', ezsp_version='7.2.2.0', ot_rcp_version=None, fw_type=<FirmwareImageType.NCP_UART_HW: 'ncp-uart-hw'>, baudrate=None)
the interesting part is the metadata doesn't seem to know the baudrate which migth be why further flashes with more recent firmware files are failing
2023-06-20 15:43:50 core-silabs-flasher universal_silabs_flasher.flasher[158] INFO Detected ApplicationType.GECKO_BOOTLOADER, version '2.0.1' at 115200 baudrate (bootloader baudrate 115200)
NabuCasa_Yellow_EZSP_v7.2.2.0_PA32_ncp-uart-hw_115200.gbl
[15:44:45] INFO: universal-silabs-flasher-up script exited with code 0
does the exit code 0 mean everything is working?
looks like it's back
nice, now zigbee2mqtt loads
appreciate the help 🙂
How do i add files to the home assistant yellow ?
I want to add files to the config folder
You can use the Samba share, File editor, FTP or Studio Code Server add-on
Yeah figured it out
Thanks
Used samba share
I want to install cameras around the house and have them tied to frigate with a coral, should I use a dedicated system for that or can this be done with the yellow without any issues ?
Use a seperate system. The m.2 Coral is incompatible and the USB one isn't working reliably with the Yellow (at least for me - I have tried 2 powered USB hubs and a big bunch of USB cables).
I tried the USB coral and I also got constant crashes
so I'm moving Frigate to the home server
Is there anywhere in the Uk selling 8gb Yellow?
No
Possible to use a webcam directly plugged in to the HA yellow?
Failed to prope running application type
Hey 👋 Is there anyone running a stock kernel without the device tree of the yellow? I'm trying to get it work but my overlays for the UART4 are off. Anyone has an idea?
nvm, got it working 🎉
Not sure this is the right place to ask, do we know if the Yellow POE hardware Kits will ship this week? Also, rpilocator.com shows no CM4 units to be had in the US. Do we know if there are CM4 units to be delivered to the US soon?
Short answer: no, we don't.
$200 for CM4008016 on eBay. -_-
Anyone drill a hole in their case for an external antenna? I didn't realize the razzberry pro 7 used one. Right now I just have to shoved inside the case.
Is there a ship date on the Yellow POE?
Hi all,
on first connection I have no led lights showing up, anybody else had the same issue ?
just received my yellow poe with nvme m2 250gb
I have followed all the steps and checked twice the module to be correctly inserted
Has anyone notice since the last Core update the yellow CPU is idleing about 20% more than before
Is the CM4 seated correctly?
That's something you need to ask the shop, you have ordered from.
I have removed it and replaced it back 3 times, making sure it clicked every time
I haven't had such a significant increase after the last update.
used to hover around 8% now around 30% which is warming it up a bit
Increases I had were caused by Multiprotocol or OpenThread add-ons. Those seem to spike up sometimes.
What else could it be? Aside the CM4
HUmm i may investigate that
Is the PoE-Port powered (correctly - no passive PoE) or are you using the correct powersupply?
Spot on Silicon Labs Multiprotocol using around 25% on its own
thank you
I can’t find on internet any spec about my router, so should I give it a go via dc power
I would try that, yes. A 12V 2A 5.1/2.1mm barrel plug
YUNBO Alimentatore 12V 2A Trasformatori 24W Adattatore di Alimentazione per Striscia LED ,Caricatore universale, Display, Radio e altre apparecchiature https://amzn.eu/d/91Z8K27
That will do it, right ?
Looks good.
Thanks 🙏
Wait
The barrel plug is too big.
In some parts the Amazon page says 5.5mm, in others 5.1mm 
It needs to be a 5.1/2.1mm one
What's the router?
Fastweb Nexxt
hmm. yeah I assume it doesn't have PoE but can't find details either. It has Alexa?
I see articles talking about 2.5 Gb ports, Wifi 6, and Alexa 👀
You could find and connect a PoE switch to it though, and then use that
Yes that’s the one
by find I mean "buy" 😄
Would you be so kind to point me to a Poe switch model
You can find a range of prices, depending on how many ports you need (you might add PoE cameras or something else in the future?). But I see 5 port Tenda and Zyxel here https://www.amazon.it/s?k=poe+switch&__mk_it_IT=ÅMÅŽÕÑ&crid=1AW8WCU75F21X&sprefix=poe+switch%2Caps%2C196&ref=nb_sb_noss_1
TP-Link too
Thanks, I’ll give it a go in case also the dc power connection doesn’t work
For one single device, you could also search for a gigabit "PoE injector".
But a switch will give you more potential down the line
Here it says 5.5
Wow. Here it says 5.1mm when you hover over the power connector. 🙄
https://yellow.home-assistant.io/hardware/yellow-v1.3-poe/
Lol 😐
I'll have a look, what connector I ordered 🤣
Mine has a 5.5mm plug. So... forget what I have said about 5.1 mm 🤣
sorry guys just one more question, in case I would like just to check the power, to have the leds on do I need the module attached right?
The CM4 needs to be attached. The LEDs are controlled by it.
Yellow PoE out for delivery today... excited 😄
@wary pivot @compact quartz thank you, eventually the dc power is working as expected, installing now on the ssd
I guess I'll be asking more questions soon, being my first time with HA
You know, where you can find us 😆
ok first question, where can I find the custom_components folder
my daikin aircon is not support by the official integration 😦
If you are using HACS, it will be created automatically. Otherwise you need a terminal or file editor add-on (or Studio Code Server) and create it yourself in the config folder (where the configuration.yaml is).
It isn't present by default.
Someone know when the next version of the operating system will be released for the Yellow?
The OS doesn't follow a strict release cycle, unlike the core
just wanted to give you feedback and praise - I got my yellow in october 2022 and since then it just works, before then I had used rpi, various servers, etc. but there was always some issues, second best option is OCI box I do still run, but that needs VPN, and VPN causes issues, so again, very happy with yellow
woke up this morning to find HA + all addons unresponsive, yellow LED was flashing in a heartbeat still. Power cycled and it came back. Any way to find out why it crashed? (logs appear to get reset on reboot)
Did you install the supervisor update?
Home Assistant 2023.6.3
Supervisor 2023.06.4
Operating System 10.3
I saw a thread to suggest that latest supervisor is problematic, no issues here (apart from the crash 🙂 )
The supervisor update needed a host reboot. Maybe that's the reason you add-ons didn't react anymore.
host was rebooted after the supervisor update was applied
HA Core was also not responding? I have had crashes due to a bad NVMe. It caused filesystem corruptions - HAOS crashed, restarted with disabled NVMe and nothing useful ran. A hint were filesystem error messages during boot. I accessed those using dmesg in the serial console (not sure anymore, If they were also shown in the frontend OS logs)
HA core was not responding. entirely possible it's a bad NVMe.. If it happens again I'll move everything back to the eMMC and see how it behaves 👍
So I have bought this cheap motion sensor device to test it, TuYa IH012-RT01, I'm trying to add it to HA via zigbee, from the logs I can see some errors happening, any clue ?
Error handling '_save_attribute' event with (a4:c1:38:56:33:b4:ef:99, 1, 1280, 19, 1) params: FOREIGN KEY constraint failed
Error handling '_save_attribute' event with (a4:c1:38:56:33:b4:ef:99, 1, 1280, 19, 1) params: FOREIGN KEY constraint failed
It might be some ZHA compatibility issue. The people in #zigbee-archived might know more about that kind of problem.
Does anyone have an idea when the Home Assistant Yellow will finally be delivered? It has been postponed for almost 4 times now. And the original date of delivery was march…
It depends on where you have ordered from. CrowdSupply is known for its unreliable estimations.
Yes I ordered from them.
Why is the delay so long?
I mean the status is “pre-order” and the estimated shipping time 30 june 2023
My guess is, they sell more than they get delivered - so the backlog gets bigger and bigger. Raspberrypi.dk for example only shows them as orderable, when they are able to fulfill the order soon.
😦
We had the same problem with CrowdSupply after the crowdfunding phase.
It is. But Nabu Casa is adding more (reliable) distributors.
Maybe they should start by “fixing” the current vendors. Otherwise the problem may get bigger and bigger
About 9 months. But to be fair - it was crowdfunding and the PoE had some delays 🤣
You could contact the CrowdSupply support - maybe they improved that 
Haaha nope they didnt
has anyone added the sonoff usb 3 as a router to their yellow?
When I try it recognises it as the coordinator and I cant figure out how to fix it my yellow coordinator is still there of course and works fine but I was hoping to make use of this dongle since its been sat in my drawer since my yellow arrived
Have you flashed the router firmware?
yeah
I used python as smartrf kept giving me an error
Unknown record type: 3.
yep just did it again i even flashed it back to a coordinator that it couldnt find but with router firmware it says it the coordinator
Can't get Z2M to run on my Yellow. ZHA is disabled and ignored; I followed the directions completely and I'm completely lost on what else to do.
This is what I get on the log:
[18:01:56] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info 2023-07-03 18:02:02: Logging to console and directory: '/config/zigbee2mqtt/log/2023-07-03.18-02-02' filename: log.txt
Zigbee2MQTT:info 2023-07-03 18:02:02: Starting Zigbee2MQTT version 1.32.0 (commit #unknown)
Zigbee2MQTT:info 2023-07-03 18:02:02: Starting zigbee-herdsman (0.16.0)
Error: Reset error: Error: {"sequence":-1} after 10000ms
at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
at Queue.executeNext (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
I get the same when I try and run zigbee2mqtt, sorry I know thats of no help to you but it may point to there being an issue somewhere
Have you been using the radio with the Multiprotocol or Open Thread Border Router add-on before?
And what is your Z2M configuration?
I started a totally clean install of HA on the Yellow.
data_path: /config/zigbee2mqtt
socat:
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
mqtt: {}
serial:
adapter: ezsp
port: /dev/ttyAMA1
baudrate: 115200
rtscts: true
And the ZHA integration is removed, not just disabled?
It is ignored. Is there a way to delete it? Isn't it built-in?
That's not the question, has it been used before (before you did a clean install). If so, it's possible it still has the multiprotocol or otbr firmware
how would I know that is there a way to check, I ask because I get the same issue and as far as Im aware I dont have multiprotocol or otbr firmware but is there a way to know for sure.
As long as no other add-on or intergration is using the radio, the Silicon Labs Flasher add-on can check, replace and update your firmware to the EZSP version.
https://yellow.home-assistant.io/guides/disable-multiprotocol/
I tried ZHA once when I newly set it up then when I couldn’t get Z2M to work, that’s when I wiped the Yellow (reinstalled from USB).
Will give this a shot!
Can I connect to console while the Yellow is already powered on? Or do I need to connect console, power up, wait for it to crash?
when it crashes for me the yellow LED still flashes in a heartbeat but HA and all it’s add-ons go unresponsive
The heartbeat flash made me think the OS is still running but supervisor (or something) has crashed, is that a correct assumption?
Quite likely, yes. But having the console running before the crash might catch some error messages.
The last time I had those crashes, a bad NVMe was the culprit - causing filesystem errors. After the crash the OS rebooted from eMMC, but the NVMe with HA Core and add-ons went missing. Only a powercycle reanimated it. If lsblk | grep nvme doesn't show anything after the crash, it might be the same in your case.
Ok, makes sense. Got screen logging to file now so lets see what happens tonight.
This worked! Finally got Z2M to work properly after this. Thanks a lot!
General question - and pardon if this has likely been asked before. New user here, located in the US. If im interested in ordering a Home Assistant Yellow - should I be worried about ordering from CrowdSupply in terms of delays? Would RaspberryPi.dk even ship to the US?
@spiral bronze seeed will ship to the u.s.
RaspberryPi.dk is a great reseller, but shipping from Denmark is quite expensive.
Hey everyone. I’m using a 2gb CM4 in my yellow currently and am finding that I’m already at 85% memory usage with my home assistant setup. If I were to swap in a new cm4 with more memory, would the yellow just automatically install home assistant from scratch and i would just restore from backup after?
I assume you have one with eMMC and installed HAOS to it?
In that case: no, you have to install it again (e.g. with the installer USB stick) yourself and restore your backup afterwards
Correct. If I remember correctly though, when I first set up my yellow, I put the cm4 in and it auto installed haos. I could be wrong.
@velvet vessel if you have a kit variant it would have to have been installed using the USB installer. Only the standard yellow came with cm4 in place and HA installed.
Thanks, I have the kit so I must have used a usb. Appreciate the info everyone!
does anyone else get constant reinitializing for the bluetooth integration with the yellow?
just after i said that i may have fixed it. i turned on the passive scanning option
I was getting that like a few versions ago
So, my CM4 finally shipped, so I'm getting ready to set up my Home Assistant Yellow - is there anything else I should pick up? Is it worth adding an M.2?
Son purchased me a Home Assistant Yellow kit in February to help me in the process of replacing my failing HAI Omnipro II, but I can't find a compute module. Will a Bannana PI 4 or one of the other alternative compute modules work with the Yellow kit?
Most likely not. Neither is the hardware tested, nor the software adapted to a Banana Pi.
Looks like the Raspberry PI compute modules will not be avialble until mid 2024. Will see if I can use a Rasberry PI 3 for now as I need to get at it this summer before I start class work up again this Fall. Picked up two Konnected boards o handle the siren and alarms and still need an X10 solution.
On my yellow, after a HA update is installed, the multiprotocol add-on keeps using around 26% CPU. A restart of the add-on brings it down to 0.1%. Anyone else seeing this?
Yellow crashed again this morning. console let me login but any 'ha' command just hung. Going to revert back to eMMC to rule out the nvme
Yes, it is a common issue
Even with the Open Thread Border Router add-on
@fallen patio I converted your message into a file since it's above 15 lines :+1:
Is the Multi-PAN add-on running?
Your error messages are stating "Yellow Multi-PAN" - and that doesn't work without add-on
If you go to ZHA in the integrations and select configure, what does it say for serial port?
Is there any indication of when it will get fixed?
🤷
@fallen patio If your ZHA serial port is like socket://c8f00288-silabs-multiprotocol:9999, follow this guide:
https://yellow.home-assistant.io/guides/disable-multiprotocol/
Does systemmonitor work in yellow?
I'm using it for disk and memory usage, as well as for CPU usage and temperature. But not sure, if every other possible sensor will be working
Hey folks, anybody have luck setting up Pi Remote GPIO integration? I have a pi zero w i'd like to control from my yellow and I'm getting a bit stuck on how to setup the yellow to do this.
https://www.home-assistant.io/integrations/remote_rpi_gpio/
First problem, I thought python was already installed on HA. For example, I've used python_scripts before. But when I SSH in, I can't find it.
What exactly are you SSHing in?
ssh into the yellow
i'm at this stage of the setup:
https://gpiozero.readthedocs.io/en/stable/remote_gpio.html#preparing-the-control-computer
i think i need to install these python packages on yellow:
gpiozero pigpio
In the SSH/Terminal add-on, the developer SSH...
i tried the addon also using putty from my PC
this is the integration:
https://www.home-assistant.io/integrations/remote_rpi_gpio/
The add-on is not the OS
i vaguely remembered something like that which is why i puttied
I'd suggest to post this question in #integrations-archived - this is not specific to the Yellow, but to HAOS. Maybe someone there has tried something similar
Hi, how long the 1st installation/1st start is supposed to take ? It's working for more than 30 min now... (I have installed a M2 drive). Thanks
Do you mean the installation with the installer USB or the onboarding?
the default onboarding: just plug the ac adapter and go..
The ping responds but the default url no..
and the red light is on
But the OS is already installed?
According to the documentation, yes
You could connect it to your PC via the USB-C port, connect to the serial console and look for error messages when you reboot the Yellow.
The first loading of the onboarding page shouldn't take so long, if everything is working correctly.
I'm going to remove the m2 drive for the 1st setup...
What m.2 are you using?
the one recommended: 970evo plus
Ok. Rules out a compatibility issue.
What ducumentation are you following? (Just to be sure)
The one included in the box:
- plug network cable
- plug alimentation
- connect
ok I have removed the NVMe drive, done a factory reset and it's working now. I think the m2 drive must not be plugged at 1st setup..
Glad it is working now.
So I have an extra m.2 sata ssd lying around…. But it sounds like the one for HA needs to be nvme?
Even though it fits, it might not work?
SATA will definetly not work
Hi! I just setup the yellow, and I’m having issue getting the zigbee service to run. Seems like the core_sillabs_multiprotocol is trying to flash the FW at boot and is failing. Disabling auto-flash allows is to start, but I still cannot setup the yellow Zigbee/multi-pan service.
Okay. Have you just installed the Multiprotocol add-on or have you selected to enable multiprotocol support in Settings - System - Hardware - Configure?
The second. I enabled under hardware.
Is the ZHA integration called "Yellow Multi-PAN" and what error messages does the auto-flash show in the add-on logs?
Yes, it changed name to yellow multi-pan. Error:
2023-07-08 20:45:53 homeassistant universal_silabs_flasher.flash[181] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.3.0', ezsp_version=None, ot_rcp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>, baudrate=460800)
2023-07-08 20:45:53 homeassistant universal_silabs_flasher.flasher[181] INFO Triggering Yellow bootloader
2023-07-08 20:45:53 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2023-07-08 20:45:55 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.CPC at 460800 baud
2023-07-08 20:45:59 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.CPC at 115200 baud
2023-07-08 20:46:04 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.CPC at 230400 baud
2023-07-08 20:46:08 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.EZSP at 115200 baud
2023-07-08 20:46:13 homeassistant universal_silabs_flasher.flasher[181] INFO Probing ApplicationType.SPINEL at 460800 baud
Error: Failed to probe running application type
s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
Is /dev/ttyAMA1 selected as device in the add-on settings?
it is
Have you powercycled it yet (shutdown, pulling power and starting again)?
Just to be sure: you are not using Zigbee2MQTT?
No. This is a freshly installed yellow, and I have not installed that add-on
A last thing to look for, before we try to revert the changes:
If you go to Settings - Devices & Services - Integrations - ZHA and select Configure at Yellow Multi-PAN, what does it show in Serial port?
I cannot see that integration. The multi-pan one is gone too. Seems like that happened after power cycling it.
Even if you look for disabled or ignored integrations?
Yes, neither in ignored nor in disabled. But if I try to add it as a new one, socket://core-silabs-multiprotocol:9999 - Multiprotocol add-on - Nabu Casa, shows up
But the Multiprotocol add-on still doesn't start with auto-flash?
that's right
Did you get a success message when you selected to enable multiprotocol support or did you reboot it meanwhile?
I did get a success message
I'd suggest to try to revert the changes. Sounds like something really is borked.
I can reflash it I guess.
Or follow that 🙂
And remove the Thread integrations (if they are present)
Yeah, that one is running due to an apple home pod on the network
There should be an Open Thread Border Router integration (well - at least if everything would have run well)
the flashing is failing
Error: Failed to probe running application type
[21:26:14] INFO: universal-silabs-flasher-up script exited with code 1
s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1
s6-rc: info: service banner: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
And no other add-on or integration is using /dev/ttyAMA1, correct?
And the Yellow has internet access?
I enabled verbose logs and get this:
2023-07-08 21:33:10 core-silabs-flasher universal_silabs_flasher.cpc[158] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 4 of 4)
Yes the yellow has internet access. Not aware of any other integration using it. Is there a way to check?
Are you using the GPIO pins inside the Yellow?
Not using any of the pins no
Okay, in that case it's quite unlikely...
My approach would be to start over completely new (installing the OS again) and running the Silicon Labs Flasher add-on as first thing after onboarding.
sure!
At least if you are not loosing too much.
https://yellow.home-assistant.io/guides/reinstall-os/ - I'd go with option 2 (just to be 100% sure)
its a completely new setup so no, not really
And as you need to open it anyways - have a look if the CM4 is really seated correctly.
If the Silicon Labs Flasher add-on still fails (which should restore the EZSP firmware as it was in the first place) it might be a hardware problem.
In that case contact yellow@home-assistant.io
The professionals might also have an idea I didn't come up with
Thanks so far 🙂
The rpi was not properly seated 😅
So it is working now?
yes 🙂
hey folks, i went through the install process and since i have a RP4 that has eMMC but I have a nvme, i did the press the blue button to "Forcing installation onto the NVMe SSD" which seemed to work fine - got to only the red LED being on. Then removed the USB and power cycled, but just the red and green stay on solid, like HA isn't booting
You can plug your Yellow into your PC via the USB-C port and look for error messages on boot via the serial console.
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
The OS might not have been installed to the NVMe correctly, the CM4s bootorder might be changed
The NVMe might be incompatible
You could also try to flash the installer directly too the NVMe (option 2 of this quide - but choosing the NVMe instead of the eMMC)
roger that, thanks for the speedy response. i'll serial console it and see what i see; i was thinking the bootorder might be a problem. i hope the nvme is compat since its the one from seeedstudio as part of the kit! but you gave me a lot to try, ill let you know
What NVMe are you using?
Oof, a rebranded one. Hard to say if one of the known working or not working ones is below that sticker
yeah, i mean... i would hope that when i ordered the kit from https://www.seeedstudio.com/Home-Assistant-Yellow-Kit-with-selectable-CM4-p-5680.html that it would have one that works
Fingers crossed
connects serial console, boots fine
i don't even know what to say, it boots now lol.....
well, i guess my lesson here is come ask for help and it'll start working. maybe i should have tried a few reboots first... it boots every time now without console connected. thanks @wary pivot for your responses
You are welcome!
I am trying to move the data disk from my emmc to my Samsung 980 500GB nvme m2.
While it’s listed as an option in the dropdown. It’s not listed in the hardware section of HA.
‘ha os datadisk list’ however shows the nvme correctly
When pressing “move” HA is rebooted but is also reset and the /onboarding.html is shown again. Resulting in a new ha instance but still using the emmc of the cm4.
Anyone an idea how I can make it work? I tried doing it manually via ssh as well.
Are you using a 980 or 980 Pro NVMe?
Just the norma 980
The reset of HA also seems to happen when I just “restart ha”. Looks like the emmc still contains the installation files?
Shouldn’t this be automatically wiped upon a succesfull installation?
The eMMC will still contain the OS
Is the NVMe correctly seated in the m.2 slot?
And the CM4 as well?
I know but when pressing “restart” in HA after a succesful installation. It looks like HA is factory resetting and wiping everything.
This shouldn’t be the case right?
The CM4 and nvme are seated as described by the guide
Without the cm4 HA wouldn’t boot anyway.
No, it shouldn't be the case. Is your red button permanently pressed (is it still clicky when you press it)?
Ehmm, let me see
Yes still clicky
Fyi, i installed the os via rpiboot onto the CM4 since it was in usb mode for some reason
I followed this guide (option 2): https://yellow.home-assistant.io/guides/reinstall-os/
If you connect to your Yellow via the serial console and reboot, does it show any error messages? Right at the beginning it shows the state of the red and blue button. Like:
gpio: pin GPIO27 (gpio 27) value is 1 gpio: pin GPIO26 (gpio 26) value is 1
Lemme see
I see some weird ass characters
Looks like it’s installing again…
Because obviously it’s rebooted
What do the gpio messages at the beginning say?
Reconnect it - and be sure the serial settings in your program are correct
It’s correct
But ha is installing the os again
Everythime i disconnect power
And restart yellow
It should be humanreadable - even if it is reinstalling the OS
So this is basically impossible
U can only connect it if the yellow is powered off
According to the guide
The red button might be electronically stuck or the data migration really went wrong.
I'd suggest to reinstall the OS (option 2 again) and to remove everything on the m.2 (delete all partitions - e.g. with an USB adapter)
And only try a migration, if the system survives a reboot without new onboarding
Same after re-installing the OS with option 2 again. Output still encoded in console
Looks like there is a minor error while writing to the cm4?
Anyhow, it turned green afterwards: https://ibb.co/YtP66VD
Right now it’s executing the installation but the serial output is encoded..
Got it working!
Forgot to attach the port
However the output is cut off in my terminal
Anyway to do it in ha as well?
The early boot messages are not visible in HA
Im viewing it from the terminal in console
As you advised
Its givivv some error:” Error setting up entry Home Assistant Yellow for homeassistant_yellow
In source/zha/radio_manager.py:144
You should check, if the CM4 is fully seated in its sockets
Jorg, if it wasn’t fully seated. The HA wasn’t able to start
I am able to install addons etc. And ha is just working fine. But, upon restart or whatever, it just randomly reinstalls the whole OS over again
So weird…
And frustrating
I got 1 error: Failed to set timeout to 10 min: invalid argument. That error occured in the serial console after pressing “move data disk”
There is also the line Machine Model: Raspberry Pi Compute Module 4 Rev 1.1 in the console. So it does recognize it
I’m kinda out of options. Maybe @robust turtle is able to help out in this matter?
Contact yellow@home-assistant.io
Have you been able to see the GPIO messages at the beginning of the boot process?
No, it’s cut of to quizk
You can log those messages - see step 12
?
Step 12 of the serial console guide
:hardcopy not found
….
@wary pivot on what line should I see the GPIO output?
I can’t see any gpio 26/27 only gpio-507 (ant 1) hogged as output/high and gpii-511 (ant-2). Hogged as output/low
@noble flare what is the current state? You have access to a fresh install of HA (though you intended to have a restored backup)?
@compact quartz the status is the same. I am able to install it. But the installation does not remain in place on reboots/restarts etc.
My HA instance on my Yellow seems to intermittently lose the ability to transmit audio via the line out port. I'm not sure if this is caused by restarts or updates, but I suspect it is one of the two. Once I recognize this issue has occurred, I can reboot the Yellow and it will be able to transmit audio via the line out port again. I'm not sure if this is a Yellow-specific issue or a general HAOS issue, so I'm even less sure where it might make sense to open an issue on GitHub. Thoughts?
Just tried it with my Yellow, which hasn't been rebooted for some time. No audio output with VLC, working audio output after reboot. 🤔
Will keep an eye on it. Anything I can look up in journalctl, which might be helpful?
There are quite a lot of entries for pulseaudio in it.
Jul 11 11:08:26 homeassistant hassio_audio[570]: W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
Jul 11 11:08:26 homeassistant hassio_audio[570]: W: [pulseaudio] main.c: Home directory of user 'root' is not '/var/run/pulse', ignoring.
Jul 11 11:08:26 homeassistant hassio_audio[570]: W: [pulseaudio] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support.
Jul 11 11:08:26 homeassistant hassio_audio[570]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Jul 11 11:08:26 homeassistant hassio_audio[570]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Jul 11 11:08:26 homeassistant hassio_audio[570]: W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card0: No such file or directory
Jul 11 11:08:26 homeassistant hassio_audio[570]: E: [pulseaudio] module-rescue-streams.c: module rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
Nothing really stands out here. journalctl -k or dmesg, wondering if the kernel driver reports some issues.
Trying to add an Eve Matter device to my HAY.
In the HA Android app, I choose to add a matter device
The device is found but then the app gets stuck as "checking network connectivity"
And then : "Can’t reach device, make sure your phone is connected to Wi-Fi"
I tried another Matter device with the same result. Any help really appreciated! Thanks!!!!!
#matter-archived might help
@wary pivot I figured out what the problem was. It indeed was the CM4 which needed to be pushed in a tiny bit further.
Thanks for your help! HA now works as expected. Also the moving of data to the nvme!
Trying to diagnose another issue on my HA, I see the eth0 flapping randomly in the systemd journal. Digging around some, seems the Ethernet controller on the Pi4 does something called Energy-Efficient Ethernet (EEE) which seems to be the culprit. Anyone else noticed issues with networking?
No ethernet issues here
Hi, About disabling multiprotocol support on Yellow: is it possible to disable it keeping Thread/Matter as default instead of ZHA?
Yes, use the Open Thread Border Router add-on.
yes but using OTBR, multiprotocol support is still active.
Uninstall the Multiprotocol add-on and ZHA first. The OTBR add-on will install a Thread-only firmware
I setup my HAY from scratch.
I don't want to use the "Silicon Labs Multiprotocol" add-on as I only want to use Thread/Matter and not Zigbee.
When installing an Open Thread Border Router, an url is requested for the OTBR API, what should I enter?
Just install the OTBR add-on. The integration will be autodiscovered afterwards
Run it as a 1-to-1 replacement for the Multiprotocol add-on
- remove Multiprotocol add-on, ZHA and OTBR integration
- install OTBR add-on
- configure and run OTBR add-on
- restart HA
@wary pivot Thank you very much for this information. I wasn't aware of the OTBR add-on.. I think my setup is all good now but I still can't pair my Matter device 😢 The device is found but "checking network connectivity" takes a very long time and at the end I get "Can’t reach device, make sure your phone is connected to Wi-Fi"
That's something for #matter-archived
Hello all:
I am still having issues with the onboard Homeassistant Yellow Zigbee chip. Everytime I try to setup I get the same error.
"Unknown error occurred"
Please help me to resolve this.
I have styarted purchasing Zigbe devices and I can go no further.
Thanks in advance!
What steps have you taken and at what point are you failing?
I click configuer and I immediality get the Unknown error occurred window,
I am unsure how to diagnose
Where are you clicking configure? There are quite a lot of configure buttons in Home Assistant
From Notifications, Check it out, Discovered...
If you go to Settings - Devices & Services - Integrations and search for ZHA, does anything show up?
The same window from discovered
Have you restarted Home Assistant yet?
Are you using Zigbee2MQTT or have you installed the Multiprotocol or Open Thread Border Router add-on?
Evidently not, is that the way to go?
I just assumed that the default would work on its own
So then I should install the Zigbee and OpenThread multiprotocol add-on then
No, but those are common things, why ZHA doesn't work.
Some people have problems with the Zigbee radio, because the CM4 ist not fully seated in its sockets. You may want to check that.
I just checked the CM4 the other day after reading about others issues...
How have you installed the operating system to your Yellow?
The Yellow starts up and I get the overview screen etc...
So you have bought one with a preinstalled CM4 - meaning you didn't have to assemble the Yellow, right?
No, I purchaed the CM4 and installed it. But everything else was complete.
And how did you install the OS to the CM4?
Was preinstalled when I got it
That sounds strange
How so
If you buy the Standard set with preinstalled CM4, the OS is already installed. If you buy the CM4 seperately, there is no operating system installed
I purchase was shipped on 3/3/23 Showing as Home Assistant Yellow "Power Cord: US"
Any way to get more details, maybe from the HA itself?
If you go to Settings - System - Hardware, does it say "Home Assistant Yellow (yellow)"?
At least it is the correct OS
Let's try to shutdown the Yellow. It's in the same menu as the restart - just in the advanced options. When the Yellow stops flashing, remove the power, wait a moment and power it on again
OK, waiting for reboot
Taking forever to boot
OK, back up. But still the same error...
If you go to Settings - System - Logs and select Home Assistant Core, does it show error messages for ZHA?
This is what I have:
Home Assistant Core
Error handling request
5:21:31 AM – (ERROR) runner.py
Error doing job: Unclosed connection
5:21:16 AM – (ERROR) runner.py
Dashboard unavailable; skipping setup: Cannot connect to host 127.0.0.1:65190 ssl:default [Connect call failed ('127.0.0.1', 65190)]
5:21:13 AM – (ERROR) esphome
Error requesting ESPHome Dashboard data: Cannot connect to host 127.0.0.1:65190 ssl:default [Connect call failed ('127.0.0.1', 65190)]
5:21:13 AM – (ERROR) esphome - message first occurred at 5:21:13 AM and shows up 2 times
Dashboard unavailable; skipping setup: Cannot connect to host 127.0.0.1:65190 ssl:default [Connect call failed ('127.0.0.1', 65190)]
5:21:13 AM – (ERROR) esphome
You can try to update the radio's firmware. Install the Silicon Labs Flasher add-on (not the Multiprotocol!). When it is installed, go the the add-ons configuration, select /dev/ttyAMA1 and save it. Run it afterwards. You can look at its logs while it is running.
OK
Go to configuration
Missing required option 'device' in Silicon Labs Flasher (core_silabs_flasher).
How do I know which one?
Device
/dev/ttyAMA0
/dev/ttyS0
/dev/ttyAMA2
/dev/ttyAMA1
You might know, if you had read my previous post
Sorry skimmed over it...
That fixed it.
Thank you so much!
You have a great day or evening whatever the case may be.
And a well meaning advice for the HA journey: don't skim over documentation - that might bite you in your bottom 🤣
Lesson learned!
Thanks again!
S/might/will
Hi all, I’m a newbie to Home Assistant, my Home Assistant Yellow (standard) just arrived in the post yesterday and I’m having trouble connecting to it. I’ve tried http://homeassistant:8123, http://homeassistant.local:8123 and http://<ip address>:8123 on multiple browsers and multiple devices (Mac and Windows). I keep getting "This site can’t be reached. homeassistant.local refused to connect". I have logged in to my router and I can see that Home Assistant is there. Has anyone else encountered this or have any tips I could try? Maybe this question lies in the installation channel, not too sure.
Did you have the network cable connected when you powered it up?
Can you connect a keyboard and monitor?
Are the red, green and yellow LEDs alive and is the yellow LED blinking evenly?
Where would one connect a monitor to their Yellow? Is the USB-C DisplayPort?
Yes, connected network cable first, then power cable
You cannot. The USB-C provides a serial console, which is a replacement for a keyboard and monitor
Red is on continuous, green and yellow are flashing
If you go to http://homeassistant.local:4357 (or http://<Yellow's IP>:4357) - does that load a page and what does it say?
Thanks for confirming, that's what I thought, but I was hoping to be wrong. I have a TV near my Yellow, but my desktop isn't.
Still getting this error: This site can’t be reached homeassistant.local refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
I have a feeling it is to do with my own settings, and less to do with the Yellow...
You could use an IP scanner app to see if it shows up? Or check your router to see if Home assistant has been given an IP
no more early morning crashes since switching back to the eMMC so I'm going to say an issue with the NVMe somehow.
What NVMe have you been using?
Samsung 980 500GB (non pro)
My crashed one was a 980 too (the 1GB version). I wonder, if the Host Memory Buffer feature has something to do with the data corruptions. I have changed mine to a Samsung 970 Evo Plus (without HMB) and haven't had any problems since.
@shut cedar Do you think, the HMB feature of the Samsung 980 might be a problem?
Hm, wasn't aware of the HMB feature. Seems a NVMe 2.0 thing. It seems though that the feature is supported since quite a while, afaik the issues started mostly with the 10.x upgrade no?
It seems there are some parameters available
https://unix.stackexchange.com/questions/681131/how-to-check-change-nvme-hmb-on-linux
I think it should be possible to disable it using nvme.max_host_mem_size_mb=0 in cmdline.txt
Mine also happened with the 9.x releases, but I'm on one without HMB now. If you want to do some stresstesting with the 980, I could send one to you.
I'm at the stage where my eMMC is getting pretty full, so I'm contemplating moving to NVMe. Looks like the 970 Evo Plus is going pretty cheap at Best Buy right now. Any other recommendations or words of warning before I pick one up?
No problems with the 970 Evo Plus yet.
I'm just suspicious about the 980 (non-Pro) - but that's not based on evidence yet
The 980 Pro is confirmed incompatible
Yeah. My Router is xxx.xxx.x.1, and the Home Assistant has been given xxx.xxx.x.37 from what I seen when I log in to the Router's dashboard, as per Jack's suggestion to check IP of the Yellow. So that's what I don't understand. No VPNs or anything of the likes.
You can plug your Yellow into your PC via the USB-C port and look for error messages on boot via the serial console.
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
thanks, I will give this a try! 🙂
Restarting your router might also help, if it is a DHCP issue
My Yellow seems to only reliably boot one out of every 20 times; when it works its fine, but if i power it off and back on it'll just have the red and green LEDs on solid and no output over serial console. eventually if i unplug the power and plug it back in numerous times, i'll have a succesful boot. no idea how to debug this 😮
You can check, if the the CM4 is fully seated in its sockets. If that doesn't help, contact yellow@home-assistant.io - it might be a hardware issue
Given the shortages, I assume you haven't got a second CM4 at hand
Correct brand new one. It’s seated fine but to be sure I’ll take it off and reseat it. If that doesn’t work I’ll email, thanks Jorg
Still waiting on my yellow order from crowd supply and I’m looking at buying from Seed. Does anyone know how much RAM the CM4 that comes from crowd supply has?
At moment no options with CM4 are available at CrowdSupply
I have an order I placed back in January this year, but I have no clue how much ram it’s supposed to come with.
If you were able to still order a Yellow Standard with preinstalled CM4 it has 2GB RAM and 16GB eMMC storage, if it hasn't been changed by Nabu Casa or CrowdSupply
Thanks! Sounds like I can get a better or cheaper one from Seeed. Go figure!
*If I ignore tariffs 😬
I bought from Seeed a month ago, 8gb ram and delivered in a couple of days
I placed an order through digikey for 5 x 8gb ram 32gb emmc no wifi cm4 at end of may. Just got shipment notice yesterday. Seems the pipeline is filling. My last such order took 9 months.
Hello all, Quick question. Do I need an Aqara hun to use Aqara devices with Hemo Assistant Yellow?
I have a hub but since it is zigbee, I don't think you do.
The Aqara Zigbee devices work directly with the Yellow's radio without extra hub.
The Thread ones I haven't tested yet - but at least somewhen those should work too (if Thread is enabled)
I just got my yellow kit from seeed with the cm4 with onboard eemc, wifi, as well as a 512 gb m2. I am trying to get HAOS installed. I have hardware in place and have usb with the OS flashed to it. With the USB in, I never could get a solid red light. Sometimes an endless flashing yellow and a flashing - the yellow never turning solid. After 2 hours of abandoning that method, if I turn the yellow on without the USB installed it just goes to solid green and solid red.
I have tried to reset by plugging in, holding red button down for 10-15 seconds thinking I would get the amber light to come on. No luck. I tried holding both buttons, plugging in, waiting 10-15 seconds, unplugging also with no change.
Is this the right place to ask this? Any other details you might need?
Have you flashed the installer or the OS to your USB stick?
yes, I did flash it onto two USB sticks.
oh sorry! I installed the Rasberry Pi imager and then the Home Assistant for Yellow OS onto a USB stick as indicated on here https://yellow.home-assistant.io/power-supply/#installing-home-assistant-software-on-kit
Well, there is an OS for the RPi 4 and the Installer for the Yellow - it needs to be the installer (just in case)
And when you apply power to the Yellow, the red LED doesn't show a solid light and no flashing green, right?
does the yellow have ethernet attached while installing? (i made the mistake to not plug the cable in while installing ;-))
Correct - it is "Home Assistant OS Installer for Yellow"
Yes, I have ethernet attached while installing
When I apply power to the yellow, the led shows solid red, heart beat yellow, and green that blinks every second.
The USB with the installer is plugged in and the ethernet and power are also plugged in.
This time, I got solid yellow and solid red. Which I read was a network issue. However I am plugged directly into my Eero Router and it reads it and shows it as connected. I have plugged my computer using the same ethernet and it has connected fine.
Let me reset it because that is unusual.
How do you troubleshoot networking issues with yellow? I wasn't getting this error before and my router no longer is seeing it hardwired to it though the green and yellow ethernet lights at the port are on.
Have you restarted your router?
Good thinking. Let me try that.
No luck. Router still not seeing hardwired yellow
What is the best path forward? Remove the M.2 storage to reduce variables? I could try to reset it again by starting it up with the red and/or blue buttons pressed (though that wasn't seeming to respond before)?
What m.2 are you using? It is also worth to check, if the CM4 is fully seated in its sockets - that's quite often the culprit
And you can connect your Yellow to your PC via the USB-C port and watch the output of the serial console.
https://yellow.home-assistant.io/guides/use-serial-console-windows/
https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
Thanks, Jorg. I doublechecked that it is fully seated. Got the satisfactory click on both sides, lights all turn on, seem good to go from that standpoint.
CM is CM4108032 and SSD is M.2 2280 SSD 512 gb - from Seeed studio
Ok now can see IP from router. Sorry for sidetrack.
No worries. Is it working now?
Not yet. I have the usb, Ethernet, power plugged in.
Amber led heartbeat with green doing brief flash every second.
Heartbeat is a good sign
Can take a bit - depending on the download speed. Just to be sure... can you access http://homeassistant.local:8123 ?
No, not yet.
Ok. So it hasn't already been installed before.
no. I was hoping it would be that simple!
Our internet connection is 500up/500down so I didn't think it would take so long.
Tanks all!
The output of the serial console might give a hint what is going wrong.
okay - let me see if I can figure that out
sorry it is taking me a while. Trying to go through other means to figure out how to get you that information.
Thank you chatGPT... 🙂
I've gotten the GNU screen pointed to the device and I need to power it on. Should it be connected to the USB drive still? How about ethernet?
With USB and Ethernet.
Having network trouble again.
@mental venture I converted your message into a file since it's above 15 lines :+1:
Is that helpful?
Not yet. Is it booting into the installer?
It just threw up the solid yellow networking led again. I don't know why it isn't staying connected and it isn't responding to factory reset instructions.
What are the last messages in the serial console?
[ 63.617445] SMP: stopping secondary CPUs
[ 63.617457] Kernel Offset: disabled
[ 63.617460] CPU features: 0x200000d1,00000846
[ 63.617467] Memory Limit: none
[ 63.853250] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---
The system crashed
Can you copy the complete messages and paste them to one of the following sites and link it here?
Please use a code share site to share code or logs, for example:
- https://dpaste.org/ (select YAML for the language, and consider picking a longer expiry)
- http://pastie.org/ (select YAML for the language)
- https://paste.debian.net/ (you guessed it, select YAML as the language)
Please don't use Pastebin, since it can randomly add spaces to the main view. Please also don't share text as images since it makes it harder for people to help you. Remember that others may have colour blindness, impaired vision, etc.
What m.2 exactly did you order at Seeed?
NVME SSD 512GB(M.2 M-Key)
I can remove the SSD and install it later.
I have 32 gb eemc
My suggestion would be to remove the m.2 and forget about the USB stick.
Already gone 😆
You can flash the installer directly to the eMMC by following this guide:
https://yellow.home-assistant.io/guides/reinstall-os/ (Option 2)
that seems to have fixed the networking issue - the router can see it now
If you use Balena Etcher instead of the Raspberry Pi Imager, you could also flash the OS directly. But you would have to pic the correct image (this one: https://github.com/home-assistant/operating-system/releases/download/10.3/haos_yellow-10.3.img.xz)
Great, BUT. When I try to activate through the Aqara app it wants a hub?
Evidently I am missing something
Yep. You don't use the Aqara app, when you pair the sensors directly to the Yellow.
Can you point me to directions. Please
I'm going to keep working to see if I can figure out how to flash to eMMC. I'm new to Rasberry Pi...
Thanks though @wary pivot for your help (and patience)!
The output yellow-installer login: looks promising
It doesn't look like it's done anything beyond that
If the yellow LED is steadily blinking, wait a while and let it do its thing
Might take a few minutes
how long do I give it
Don't think it should take longer than 10 minutes
ok I'll give it a few more
no change. Maybe I can flash it
Just need to find an old PC I have stashed somewhere
Nevermind. Etcher will work!
Flash Successful and now visible!
I read the boot order was eMMC>SSD>USB. I am thinking it was trying to boot from the SSD which was throwing network errors and the like and it must have caused some boot level problem. Flashing it using Balena Etcher and the image (https://github.com/home-assistant/operating-system/releases/download/10.3/haos_yellow-10.3.img.xz) seemed to solve the problem!
Do you think I could put the SSD back in now?
Do the onboarding first - just to be sure everything works. After that - sure. But Seeed sells rebranded SSDs, so no clue if it is really compatible.
interesting. good to know.
Looks like I am all booted in. Thanks again for your help.
Has anyone encountered Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? when entering commands in the Home Assistant CLI? Thanks to @wary pivot 's help the other day with troubleshooting the Yellow. I'm still having issues connecting to my Yellow but I believe this might be the issue.
You might consider to reinstall the OS. Preferrably without SSD installed until the install and onboarding is completed (unless you are using a CM4 Lite), just to avoid possible problems. Follow option 2 of this guide:
https://yellow.home-assistant.io/guides/reinstall-os/
I got the onboarding screen, this worked!! Thank you very much for your help, I appreciate it a lot 🙂
Haven't had the audio output failing meanwhile. How about your Yellow?
Mine didn't fail during the upgrade to 2023.7.2 from 2023.7.1. I can ping you if it fails again if that would be ideal.
FWIW, I just stumbled across https://community.home-assistant.io/t/no-sound-output-vlc-telnet-after-update-2023-6-0/579849/9 so hopefully the behavior is actually fixed and not just MIA.
Thanks for the info!
Hey everyone. Has anyone run into an issue with Home Assistant booting back up after the Yellow loses power or does a full system reboot? I am running the Yellow with a 32gb emmc CM4 and a Samsung NVME. I believe it could be a boot order issue since I don’t have this issue when running only on emmc. I tried the serial connection to see if anything stood out but a lot of the commands in the faq don’t work in the console, such as the ha and hassio commands.
What exactly is happening?
And when running from emmc is the data missing?
-
Install Home Assistant on emmc. Runs perfectly. I can reboot the host and it recovers cleanly after a power outage.
-
install the Samsung nvme.
-
Transfer the data to the nvme. Everything runs perfectly after. I can reboot home assistant just fine.
-
As soon as there is a power outage or I reboot the host, home assistant doesn’t come back up. The Yellow powers on and it shows there is network connectivity but home assistant itself does not start up.
-
When I serial in to the box after the failure in step 4, running the ha or hassio* commands hangs.
Hello.
I've been holding down the blue and red buttons at system startup to try and reinstall os by putting a device that already has os installed in USB boot mode, but I just end up getting solid red lights regardless of whether or not I have a USB flash drive connected.
Now I can't either reflash the os or exit usb boot mode to get to the installed os, what can I do next?
I don't have a JP2 jumper, so it's a v1.3+ version.
After wiping the Yellow you either use an installer USB or use usbboot to flash the installer to the eMMC
https://yellow.home-assistant.io/guides/reinstall-os/
Yes, I've done this while having further discoveries, even with this method I get a solid red color as soon as the ssd is inserted into the M.2 slot.
When I unplugged the ssd, everything went back to normal and now the yellow light is blinking regularly.
Any idea on this? I tried three ssd's from different manufacturers and got the same result.
What SSDs are you using?
both try kingston/kioxia/longsys
Details?
kingston nv1 500gb pcle nvme m.2 ssd/kioxia exceria g2
I would check, if the CM4 is fully seated in its sockets and install HAOS without inserted SSD
Thank you for your help. I already double confirm that CM4 has been correctly installed on the carrier board.
Just ruling out the usual culprits 😆
Hello: Can someone suggest a place to get help on Google Nest Thermostat integrations.
I have followed the steps from within Hoome Assistant but I am getting the This step requires you to visit an external website to be completed pop up.
When I click I get "Can’t link to Nest Please contact Nest if the issue persists"
Help?
#integrations-archived might be able to help
I went through the instructions from within Home Assistant.
And finished with an error pf sorts.
"This step requires you to visit an external website to be completed"
When i click on the link from Home Assistant I get from
https://nestservices.google.com/
"Can’t link to Nest
Please contact Nest if the issue persists"
But I have no idea where to go from here...
Doesn’t boot up on emmc only after transferring data to nvme.
Hey there, finally managed to score a CM4… but my Yellow with PoE isn't PoEing. No LED reaction at all… I haven't plugged in a flash drive for installation yet, but shouldn't it power on anyway?
[To be fair, no way to check if it's the CM that's borked or the Yellow, but I'd assume it would at least light up?]
my home assistant yellow is getting full disk, is there a way to check how much size the disk actually is through the OS ?
Ugh, nvm, I was on Port 5 of the switch.
Is it the correct PoE standard and no passive PoE?
Yeah, just happened to pick a non-PoE port… 🤦
Let's call it energy saving port 
Only noticed that when trying to plug in a 12V/2A splitter and not getting any solid results… Ding.
Is the yellow supposed to only have 13.6 storage disk space ?
Your CM4 brings the eMMC with it
So you've probably got a 16 GB one
And 16 marketing GB is 14.9 oldschool GiB, substract some system storage, and 13.6 sounds about rigth.
NVMe m.2 drive (one of the known working ones)
Samsung 970 EVO Plus MZ-V7S500BW
500gb should be way more than enough right ?
or is it overkill ?
The 250GB version would likely be enough - depending on what you are going to store
Hey everyone. Is there a way to download a backup from an NVME that was being used as a data disk? I tried plugging it into my Mac with an adapter and it says it can’t read the format. How does home assistant yellow format the nvme?
It's an ext4 filesystem, so you would need to add support for this filesystem to MacOS
Oh ok that makes sense. Thanks.
I’ve narrowed down my issue to either my nvme or the connector on the yellow. Seems like it connects just fine to my Mac, just can’t read it.
In side that filesystem you can find the docker volumes
Which Samsung NVMe are you using?
Yeah I was wrong. It’s actually a WD_BLACK SN770
I had used a Samsung for something else, the Yellow is using Western Digital.
The WD Black SN770 is known to be not compatible.
Ahh well that makes sense. Well hopefully I can pull down the backup and start again on a more compatible nvme. Any recommendations? I’ll do a search too, I imagine it gets asked a lot.
There are cheaper compatible NVMes, but I am recommending Samsung 970 Evo Plus, as I have tested it myself without problems.
The Samsung 980 Pro is incompatible and the 980 (without Pro) might have issues (a big "might", as I have no reproducable proof yet - nevertheless, I wouldn't recommend it due to those potential problems)
Crucial P3 CT500P3SSD8 seems to be working fine here, and was £25
Hello: Can someone suggest a place to get help on Google Nest Thermostat integrations.
I have followed the steps from within Hoome Assistant but I am getting the This step requires you to visit an external website to be completed pop up.
When I click I get "Can’t link to Nest Please contact Nest if the issue persists"
I went through the instructions from within Home Assistant.
And finished with an error pf sorts.
"This step requires you to visit an external website to be completed"
When i click on the link from Home Assistant I get from
https://nestservices.google.com/
"Can’t link to Nest
Please contact Nest if the issue persists"
But I have no idea where to go from here...
Thanks in advance
Again... #integrations-archived is the right place for that.
Hello. Can someone help me understand cm4 module specs of this standard home assistant yellow shop? 2gb or 4 gb of ram? 16 gb or 32 gb of eMMC? https://raspberrypi.dk/en/product/home-assistant-yellow/
Edit: found somewhere in Reddit that standard means 2gb of ram and 16gb of eMMC. It's on the lower level of recommended requirements, right?
yes, it is on the lower level.
In an ideal timeline, there would be plenty of CM4 variants to choose from, go with a Kit version and pick your own CM4 but...that's not how it worked out 🙂
I saw some 4gb cm4 module in stock somewhere in EU shops for like ~100€ so maybe I will try my luck. Wonder if I go with 32GB eMMC or with lite version and separate SSD. Usually 32gb is enough for me for quite extensive database logging
It's a little more finicky to boot from NVME than it is to use it as extended storage. So I think the lite versions are kind of a headache
So a 2 GB RAM 16 GB storage can be easily upgraded to hold more if needed but obviously the RAM is going to stay where it's at
I have deleted and reinstalled several time and I end up in the same place... Thanks anyway.
As long as you are keep posting your question in the wrong channel, you cannot expect much more help. Your problem is not Yellow related.
And that is why I ask for guidance...
I Guess I misunderstood your statement "Integrations" as a suggestion not a direction "Go There".
Thanks all!
Has this problem been solved already? ConnectionRefusedError: [Errno 111] Connect call failed with the zigbee in the yellow, I've just run into it, been having stability issues with zigbee on/off for a while. 2023.7.2
nvm full reboot resolved it
Are dtoverlay=disable-wifi and dtoverlay=disable-bt in config.txt not working anymore? 🤔
Does anyone else have constant issues with thread and zigbee with the yellow, seems to go down every 24 hours or so, using Nanoleaf bulbs
How is the yellow shipping situation as of late?