My grand plan is to implement Bluetti2MQTT (add-on) first and then upgrade with your ESP32 solution to allow WLAN connectivity. I want to establish a baseline before diving into ESP32 programming.
Since Warhammerkind seems unavailable to ask directly, I hoped for this back door into finding out why I cannot establish BT. I read that many have successfully connected their AC500 so there is hope.
The AC500 never goes out of BT disconnect mode. Not even briefly. It works with the Bluetti app. Both internal and external BT adapters are recognized by HA. I only use one at a time.
I am running HAOS on a standalone old Surface Laptop. I wanted to take advantage of the add-on store (and the laptop was useless for W11). A good repurpose. I did try Ubuntu first with Home Assistant Container and actually had an AC300 talking to HA, but that was on another device that died.
In the Log I read that my AC500 is found.
"Found AC5002308000844715: address B8:D6:1A:BE:5D:2E"
Then it shuts everything off.
"s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped"
Here are excerpts (the beginning and end) of the log:
Add-on: Bluetti to MQTT
MQTT bridge between Bluetti and Home Assistant
Add-on version: 1.4.1
You are running the latest version of this add-on.
System: Home Assistant OS 12.3 (amd64 / generic-x86-64)
Home Assistant Core: 2024.5.4
Home Assistant Supervisor: 2024.05.1
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[19:03:20] INFO: Reading configuration settings...
[19:03:21] INFO: Debug mode is enabled.
[19:03:21] INFO: Starting bluetti-mqtt...
2024-05-23 19:03:22 DEBUG Using selector: EpollSelector
Scanning....
....
End...
2024-05-23 19:03:27 DEBUG received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0): ['org.bluez.Adapter1', {'Discovering': <dbus_fast.signature.Variant ('b', False)>}, []]
Found AC50023080008XXXXX: address B8:D6:1A:BE:XX:XX
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
In the home-assistant log I found this:
WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci1 [BC:83:85:DC:BD:91]: [Errno 110] Operation timed out
2024-05-24 10:10:19.159 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci1 [BC:83:85:DC:BD:91] due to timeout after 5 seconds
2024-05-24 10:20:00.743 ERROR (MainThread) [homeassistant.components.shelly] Error fetching A
My grand plan is to implement Bluetti2MQTT (add-on) first and then upgrade with your ESP32 solution to allow WLAN connectivity. I want to establish a baseline before diving into ESP32 programming.
Since Warhammerkind seems unavailable to ask directly, I hoped for this back door into finding out why I cannot establish BT. I read that many have successfully connected their AC500 so there is hope.
The AC500 never goes out of BT disconnect mode. Not even briefly. It works with the Bluetti app. Both internal and external BT adapters are recognized by HA. I only use one at a time.
I am running HAOS on a standalone old Surface Laptop. I wanted to take advantage of the add-on store (and the laptop was useless for W11). A good repurpose. I did try Ubuntu first with Home Assistant Container and actually had an AC300 talking to HA, but that was on another device that died.
In the Log I read that my AC500 is found. "Found AC5002308000844715: address B8:D6:1A:BE:5D:2E" Then it shuts everything off. "s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped"
Here are excerpts (the beginning and end) of the log:
Add-on: Bluetti to MQTT MQTT bridge between Bluetti and Home Assistant
Add-on version: 1.4.1 You are running the latest version of this add-on. System: Home Assistant OS 12.3 (amd64 / generic-x86-64) Home Assistant Core: 2024.5.4 Home Assistant Supervisor: 2024.05.1
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0 cont-init: info: running /etc/cont-init.d/01-log-level.sh cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [19:03:20] INFO: Reading configuration settings... [19:03:21] INFO: Debug mode is enabled. [19:03:21] INFO: Starting bluetti-mqtt... 2024-05-23 19:03:22 DEBUG Using selector: EpollSelector Scanning....
....
End...
2024-05-23 19:03:27 DEBUG received D-Bus signal: org.freedesktop.DBus.Properties.PropertiesChanged (/org/bluez/hci0): ['org.bluez.Adapter1', {'Discovering': <dbus_fast.signature.Variant ('b', False)>}, []] Found AC50023080008XXXXX: address B8:D6:1A:BE:XX:XX s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped
In the home-assistant log I found this:
WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci1 [BC:83:85:DC:BD:91]: [Errno 110] Operation timed out 2024-05-24 10:10:19.159 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci1 [BC:83:85:DC:BD:91] due to timeout after 5 seconds 2024-05-24 10:20:00.743 ERROR (MainThread) [homeassistant.components.shelly] Error fetching A