Home Assistant Yellow

Blog
449

Thanks for all the detail @ogiewon. So editing the config.txt was the only change you originally made? And you did that by removing the SSD and mounting it on another computer? I also installed everything on an SSD, so I might just try that. When I asked for “steps” it was this level of detail I was looking for. There’s lots of advice online about how to do this, and some of it conflicts. But our systems are almost identical, and it looks like you’ve been successful, so “I’ll have what you’re having”. :grin:

I enabled the bluetooth integration when it first started up, so I’m thinking I’ll get some errors now if I disable it in config.txt. But I habven’t done much with HA yet, so if I screw it up, I guess I can reinstall it from scratch easily enough.

-Tom

450

Yes, that’s right.

Yes, I removed the NVME drive, installed it in an external USB to M.2 NVME drive enclosure, and the simply plugged it into my Windows PC. I was then able to simply edit the config.txt file using Notepad++.

I would recommend removing the Bluetooth Integration from Home Assistant before starting this procedure. That will at least make sure nothing within HA is trying to use the GPIO pins.

In fact, simply removing the Bluetooth integration may be all that is required if you’re trying to add a Z-Wave radio to the GPIO pins on your HA Yellow. As I mentioned earlier, I am not 100% certain that my edits to config.txt are actually still in place after about 2-3 HAOS upgrades this year.

451

Have the Home Assistant Yellow PoE addition and added a 4G CM4 Lite along with nVME SSD drive.

How does one edit the boot configuration if you cannot simply put an sd-card into the computer?

452

yes

I believe there is also an unofficial add on for this.

1 Like
453

I didn’t edit the boot configuration, nor did I disable BlueTooth.
My ZooZ 800 series GPIO board (ZAC93) is working great and apparently so is BlueTooth.

Perhaps BlueTooth is limited in functionality? However I’ve paired several BT BLE devices, such as light controllers and those are working correctly.

Did an update to HAOS allow for this functionality? Will continue to observe, but no issues with Z-wave switches and dimmers that I have added. I was lead to believe that disabling BlueTooth was necessary by some of the forum posts as well as this instruction guide - ZAC93 800 GPIO Module Installation Guide - Zooz Support Center

If it makes any difference I have Home Assistant Yellow PoE hardware rev 1.3.

1 Like
454

Sorry for replying to this old post but now it took almost 60 days instead of the usual 30 days before HA crashed.
Only the red LED was on and network LEDs, not the yellow one.
I got something from the log anyway.

Welcome to Home Assistant OS 10.5!

[   32.130157] systemd[1]: Hostname set to <homeassistant>.
[   32.136032] systemd[1]: Installed transient /etc/machine-id file.
[   32.499299] systemd[1]: Queued start job for default target Multi-User System                                                                                                      .
[   32.583348] systemd[1]: Created slice Slice /system/ha-cli.
[  OK  ] Created slice Slice /system/ha-cli.
[   32.607302] systemd[1]: Created slice Slice /system/modprobe.
[  OK  ] Created slice Slice /system/modprobe.
[   32.631109] systemd[1]: Created slice Slice /system/serial-getty.
[  OK  ] Created slice Slice /system/serial-getty.
[   32.675371] systemd[1]: Created slice Slice /system/systemd-fsck.
[  OK  ] Created slice Slice /system/systemd-fsck.
[   32.700099] systemd[1]: Created slice Slice /system/systemd-growfs.
[  OK  ] Created slice Slice /system/systemd-growfs.
[   32.723508] systemd[1]: Created slice User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[   32.745383] systemd[1]: Started Dispatch Password Requests to Console Directo                                                                                                      ry Watch.
[  OK  ] Started Dispatch Password …ts to Console Directory Watch.
[   32.768903] systemd[1]: Started Forward Password Requests to Wall Directory W                                                                                                      atch.
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[   32.792868] systemd[1]: Reached target Local Encrypted Volumes.
[  OK  ] Reached target Local Encrypted Volumes.
[   32.812672] systemd[1]: Reached target HassOS zram targets.
[  OK  ] Reached target HassOS zram targets.
[   32.832754] systemd[1]: Reached target Local Integrity Protected Volumes.
[  OK  ] Reached target Local Integrity Protected Volumes.
[   32.856862] systemd[1]: Reached target NFS client services.
[  OK  ] Reached target NFS client services.
[   32.876696] systemd[1]: Reached target Path Units.
[  OK  ] Reached target Path Units.
[   32.896694] systemd[1]: Reached target Preparation for Remote File Systems.
[  OK  ] Reached target Preparation for Remote File Systems.
[   32.920670] systemd[1]: Reached target Remote Encrypted Volumes.
[  OK  ] Reached target Remote Encrypted Volumes.
[   32.940690] systemd[1]: Reached target Remote File Systems.
[  OK  ] Reached target Remote File Systems.
[   32.960616] systemd[1]: Reached target Remote Verity Protected Volumes.
[  OK  ] Reached target Remote Verity Protected Volumes.
[   32.984701] systemd[1]: Reached target Slice Units.
[  OK  ] Reached target Slice Units.
[   33.004711] systemd[1]: Reached target Local Verity Protected Volumes.
[  OK  ] Reached target Local Verity Protected Volumes.
[   33.025525] systemd[1]: Listening on D-Bus System Message Bus Socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[   33.109174] systemd[1]: Listening on RPCbind Server Activation Socket.
[  OK  ] Listening on RPCbind Server Activation Socket.
[   33.132994] systemd[1]: Reached target RPC Port Mapper.
[  OK  ] Reached target RPC Port Mapper.
[   33.162320] systemd[1]: Listening on Process Core Dump Socket.
[  OK  ] Listening on Process Core Dump Socket.
[   33.185757] systemd[1]: Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Audit Socket.
[   33.205381] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[   33.229295] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[   33.252551] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[   33.273189] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[   33.293267] systemd[1]: Huge Pages File System was skipped because of an unme                                                                                                      t condition check (ConditionPathExists=/sys/kernel/mm/hugepages).
[   33.349061] systemd[1]: Mounting POSIX Message Queue File System...
         Mounting POSIX Message Queue File System...
[   33.373431] systemd[1]: Mounting Kernel Debug File System...
         Mounting Kernel Debug File System...
[   33.398791] systemd[1]: Mounting Kernel Trace File System...
         Mounting Kernel Trace File System...
[   33.430992] systemd[1]: Starting Create List of Static Device Nodes...
         Starting Create List of Static Device Nodes...
[   33.459942] systemd[1]: Starting Load Kernel Module configfs...
         Starting Load Kernel Module configfs...
[   33.521506] systemd[1]: Starting Load Kernel Module drm...
         Starting Load Kernel Module drm...
[   33.545401] systemd[1]: Starting Load Kernel Module efi_pstore...
         Starting Load Kernel Module efi_pstore...
[   33.613600] systemd[1]: Starting Load Kernel Module fuse...
         Starting Load Kernel Module fuse...
[   33.630954] fuse: init (API version 7.37)
[   33.652182] systemd[1]: Starting Journal Service...
         Starting Journal Service...
[   33.673266] systemd[1]: Starting Generate network units from Kernel command l                                                                                                      ine...
         Starting Generate network …ts from Kernel command line...
[   33.753166] systemd[1]: Starting Remount Root and Kernel File Systems...
         Starting Remount Root and Kernel File Systems...
[   33.776986] systemd[1]: Starting Coldplug All udev Devices...
         Starting Coldplug All udev Devices...
[   33.841219] systemd[1]: Starting Disk Manager...
         Starting Disk Manager...
[   33.861062] systemd[1]: Starting HassOS ZRAM tmp...
         Starting HassOS ZRAM tmp...
[   33.885412] systemd[1]: Starting HassOS ZRAM var...
         Starting HassOS ZRAM var...
[   33.903478] zram1: detected capacity change from 0 to 65536
[   33.904120] zram2: detected capacity change from 0 to 32768
[   33.947571] systemd[1]: Started Journal Service.
[  OK  ] Started Journal Service.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted Kernel Trace File System.
[  OK  ] Finished Create List of Static Device Nodes.
[  OK  ] Finished Load Kernel Module configfs.
[  OK  ] Finished Load Kernel Module drm.
[  OK  ] Finished Load Kernel Module efi_pstore.
[  OK  ] Finished Load Kernel Module fuse.
[  OK  ] Finished Generate network units from Kernel command line.
[  OK  ] Finished Remount Root and Kernel File Systems.
[  OK  ] Finished HassOS ZRAM tmp.
[  OK  ] Finished Coldplug All udev Devices.
[  OK  ] Finished HassOS ZRAM var.
[  OK  ] Reached target Preparation for Network.
         Mounting FUSE Control File System...
         Mounting Kernel Configuration File System...
         Starting D-Bus System Message Bus...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Finished Create Static Device Nodes in /dev.
[  OK  ] Reached target Preparation for Local File Systems.
[   34.462963] audit: type=1334 audit(1680605724.431:2): prog-id=6 op=LOAD
[   34.470817] audit: type=1334 audit(1680605724.443:3): prog-id=7 op=LOAD
         Starting Rule-based Manage…for Device Events and Files...
[  OK  ] Started Disk Manager.
[  OK  ] Started Rule-based Manager for Device Events and Files.
[  OK  ] Found device /dev/zram2.
[  OK  ] Found device /dev/ttyAMA2.
[  OK  ] Found device /dev/disk/by-label/hassos-overlay.
[   35.018711] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[  OK  ] Found device /dev/disk/by-label/hassos-boot.
[   35.095328] videodev: Linux video capture interface: v2.00
[   35.104732] vc_sm_cma: module is from the staging directory, the quality is u                                                                                                      nknown, you have been warned.
[   35.126366] vc_sm_cma: module is from the staging directory, the quality is u                                                                                                      nknown, you have been warned.
[   35.127010] vc_sm_cma: module is from the staging directory, the quality is u                                                                                                      nknown, you have been warned.
[   35.130766] vc_sm_cma: module is from the staging directory, the quality is u                                                                                                      nknown, you have been warned.
[   35.140868] rpivid_hevc: module is from the staging directory, the quality is                                                                                                       unknown, you have been warned.
[   35.146983] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[   35.167050] i2c-bcm2835 fe205c00.i2c: Could not read clock-frequency property
[   35.173624] rpivid feb10000.codec: Device registered as /dev/video19
[   35.175661] [vc_sm_connected_init]: start
[   35.182644] [vc_sm_connected_init]: installed successfully
[   35.190662] snd_bcm2835: module is from the staging directory, the quality is                                                                                                       unknown, you have been warned.
[   35.200496] bcm2835_mmal_vchiq: module is from the staging directory, the qua                                                                                                      lity is unknown, you have been warned.
[   35.202221] bcm2835_mmal_vchiq: module is from the staging directory, the qua                                                                                                      lity is unknown, you have been warned.
[   35.205283] bcm2835_mmal_vchiq: module is from the staging directory, the qua                                                                                                      lity is unknown, you have been warned.
[   35.234163] bcm2835_v4l2: module is from the staging directory, the quality i                                                                                                      s unknown, you have been warned.
[   35.239619] bcm2835_isp: module is from the staging directory, the quality is                                                                                                       unknown, you have been warned.
[   35.239629] bcm2835_codec: module is from the staging directory, the quality                                                                                                       is unknown, you have been warned.
         Starting File System Check…v/disk/by-label/ha[   35.270118] dwc2 fe9800                                                                                                      00.usb: supply vusb_d not found, using dummy regulator
ssos-boot...
[   35.285928] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[   35.293629] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[   35.309132] dwc2 fe980000.usb: supply vusb_a not found, using dummy regulator
[   35.331237] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev                                                                                                      /video13
[   35.339495] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[   35.346610] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[   35.348394] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /de                                                                                                      v/video14
[   35.361912] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /de                                                                                                      v/video15
[   35.372496] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/                                                                                                      video16
[   35.380429] bcm2835-isp bcm2835-isp: Register output node 0 with media contro                                                                                                      ller
[   35.388042] bcm2835-isp bcm2835-isp: Register capture node 1 with media contr                                                                                                      oller
[   35.395677] bcm2835-isp bcm2835-isp: Register capture node 2 with media contr                                                                                                      oller
[   35.403934] bcm2835-isp bcm2835-isp: Register capture node 3 with media contr                                                                                                      oller
[   35.422844] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[   35.429932] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[   35.464772] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev                                                                                                      /video20
         Starting File System Check…isk/by-label/hassos-overlay...
[   35.496797] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /de                                                                                                      v/video21
[   35.509574] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /de                                                                                                      v/video22
[   35.519600] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/                                                                                                      video23
[   35.527502] bcm2835-isp bcm2835-isp: Register output node 0 with media contro                                                                                                      ller
[   35.535656] bcm2835-isp bcm2835-isp: Register capture node 1 with media contr                                                                                                      oller
[  OK  ] Finished File System Check…dev/disk/by-label/hassos-boot.
[   35.550587] bcm2835-codec bcm2835-codec: Device registered as /dev/video18
[   35.566903] bcm2835-codec bcm2835-codec: Loaded V4L2 image_fx
[   35.580623] dwc2 fe980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM
[   35.588628] bcm2835-isp bcm2835-isp: Register capture node 2 with media contr                                                                                                      oller
[   35.609985] bcm2835-isp bcm2835-isp: Register capture node 3 with media contr                                                                                                      oller
         Mounting HassOS boot partition...
[   35.627873] bcm2835-codec bcm2835-codec: Device registered as /dev/video31
[   35.635040] bcm2835-codec bcm2835-codec: Loaded V4L2 encode_image
[   35.642175] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[   35.643118] cfg80211: Loading compiled-in X.509 certificates for regulatory d                                                                                                      atabase
[   35.657599] dwc2 fe980000.usb: DWC OTG Controller
[   35.664564] dwc2 fe980000.usb: new USB bus registered, assigned bus number 1
[   35.667220] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   35.671804] dwc2 fe980000.usb: irq 41, io mem 0xfe980000
[  OK  ] Mounted Hass[   35.691203] usb usb1: New USB device found, idVendor=1d6                                                                                                      b, idProduct=0002, bcdDevice= 6.01
OS boot partition.
[   35.704610] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=                                                                                                      1
[   35.711907] usb usb1: Product: DWC OTG Controller
         Starting Home Assistant OS Agent...
[  OK  ] Finished File System Check…/disk/by-label/hassos-overlay.
[   35.808358] usb usb1: Manufacturer: Linux 6.1.21-v8 dwc2_hsotg
[   35.814699] usb usb1: SerialNumber: fe980000.usb
[  OK  ] Started Home Assistant OS Agent.
[   35.983825] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio f                                                                                                      or chip BCM4345/6
[   35.994123] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455                                                                                                      -sdio.raspberrypi,4-compute-module-ha-yellow.bin failed with error -2
[   36.011003] hub 1-0:1.0: USB hub found
[   36.015514] hub 1-0:1.0: 1 port detected
[   36.084491] usbcore: registered new interface driver brcmfmac
         Mounting HassOS overlay partition...
[   36.207608] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Q                                                                                                      uota mode: none.
[  OK  ] Mounted HassOS overlay partition.
[   36.232117] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Nov  1                                                                                                       2021 00:37:25 version 7.45.241 (1a2f2fa CY) FWID 01-703fd60
         Mounting Dropbear persistent keys...
[   36.432562] usb 1-1: new high-speed USB device number 2 using dwc2
         Mounting Kernel persistent modprobe.d...
[   36.473153] rtc-pcf85063 6-0051: registered as rtc0
         Mounting Kernel persistent modules-load[   36.482415] rtc-pcf85063 6-00                                                                                                      51: setting system clock to 2023-09-01T16:18:02 UTC (1693585082)
.d...
[   36.498867] systemd-journald[140]: Oldest entry in /run/log/journal/9a0596709                                                                                                      c884517882c3dd5e1a9d75f/system.journal is older than the configured file retenti                                                                                                      on duration (1month), suggesting rotation.
[   36.516722] systemd-journald[140]: /run/log/journal/9a0596709c884517882c3dd5e                                                                                                      1a9d75f/system.journal: Journal header limits reached or header out-of-date, rot                                                                                                      ating.
         Mounting Udev persistent rules.d...
         Mounting Docker persistent user...
         Mounting Dropbear persistent user...
         Starting HassOS overlay setup...
[   36.653285] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, bcd                                                                                                      Device= 1.00
[   36.661539] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   36.661551] usb 1-1: Product: USB 2.0 Hub [MTT]
[  OK  ] Mounted    36.673721] hub 1-1:1.0: USB hub found
;39mDropbear persistent [   36.680098] hub 1-1:1.0: 4 ports detected
keys.
[  OK  ] Mounted Kernel persistent modprobe.d.
[  OK  ] Mounted Kernel persistent modules-load.d.
[  OK  ] Mounted Udev persistent rules.d.
[  OK  ] Mounted Docker persistent user.
[  OK  ] Mounted Dropbear persistent user.
[  OK  ] Finished HassOS overlay setup.
[  OK  ] Reached target Sound Card.
[  OK  ] Reached target Hardware activated USB gadget.
         Mounting NetworkManager persistent system connections...
         Mounting Hostname persistent configuration...
         Mounting Hosts persistent configuration...
         Mounting Timesyncd persistent configuration...
         Starting Retrigger udev rules after user rules mounted...
         Starting Apply Kernel Variables...
[   37.096597] usb 1-1.1: new full-speed USB device number 3 using dwc2
[  OK  ] Mounted NetworkManager persistent system connections.
[  OK  ] Mounted Hostname persistent configuration.
[  OK  ] Mounted Hosts persistent configuration.
[  OK  ] Mounted Timesyncd persistent configuration.
[  OK  ] Finished Apply Kernel Variables.
[  OK  ] Finished Retrigger udev rules after user rules mounted.
[ TIME ] Timed out waiting for device ▒▒dev/disk/by-label/hassos-data.
[DEPEND] Dependency failed for File…dev/disk/by-label/hassos-data.
[DEPEND] Dependency failed for HAOS data disk detach.
[DEPEND] Dependency failed for HassOS data partition.
[DEPEND] Dependency failed for Grow File System on /mnt/data.
[DEPEND] Dependency failed for Docker persistent data.
[DEPEND] Dependency failed for Dock… Application Container Engine.
[DEPEND] Dependency failed for HassOS supervisor.
[DEPEND] Dependency failed for HassOS AppArmor.
[DEPEND] Dependency failed for HAOS swap file.
[DEPEND] Dependency failed for Systemd persistent logging.
[DEPEND] Dependency failed for Flus…Journal to Persistent Storage.
[DEPEND] Dependency failed for HAOS swap.
[DEPEND] Dependency failed for HassOS data resizing.
[DEPEND] Dependency failed for Home…t OS data partition migration.
[  OK  ] Reached target Swaps.
         Mounting Temporary Directory /tmp...
         Mounting Buildroot /var tmpfs...
[  OK  ] Mounted Temporary Directory /tmp.
[  OK  ] Mounted Buildroot /var tmpfs.
         Mounting NetworkManager persistent data...
         Mounting Bluetooth persistent state...
         Mounting Systemd persistent state...
[  OK  ] Mounted NetworkManager persistent data.
[  OK  ] Mounted Bluetooth persistent state.
[  OK  ] Mounted Systemd persistent state.
[  OK  ] Reached target HassOS overlay targets.
[  OK  ] Reached target Local File Systems.
         Starting Load/Save Random Seed...
         Starting Create Volatile Files and Directories...
[  OK  ] Finished Load/Save Random Seed.
[  OK  ] Finished Create Volatile Files and Directories.
         Starting Network Name Resolution...
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
         Starting Docker Socket for the API...
[  OK  ] Listening on Journal Gateway Service Socket.
[  OK  ] Listening on Docker Socket for the API.
[  OK  ] Reached target Socket Units.
[  OK  ] Reached target Basic System.
         Starting Network Manager...
         Starting Configure multigenerational LRU...
         Starting HassOS persists data on bootstate...
         Starting Configure Bluetooth Modems connected by UART...
[  OK  ] Started Input Event Daemon.
         Starting RAUC Update Service...
         Starting RPC Bind...
         Starting User Login Management...
         Starting WPA supplicant...
[  OK  ] Started RPC Bind.
[  OK  ] Finished Configure multigenerational LRU.
[  OK  ] Finished HassOS persists data on bootstate.
[  OK  ] Started RAUC Update Service.
[  OK  ] Started Network Manager.
[  OK  ] Started WPA supplicant.
[  OK  ] Reached target Network.
         Starting Network Manager Wait Online...
         Starting containerd container runtime...
         Starting HassOS Configuration Manager...
         Starting Hostname Service...
         Starting Permit User Sessions...
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started User Login Management.
[  OK  ] Started Home Assistant CLI.
[  OK  ] Started Serial Getty on ttyAMA2.
[  OK  ] Reached target Login Prompts.
[  OK  ] Finished HassOS Configuration Manager.
[  OK  ] Started Hostname Service.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started containerd container runtime.
[  OK  ] Started Configure Bluetooth Modems connected by UART.
[  OK  ] Created slice Slice /system/bthelper.
[  OK  ] Reached target HassOS hardware targets.
[  OK  ] Reached target Multi-User System.
         Starting Raspberry Pi bluetooth helper...
[  OK  ] Finished Raspberry Pi bluetooth helper.
         Starting Bluetooth service...
[  OK  ] Started Bluetooth service.
[  OK  ] Reached target Bluetooth Support.
[  OK  ] Finished Network Manager Wait Online.
[  OK  ] Reached target Network is Online.
         Starting Notify NFS peers of a restart...
         Starting Wait Until Kernel Time Synchronized...
         Starting Network Time Synchronization...
[  OK  ] Started Notify NFS peers of a restart.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Set.
[  OK  ] Finished Wait Until Kernel Time Synchronized.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Discard unused blocks once a week.
[  OK  ] Reached target Timer Units.

Welcome to Home Assistant
pi@raspberrypi3:~ $

it’s unfortunate there are no timestamps, else the issue would be easier to locate.

I believe this part is impotant,

[  OK  ] Finished Retrigger udev rules after user rules mounted.
[ TIME ] Timed out waiting for device ▒▒dev/disk/by-label/hassos-data.
[DEPEND] Dependency failed for File…dev/disk/by-label/hassos-data.
[DEPEND] Dependency failed for HAOS data disk detach.
[DEPEND] Dependency failed for HassOS data partition.
[DEPEND] Dependency failed for Grow File System on /mnt/data.
[DEPEND] Dependency failed for Docker persistent data.
[DEPEND] Dependency failed for Dock… Application Container Engine.
[DEPEND] Dependency failed for HassOS supervisor.
[DEPEND] Dependency failed for HassOS AppArmor.
[DEPEND] Dependency failed for HAOS swap file.
[DEPEND] Dependency failed for Systemd persistent logging.
[DEPEND] Dependency failed for Flus…Journal to Persistent Storage.
[DEPEND] Dependency failed for HAOS swap.
[DEPEND] Dependency failed for HassOS data resizing.
[DEPEND] Dependency failed for Home…t OS data partition migration.
[  OK  ] Reached target Swaps.
         Mounting Temporary Directory /tmp...

however, later on, the system is able to mount /tmp and /var, so not sure why it crashes.
I think, I need to replace my SSD :frowning:

455

Mhm, yes, this looks like a failure during boot (not being able to mount the filesystems), might be a bad SSD. Its definitely different from what I experienced with the SSD suddenly being unavailable mid-operations.

1 Like
456

the strange thing is that the last boot was over a week ago,
anyway I will try replacing the SSD

now I’m using a samsung 980 (non pro)
but in the FAQ “Samsung 970 EVO Plus” is suggested, So I will try that one.

457

Ordered my Yellow 4th Feb, still no delivery or notification of any kind. Anyone know how to check on delivery progress?

458

Where did you order it from? Which version did you order?

There are models (without the CM4 module) readily available at Crowd Supply.

CM4 modules have been showing up in stock at various sites more frequently. Check out https://rpilocator.com/ to find one near you.

459

Ordered thru Crowd Supply with the CM4.

460

I have Yellow with CM4 Wi-Fi/Bluetooth on order. I want to add a Z-Wave controller board to the GPIO
Should I select a Z-Wave.Me RaZberry 7 Pro, Zooz 800, or Aeotec Z-Pi 7.

461

I have the ZOOZ 800 SERIES Z-WAVE LONG RANGE GPIO MODULE, which is available direct from Zooz for ~$12 USD. This is significantly less expensive than either of the other two choices, and is using Silicon Labs latest 800 series Z-Wave Radio. I have one installed on my HA Yellow, and it seems to work fine with Z-Wave JS UI. I have only used it for some simple testing of older Z-Wave 500 series GE/Jasco switches, which worked fine. I have no long-term ‘production’ experience with using it for a large Z-Wave network.

For the price, it is definitely worth trying, IMHO.

1 Like
462

Thanks.
Does your Yellow have a CM4 with Wi-Fi and Bluetooth? I’ve seen conflicting information that Bluetooth must be disabled for the Z-Wave modules to work. Some info indicated that BT used the same UART as the one on the GPIO header and must be disabled, and other info said it works fine on Yellow. It may be that the BT problem is only on RPi’s, and not Yellows. It’s not clear to me

463

Yes, my CM4 has wireless radios. I am not using the WiFi nor the Bluetooth radios, though. If you read further up the this thread, you’ll find some of my earlier posts where I describe how I originally did disable the Bluetooth radio on the CM4 based on the Zooz documentation. However, like you, I am not convinced that it really needed to be disabled. Wish I could provide a better answer, sorry.

464

I’ve the Samsung 970 Evo Plus and it’s been working very well for me. Not sure the difference in the newer Samsung nVME drives that might be causing this issue.

1 Like
465

I also have the Zooz 800 ZAC93LR GPIO module. Was extremely easy to install. You don’t need to disable anything. Leave Bluetooth alone, etc.

1 Like
466

thanks, I was hoping someone had some good experience with it,
I have already ordered a “Samsung 970 Evo Plus 1TB” but something went wrong so I have to wait a few days longer :slight_smile:

1 Like
467

I was about to cancel the order with cm4 from crowdsupply since the other suppliers have stock. Ordered in January, eta 31st of August. After contacting apparently they expect to ship in about two weeks from now so I guess I’ll wait on that anyway.

Communication has been very poor on this,or actually non existent since there was no update from home assistant since February…

1 Like
468

Probably busy on the next device, the Green.

1 Like