There are posts claiming otherwise, perhaps post an issue if it is not working for you.
Well when I bought them they had the old firmware and that didn’t work at all.
Already did. Could you please point me to these posts?
Edit: Never mind, found some.
Replying to myself. Samsung 980 500GB works!
➜ ~ dmesg | grep nvme [ 1.212386] nvme nvme0: pci function 0000:01:00.0 [ 1.212541] nvme 0000:01:00.0: enabling device (0000 -> 0002) [ 1.221640] nvme nvme0: Shutdown timeout set to 8 seconds [ 1.237086] nvme nvme0: allocated 64 MiB host memory buffer. [ 1.609890] nvme nvme0: 4/0/0 default/read/poll queues [ 1.650561] nvme0n1: p1 [ 54.713438] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: commit=30. Quota mode: none. [ 54.828654] EXT4-fs (nvme0n1p1): resizing filesystem from 7455483 to 122096384 blocks [ 55.614051] EXT4-fs (nvme0n1p1): resized filesystem to 122096384 ➜ ~ lspci -nnvv -s 01:00.0 01:00.0 Non-Volatile memory controller : Samsung Electronics Co Ltd Device [144d:a809] (prog-if 02 [NVM Express]) Subsystem: Samsung Electronics Co Ltd Device [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- Latency: 0 Interrupt: pin A routed to IRQ 46 Region 0: Memory at 600000000 (64-bit, non-prefetchable) [size=16K] Capabilities:  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:  MSI: Enable- Count=1/32 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities:  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=13 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 Kernel driver in use: nvme
Oh ok. that ain’t good. In fact I have a bunch of Miflora sensors which I connect via Plantgateway running on a Pi Zero and another Pi. It works generally well but I was planning to move to the BT Proxy solution soon because then I don’t have to deal with the MQTT workaround and can connect them directly to HA. Also what is annoying that when you restart the HA it takes quite a while until the plant gateway sends data again (if you don’t trigger manually). I guess I will try it and see if it works as I already have the ESPs lying around.
@hesspoint Interresting, didn’t know that this existed. I personally use MQTT quite a lot, especially for my Zigbee network. So that wouldn’t bother me at all, perhaps I’ll try this as well.
Feel free to get back with an update on how your BT proxy experience was/is.
Hi Jump, just started using my Yellow, great device. The problem I have is that the zigbee radio seems very weak. Only works at a 2-3 meters. When I plug in the sonoff zigbee stick I get range of 15 m
Ouch that’s not good. I have an external antenna on my ZigBee stick too. Hopefully it’s possible to modify the home Assistant SkyConnect to extend the range.
Same here , terrible connections , am using a conbee II now, works fine
@nickrout what external antenna? Didn’t know it is an option
Then read this thread, I only heard about it in this thread.
@nickrout if you mean CM4 external antenna, I don’t think you can use it for zigbee
Y’know I think I was confused over the antenna.
The pics on crowd supply some some headers near the zigbee chip, maybe worth investigating.
Has anyone designed a wall mount option yet?
When will this thing be available? 2055?
@sygys I believe that is the best estimate so far
I see that there is an antenna plug next to the zigbee radio, I will try connecting an external one to this
No, I was looking at the picture of the board, when I checked my board it has no plug
But perhaps a place to solder one?