Tried to get frigate + coral usb running too and ran into the same problem.
After boot it would run for about an hour before running into the wall, after that I would only get that error on start and would have to reboot again to get it running.
What is your inference speed? While on my normal server it runs at about 8.7, on yellow it would start out at about 40, slowly creep up to 50 and then die.
#yellow-archived
1 messages ยท Page 3 of 1
Tried it without a powered hub and with 3 different powered ones (2x 2.0 hubs and 1x 3.0 hub) but still no success, only even higher inference speed
how can you see interference speed ?
in frigate -> Debug and there should be detector -> coral and its inference speed
That is ms per frame, so lower is better
oh nice
I currently only have one camera active, front camera is down after I cut the cable and removed my greenhouse camera for now
I only have on cam running as well. Interesting that there is no difference between pcie and a usb 3.0 coral
This is via a $10 Aliexpress Wifi M2 -> PCIe card
on a 13 year old rack server
I just got my dual TPU adapter, so I'm gonna use that when I move to my new production server

"new" as in made after the year 2000 or?
dual 2609 ?
Think it was 2660s
but need to check
not interested in your sub 10c sub 2ghz nonsense ๐

In case anyone gets the same error and searches this discord "Something went wrong loading onboarding, try refreshing" > switching to incognito on chrome on my computer fixed this issue. It's working on mobile chrome and edge. There must have been something restricting it on my specific profile.
@shut cedar It was the SN750 SE - it doesn't show up on the available drives, the only one that shows up is sda.
@rugged creek hm, sda is probably a USB flash drive plugged in as well? But yeah, someone reported that previously, and that confirms that the WD SN750 SE indeed isn't working with the CM4/Yellow.
Oh you're right. Is there a list of compatible NVME drives or did I just luck out that this is one of the few that don't work?
Yes, seems so. I am sorry.
I am in contact with Raspberry Pi (https://github.com/raspberrypi/linux/issues/5217) and opened a support request at WD, because in theory, these devices should be compatible... But I don't have high hopes that something can be done (on software side)...
Well I really appreciate you being helpful. I would have just assumed I was being dumb.
omg... i can actually touch my yellow ๐
But don't lick it. Electronics usually don't like it wet. ๐
lol, at work they asked today to the younger guys, how do we measure if this stuff is still powered... So i suggested licking it... chef didn't agree
It is a valid option
Does yellow really exists? Ordered mine in august, standard no cpu no poe version. Shipping postponed to September, then 2 dates in October and now it says January 2023. Is this a joke?
Itโs been a bumpy ride lol
i got mine today. took a bit, but the yellow is real!
and the issue is that production and shipping isn't done as quickly as hoped
i do understand your concern, mine has been delayed a couple of times also. and FEDEX was also very frustrating
Oh man. I cancelled my PoE order because the vanilla one was available sooner. At this rate, the PoE will be shipping earlier before mine ships.
Seems like I can better cancel my current order (again), and order the PoE version instead. What a mess.
Every time you cancel the order you go back to the end of the queue
So you end up waiting a lot longer
๐
The best thing you could possibly do is just forget you ordered a yellow
Treat it as a sunk cost
Sorry if this has been asked a million times, but what are the pros/cons of getting a CM4 with MMC storage?
I'll (obviously) be supplying an NVMe drive, but is it worth getting a CM4 with MMC storage over one without given this use case?
Like normal people and AliExpress then
If you want to use a nvme you are better off without the emmc
Why are you then better off?
Well. The description clearly states a shipping date. That's also why I cancelled my PoE last time since it was delayed for 4 months and ordered the regular one.
Because nvme will be default storage device, and you don't have to pay for the unused emmc
Mmc is like an SD card which isn't as durable as a ssd/nvme drive.
You ordered a regular Kit right? It will ship before PoE.
Did you check the latest shipping updates?
What do you mean?
My order went from August to September, shifted a couple of times in October and is now set to 27th of January.
Yeah fully agree with that. The only worry I have with NVMe boot is in case some NVMe's have trouble booting (like some RPi4 SSD setups have) But, afaik, so far, we have not identified a single instance of that with NVMe (the WD's don't work at all, but thats a different topic).
Getting a CM4 Lite and booting HAOS from NVMe directly is really a nice setup.
And that's the same shipping date as the regular and PoE version if you order now.
I would not be trusting their shipping dates listed. CS seems to be lying about that
Well. Too late for that.
We asked Crowd Supply to set all dates to end of January, since last time it took 2 months to transfer the goods from HK.
But today more Kits left the factory and are on their way to Mouser. With these Kits Mouser should be able to fullfill all pending orders. PoE will follow soon, but the Yellow Kits will most likely arrive first.
Would those dates actually include people who have cancelled and re ordered and now lower in the list though
Btw, I raised a support request with Western Digital, specifically for the WD_BLACK SN850X, and their answer:
Thank you for the feedback and information. We have gathered the details and sent it along to our engineering team to investigate. We have no ETA on a response at this time however, these devices are designed for work in Windows PCs specifically as they are part of our gaming brand and the only way to update FW on them is via Windows software Western Digital Dashboard.
๐คทโโ๏ธ
Just double checked the numbers, so it depends on the PSU type have ordered. Mouser will be able to fullfill all YELLOW-KIT-STD-US pending with that shipment, so even if you are at the back of the queue. YELLOW-KIT-STD-EU and YELLOW-KIT-STD-UK we are already sold out of that batch, but unless you ordered just very recently you should still be getting it with that shipment.
Well. That also means that if someone orders the EU kit right now, they won't get it at the end of January as specified on the CS page, because of production and shipping lead times.
Yes. And I am raising that with Crowd Supply.
It's just about setting the right expectations here.
Just be like me, i never expect anything, that way I am never disappointed and I'm usually pleasantly surprised, wife hates this one trick
Great mindset when your customers and partners are always letting you down

Yeah with that hole shortage I went with that "expectancy model" as well ๐
I love waiting for 450 servers with expected delivery in march 2023, then suddenly getting a call on a Friday in September 2022 saying 200 are delivered
That said, we of course don't want to let people down, and try to communicate what we know. It's just that we don't have direct control over the dates communicated on the Crowd Supply page, so its always a bit laggy.
Oh wow, that sounds like a lot of work though ๐
Not that bad, usually when I do an installation it is somewhere between 200-800 servers
HPC is funtimes
Cabling stuff like that is mindfulness Mandala drawing for me
Hopefully I'll be doing some raspberry pis on steroids soon
Cray has a few interesting arm based systems
21500 arm cores in Isambard II
Qualcom/Nuvia have nothing on the horizon yet?
HAOS 10 based on Windows for ARM confirmed? ๐คฃ
And it needs to have Minesweeper, so we are also safe on the gaming part.
Hearts or bust
My order of the SN530 nvme drive through CrowdSupply that was a part of the Yellow POE kit has had the NVME drive cancelled. I didn't cancel it on my end so why did it get cancelled? No update at all from CrowdSupply with regards to it. Just an updated order confirmation with the same order number confirming the purchase of 1 x of all items in the POE kit.
Why did they cancel my NVME drive without any update?
Transactions
Date Amount Type Method
Sep 18, 2021 (UTC) $200.20 Payment Credit card
Sep 19, 2021 (UTC) $99.00 Payment Credit card
Oct 20, 2022 (UTC) ($97.90) Refund Credit card
The refund on Oct 20, 2022 is when it appears they have cancelled the NVME drive
Does anyone have experience with Patriot SSDs (P300 128G)? I bought them for Yellow, currently I'm also thinking of buying the lite version of CM4, hence I can't rely on migrating to eMMC in case of a problem.
Crowd Supply notified us that the SanDisk SN520 128 GB has been discontinued and needs to be canceled. However, I'd expect that they would send you a separate email about it (similar to the CM4s which got cancelled).
No. They did not. The email they have sent is an order confirmation. Same order number. Same devices, all listed with qty of 1 beside them. I received this email from them 20th Oct, when they have processed the refund. If I could figure upload it I would send through the screen shot of the email.
But to be honest - the cancellation of the NVMe is the best what could have happened to you. You get much better NVMes at that price if you buy them elsewhere. Almost 100 bucks for a 128GB NVMe...
Just don't get a WD ๐
I just bought a "unused" 512 NVMe for $50 ๐
Now I just need to find one more to make it a mirror
A WD Blue SN 570 is doing a decent job in my Yellow
Ok, so there are some which work, interesting
Perfect, found another nvme unused for $50 now i have my mirror
Home Assistant Yellow, Power Cord: US
Placed on Sep 16, 2021 (UTC)
Estimated to ship on Jun 30, 2022
Currently estimated to ship on Aug 12, 2022
Currently estimated to ship on Sep 30, 2022
Currently estimated to ship on Oct 07, 2022
Cancel and refund only the 128 GB NVMe SSD, by Crowd Supply
Currently estimated to ship on Oct 21, 2022
Estimated to ship: Jan 27, 2023
Told I could not cancel because I was part of original Crowdfunding. This is borderline fraud. First orders in should have been first out.
Original crowdfunding doesn't mean you're the first order
Sending a letter to Mike Schmidt District Attorney in Multnomah County (Portland, Oregon)
Plus their SSD is very bad value, and you can't get it anymore so that's a positive
Why not just do a chargeback on your card and cancel the order that way instead of spending money on a lawyer
Ordering in the first few days of the crowdfunding should have beat those ordered this year. I will contact the credit card, but may have a problem due to time since payment Sept. 2021. I will not be paying a lawyer, the district attorney job is to handle prosecutions for fraud and other potential crimes.
However if your order isn't ready to ship (for example you purchasing an SSD that isn't produced anymore) then CS shouldn't be stopping everyone else's orders until that is resolved.
Also apologies for that, I don't know how the USA legal system works, just weird that you're going to an attorney rather than your bank when this just seems like you're unhappy with shipping being pushed back in a world where electronics shortages is commonplace
(Though yes communication should have been better)
@blazing aurora I am very sorry that your order did not went out! I am checking with Crowd Supply why that happened, I was told its only CM4s which can hold up such an order. Can you DM me your order number? You of course can always cancel the whole order and will get your money back.
Hello !
How to know if the yellow has 128 in the gpu_mem of /boot/config.txt
How to set it to 128+.
I have a cm4 4GB.
I need to set it for frigate hwaccel.
@shut cedar I will DM, I have a Samsung 970 Evo Plus 500 gb ssd and a CM4 4gb ram, 32 gb mmc wifi sitting on my desk, I would still like to have a yellow.
Hi, have you got your yellow ones home yet? I'm still waiting unfortunately and the dates keep getting pushed back ๐ฆ
Follow the instructions below to SSH to the host. You should be able to access the confix.txt there.
https://developers.home-assistant.io/docs/operating-system/debugging/
Just add gpu_mem=128 or the desired value in that file.
Some have, some still have to wait.
we've been complaining about it for months and apparently it's all crowd supply's fault so we just get to keep waiting or cancel our orders
Estimated to ship:
Jan 27, 2023
Originally estimated to ship:
Sep 30, 2022
Do you have it the same way?
no, mine started in may of 2022 and got pushed back like 4 times with only one notification iirc
i reached out to crowdsupply and got this email back: ```For what it's worth, we've received over 2k units of the Home Assistant Yellow and to date have shipped over 400 units. They continue to ship to customers daily.
As for the lack of response, we've had some issues with our customer service platform, HappyFox, and Gmail, which we resolved last week. The issue of customers not receiving our responses has been resolved.
Above all, I'm sorry for your bad experience with Crowd Supply. The nature of getting things produced and delivered on time is a constant battle and we try to do our best with our creators to create a positive experience with customers. ```
I did: Placed on Sep 20, 2021 (UTC) ๐ฆ
i bought the cm4 and yellow separate because the dates were a month or two months earlier for the two devices. eventually they cancelled my cm4 order so im just going to cancel the whole thing unfortunately
I'm a little disappointed. Didn't expect the delivery of the products to take so long. Plus the delivery dates keep getting pushed back ๐ฆ
Currently you need to access debug SSH shell (see https://developers.home-assistant.io/docs/operating-system/debugging#ssh-access-to-the-host) and then you can edit config.txt at /mnt/boot/config.txt.
im not mad at nabu casa im just disappointed in the whole thing at this point
CrowdSupply's processing speed will be a legend one day, we are telling our grandchildren. Let's hope they ramp up their pace until then.
I got it anyway.
@shut coral did you had a CM4 or NVMe in your order? It seems that the additional items hold up the shipment of the Yellow.
I had ordered 2x "Home Assistant Yellow Kit with Power-over- thernet". But they had problems with them. I didn't want to wait that long. So I asked crowdsupply to send me the Home Assistant Yellow
Yellow Kit with Power Supply Power Cord: E". But unfortunately no positive change, rather the opposite :(. But I have only ordered the yellow ones.
This is not the place to post pictures in this thread?
there's nothing they can do to help you here but you can use imgur to upload images if you want
you're at the mercy of crowdsupply and their shipping and whatever else delays
And the Home Assistant team is OK with the situation?
they've said before they've done everything they can on their side and it's all on crowdsupply supply chain and shipping as far as how quickly your yellow gets to you. they've posted updates about PoE models here and how that is progressing too
@shut coral want me to go rough somebody up?
I'm a fan of Home Assitent, but this puts me off.
What do you need to post pictures of?
What kind of question is that?
it's their first time doing something like this and only thing they really dropped the ball on is a bit of lack of communication
It was a joke.
cogneato is joking and not a part of home assistant parent company just a mod being silly
no, I work for Nabu Casa
orly
also
My order and share it with others
@compact quartz would be nice if you guys had a role denoting that
that won't really help anything here. If you want to pass me your order number I might be able to find info but can't promise anything
Order 127905 Invoice
Placed on Sep 20, 2021 (UTC)
@shut coral for what it's worth- i recently moved from a pi4 ssd booting to an old laptop and webui and addons and such are loading quite a bit faster- especially with stuff like camera feeds. so maybe you'd be better off using the yellow (when it eventually comes) at a friends place or something and upgrading to a more powerful system ๐
The yellow is cool for a stable use.
But for people like me doing dev or having fun configuring and restarting a lot, a 2nd instance of HA on a powerful computer is a must have.
just installed my yellow with an ssd plugged in. Installed fine but did not recognize the ssd/data disk. What would I do? Is there any command line access via the homeassistant UI? (without the serial cable). Update: got to the shell in the meantime, but no idea how to get the ssd detected. I see a "mmc1: new high speed SDIO card at address 0001" message but thats about it ...
i'm happy with my HA yellow running right now ๐ Setup was easy and quick
What SSD are you using? It isn't listed in Settings-System-Storage-Move Datadisk (3-dot Menรผ)?
TRANSCEND 430S M.2 512 GB Serial ATA III 3D NAND
I assume it is a m.2 SATA SSD and not a NVMe - so it is not supported, if I'm correct.
tf
NVMe is a PCIe device - SATA needs an additional controller.
The connector is the same. Just another technology.
I'm in shock, I have a tracking number, 1 November (this year) ๐
Go buy a lotto ticket
He won already something nice from the lotto๐๐
Any tip other than https://rpilocator.com to get a cm4?
I ordered a kit thinking I could get a cm4 and another carrier board early while waiting for the yellow... I was wrong.
No thatโs the best option people have and itโs not a good one lol
In Europe BerryBase often has some in stock for a short period. But they locked them behind some club membership to prevent scalpers to buy them.
Got an availability message from Berry Base yesterday
Still waiting for mine. Very frustrating
Well, if it's any comfort or hope to anyone, on Wednesday, my order updated to expect to ship Jan 27, but yesterday I got a tracking number and today it showed up. So they are still actually shipping units and not stuck waiting for another batch.
The regular one?
Correct, kit with power supply
Ah. I was hoping the poe ones started shipping
They only just went into production this week
Well, given the overall lack of information from either NC or CS, itโs hard to keep track of the excuses
They have said more have left the factory, and Poe should be following shortly. That's information on NCs side
Sure. However, I stand by what I said. The level of information from all parties in this project is really bad
Then vote with your wallet if you're upset and cancel 
NC have said they're limited in what info they get from CS
Iโve already bought it and will wait for its potential arrival. However, I believe Iโm still entitled to feel there is a lack of communication, or would you say Iโm not allowed that?
Personally I feel you're being rude about it, but sure you think you
Its not an excuse if NC are apologising for the inability to get info from CS
Plus NC have tried to fix it by forcing all delivery dates to be pushed to jan, so that they may ship earlier and stop the constant slipping. They announced that
My biggest gripe is that there was distancing from NC from NS in the beginning. If you feel Iโm being rude, I apologise. The lack of e-mails being sent out, there is information that is lost if discord isnโt check everyday
Let's hope so.
I made a backup on my VM install and restored it to my Yellow, but then my Yellow fails to start. In the supervisor logs, I get "Home Assistant has crashed", but that's the only error level log I get. Where do I start looking at other logs to figure out why it crashed? I'm guessing I need to disable some add-on before I make the backup
Core logs? Also #installation-archived would be better as it seems like a general ha issue not yellow specific (plus you'll get more help there)
In case anyone else has this issue, my VM HA OS install was too big for my 16GB CM4 so the backup was never getting fully installed. So I ran through the inital config on the yellow, moved storage to the NVMe SSD, then restored the backup and things are working now
I'm thinking about placing an order for HA yellow. Could someone explain to me if there are benefits to using PoE rather than the power supply model?
If you already have poe infrastructure, it makes a lot more sense than an external power supply
that said, expect long delivery times
It looks like either way I'll be waiting until late January but that's just fine. PoE would give me the option for either so I think I'll go that route - thank you!
Expecting january for the poe would be optimistic from what we've seen so far
bet on June and be glad if you get it before christmas ๐
Yea
Once itโs on crowd supplyโs side all bets are off
And that assumes no other roadblocks until then
I just pulled the plug on my yellow without doing any shutdown as I needed to move the plug. When I plugged it back in the device didn't start itself up. I unplugged the DC connector at the back and plugged it back in, then it did start up. Seems odd it didn't do so when the plug was put back in (the DC connector wasn't pulled out or anything). What is the behaviour supposed to be here? If there is a power cut I want the Yellow to start up. Seemed very sluggish for HA to get started too.
Yellow is a computer running a full Linux operating system. If you pull the plug without a shut down there is a chance of corruption, just like with a Mac or PC.
(It might have been replaying database journals etc to get started back up)
Yeah appreciate that should have shut it down first, just didn't think. Why didn't it boot up when the power was restored though? Other than when removing and reinserting the DC cable?
That i don't know. Was the DC connector left in when you moved the plug? How long was it unplugged?
Yeah the DC connector was left in when I moved the plug. Would have been unplugged for about 15 seconds.
And was in the same sort of time when you re-plugged the DC connector?
No a few mins later when I realised it hadn't started
I pulled the connector out and put it back in straight away
Define "hadn't started". Where the LEDs on?
Speaking of LEDs - the schematics state a blue LED at the Zigbee module. Can that one be controlled like the other LEDs?
No, that one is controlled by the Zigbee firmware
i don't like to say this, but my homeassistant became unresponsive to webrequests. aka, i try to connect to it, by ip and portnumber and there is no website loading. Neither is homeassistant.local:8123 loading
orange and green led are flashing though
D6 is flashing twice a seccond, rebooting seems to activate it, but it doesn't respond on the network
i can ping it though
tried to find a guide online how to reset it, or to reinstall, but can't seem to find a good documentation
well, that was probably a network error that was very persistent. After removing the permanent DHCP lease, rebooting the router and rebooting the yellow, i have access again. Will have to figure out how to give the HAyellow a permanent IP outside the DHCP pool
You can set a static IP in Settings-System-Network-Configure network interfaces-IPv4-Static
yeah, trying that now ๐ normally i make a static lease, so i can keep track of the ip's on my network ๐
and back to being able tp ping but not to connect.. oops
let's try that usb cable
My NvME SSD "WD_BLACK SN770 NVMe" does not show up in the storage for the yellow
Is this ssd not supported?
i might have read before, WD has issues, but i don't know exact.
On a sidenote of that, have you tried the 3 dots top right?
Yeah for the move to datadisk
if it is not moving, it might be WD currently being incompatible
Yes, WD (Black) SSDs have good chances not to work. https://yellow.home-assistant.io/support/#which-ssds-are-supported
Well, i think i screwed something up, so i want to do recovery. I get an error though, that the wipeservice cannot be started... which is annoying, cause now it keeps booting into the not working config. the reset trick didn't work and i cannot find too much good info on any other way of resetting or reflashing anything.
I think that part of the manual either is too well hidden, or needs to be a bit more out in the open ๐
the reason i know it isn't working is cause i can view over the uart (at least that is working, but it isn't accepting my username and password)
why couldn't i find that page... lol
If it is just the username/password, this might help:
https://www.home-assistant.io/docs/locked_out/
blue and red worked ๐ it is reinstalling to emmc now. Will put back the SSD later and then use completely different IP adresses.
Thanks for showing me this. I will get it working again, i am glad this happened now instead of after making a complete config
Also, i am glad i know putty and could find the speed for the Uart, so now i can see what the HA yellow does
2 Devices 1 IP was never a succes story, nor a meme
Better than broken hardware
that is for sure, will be moving my switch to the next logical ip, as i want a bit of logic in my ip adresses. so switch should be 3, as wifi AP is 2, although i could swap those too
What date did you guys order? For the people who are getting their units shipped now?
I placed it on sep 22nd for the kit with power and no updates for me
Sep. 24th 2021 - but the PoE-Kit
Yellow Kit w/ PS, Ordered- July 14, Shipped October 27, Delivered October 29
Home Assistant Yellow (not kit) - Sep 27 2021, shipped Oct 7 2022, Delivered Oct 17 2022
interesting. I had a Samsung 970 Plus 1TB sitting around from a previous PC build. I try putting it into the yellow, and it doesn't recognize it. I delete all the partitions through a usb nvme converter, and pop it back in and it sees it, but when i do "move storage", it goes offline and stays that way for several hours, never coming back. I'm wondering if the 1TB is not supported, despite being what is shown in the marketing images, or if I'm just doing something goofy
Pretty sure this is a known incompatible nvme
Samsung ones are not known as incompatible yet, according to the support website.
Every mention of Samsung 970 and 980 show them as being compatible. But I donโt see anyone using the 1tb that I have here
I ordered a 980 512gb which Iโve also seen mention of working. We will see
I see talk about older firmwares on some of the 970 making them not work but I donโt have a computer set up to update the firmware easily. Samsungs updater wonโt work in a usb nvme adapter, and replacing the nvme in my pc is more effort than I want to do right now
Maybe a positive list of confirmed working NVMes would be a good idea. ๐ค
More documentation in general would be good too. I canโt find anywhere what all the jumpers do, or even the buttons. I see that a factory reset uses both blue and red, and I assume blue is reboot
oh man, that's great! I never ran across this in all my searches
It's under documentation though
it doesn't say what the Cls3 and Cls4 jumpers are for. Am I missing that one?
It's for Class3 or 4 for PoE version
gotcha
hmm yeah the battery holder kinda covers those. I'll ask about that
then i retract my comment on the pin layouts
There are ideas to replace JP1 with a button.
I would still like to see some additional lists of supported/unsupported nvme. i saw some basic ones, talking about WD for example. But I have yet to get the 970 Plus 1TB to work, despite it being the one shown in all the images. I've tried 2 of them now. Gonna try a 980 512GB next
There's no known supported list. This should be what is supported by a RPi 4
Yea, but it could be curated
There aren't that many to curate at this point
That's the only list i've found as well
as more data comes in... I've already seen a bunch of forum posts, and I have some to contribute as well
In theory, according to standards, all should work.
So that is why I opted to for a currated "broken" list
everyhting else is supposed to work
sure. I'm troubleshooting mine, since my samsung 1tb doesn't work, despite All Samsung NVMe SSDs seem to work far.. I'm not whining, just trying to help provide additional info to help people in the future
I am guessing you can find about ~50 different types working at this point
That is surprising, what happens?
it never gets detected. nothing in dmesg, nothing in the hardware tab of HA, etc.
Sometimes things also fail on a higher level (software/partitioning errors). That doesn't count as "not working" from a HW perspective.
Which exact model is that?
Samsung 970 Evo Plus 1TB
Yea, that's what all the marketing material says
One of them is that. The other is MZVL21T0HBLU
And both don't work?
both read fine in a USB enclosure to my PC. Neither show up on the yellow
I'm trying this 980 512GB here shortly, since I saw lots of folks saying it would work too
If the 512GB does not, then I'm going to guess it's the yellow or CM4
I have another CM4 somewhere that I can test as well, but I'll have to install HA to it
if it is the yellow, is there any recourse?
Can you visually check the M.2 solder contacts (there should be no shorts between contacts, especially in the marked region?
Yeah I think we can replace the unit if it proves to be Yellow.
Did you order a Kit?
no, the standard one with the CM4 included
I have a work call I have to join for an hour. I'll look at it under my soldering microscope afterwards
What you also shoud check if the CM4 is properly seated. Maybe even remove the heatsink, and put some force on the two long edges (above the connectors) to make sure its properly seated.
Oh wow cool, you have gear, that is awesome ๐
I'm a security researcher for a security/pentesting firm. I do hardware hacking sometimes, and lots of tinkering in my freetime.
it sometimes helps
Did you test the Zigbee radio already?
Yup, zigbee is working great. zwave is working with my old usb dongle, but i have the aeotec clone coming today
Everything works great, outside of just trying to move to an NVME drive
all 3 NVMEs are working fine in Windows on a USB adapter. After this call, I'll try the 512GB and inspect the solder joints for the NVME on the yellow board
On the CM4 side the PCIe signals terminate in this region
However, a short is very hard to see there as they are usually under the connector. I think if reseating the CM4 does not help, we probably have to go through RMA.
hopefully i find something useful
We had all kinds of problems with not properly seated CM4, so I give that a rather high chance to actually resolve the issue.
took off the heatsink, and re-seated the CM4. I inspected the NVME pins on the board and i don't see any shorts. It looks clean. Popped in the original 1TB Samsung 970 Plus to try
hey, this is at least a good sign:
โ ~ dmesg | grep -i nvme
[ 1.194981] nvme nvme0: pci function 0000:01:00.0
[ 1.195134] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[ 1.198362] nvme nvme0: missing or invalid SUBNQN field.
[ 1.198480] nvme nvme0: Shutdown timeout set to 8 seconds
[ 1.211499] nvme nvme0: 4/0/0 default/read/poll queues
[ 1.218741] nvme0n1:
rebooting and moving data disk. Let's see if it was just the CM4
Cool! Glad that resolved it ๐
So we can conclude that Samsung is still without a failing NVMe?
I'd say it's wise to wait until the migration is complete, but so far it's indicative
I'm very much hoping that was it ๐
@thorn oracle I converted your message into a file since it's above 15 lines :+1:
i spent way too much time trying to update firmwares on NVME, when it appears to have been such a simpler problem
thank you @shut cedar. I checked all the difficult things, but your help of checking the most overlooked thing first was great. I owe you one
No problem, glad it works now!
Now to wait for the z-wave GPIO adapter to arrive, to inevitably break everything again
the USB dongle just makes me sad for some reason.
Yeah I know what you mean ๐
If it is the Z-Pi 7 and you want to update it's firmware - there is just one file for all regional frequencies (used to be separate files). The Z-Pi's frequency might be wrong after firmware update and your devices won't work anymore. According to Aeotec's support the frequency can be set via software. In our case we need the Z-Wave JS UI add-on (not the regular Z-Wave JS) to set it in the UI. Afterwards either of the add-ons can be used.
I saw that note. I couldn't find the Aeotec one in stock anywhere, so I grabbed the Z-wave.me cloned RaZberry 7. It has it's own firmware updating issues
ok, yellow came in mail, added my CM4 I have had sitting in a box for a while, and bottom line, no boot, red and green on all the time. I see link and activity on the plugged in ethernet. trying reset with red button never gives flashing yellow. Where next? is there a port to read out a diagnostic. yes I flashed and reflashed the usb. the CM4 is CM4002016. Help!
thanks for the quick response! I like console ports!
Is there an option to use a regular PI with the Yellow? I can't find a reasonably priced CM4 module anywhere in Canada
No. The Yellow requires a CM4.
boourns
But you could use a regular Pi with the SkyConnect stick to get the same Zigbee/Thread radio.
I'm guessing he already ordered a yellow
I ordered a yellow and the cm4 module
But had the module cancelled
So now i have a useless yellow on the way
The only available CM4s on rpilocator are only shipped within the EU, Switzerland and Norway.

We should sell CM4 shopping voyages to Europe (CM4 not included).
right, I'm in Canada, so I'm completely hosed at the moment
though https://canada.newark.com/ seems to have some UK stock they are willing to ship to Canada,
@shut cedar I sent you a DM as requested, any response back from CS?
I'm not sure $160 USD is justified for a CM module
And all for back order - not in stock.
I'm currently running docker containers for everything
so, it's not like i'm not able to do things, I was just hoping i'd have the Yellow to take over that
What are you running on today?
2010 mac pro, running ubuntu
I'm a devop by trade, so I put everything in docker containers
I like the integration that HAOS gives, but I don't have the dedicated hardware to run it
So you'll probably be roughly the same performance CPU wise in the yellow compared to that
But with nvme you'll probably have better storage performance
Actually it might be a slight upgrade on the CPU side
I was thinking of the pi3b+
Well, I cannot even do the reset, pressing and holding the red button never gives the yellow LED, so can I assume the CM4 I bought is bad?
@junior gulch the CM4 you bought has no HAOS installed. Did you follow the installation guide?
Specifically the part installing HAOS:
https://yellow.home-assistant.io/power-supply/#installing-home-assistant-software-on-kit
yes, read my earlier post from today at 10:26 am.... never boots
irrespective of loading the os, shouldn't pressing the red button do a reset anyway?
No, the OS needs to be loaded for that to work
The red button is just a signal to the CM4, but software needs to be present on the CM4 to make something out of that signal ...
10:26 which time zone? ๐
Or better: Can you link your messages
So did the steps "Installing Home Assistant Software on Kit" go through correctly? Specifically, did step 10 showed the led in the described squence? https://yellow.home-assistant.io/power-supply/#watching-the-leds
so help the newbie, don't see the terminology to "link" existing messages, is this the create thread command?
Press the three dots on the right side, then "Copy Message Link"
got it... #yellow-archived message yep, do everything to start of step 10 and no change in red and green leds... ethernet link and activity are ok.
did the USB over, will try different usb stick, but this one has worked many times...
So stays just red, never a green LED? And you did not install Software on that CM4 before right?
sigh.... I linked linked the post as you asked, i guess you did not read it.. the linked post says: red and green on all the time.... this CM4 might have been used...
I did read it.
ok, yellow came in mail, added my CM4 I have had sitting in a box for a while, and bottom line, no boot, red and green on all the time. I see link and activity on the plugged in ethernet. trying reset with red button never gives flashing yellow. Where next?
That nowhere says that you went through the getting started steps, especially, it does not say if you have the USB flash drive with the "Home Assistant OS Installer for Yellow" pre-installed in your Yellow.
To help you, I need to know where you exactly stand ๐
With red and green on all the time it does not seem that the CM4 boots another OS. It seems as if the firmware cannot boot from you flash drive.
ok, so now you know, right? no confusion... followed directions, fail at step 10, red and green LEDs on solid since power on. Tried another usb memory stick in mean time.... any jumpers that could affect the boot/
Yeah I think it's all clear, unfortunately I am not 100% sure why it is stuck there (could be the previously installed CM4 software starting to boot/getting stuck or that the USB flash drive somehow is not readable).
I think the best approach is to use the USB recovery https://yellow.home-assistant.io/guides/reinstall-os/ (Option 2)
using 2 different small (16 gb) usb memory sticks convinces me it's not them.... the imager writes and verifies... so that is out... I'm going to try the console output with putty.... see if I get anything, and then perhaps the reload using RPI boot.... in the mean time, ordered another RPI from a guy in Canada, on ebay, so that's another crap shoot
great, trying to set up the console, and the uart on the yellow is a cp210x and stupid windows 11 did not have the driver... found it, but no response from the RPI..... pretty sure it is dead...
actually, means there is no functioning o/s
ok, tried the reinstall, and the RPI imager loads, etc, but never finds the board.... so cannot write to it. I assume SOL at this point...
thanks for the help
Just to check. Did you ensure the CM4 is properly seated in the yellow? You may have to push it back in
4 times, inspected with 7x optivior, this is not my first rodeo, I lead a chipset and product design team, I ordered without CM4 as indicated, and bought a CM4 off evil bay
Watch rpilocator and some raspberry pi discords, and you'll find one. I've bought 3 variations in the last month or so.
You don't need to be rude btw. No clue what optivor even is.
But asking because it has been one of the most common issues here. If you ordered it off eBay then it may well have been a broken device
Yep, I had issues with my NVME because my CM4 needed re-seated.
not rude, told you I did it 4 times, used deoxit for any possible oxidation, and used an optivisor (google it) to inspect the contacts... I was not rude in the least.
Shatter: I looked RPI locator, only ones that showed up today were with a company that won't ship to USA... drat
You're being very abrasive right now. Its a genuine question. I don't need to google what one of those is, I'm just saying myself & probably others don't what it is
not abrasive, you might need an optivisor some day, good tool to have with miniature connectors
No I think I'll be fine
Anyway, back on the track, I think I have exhausted all reasonable options, and will wait for the board from Canada.
@thorn oracle Can you walk me through how you got the Z Wave working. I set up my Yellow and restored from a full back up of my Pi4. I have a Z Wave USB dongle that worked fine but I can't get Z Wave JS to start up. It simply says:
2022-11-03T05:00:27.150Z DRIVER version 10.3.0
2022-11-03T05:00:27.151Z DRIVER
2022-11-03T05:00:36.272Z DRIVER Failed to open the serial port: Error Resource temporarily unavailable Cannot
lock port
Unable to start driver ZWaveError: Failed to open the serial port: Error Resource temporarily unavailable Cannot lock port (ZW0100)
at Driver.openSerialport (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1070:9)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:947:5) {
code: 100,
context: undefined,
transactionSource: undefined
}
[05:00:36] WARNING: Halt add-on
Sounds like a wrong device path for the USB dongle. What is set as device in the Z-Wave JS addon?
I received the Home Assistant Yellow and set it up according to the online
guide. It installed, boots up and I am able to log in. But the connection to
Home Assistant keeps dropping frequently (connection lost, reconnecting) and the yellow
led never stops doing the heartbeat pattern.
I already checked the connection of the CM4 to the board and did several
reinstalls but the yellow led is continuously doing a heartbeat pattern and the
connection keeps dropping. Anyone have a clue what could be causing the connection drops and if it is related to the yellow led doing the heartbeat pattern constantly?
The heartbeat is meant to be pulsating - it's a sign Yellow is alive. Is it possible, that two devices are using the same IP address (e.g. old HA instance and HA Yellow running at the same time) in your network?
The 2 instances have diferent ip addresses. I also tried shutting down old instance but still the same happens: yellow led keeps flassing twice every second and the connection drops frequently.
Are you trying to access it using homeassistant.local?
No, I access it using the ip address. I am able to login but every 30 seconds or so the connection drops and I have to wait for it to reconnect
It's pingable continuously?
Iโm not sure. Mine โjust workedโ
Zigbee2MQTT
No, it times out about one-third of the time. Pings to the old instance is continuosly
Yes, it is wired
Then i would guess on a os issue if no other wired devices have issues
Let me know if you would be interested in selling the kit
I connected the new instance on the same switch as the old instance. The old instance (and all other devices) have no issues but the ha yellow keeps dropping connectivity. If it is an os issue, what could I do to solve it? I tried recreating the USB and reinstalling but still have the issue....
No idea, I don't use yellow or haos, but if no other devices experience the issue it is very local
How do pings to Yellow behave?
No, it times out about one-third of the time. Pings to the old instance is continuosly
(using IP)
Ah I see, that was referring to ping. Hm ๐ค
Could be IP conflict, but that was mentioned as checked i believe
And if connected to the same physical switch as the other instance I would say networking is fine at the physical layer
@fresh lake can you DM me your serial number? I can check the test logs
We do run Ethernet tests at the factory, and in theory they should only go out if that succeeds.
Physical port issues should manifest harder imo, hence why I would perhaps rather think software somewhere
Even a bad cable should be a lot more errors than that
Yeah agreed, it smells more software.

I even switsched cables to rule that out. ๐คฃ
Done
Yeah the testing logs do look good, I think we need to look into SW a bit closer
Can you setup a serial console (using USB-C cable)? This allows to monitor what is happening when Yellow disappears from the network. You can find a guide how to setup the serial console for Windows/Linux/MacOS here:
https://yellow.home-assistant.io/documentation/
FWIW, the yellow LED blinking in a heartbeat pattern is expected, on HAOS.
Shouldn't it be more like pulsing instead of quick blinking twice every second? That's what I thought...
Checking it out now
During installation yes. But once HAOS is on there and running, the heartbeat pattern indicates it's alive and running
I'm in the serial console
hacker voice: I'm in
Cool, so you have a root prompt? Check dmesg next time ping doesn't work
Also check journalctl -b 0 -u NetworkManager.service.
Done both. Anything specific to look for?๐ฅบ
Link down/up events or device (eth0): state change: in that time where it wasn't reachable
Since you probably don't have a managed Switch, we can't see error packages, can we do that with any of the built in software of haos?
See this: device (eth0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: ' managed'
Nope, I just need the pi
Hm, that sounds like a software caused state change
@fresh lake did you use the frontend to set a static IP?
No, it gets an ip address from DHCP server (reserved)
With "ha network info" I can see it has the ip address, gateway and nameservers correct. wlan0 disabled and ipv6 disabled
Can you try using a static? Just to isolate the problem.
Issue persits with static ip address
Can you check what nmcli con show is saying (when it pings and when it doesnt)?
what is the upstream switch ?
Supervisor eth0 d6659a40-d6c6-3431-963d-6c170080432c ethernet eth0
Same output in both situations
@fresh bough , what do you want to know about the switch?
@fresh lake Hm, weird, I wonder what causes the state change on NM side. Can you share a bunch of logs from the above journalctl command when it happens? E.g. using https://hastebin.com/
Was wlan enabled previously?
no, it was not
@fresh lake can you check ha su logs, in particular around Nov 03 16:30:03
22-11-03 17:33:02 WARNING (MainThread) [supervisor.updater] Can't fetch versions from https://version.home-assistant.io/stable.json: Timeout
Do you have a firewall or similar in place?
A model number is a good start
I do have a firewall. I can ping version.home-assistant.io from several devices
Ubiquiti USW-48
Ah, so it is managed then
I don't touch ubiquiti with a ten foot pole, but you should be able to gather interface statistics from it
Yes it is
would be interesting to see any kind of discards \ error counters on the port
It does feel to be Supervisor related, I think the audit: op="connection-update" just before the connection gets deactivated is caused by the Supervisor.
The timestamp correlates with 22-11-03 17:30:03 INFO (MainThread) [supervisor.host.network] Updating local network information
@fresh lake can you check if you see Updating local network information in ha su logs every time ping starts to fail?
I do not see it every time. The log doesn't change much > https://hastebin.com/omokobuhop.yaml . Log taken at 18:52
Do you have a snapshot of NetworkManager log, where ping does not answer and there is no 'Updating local network information' in the su logs?
It seems that there is a DNS issue too. @compact quartz setting Google usually helps there right?
Setting a fast public DNS can help, Google's, Quad9, or Cloudflare, but @fresh lake has another installation of HAOS going, yes?
Yes, I hav an current installation running on the same network, same switch even
HAOS
Does it reliably connect and then disconnect in some amount of time?
As in does it connect every time you restart it?
You mean the current instance?
The current instance is reliable and has perfect connection
No sorry the new yellow instance
While you can ping it, the connection is reliable and I can login and do stuff in HA. When the connection drops (not pingable) HA is not responsive and I have to wait until the connection comes back up. I let a ping run for a llong time and there is around 33% packet loss
Did you try swapping the Ethernet port? Just in case ๐
Hi, what size nvme is recommended for the Yellow?
@warped barn 32GB is recommended for HA. But you can find much larger NVMe for less than $50
Not exactly swapping but I did try different ports
Is there a switch between Yellow and the router?
Thanks, is it a case of the bigger the better? Will 500gb cover most of my storage concerns? Or should I just go for a tb?
I don't think 1TB is necessary, personally. I wouldn't use HA as an NVR or Media server however.
Okay, perfect. I will get something a little smaller so. Thanks for the info, very helpful.
Yes, there is. The same switch as the current HAOS instance
As a test I did the following. I have a yet unused rpi4. So I installed haos and connected to the same switch/port. Connectivity was stable en ha was very responsive. Tested for an hour and had no connection drops or other issues.
So we can exclude the switchport and cable ?
we are down to the issue being local to the yellow itself ?
Sounds like it
Can someone please confirm what the current position is with support for Matter in both the Yellow, and HA? Are these available now, and if not what is the rough timeline for support being added? Thanks.
do you have matter devices yet?
I'm confident you will see a dedicated channel available here when its time to "matter" hehe cheesy AF
Aqara are adding matter support in December. https://9to5mac.com/2022/11/03/aqara-matter-devices/
then take another look around here when you have it
We're in that position where suddenly you have to question future purchases. Should I just stick to Homekit for now, or hold off a few weeks and get a Matter device. Since Home Assistant is my central brains for controlling everything, it would be useful to have a rough idea when it will support Matter to help in purchase decisions.
there are devices out there which support both, they just get a software update later to support matter
Matter won't kill all the other standards
And jumping on the latest bandwagon is often costly and useless
And it might well not be yellow that is your stumbling block for matter. We are seeing home networks that need quite a bit of work to support matter. From hardware that breaks ipv6 and mdns to people simply having their border routers on different vlans to their ha instances.
I just wanted to know what the roadmap is. I'm well aware of potential issues around early adoption etc ๐
The roadmap is unclear because matter is so damn new. It'll need a couple months before the standard is understood in its entirety
Matter in HA may be next release, or may be the release after. Its not clear
It's just a Matter of months. I'll find out myself. ๐คฃ
It doesn't matter really
I can't wait for the matter channel and all the puns
And #dark_matter for NSFW?
I made a joke about #devs_matter-archived claiming that alls_matter, but I've already did that twice, and it wasn't funny even the first time, so I won't do it again.
But devs don't matter ๐ค
Nothing's the matter now that I've fixed the matter compressor.
This matter gets out of hand.
As a test I did the following. I have a yet unused rpi4. So I installed haos and connected to the same switch/port. Connectivity was stable en ha was very responsive. Tested for an hour and had no connection drops or other issues.
Are we going to get an addon or integration for matter devices within home assistant when december comes around?
We are hard at work on Matter. Related to that, is also thread network capability. We are working on both, but Thread is currently second priority. I have tested the multi protocol add-on on Yellow just yesterday it does work, but it is quite some manual steps currently to get the Thread credentials from it and do Matter over that Thread network ๐
I really appreciate all the hard work you do. Looking forward to what is to come. If I have further questions ill let you know.
Will the multi protocol capability be limited to ZHA or is possible to use Zigbee2MQTT with the internal module and still use Thread?
The lack of CM4s is a PITA. I've been supposedly 2nd in line for one for 18m now, still nothing ๐
By the time my PoE SKU appears it'll be well north of 2 years ๐ฆ
The cm6 will be out!
Found a guy in Canada, has a few, by the rpilocate, will see if I really get it or get ripped off... the first one I bought months ago is dead.
Imagine running a yellow with a cm4 and waiting 1.5 years for it, then the cm4 dies and you have to wait 1 year to find a other cm4

I may be in that situation soon.... we will see... SUX
This is my fear. My yellow will turn up and my CM4 will have been DOA the whole time and I wonโt be able to get it replaced
laughs in x86
Hi all, I was told to come and ask this here. I have a Yellow with a 8GB RAM Wifi Lite CM4, and a Samsung 950 Pro nvme ssd. Installation seems to go fine, and if I remove the ssd from the Yellow and look at it on a PC, I see partitions for hassos and such. But the thing doesn't actually boot. I get a green and red light, both of which are solid, and the indicator lights on the ethernet cable, but no other activity at all. Attempting to reinstall from the USB does not work. I have to manually remove the ssd, format it on my PC, and then I'm able to run the installer again (as verified by the lights). Any suggestions?
Have you connected to the serial console to watch for error messages during booting yet? Those messages might help the support pros later.
https://yellow.home-assistant.io/guides/use-serial-console-windows/
Indeed I have. After the installer completes and I reboot, nothing ever shows up in the console
I've watched the installer in the serial console, and it appears to complete successfully too
I just reran the installer, watching first boot now. Nothing at all. I'm at a loss.
Given that this CM4 has no eMMC and I remove the USB drive before powering up again, I assume it isnโt able to locate the installation and hence nothing happens, but as I noted the partitions do appear to be there
Well it's been sitting here nearly 20 minutes without a single line in the console. I'm assuming it's not booting. If anyone has any pointers or perhaps a nightly build or something to try, I'd appreciate it. After waiting more than a year for it and then having to source a CM4 at more than twice the original price, this whole ordeal has me quite fed up.
I know it's frustrating, but I'm sure one of the devs will answer soon.
Just to be sure... when have you created the installer USB stick? Later than October 6th? They added some new Raspberry Pi firmware with that installer release.
Have you disconnected JP2 after installation ?
If JP2 is bridged it will try USB boot infintly afaik
Good point.
I didnโt touch JP2 at all. Itโs only attached to one pin, so shouldnโt be jumped. I created the installer three days ago.
Is there something I should be doing first? Should I set the jumper prior to the install?
Iโll try anything at this point :)
Now that I look at it, I think the date in the USB creator app was 10/5. I need to check that
I created it a few days ago but I think the build date for the โHome Assistant Installer for Yellowโ option had an earlier date
The RPi Imager should get the latest. But you could download the latest release here and use that image for the stick (e.g. using Balena Etcher, if the RPi Imager won't let you select a file).
https://github.com/NabuCasa/yellow-buildroot
Hmm are images not allowed in this channel? I tried pasting a screenshot of the Pi Imager. It shows "Released: 20221005"
That's the newest one.
Please use imgur or other image sharing web sites, and share the link here.
Image posting is blocked in most channels to discourage people from sharing text as images. Sharing text as images assumes that everybody sees the world as you do, which isn't the case. Some people are colour blind, or have visual impairment that means they can't make sense of an image of text.
All right, then I'm using the latest image.
Gonna try a different usb stick just in case. Who knows right?
No dice. grrr
I tried disconnecting it entirely. No change.
All right, out of an abundance of caution, I went and got a new nvme ssd. Worked first try.
So mark down the Samsung 950 Pro as potentially incompatible
Swapped in a 970 Evo Plus
Thank you to everyone who tried helping earlier today.
@opaque monolith interesting find. It seems that the 950 does work in Linux, but presumably the firmware or UBoot has trouble initializing it. Would be interesting what the serial console shows when trying to boot from it https://yellow.home-assistant.io/guides/use-serial-console-linux-macos/
It doesnโt show anything at all
It was a boot disk on my Hackintosh for a couple years. I must have removed and reinstalled it half a dozen times in the Yellow
Then, it was probably a bad little drive! In the box you go!
just to close the loop, the guy in canada that shows up at the top of rpilocator did ship my RPI, and I got it today, and system came up fine... did not seem to come up with the DNS name the first time, second reboot after loading I used the console, checked the ip address, hooked to that with FireFox and it lives. So I've been holding onto a bad RPI for months.... think I'll get my money back on that one? Anyway onwards and upwards, need to figure the best Z-Wave dongle, will do more reading, and have bought a couple of Zigbee devices. Thanks to Falstaff and those who helped.
You may guess - the Z-Pi 7 seems to be hard to get in the USA. ๐
Aeotec doesn't even list it on their US website.
In Europe? Sure. ๐
Eh, I'm still waiting for backlogs of hundreds of servers
But you've been able to order them. ๐
I got my CM4 three days after I ordered it on Amazon. I am ashamed at what I paid for it, though.
More or less than $150
YIKES
You know, after waiting more than a full year for the Yellow, I was debating recycling it and just being done. Who knows when an affordable CM4 will show up, or to what lengths Iโd have to do to get one. So, I, yeah I said Iโm ashamedโฆ
While waiting for the yellow, somebody told me where to order a CM4. Had it at home 4 months prior to my yellow even shipping.
Except for an IP conflict, installation went very smooth
I read a bit on the z pi 7, not sure the results are definitive, some yellow officials says it worked, but it was some time ago... would like to hear from a current user
Works great on my Yellow
I'm finding it frustrating that all the CM4 stock, which, at least, originated in the UK (Raspberry Pi Foundation rather than manufacturing), is going to a German company which wont, because of Brexit, sell to UK users!
Have you tried to contact the Raspberry Pi Store in Cambridge? They don't ship, but they sometimes have some in stock.
I'll check!
I'm too far away to drop in on the off-chance that they had some stock. I guess I'll just have to wait!

๐
@cloud raptor thanks for the response, can you point me to something to read about installing it, i.e. any other libraries/software needed? Don't want to drag the group down because I am a newbie.
There isnโt documentation Iโm aware of. Though itโs not that complicated. You connect it to the headers, there is only one way to do it. After booting youโre Yellow you can add the Z-Wave integration, and ask to install the Z-Wave JS add-on. After that you need to select the ttyAMA0 port and it should work.
Has anyone manage to make frigate + coral works ? I only see reddit posts and issues on the github about that problem.
It was written in the Crowd Supply update that the yellow will support the usb version of the coral so I'm a bit lost.
Can you see the coral?
I don't use a yellow, but I have both dual tpu and single tpu m2 versions working fine with frigate
The m.2 Corals are not working in Yellow due to some weired CM4 hardware restriction (bug).
yes frigate sees the coral
it's the usb version
There is the log here: https://github.com/blakeblackshear/frigate/issues/4073#issuecomment-1307790980
I found other people having the LibUsbDataOutCallback error
If you have a pi laying around, I'm curious if you can make it work with that and docker @pliant whale
i have my usb coral working in container on rpi
never seen anything about LibUsbDataOutCallback
Another user (other Discord) had problems with his USB Coral after updating Frigate to version 0.11. Don't know if 0.11.1 fixed it. ๐ค
I tried in docker and it work @fresh bough .... And I retried just now with the Yellow but I changed the official cable with my phone cable. It works.
So maybe the yellow just hates the official cable. The official cable works only on my rpi4, not on the yellow. Now it's working but I need to buy another usb cable lmao.
that was my observation too, usb corals are picky about the cabling
Huzzah, long live my m2 corals connected through $10 AliExpress adapters
Yup, it works on the worst usb cable of my house, used af. Not on my shiny coral cable. ๐ข
I got my kit today, followed the instructions, and once I rebooted post install I am not seeing the yellow on my network and am not able to connect to the local url. Is there something I can try?
Using a yellow kit with cm4 lite and Samsung evo nvme
Hi there,
After Upgrading my new Yellow to 2022.11.2 the following 3 repair warnings showed up and I wanted to know, what I can do about those. Any help would be greatly appreciated.
Unsupported system - Systemd issues
Unsupported system - CGroup version
Unsupported system - Operating System
If you have a terminal add-on installed, I'd try the following command to make sure the latest OS version is installed
ha os update
If you have a terminal add on installed
Any news about the POE version? I see, the shipping date was changed on CrowdSupplyโฆ..
A question from a slightly different direction. Have you received a refund from a cancelled order for CM4? They said within 10 days, but I've been waiting 3 weeks. I've emailed them but so far no reply. I don't want to rush unnecessarily, I don't need the money right away. But I don't want to underestimate it.
So CEO of pi trading says shortage expected to continue to end of 2023
As I expected
How can I cancel my Yellow Order, I am done being lied to. I purchased a yellow with CM4 and SSD on day 1 of the campaign. Crowd Supply cancelled the SSD and moved the delivery date from one of the first to Jan 27 2023. I can not help that they didn't have the SSD but others are available for purchase. I have a CM4 and SSD sitting on my desk, but no yellow. Very bad experience with Crowd Supply.
If you placed your order during the crowdfunding phase, CrowdSupply's customer support won't cancel the order, according to the terms of use. Maybe the NC team can help to cancel the crowdfunding.
Or you could just treat it like a sunk cost, and then one day you get a nice surprise in the mail.
I installed a Razberry 7 Pro into the Yellow and got it up and running. The logs seemed
ok, no errors. But when I attempt to include (or exclude as well), nothing happens at all. Oddly, attempting to add a device from within the Configure page, the logs show that the exclusion process began. Adding from Integrations/Add Integration/Add Z-Wave Device does correctly show as inclusion in the logs, but nothing actually gets added.
I've attempted using 3 totally different devices/device types and manufacturers and even successfully excluded them using Hubitat to make sure to be starting clean but it just spins as though nothing was trying to connect. Then it just times out with no errors. The log only shows that inclusion and exclusion were started and stopped (copied below).
I'm not sure where to go at this point. Without an error message to indicate the problem, it's a bit challenging to know how to fix it. Does anybody have any thoughts or suggestions please?
Log:
2022-11-12T21:42:00.422Z CNTRLR Starting inclusion process with strategy Default...โจ2022-11-12T21:42:00.438Z SERIAL ยป 0x0105004ac10978 (7 bytes)โจ2022-11-12T21:42:00.439Z DRIVER ยป [REQ] [AddNodeToNetwork]โจnode type: Anyโจhigh power: trueโจnetwork wide: trueโจcallback id: 9โจ2022-11-12T21:42:00.441Z SERIAL ยซ [ACK] (0x06)โจ2022-11-12T21:42:00.445Z SERIAL ยซ 0x0107004a09010000ba (9 bytes)โจ2022-11-12T21:42:00.446Z SERIAL ยป [ACK] (0x06)โจ2022-11-12T21:42:00.449Z DRIVER ยซ [REQ] [AddNodeToNetwork]โจstatus: Readyโจcallback id: 9โจ2022-11-12T21:42:00.456Z CNTRLR The controller is now ready to add nodesโจ2022-11-12T21:42:20.572Z CNTRLR stopping inclusion process...โจ2022-11-12T21:42:20.588Z SERIAL ยป 0x0105004ac50a7f (7 bytes)โจ2022-11-12T21:42:20.590Z DRIVER ยป [REQ] [AddNodeToNetwork]
Is the Razberry 7 Pro using the same regional frequency as your other devices?
Does the HA Yellow hardware have any modifications for m.2/PCIe compared to the RPi IO board?
Background: I have installed the HAOS Yellow image to the eMMC of my CM4 using the IO board as temporary solution until the Yellow arrives. Working fine, onboarding is completed. But when I add a NVMe (with an m.2-PCIe adapter) to the PCIe slot on the IO board, HAOS won't boot anymore. The last message the HDMI output is showing, is Starting kernel ..., then it freezes. After removing the NVMe, HAOS can boot again.
Im trying to buy CM4 for Yellow in USA (Hopefully that might come in Jan). Did anyone use RAKwireless?
looks like they have CM4 8gb, but never heard about them
Crowd supply was really good about changing an order, I switched from the PoE to just a normal power supply they responded within a couple of hours and I received the unit last month. As far as crowdfunded projects go they have been pretty good.
you are probably the only one to say that out loud so far ๐
Is there updates for the yellow poe? Is it still on track for Jan?
๐คทโโ๏ธ

"Orders placed now ship Mar 31, 2023."
The question is that, is this only valid for new orders, or valid for all orders?
New orders
What
all new orders. not a portion of them ๐
Unless new order volume exceeds expected Production, then it will of course ship later 
If we are doing semantics
Apparently we are
At least new orders less of wait that if they do arrive in Jan ๐ from an original backer
Hmm, I requested a change of my shipping address and that got processed by CS overnight. Still showing the same shipping date so no delay.
does anyone know where to get compute module 4's? I'm starving over here (USA)
I wish there was a way to disable the eye-searing LED
There is.
Brilliant, how?
I hear december 2023 looks good @weak sable
@wary pivot I converted your message into a file since it's above 15 lines :+1:
ah nice. I suppose it's either or?
Yes. I'd recomment to use the switches and turn them off by an automation on HA start. This way you can still turn them on when needed for troubleshooting.
And you don't need to mess with the OS. ๐
yep get it. In fact maybe I just want to disable the disco at night ๐
To make it more clear, you can make ON refer to the default behavior of the LED. OFF switches it off and ON makes it behave like before
command_off: 'echo none > /sys/class/leds/act/trigger' (and for the others too)
And back on via
activity
command_on: 'echo activity > /sys/class/leds/act/trigger'
heartbeat
command_on: 'echo heartbeat > /sys/class/leds/usr/trigger'
power_led
command_on: 'echo default-on > /sys/class/leds/pwr/trigger'
- I have an automation that switches on and off at sunrise and sunset
I found one on eBay without too great of a markup.
On HA Yellow getting problem installing core_silabs_multiprotocol: error is:
app_version, application_type = await _get_application_version(ctx)
File "/usr/local/lib/python3.9/dist-packages/universal_silabs_flasher/flash.py", line 213, in _get_application_version
raise RuntimeError("Failed to probe CPC")
RuntimeError: Failed to probe CPC
s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1```
Is this addon too beta for Yellow?
They haven't announced the Thread firmware update for the wireless module yet.
Maybe I'm just a bit early
I'd say 2 years for stable yes
atxbyea is optimistic as usual ๐คฃ
I'm a realist you see
Just to confirm, this is a fresh Yellow, no ZHA, Z2M, etc. running?
Nope, it's fresh
Hmm. Can you try powering off the Yellow completely (not rebooting) and then try installing the addon again?
Does ZHA show up as a discovered integration (before installing any addons)?
I'll check after boot
Have a bigger issue now, frontend won't load. At least I had ssh installed
But yeah perhaps its related to ZHA await app.startup(auto_form=auto_form) File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 124, in startup await self.connect() File "/usr/local/lib/python3.10/site-packages/bellows/zigbee/application.py", line 124, in connect self._ezsp = await bellows.ezsp.EZSP.initialize(self.config) File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 106, in initialize await ezsp._startup_reset() File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 97, in _startup_reset await self.reset() File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 126, in reset await self._gw.reset() asyncio.exceptions.CancelledError
Did you try to configure ZHA?
Hmm, that's unusual. What version of HA Core are you running?
I will do a full reset I guess
It should only try to connect to the Yellow's Zigbee radio if you click the "Configure" button on the discovered ZHA integration and go through the setup
arch: aarch64
audio_input: null
audio_output: null
boot: true
image: ghcr.io/home-assistant/yellow-homeassistant
ip_address: 172.30.32.1
machine: yellow
port: 8123
ssl: false
update_available: false
version: 2022.11.2
version_latest: 2022.11.2
watchdog: true```
Interesting. To me, it seems like you may have set up ZHA (or the addon did even though flashing failed)
Yeah, and something totally messed now. ```โ ~ ha core stop
Processing... Done.
Error: Unknown error, see supervisor
โ ~ ha core start
Processing... Done.
Error: Unknown error, see supervisor
โ ~```
I'll do a full reset and start over, but can't do it right now.
What are the logs saying? ha supervisor logs
22-11-16 13:14:12 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-16 13:14:48 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-16 13:15:24 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-16 13:16:00 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-16 13:16:01 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/logs access from a0d7b954_ssh```
I tried to rebuild supervisor
Hm, some tasks seem to be stuck... Maybe a ha supervisor restart fixes it?
I wonder what kind of task that is... Are there more insights further up?
On starting ha core looks like this is the error: services-up: info: copying legacy longrun home-assistant (no readiness notification) s6-rc: info: service legacy-services successfully started 2022-11-16 13:17:52.175 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly 2022-11-16 13:18:02.862 WARNING (MainThread) [homeassistant.setup] Setup of bluetooth is taking over 10 seconds. 2022-11-16 13:18:14.510 ERROR (bellows.thread_0) [bellows.uart] Lost serial connection: SerialException('device reports readiness to read but returned no data (device disconnected or multiple access on port?)') 2022-11-16 13:18:14.523 WARNING (Recorder) [homeassistant.components.recorder.core] Recorder startup was externally canceled before it could complete: 2022-11-16 13:18:14.544 ERROR (Recorder) [root] Uncaught thread exception Traceback (most recent call last): File "/usr/local/lib/python3.10/threading.py", line 1016, in _bootstrap_inner self.run() File "/usr/src/homeassistant/homeassistant/components/recorder/core.py", line 632, in run
I can reset everything pretty easily, didn't do much with this
Starting fresh, I'll let you know without enabling anything else @dusk vortex! Thanks.
Thanks!
Hope everything ok, its been longer than 20 minutes waiting for setup
Lights are still blinking, guess thats a good sign
Heh saved my config, I guess on the nvme. Doesn't start, issue is 2022-11-16 14:55:52.249 ERROR (Thread-3) [pychromecast.discovery] Unhandled exception in worker thread
@random summit I was running into big issues when I tried tackling with the firmware on the yellow. It took multiple resets for me to finally figure out how to do it safe because I am not well versed in this kind of stuff.
@wintry stream I converted your message into a file since it's above 15 lines :+1:
Are there any alternative boards for the yellow I could use in the absence of the unobtainium CM4 modules?
i have a CM4, but the expected delivery time of my yellow was August, now pushed back to the end of January ๐ฆ
I've put my CM4 in a CM4 IO board. But I wasn't able to get the NVMe running with the PCIe slot as data disk. Keeps crashing on boot.
@daring kelp there are clones but they aren't 1:1 swaps
fsck, 2017 mac mini it is!
How do you like it? Working well?
@feral hare I upgraded from an out of date husbz-1 and it's much better, yes
No issues with range in the clear case?
Nope. It's in the basement too
I only have 12 devices though
The first device is probably less than 3 m away though and it's mains powered, so I assume the mesh networking helps
I do have new issues with some zigbee Xiaomi motion sensors but those are pretty old too and one was dropping out before I switched to yellow. Now 2 more are. I've got some linkind on the way to see if there is improvement
I should probably strategically add more mains powered zigbee devices to my setup. Most of that is battery powered sensors
Thanks for letting me know.
I like the idea of an all in one box with no dongles hanging off
Just a single ethernet Poe connection
the dream
I also have problems with the firmware. I followed the instructions, but the following error keeps coming back: โError: Failed to probe running application typeโ
That is probably more an issue of them not changing parents, so if it chose a bad parent it will have continuous issue, I've had zero issues with Xiaomi motion sensors with zigbee2mqtt and cc13/26 the last 3+ years
Hmm not sure. I am not an expert at this but all I can say is make sure you follow the instructions to a T. Also the ls/dev/ttyAMA1 should have had a space. So โls /dev/ttyAMA1โ. I had success also when rebooting the machine and then attempting it right after startup
Make sure ssh is in unprotected mode also
Also on the pip install make sure to wait and let it install the things. It should say some warning message and successfully install of it
@dusk vortex Just an update - was able to get a clean install (had to remove nvme and clear it manually) - started with the Silabs module and the universal_silabs_flasher worked properly. So yes, must have set up ZHA first.
Check ebay, I got one for $120, wasn't too bad of a premium over $90 retail, and I had it in a few days.
I tried it again immediately after booting and followed the instructions exactly, but the same error occurs. I had already noticed and changed the space in "ls /dev/ttyAMA1". SSH also works in unprotected mode. I've tried several things but nothing has helped so far. How can I upload an image here to show the error?
Did you wipe home Assistant?
yes, several times
Also remove any nvme if have eemc rasp pi
My install got corrupted somehow when I did it
Yes, I have already removed the NVME since the first wipe
How did you wipe it? I followed option 2 and plugged it into pc and wiped with rasp pi boot or something like that and then reinstalled it
Gotta move those pins on the inside of device temporarily
DM me a video of it if you can and maybe I can try to help
Make sure you install Home Assistant yellow software not the generic rasp pi software on the boot loader
I tried option 1 (red + blue button) and option 2 (rpiboot), always the same error when flashing
Red and blue button didnโt do anything for me
Let me finish my lecture slides and then we can video chat if want
my english is not good, i write here with translated, but if it still helps you to help me we can video chat
I'll wipe the yellow again in the meantime
Ill be in hangout channel
@twilit wigeon I had to hold down the red+blue button for about 60 seconds before system was wiped.
The instructions say 5 seconds but I didn't see that.
Sorry I mean @wintry stream
Woof, my 8GB ram cm4 was cheaper than that
look here, mr fancy pants having a CM4
part of one's retirement portfolio
Someone on the local Facebook marketplace is selling a Pi Zero W 2 for $100aud
Thatโs like 400% markup
If ever there was a time to offload my 8x Pi Zero Wโs, now would be it
Mmm lead and zinc
Ja
Explains a few things tbh
My retirement fund is complete. CM4, Z-Pi 7 and Google Coral USB accelerator.
If my NVMe would work, the CM4 could temporaryly take over until the Yellow arrives.
You should see my dual tpu in a bifurication specially designed PCB
I'd be happy enough to get the m.2 to PCIe adapter with the NVMe working with the IO board. It is detected with a m.2 to USB Adapter, but the OS crashes in boot when using the PCIe slot. Not even an error message. ๐คฃ
I just dropped my wattage from 220w to 85w, I'm happy with that
How likely is it that I my yellow poe will ship 27 january as it says on the page? Im moving house and really need this for the new house and also for it to be delivered to the right adresse ๐
I wouldn't bet any money on it.
Not at all. I gave up and cancelled my orders.
Hi, can someone please help me to fix the firmware of the Yellow Zigbee?
I think I'm using the Waveshare adaptor and that works fine in the IO board for me.
Are you using the HAOS image for the Raspberry Pi or for Yellow? And is your CM4 the lite or eMMC version? I'm trying to get the Yellow image running with the NVMe as data disk.
Let me know if you figure out a way to complete this. I want to do the same. I have the eMMC version.
Well... today I found some issues on GitHub. Others seem to have problems with the combination eMMC/NVMe too. But I don't know why the Yellow seems to be able and other boards aren't. I'm using a Samsung NVMe, so i guess/hope it's not a compatibility issue.
Wow. I already bought the cm4 module. People seemed a bit negative now.
Not negative. CrowdSupply just have no good track record with their shipment estimations yet.
The best estimated shipping date is: "it will be shipped shortly before you receive it - somewhen"
Alright, thanks
is it possible to use zigbee2mqtt on the yellow using the onboard radio?
the addon doiesnt appear to start atm but maybe im doing something wrong
I know I can use ZHA but the aqara fp1 isnt that well supported
Zigbee2MQTT needs some more parameters.
serial:
port: /dev/ttyAMA1
baudrate: 115200
rtscts: false
adapter: ezsp
thank you I just found that info
but thank you for the reply
much appreciated
hmm that still didnt work for me fails to start
MQTT broker is running and configured correctly?
yeah
What error messages are the logs showing?
had it running using a sonoff usb stick but wanted to use the on board radio didnt really want everything but the fp1 on zha
Exiting...
Zigbee2MQTT:error 2022-11-20 17:22:03: Error: Failure send version:{"type":"Buffer","data":[0,0,1,0,0,8]}
at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:512:23
at Queue.executeNext (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
Is ZHA still running?
damn yeah that could be it
knew I was missing something but couldnt see it for looking lol
The Zigbee module cannot serve ZHA and Zigbee2MQTT at the same time.
yeah i know hence me using the sonnoff but I i forget to get rid of it thank you
in case someone is interested, I successfully got my aoetec z-pi 7 z-wave module to work on the yellow, I was even able to update the firmware directly out of hassos
So the CS page shows the yellow ships with a 12V 2A power supply, but then has a separate 12V 3A supply listed for purchase.
No issue with buying a 3A unit from a 3rd party?
I bought the POE kit, but Iโm unlikely to run it off POE when it arrives
That
... Seems very low for a default psu
Also, Poe > *
Just get an injector until you replace the switch if that is the issue
24w is still higher than the default pi power supply of 5v 3a
Has anybody been so crazy and tested the 2TB Samsung 970 Evo Plus in the Yellow yet? ๐
No but please let me know if it works ๐
I can get one for cheap. But the limiting factor for testing is the PoE Yellow ๐
same except the cheap drive ๐
and the yellow poe
I believe I am using the 1TB and it works
Can't really think of a reason why it wouldn't work.
It has a bigger capacity than the usual NVMe which have already been tested. And in theory the WD ones should work as well. I'm tempted to get one (especially for the price I'm offered), but I also don't want to spend the money if it won't work. ๐
Iโll buy it off you ๐ location?
is a "RPi CM4 - 2GB RAM, 16GB MMC, No Wifi" sufficent for a yellow?
Cause I finally managed to get my hands on one!
@daring kelp that's what it comes with by default
more storage would be good, but you can also add that using an nvme drive
I have an NVME disk sitting here waiting for it ๐
then that will be fine
Excellent, Thanks
Has anyone found a way to run the HASSIO on NVME only. I feel like there has to be a tutorial somewhere online for this kind of thing. I have not had time to search hard for it.
@wintry stream cm4 lite?
Nah I got the CM4 eMMC
Just don't expect installing any larger add-ons
Like vscode
the switch isn't the issue, it's that when i have a power outage i cut power to my PoE switch after 60 seconds to extend UPS runtime
I have a dedicated ups for my Poe switch upstairs, lasts around 30 minutes with a 1400va ups
i think mine is 700va
i get 8-10 minutes out of it
I can extend that out to 40 minutes if I drop the switch
Yikes
well, 35
That's a power hungry switch
yeah
9 cameras, a couple of Pi's and a couple of AP's
2530-24 aruba
I shifted one AP onto a PoE injector so I can maintain a minimal wifi network
How often does power drop? I have 1s blips 5-6 times a year and outages more than 2 minutes maybe once every 5 years
I've had two outrage more than 1h the last 15 years
we're semi-rural, so it's not unheard of
we were offline for a day or two in February this year during the floods
and we've had some hours-long outages on high-wind days when branches take out lines
See this is why you live in urban Australia, no power outages for the last 12 months. Even when the power company warned there might be lol
Yuck neighbours
Just move to Norway, we have them, we just never see them or talk to them
That's what we do here too
I'm in an apartment block and rarely see neighbours and if I do it's just a smile to each other
Maybe pet the dog if they have one
They're great for cheaper living
Only downside is no garden but can live with that
Yeah but you can say that for any place for renting
Yes, renting is never a great idea for anything
Hi! On the web-page it states in the details for the Yellow:
Expansion slot
For NVMe SSDs (M-Key)
..
PCIe x1
Is this accurate? The bundled SSDs are x4. Any insight would be helpful ๐
The CM4 only has a single PCIe lane.
Mechanically it's a standard M.2 x4 slot, electrically it's x1.
M.2 x4 NVMe SSDs need to be able to fall back to x1 (if they follow standards...)
(which most of them do)
Ok! I was not aware of the mechanical vs. electrical specification. There are, however, generations (1, through 4) of each of the x1, x4, x8, x16 (mechanical). Are we perhaps mixing up the terms here?
x1, x4, x8, x16 are the number of lanes. And for PCIe slots, it also defines the mechanical length.
The M.2 (M-Key) always provides x4 lanes.
Per spec, a PCIe device needs to start talking on x1 lane, with Gen 1 PCIe speed, and the negotiate/detect speed as well as lane count.
Thank you for your insight๐๐ผ I was just confused to why it was specifically spelled 'x1' on the details. This cleared that up. There is a myriad of different SSDs out there, and i dis not want to order the wrong type ๐
Just to chip in here for you, as you said "SSD" and you want to be sure to get the right thing:
It is important that you buy not an SSD, but a NVMe or PCIe SSD.
The old M.2 format SSDs which use the SATA protocol will not work
Yes, a NVMe SSD ๐ This one, actually:
https://www.komplett.no/product/1201392/datautstyr/lagring/harddiskerssd/ssd-m2/kingston-fury-renegade-pcie-m2-nvme-ssd-1tb#
While it seems to be a nice top of the line 4th gen pcie nvme, it might not be very cost effective.
I have no idea if that price is good or bad in relation tot he local market.
The CM4 only has a 2nd gen pcie, so it is a good price to performance approach to check out older 3rd gen pcie nvme models, as they should have the same performance on the cm4.
Only thing that comes to mind that might differ is iops (as newer models have higher iops), although I don't know how depended that is on bandwidh too and how relevant to HA performance.
I wouldn't say the yellow would benefit from high performance stuff for 99.9999% of users
I did get 2 nvme (un)used in Norway for the same price recently, 512GB each, and they will probably cover all my needs as OS drives for years to come
HA can run on a Pi with an sd card and have perfectly fine performance for the average person (ignoring reliability parts). A fast nvme drive is overkill
would buy a cheap Sata SSD and a cheap usb adapter
Whereโs my elephant
On its way from the port to the CrowdSupply warehouse.
So it's gonna be 5 more months you say
they should reconsider shipping via elephant
Quiet, or else Hannibal might hear you
Just one more crossing of the Alps.
One screw at a time
Hey, first install of home assistant (yellow). I'm very new. I cannot see any of my devices on the integrations page. I have a Tradfri plug and hue motion sensor. Can't see any of them. My ZHA has a blue configure button, but when I click into it, it says 'Upload a Manual Backup'?? When I try to add integration, like hue, it asks for a bridge, which I don't have, how can I do this without a bridge? Thanks for help.
ZHA (or Z2M) needs to be configured and after that you can add Zigbee devices in it.
How can I configure ZHA if everytime I click configure I only get the option of a backup? Can I revert back to having more than just this option?
Is there already an old ZHA instance from an old backup?
No, that's the thing. I just clicked on it by accident, and now I'm stuck at this point. I have never setup HASS before.
Is ZHA shown as newly discovered or is there also one ZHA as active integration or disabled/ignored?
It says 'Discovered' over it, no sign of any other one.
Have you tried to reboot?
Nope, I will try now.
I reset and now under ZHA when I select 'Configure' it says 'Do you want to setup Yellow'?
The two options I get when I select 'Submit' are 'Upload a manual backup' and 'Erase network settings and form a new network'?
I guess I try the latter?
Yes
yellow PoE still in production?
Has it started production?

@shut cedar any updates on Poe?
Could anyone suggest what setup best to get.
- 2gb ram sounds short for future with multiple extra integrations (unifi, adguard, zwave, Nginx, let's encrypt, wireguard, etc...)
- not sure about eMMC, (long life?)
- ideally POE option.
- housing for entire unit
So where to look for housing & cm4 units when you don't get the base unit
All kits include housing. You can find rpi with https://rpilocator.com/
@sharp coral POE should be shipping January
Has it passed all tests and been signed off?
Yes it has! Production complete, and its on its way to Mouser warehouse. Official update comming soon.
Christmas 2023 is saved!
thats optimistic!
Santa Mouser might be delayed due to... insert reason here
But I'm looking forward to tinkering with the Yellow PoE. I hope the NVMe will work better than with the RPi IO Board.
What problems did you have with the CM4IO board? Poe working for me, just the hat has a whining noise issue.
HA doesn't start, when an NVMe is attached to the IO Board's PCIe.
Hi, I have a Home Assistant Yellow with a CM4. When I try to start the install of the Zigbee Home Automation to connect to the Yellow's Silicon Labs's MGM210P, I get "Failed to Connect" and this from the logs:
No response to 'Command.read_parameter' command with seq id '0x02'
Also, Home Assistant sees the SIlicon Labs Zigbee MGM210P at /dev/ttyAMA0 not /dev/ttyAMA1 such as the Yellow's documentation states.
Other github responses say "update the device firmware." I cannot seem to find how to update the Silicon Labs MGM210P. I am familiar with *nix CLI.
Does anyone have any pointers?
When you try to set up the Yellow, are you clicking the Configure button for the discovered entry?
Have you run the Add-on "Silicon Labs Multiprotocol"?
A guide to revert to the Zigbee-only-firmware:
https://github.com/NabuCasa/silabs-firmware/wiki/Flash-Silicon-Labs-radio-firmware-manually
These yellows seem to be causing a few problems hey
like most places on the net where people gather to talk about products, people having problems with the product are greatly overrepresented in the messages. people having no issues with HA yellow are presumably off complaining about other things elsewhere on the net.
for example, I got my HA yellow a couple months earlier than I expected. I opened up the box to reseat the CM4 (having already seen that troubleshooting step here), installed an NVMe (I knew what to get after seeing people having issues with specific models), booted it up, restored backup (redid the ZHA setup because the new setup completely lost track of which devices were what) and got everything running in the space of perhaps three hours. It's been running problem-free for the last week (my definition of problem-free is perhaps quite a bit looser than others, I guess). I'm grateful to people who have brought up their problems here, because it lets me be warned of problems in advance.
I don't see a "Configure" when I click the "Settings" -> "Devices and Services" -> "Zigbee Home Automation"
Do you already have it set up then?
No, the "Zigbee Home Automation" dialog asking for "Select a Serial Port" shows the /dev/ttyAMA0 - ttyAMA0, s/n: na
Unless you have another Zigbee stick configured, you should be seeing a discovery card in the Integrations list: https://i.imgur.com/KajyTYr.png. For manual configuration, the serial port is /dev/ttyAMA1.
I don't have a /dev/ttyAMA1 listed in my /dev/. I only have a /dev/ttyAMA0 (zero). I'll look into Jorg's link for flashing the Silicon Labs Zigbee radio.
That also relies on being able to connect to /dev/ttyAMA1 so if the serial port isn't being listed, something strange is happening. You're using the Home Assistant Yellow, right?
What version of Home Assistant OS, Supervisor, and Core are you running? You can find that in Settings > About.
If Iโm not wanting to invite the hassle of changing my zigbee coordinator when I migrate to the yellow, can I just plug my current coordinator into a USB extension from one of the USB ports?
Yes, that's the easiest way to do it. From there, migrating is just clicking a button.
I have not read the documentation at all ๐ซ
Anyone get the silicons multi protocol add on to work? Every time I install it my Zha goes haywire and wont stay connected to my devices
Also said cannot find file zigbeed.conf
In what way? Does reverting back to the normal EmberZNet fix the connectivity problem?
Yes it does
Which device specifically? Battery-powered sensors near the coordinator?
All of them
I will get them running and then I restart home assistant and actually what happens is it crashes
Can you message me your Home Assistant debug log after restarting and letting it crash/stop working? You can enable ZHA debug logging with https://www.home-assistant.io/integrations/zha/#debug-logging.
When zha tryโs to run my home assistant loses connection and freezes unless I unplug and replug
Is ZHA still configured to run on /dev/ttyAMA1 when running the Multiprotokoll add-on or is it configured to use the websocket as per documentation?
It connects to the multi-protocol addon over TCP (and the addon itself talks to /dev/ttyAMA1)
Nah I have it running with the web socket
I reverted back to emberznet for now. If I have time next week I will experiment and show you guys the issue.
Hi, i just deploy my new home assistant yellow, but after powered on the LED Green seem blinking 7-8 times and now LED Red and Green always static. How to fix this issue?
7 short flashes: Kernel image not found, 8 short flashes: SDRAM failure
how to fix SDRAM failure?
You can try to completely reinstall the OS. If the SDRAM really is damaged, the CM4 needs to be replaced.
ok, seem like SDRAM is damaged, not able to detect the storage
We also had a case in production of Yellow where a CM4 came with the blinking pattern of SDRAM failure. I don't think that anything can be done if that is the case.
You most likely have to RMA the CM4.
yes, glad i bought 2 CM4
i able to get yellow up now with secondary CM4
and also, i solved by doing option 2 on this article : https://yellow.home-assistant.io/guides/reinstall-os/
Hm, so it was 7 flashes then "Kernel image not found"
8 flashes
I remember I used my phone's camera slow motion function to actually reliably count.
Ah right, you got the other CM4 running.
oh, lol, i count it fast using my naked eyes ๐
EIN ZWEI DREI ! that is not a pi!
But drei is almost pi.
Just off by .14159265...

The only issue I have is not being able to find a CM4 module that isn't a 3month wait to get my hands on
that's an optimistic estimate from what I've seen users saying
Three months? Luxury!
I waited a year
18m being 2nd in the queue with one supplier ๐
laughs in xeon
I ordered 2 from germany and was told they would be shipped by sea... I live on the west coast of Canada...

Because I live on an island of fools (uk, brexit) most of the EU sellers wont ship here ๐ญ
Maybe now is the time to sell all my rpis at scalper prices
You monster ๐
I've got a spare 2GB lite CM4 in Australia that I've been meaning to advertise if that helps anyone here
Has anybody successfully used CM4 alternative with their HA yellow, like the Radxa rock CM3?
Same form factor and board to board connectivity
I have 8x Pi Zero Wโs Iโve been thinking of selling so I can retire early
๐
Haha, true. I would not look to profit though. Just cover my non inflated purchase price + postage.
I bought a pi4 I happened across in a retail store with the intent of reselling for a profit, but I used it to spin up a mastodon server instead
@dreamy plume they are not a 1:1 swap unfortunately
Thanks - good to know


