Hello, just installed a fresh new HA supervised straight from OOWOW. It runs HA 2023.10.5 on kernel 5.4.180
I still have this running error :
Failed to start Bluetooth: [org.freedesktop.DBus.Error.ServiceUnknown] The name org.bluez was not provided by any .service files; Retrying in background...
I installed the terminal an SSH add-on to try your fix, but it seems to be a wrong way as sudo is not recognized. I think my mistake is trivial, but can you help me to get control of HA.
Hello,
I gave up with ssh and plugged a keyboard and a TV to the khadas. The bluetooth is now OK with your commands. I had to do some sudo apt-get update and apt-get upgrade to make it run without errors on a fresh install from oowow.
Given this, HA is now running fine. I had some problems with integrations and since the bluetooth is fixed, i could add them to my set.
My project is to migrate from my old raspberry pi 3 because it is is short in memory. I plan to move also from ZHA to Zigbee2MQTT with the MQTT broker and Zigbee2MQTT on a VM
I had a little look at the host log and discoverd this running error
Nov 08 06:34:07 Khadas systemd-journal-gatewayd[39563]: microhttpd: Setting TCP_NODELAY option to ON state failed: Operation not supported
Nov 08 06:34:07 Khadas systemd-journal-gatewayd[39563]: microhttpd: Setting TCP_CORK option to OFF state failed: Operation not supported
Nov 08 06:34:07 Khadas systemd-journal-gatewayd[39563]: microhttpd: Failed to push the data from buffers to the network. Client may experience some delay (usually in range 200ms - 5 sec).
I googled it and it seems to be an issue with Debian 11.
According to HA,I am running run the supervisor-2023.11.0.
Any fix to this ?
I was trying to figure out why my attempt to Add network storage via NFS did not work (my raspberry on the same network can with the same settings / the NFS rules on my NAS are wide open (192.168.0.0/24).
Mounting KhadasBackup did not succeed. Check host logs for errors from mount or systemd unit usr-share-hassio-mounts-KhadasBackup.mount for details.
After a long time and a reboot, it’s gone. Don’t ask me how
And here is the log about mounting NFS :
Nov 08 18:20:28 Khadas systemd[1]: Mounting Supervisor nfs mount: KhadasBackup...
Nov 08 18:20:28 Khadas mount[5136]: mount: /usr/share/hassio/mounts/KhadasBackup: unknown filesystem type 'nfs'.
Nov 08 18:20:28 Khadas kernel: request_module fs-nfs succeeded, but still no fs?
Nov 08 18:20:28 Khadas systemd[1]: usr-share-hassio-mounts-KhadasBackup.mount: Mount process exited, code=exited, status=32/n/a
Nov 08 18:20:28 Khadas systemd[1]: usr-share-hassio-mounts-KhadasBackup.mount: Failed with result 'exit-code'.
Nov 08 18:20:28 Khadas systemd[1]: Failed to mount Supervisor nfs mount: KhadasBackup.
Hello,
I have the same problem with bluetooh.
I followed instructions in terminal & ssh but I have no password. I created it by typing passwd but now I have "permission denied (publickey.password).
Needless to say that I am newbie.
Thanks for your help.
I’m not sure where the limitation lies, however you can’t move data disk within HA, to an external drive with this device/image. The only solution for now is to use an external drive/SD card as a boot drive
Hello, thank you for your response. Can you please specify the steps or provide a link to a tutorial on using an external drive as a boot drive for the Khadas?
I downloaded armbian file for vim1s : Armbian_24.8.1_Khadas-vim1s_bookworm_legacy_5.15.137-homeassistant_minimal.oowow.img.xz
In oowow, I needed to disable “vim1s only” file type, to view image.
After installation, system created an error and stayed on initramfs
“failure file system check of the root”
cannot boot mmcblk0p1
oowow didn’t work anymore, and sd card boot wasn’t active.
after many tests, i used Aml_USB_Burn_Tool, and succeed in restoring an image mmc compatible : “vim1s-ubuntu-24.04-server-linux-5.15-fenix-1.7-240926-emmc.img”
I recovered oowow and restored debian 11 ha, the only ha proposed by oowow.