I did a quick test yesterday using Z-WaveJS on my Yellow, with the Zooz 800 series Z-Wave radio module. I made sure that I first edited the operating system’s ‘config.txt’ to disable my CM4 onboard Bluetooth. This was mentioned on the Zooz website for this module. I did not test it prior to disabling Bluetooth. Z-WaveJS discovered the device without issue. I was able to pair an old GE/Jasco in-wall Z-Wave switch, without any issues. This was a very old Z-wave (non Plus) model switch. It worked fine. Not a very extensive test, but better than nothing.
I really do not use Z-Wave currently, but it is nice to have the option! A few years ago, I replaced all of my Z-Wave switches and dimmers with Lutron Caseta switches, dimmers, fan controllers, and pico remotes. The Lutron system has been 100% reliable and performs very quickly.
My Yellow PoE arrived today (just finished opening the box) which is fantastic, but its a glorified paperweight until the CM4 that I ordered in April finally arrives
Hello @bacco007, congrats!!. When did you order your yellow? I ordered mine on Nov, 29 2022 with originally estimated to ship on Jan 27, 2023 and it has been delayed recently to March, 03!
If I don’t need onboard WiFi on the CM4 is it better to use a USB Bluetooth dongle than opt for the module with WiFi/Bluetooth? I’m presuming a separate Bluetooth device might offer better range?
I would tend to agree with the above assumption. Really no need to get the WiFi and Bluetooth (aka “Wireless”) features on the CM4. When I bought my CM410832, I figured I would get the top of the line CM4 to future proof things a bit. Turns out, trying to edit “config.txt” on HAOS in order to disable the Bluetooth to allow the 10 pin RPi GPIO header to work with other devices is a tedious task. Fortunately for me, I installed HAOS 100% on a NVME SSD. This allowed me to simply remove the SSD, attach it to a USB enclosure, and then edit “config.txt” using my MS Windows PC. This was much simpler than trying to edit that file if it was on the eMMC. It is still doable, but a little more work.
I would tend to agree with this as well. The recent addition of Bluetooth Proxies essentially solves a few problems, IMHO. It allows BT radios to placed strategically throughout one’s house, significantly improving BT coverage/range. It also eliminates the need to find a CM4 with “wireless” features.
My Yellow is in a remote location of my home, so having BT onboard is really not very helpful. YMMV, of course.
Well, I received my Yellow PoE Kit in January 2023, as was mentioned in the December 2022 update. So, seems pretty legit to me. I ordered it in September 2021, during the initial Crowd Supply funding campaign. So, for those who ordered over a year later…patience please… It was worth the wait!
The project updates all along have been a joke. When I ordered in August, the most recent update stated “we are shipping” and did not indicate that new orders would have to wait months for future production batches to be completed.
I thought I was ordering with plenty of time to spare to get Home Assistant up and running before SmartThings shut down Groovy and Webcore. Now I’m sitting on a load of broken automations with no end in sight…
Hello,
I have my yellow running since Jan 4th,
and for the 3th time now without any reason it suddenly stopped working.
I can’t see in the log what is wrong, because the last couple of minutes are missing, probably because of the file write delay.
the first two times I didn’t pay attention either, actually the first time I thought it was the esphome build, but now HA crasht at 5:35 AM. I was a sleep, and HA wasn’t actually doing much and I use the original power supply. So in my case I don’t think it has to do with high power demand.
So not sure. I didn’t check the blinking pattern to be honest.
Are you sure it is not DB who is causing it? at night DB does some stuff and for me while I had raspberry + SSD it was causing crashes because of insufficient power.
That could be, but it can be any kind of thing, software or hardware,
and hardware can be the HA yellow, RPI CM, SSD, zigbee stick or usb drive.
for now I removed the key which opens port 22222 and hope it has something to do with that, haven’t had the issue since.
but as not many people have this issue, I’m now thinking it might be an issue with ssd drive. But I don’t know how to proof this.
You’ll almost certainly have better luck with a High performance bluetooth adapter on a USB extension cable or a bluetooth proxy vs the onboard bluetooth.
