Estimation for shipment is still October 14th. No update and no tracking number received.
How difficult can it be to send a simple status update?
3 Likes
Oh wow. I thought the +7 days when the date is passed would be automatic. I guess not and someone forgot to update it this time.
2 Likes
I share you frustration, communication is sub par and spotty at best.
For what it’s worth, my order status was changed to “Actually shipped on Oct 13, 2022” on the 14:th and later on the 14:th I received an actual e-mail with the status update. FedEx tracking also states that FedEx received the package on the 13:th.
Seems like Crowd Supplys logistics and communications is anything but working and more like a lottery.
1 Like
It seems nvme support on Yellow Kit is very weak. This kit cannot initialize 2 of my spare drives. Is there known compatible nvme drive list?
Samsung 960 Evo 250GB:
➜ ~ dmesg | grep nvme
[ 1.194766] nvme nvme0: pci function 0000:01:00.0
[ 1.194921] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[ 31.697903] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0
[ 31.705009] nvme nvme0: Removing after probe failure status: -19
➜ ~ lspci -nnvv -s 01:00.0
01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 [144d:a804] (prog-if 02 [NVM Express])
Subsystem: Samsung Electronics Co Ltd SM963 2.5" NVMe PCIe SSD [144d:a801]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 46
Region 0: Memory at 600000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L1 <64us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s (downgraded), Width x1 (downgraded)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS- TPHComp- ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled,
AtomicOpsCtl: ReqEn-
LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1-
EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
Retimer- 2Retimers- CrosslinkRes: unsupported
Capabilities: [b0] MSI-X: Enable- Count=8 Masked-
Vector table: BAR=0 offset=00003000
PBA: BAR=0 offset=00002000
Capabilities: [100 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [148 v1] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [158 v1] Power Budgeting <?>
Capabilities: [168 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Capabilities: [188 v1] Latency Tolerance Reporting
Max snoop latency: 0ns
Max no snoop latency: 0ns
Capabilities: [190 v1] L1 PM Substates
L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
PortCommonModeRestoreTime=10us PortTPowerOnTime=10us
L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
T_CommonMode=0us LTR1.2_Threshold=25600ns
L1SubCtl2: T_PwrOn=10us
Plextor M8PeGN 512GB:
➜ ~ dmesg | grep nvme
[ 1.194958] nvme nvme0: pci function 0000:01:00.0
[ 1.195112] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[ 66.525017] nvme nvme0: I/O 16 QID 0 timeout, completion polled
[ 127.964946] nvme nvme0: I/O 12 QID 0 timeout, completion polled
[ 189.405062] nvme nvme0: I/O 17 QID 0 timeout, disable controller
[ 190.164955] nvme nvme0: Removing after probe failure status: -19
➜ ~ lspci -nnvv -s 01:00.0
01:00.0 Non-Volatile memory controller [0108]: Lite-On Technology Corporation M8Pe Series NVMe SSD [14a4:22f1] (rev 01) (prog-if 02 [NVM Express])
Subsystem: Marvell Technology Group Ltd. Device [1b4b:1093]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 46
Region 0: Memory at 600020000 (64-bit, non-prefetchable) [size=16K]
Expansion ROM at 600000000 [size=128K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L1 <64us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s (downgraded), Width x1 (downgraded)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR+
10BitTagComp- 10BitTagReq- OBFF Via message, ExtFmt- EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS- TPHComp+ ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled,
AtomicOpsCtl: ReqEn-
LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1-
EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
Retimer- 2Retimers- CrosslinkRes: unsupported
Capabilities: [b0] MSI-X: Enable- Count=19 Masked-
Vector table: BAR=0 offset=00002000
PBA: BAR=0 offset=00003000
Capabilities: [100 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn+ ECRCChkCap+ ECRCChkEn+
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [148 v1] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [158 v1] Power Budgeting <?>
Capabilities: [168 v1] Alternative Routing-ID Interpretation (ARI)
ARICap: MFVC- ACS-, Next Function: 0
ARICtl: MFVC- ACS-, Function Group: 0
Capabilities: [178 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Capabilities: [2b8 v1] Latency Tolerance Reporting
Max snoop latency: 0ns
Max no snoop latency: 0ns
Capabilities: [2c0 v1] L1 PM Substates
L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
PortCommonModeRestoreTime=10us PortTPowerOnTime=10us
L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
T_CommonMode=0us LTR1.2_Threshold=25600ns
L1SubCtl2: T_PwrOn=10us
1 Like
One hard lesson learned is don’t use a WLAN connected ZBridge. Really, just don’t.
Hint: click the links above and read the reports BEFORE buying a ZBridge!
As said in several threads already, the best part of my Sonoff ZBBridge device was smashing into small pieces with a large hammer! 
Hint: Flash a different firmware and re-use the ZBridge as a Zigbee mesh router (not as a coordinator) to reduce landfill.
Even after flashing the ZBridge with two different Tasmota firmware blobs, the EZSP (EmberzNet Serial Protocol) will break randomly over 2.4G Wi-Fi and disconnect the Zigbee bridge from ZHA. Wired Ethernet Zigbee devices exist that may be more stable if you really can’t get USB to work (e.g. virtualisation troubles).
Hint: To get more range, add more mains Zigbee devices to the mesh, not a remote coordinator (Zigbee a mesh, unlike Bluetooth Low Energy).
2 Likes
Is your Device not ready log from initial installation?, or after “Move datadisk” please?
My 980 works fine, but was installed via “Move datadisk” as the hass-data partition only. Early discussions might suggest initial installation (e.g. CM4 Lite) is more troublesome. There might also be some some issues caused by trying the generic RPi4 image, rather than the Yellow specific one. The reality is we’re all still finding out!
The list I’ve seen of M.2 SSD known working are:
1TB Samsung 970EVOPlus M.2 SSD (press images - likely Frenk’s test device, 1TB waaay big for general use)- 250GB Samsung SSD 980 NVMe M.2 (was the smallest in-stock at Amazon, several users datadisk and boot)
250Gb Samsung 960EVO - Your Device not ready; aborting initialisation
Any more to add? (new thread perhaps?)
I’ve not seen a full list (sadly, the data sheet just says “2230/2242/2260/2280”), but there are a couple of Yellow threads discussing NVMe M.2 SSD installation.
1 Like
Is your Device not ready log from initial installation?, or after “Move datadisk” please?
My 980 works fine, but was installed via “Move datadisk” as the hass-data partition only. Early discussions might suggest initial installation (e.g. CM4 Lite) is more troublesome (and use the Yellow specific, not the generic RPi4 image).
The list I’ve seen of M.2 SSD known working are:
- 1TB Samsung 970EVOPlus M.2 SSD (press images - likely Frenk’s test device, 1TB waaay big for general use)
- 250GB Samsung SSD 980 NVMe M.2 (was the smallest in-stock at Amazon, several users)
I’ve not seen a full list (data sheet just says “2230/2242/2260/2280”), but there are a couple of Yellow threads discussing NVMe M.2 SSD installation.
I’d also suggest voting for the WTH Yellow discussion category to help find posts.
I´m using the Zig Star LAN Gateway, is very stable 
I bought a brand new crucial NVMe which installed fine via the “Move Datadisk”. Crucial P3 500GB M.2 PCIe Gen3 NVMe Internal SSD model CT500P3SSD8.
1 Like
I had severe issues with a Crucial P2 250GB M.2 SSD NVMe, even without any partion on it the Yellow would not boot.
When the NVMe was removed the Yellow boot without issues. To continue troubleshooting a got a brand new Samsung NVMe SSD 980 (256 GB) and after installation the issues disappeared.
Even moving the datadisk from the GUI went without issues and until now the Yellow works and boot as expected.
The NVMe specs “2230/2242/2260/2280” apply to the length of the SSD.
1 Like
I’ve got a 1 TB Samsung 980 working as the only disk (now with the correct HAOS image). Manual install though, as I didn’t want to have the OS in eMMC and I’ve got a non-lite CM4.
You planned for future growth 
My order is just postponed until the October 21. So I’m actually wondering if they will postpone this on a weekly basis till somewhere in January.
1 Like
It is not a surprise anymore that the shipment date postpone week by week.
How difficult can it be to send a small update when we can expect the Yellow.
Can I expect to receive the Yellow before November?
3 Likes
I installed HA on CM4’s eMMC without any issues and then wanted to add SSD as data disk as I need quite a space before I migrate from VM on my workstation to dedicated hardware. Currently 40GB of history I want to preserve.
Yep, mine rolled over to the 21st as well… Hopefully the hardware was designed better than the logistics or customer service, which are both absolute embarrassments. Completely disrespectful that no one can take the time to say either; “don’t worry, if you have an Oct ship date you will be getting your Yellow soon,” or “sorry, we effed up our inventory count, and your Yellow will now be in the next batch.”
When did you order the Yellow?
I’ve sent them also a status request mail. I ordered my Yellow at the end of May.
I’m not happy anymore and very disappointed in the way they communicate. It looks like we have to wait 3-4 months before the new batch arrives. I got this answer a minute ago:
Hello,
Thanks for contacting Crowd Supply! So from the creators recent update, Home Assistant Yellow - Yellow and Yellow Kit are shipping & Yellow Kit with PoE passed tests | Crowd Supply, the first batch only included the first 1046 units of home assistant and 1000 of the yellow kit, and that the PoE version is not shipping yet.
From what they have told us, we can expect the next batch of units to ship in January 2023. Apologies if my statement from a previous support ticket got your hopes up for an earlier shipment time, we can only provide info to customers with the info we are given at that given time from the creators. If you do not wish to wait that long, we can always cancel your order and refund as well.
Regards,
Tanner
Regards,
Crowd Supply Support
Got a project in the works? Launch with us.
Any other questions about Crowd Supply? Check out our Guide.
but when you login it says ?
Estimated to ship:
Oct 21, 2022
that would be really odd and contradictory
