hassio-addons: Addon doesnt start [Supervisor Installation]

Just pushed 0.3.6. Should be available within 15-20min. Thanks a bunch @MariusHerget for your help.

Closing as working and New issue created by @mesut3000

I am running my Home Assistant on Raspberry Pi 4 hardware, but I am not sure is it an answer to your question.

Ok, then I would suggest waiting until @lolouk44 has validated and tested my solution and then updated the plugin. Hopefully, that fixes it for you aswell 😃

With “Bluetooth Low Energy Monitor” integration i can read from scale, so this means is no problem with bluetooth connection. I hope to fix it because i like this addon.

It was an permission problem of accessing and communicating via the system bus with MQTT and BlueZ. If it works on BLE it is most likely the same issue on your side so just wait a little bit 😉

@MariusHerget discord is probably best: lolouk44#7180

@lolouk44 thanks! Before my first insights: I restarted my server this morning (unrelated to hassio) and afterwards it worked again. Now I did another restart and it stopped working again.

Regarding the log level: On my side it defaults to error in the config after updating, setting it to DEBUG worked fine.

Log

2022-10-10 13:37:02 - Loading Config From Add-On Options...
2022-10-10 13:37:02 - (INFO) -------------------------------------
2022-10-10 13:37:02 - (INFO) Starting Xiaomi mi Scale v0.3.5...
2022-10-10 13:37:02 - (INFO) Loading Config From Options.json...
2022-10-10 13:37:02 - (INFO) Logging Level Set to DEBUG...
2022-10-10 13:37:02 - (DEBUG) MISCALE_MAC read from config: <*****>
2022-10-10 13:37:02 - (DEBUG) MQTT_USERNAME read from config: <*****>
2022-10-10 13:37:02 - (DEBUG) MQTT_PASSWORD read from config: ***
2022-10-10 13:37:02 - (DEBUG) MQTT_HOST read from config: localhost
2022-10-10 13:37:02 - (DEBUG) MQTT_RETAIN read from config: True
2022-10-10 13:37:02 - (DEBUG) MQTT_PORT read from config: 1883
2022-10-10 13:37:02 - (DEBUG) MQTT_TLS_CACERTS read from config: Path to CA Cert File
2022-10-10 13:37:02 - (DEBUG) MQTT_TLS_INSECURE read from config: False
2022-10-10 13:37:02 - (DEBUG) MQTT_PREFIX read from config: miscale
2022-10-10 13:37:02 - (DEBUG) MQTT_DISCOVERY read from config: True
2022-10-10 13:37:02 - (DEBUG) MQTT_DISCOVERY_PREFIX read from config: homeassistant
2022-10-10 13:37:02 - (DEBUG) HCI_DEV read from config: hci0
2022-10-10 13:37:02 - (DEBUG) BLUEPY_PASSIVE_SCAN read from config: False
2022-10-10 13:37:02 - (INFO) Config Loaded...
2022-10-10 13:37:02 - (INFO) MQTT Discovery Setup Completed...
2022-10-10 13:37:02 - (INFO) -------------------------------------
2022-10-10 13:37:02 - (INFO) Initialization Completed, Waiting for Scale...
2022-10-10 13:37:02 - (DEBUG) Using selector: EpollSelector
2022-10-10 13:37:02 - (ERROR) Unable to connect to Bluetooth: [org.freedesktop.DBus.Error.AccessDenied] An AppArmor policy
 prevents this sender from sending this message to this recipient; type="method_call", sender="(null)" (inactive) 
 interface="org.freedesktop.DBus" member="AddMatch" error name="(unset)" requested_reply="0" 
 destination="org.freedesktop.DBus" (bus)

So it definitely looks like a special bug for the supervised Hassio installations. I looked a little bit in the Hassio documentation and found this: https://developers.home-assistant.io/docs/add-ons/presentation/#apparmor

I am not experienced in any Hassio AddOn development or their underlying infrastructure, but it seems that we need an apparmor.txt in the repo with the correct permission settings (maybe something in the direction of this?).

@MariusHerget just pushed 0.3.5, which should be on docker in the next ~10-15min. The new verson adds more logging. Defaults to INFO level, I’d suggest you set it to DEBUG so we get more info (check the doc for more) Also after moving to bleak I realised I had forgotten to take care of multiple HCI interfaces, this has now been restored, in case it was your issue. Let me know how you get on.

due to many breaking changes when bluetooth changed over i had something similar. check the diagnostic file from the bluetooth adapter in devices to see if your mac address is in it, if not, its probably a bluetooth issue before it gets to the addin. my fix was to stop and start the bluetooth device from a putty console

check with service bluetooth status

then bluetooth stop, bluetooth start, bluetooth restart if needed

Can you share your [redacted] config please? I’ve removed the no longer required MISCALE_VERSION, wondering if it’s still in it and maybe stopping the container from running?