Error connecting

[torrespro]

Hi there,

I managed to use the python scripts from Alistair to connect to my robot and send commands. I have the Mac Address and the HA integration find the robot and auto fill in that field also but when I try to add the robot I get an "unknown error".

The only thing I see in the logs is:

`2024-10-22 15:49:07.590 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open with args (PosixPath('/usr/local/lib/python3.12/site-packages/automower_ble/protocol.json'), 'r') inside the event loop by custom integration 'husqvarna_automower_ble' at custom_components/husqvarna_automower_ble/config_flow.py, line 72: (manufacture, device_type, model) = await Mower( (offender: /usr/local/lib/python3.12/site-packages/automower_ble/protocol.py, line 275: with files("automower_ble").joinpath("protocol.json").open("r") as f:), please create a bug report at https://github.com/andyb2000/HACS-husqvarna_automower_ble/issues

2024-10-22 15:58:00.159 ERROR (MainThread) [automower_ble.protocol] [Characteristic] 98bd0003-0b0e-421a-84e5-ddbf75dc6de4 (Handle: 13): Unknown (read,notify), Error: [org.bluez.Error.NotPermitted] Not paired`

Any suggestions where to look for a fix? I tried passing my Pin Code and without just in case, same error both. I also got the robot close to my raspberry pi where the Bluetooth is.

Thanks in advance

[andyb2000]

There are two errors showing up here. The first error "Detected blocking call to open with args" is due to a change in HA itself somewhere like 2024.7.x onwards if you have WARNING logging enabled. It's a feature change to the upstream library that we'd need to take into account.

The second is the true error you're facing which is the not paired message.
You probably just need to keep retrying the pairing, as it's very hit or miss as to getting the BLE proxy to pair and connect to your mower.
Go with the method you used (pin or not) from the command lines and repeat the process several times to get the pairing working. I've not tried/used native bluetooth on the raspberry PI also, so not sure if this may be the issue so an option would be to try the esphome esp32 BLE proxy.