sure!
So, if the device isn’t getting discovered, then the problems are confined to:
- the custom component isn’t getting loaded at all (should be able to tell from the log)
- bluetooth not working for some reason
- everything is working, but the chlorinator uses a different service UUID to mine
I know for sure @Mikkaat’s UUID is the same as mine (Viron Astral Pool ChlorinatorGo integration - #13 by Mikkaat). @xarmoda, you may wish to install “nRF Connect” on you phone and look to see what your chlorinator is advertising (and for that matter, what the signal strength is like where your HA bluetooth adapter is located).
1 Like
This is the kind of stuff we want to be seeing in the log file:
2023-03-20 09:28:03.946 INFO (MainThread) [homeassistant.setup] Setting up bluetooth
2023-03-20 09:28:10.224 INFO (MainThread) [homeassistant.setup] Setup of domain bluetooth took 6.3 seconds
2023-03-20 09:28:52.172 INFO (MainThread) [homeassistant.setup] Setting up bluetooth_adapters
2023-03-20 09:28:52.173 INFO (MainThread) [homeassistant.setup] Setup of domain bluetooth_adapters took 0.0 seconds
if you are using a ESPHome proxy:
2023-03-20 09:28:53.690 INFO (MainThread) [aioesphomeapi.reconnect_logic] Successfully connected to esp32-bluetooth-proxy-15185c @ 192.168.1.54
roger that. i was thinking maybe the fanless case i have on my RPi might interfere with the BT range.
@xarmoda, interesting. -89 dBm is borderline. -100 it’s amazing your phone was able to detect that at all.
Probably a huge PITA, but you could experiment with temporarily locating your RPi somewhere optimal.
Another line of enquiry to follow:
In your bluetooth adapter device:
Hit the download diagnostics button:
Within, you can search for what devices your bluetooth adapter has discovered:
"discovered_devices_and_advertisement_data": [
{
"name": "POOL01",
"address": "EF:1B:FD:4A:38:44",
"rssi": -85,
"advertisement_data": [
"POOL01",
{
"1095": {
"__type": "<class 'bytes'>",
"repr": "b'\\x01\\x04\\x00\\x01\\x00\\x00\\xaa\\x10QK\\x8c\\xd8\\xb0e\\x05\\t\\x01\\x02\\x02\\x00'"
}
},
{},
[
"45000001-98b7-4e29-a03f-160174643001"
],
-127,
-85,
[]
P.S. My RPi doesn’t have a remote chance of being in range.
I use an ESP32 board, configured with ESPHome bluetooth proxy.
Disclaimer: I have never tested connecting with the RPi built in bluetooth.
1 Like
will test RPi on bench in full view of filter. my pool filter is literally only 10m away from the cabinet where i keep my HA RPi. albeit behind a brick wall, and as mentioned I have a fanless case that is effectively a huge chunk of aluminum. so who knows.
one of the first things i looked at was the bluetooth diagnostics. couldn’t see anything interesting in it at all.
Apologies for the delay in my response, have been extremely busy with family stuff.
I have not added the bluetooth: to my config (yet, unless you tell me to after this information…) as I already have the bluetooth integration successfully running with a SwitchBot.
I have just downloaded the diagnostics .txt file as you have described above and can see my chlorinator in the file and can even see the UUID you have mentioned.
"/org/bluez/hci0/dev_D5_7D_B7_06_22_D0",
{
"Address": "D5:7D:B7:06:22:D0",
"AddressType": "random",
"Name": "POOL01",
"Alias": "POOL01",
"Paired": false,
"Trusted": false,
"Blocked": false,
"LegacyPairing": false,
"RSSI": -85,
"Connected": false,
"UUIDs": [
"45000001-98b7-4e29-a03f-160174643001"
],
"Adapter": "/org/bluez/hci0",
"ManufacturerData": {
"1095": {
The integration is still not auto discovered and I am still not able to add manually. Happy to DM you my whole txt file if you want.
Next step for me is to add the bletooth line then create a bleutooth proxy device.
Will keep you updated.
thanks
m
@pbutterworth Update:
I have configured and added a bluetooth proxy to my environment. No chlorinator discovered after 30 mins. Checked the diagnostics file again and it looks the same.
I have added bluetooth: to my configuration.yaml file, rebooted, waited another 30 mins and no chlorinator discovered. Checked the diagnostics file again and it looks the same.
Screenshot of my ESPHome Logs for the bluetooth proxy esp32 device (MAC and SSID blanked out)
I have also tried to add the integration manually with the same result as before.
The ESP is sitting within one foot of the chlorinator. I will leave this running all night to see if it discovers…
I’m going to install an add-on that integrates my Bluetooth barbecue thermometer just to double check the Bluetooth side of things on my RPi.
@Mikkaat helped me find a bug with the version that I had pushed to github.
I’ve fixed it and pushed changes to github.
Please grab the latest, overwrite the old and try again.
1 Like
installed. i’ll let you know how i go.
We have action. Looks awesome… Will test it out over the next few days and report my findings…
Great work
Update: For some reason All of the entities became unavailable after posting this morning, and then when I went to Reload the integration, a message popped up and stated “to finish reloading the integration, please reboot”. I rebooted and they did not come back, so I then deleted the integration and re-added and they all came back.
Thought I might test my BT while I was at it, so i disconnected my Bleutooth Proxy ESP32. The entities became unavailable again. I rebooted HA and they did not reattach. I deleted the integration, rebooted then waited for it to discover. I think my NUC is just a little too far as it did not rediscover automatically. I then added the following to one of my existing ESPHome devices (which is a few feet away from the pool controller), and HA discovered the pool controller instantly.
esp32_ble_tracker:
scan_parameters:
interval: 1100ms
window: 1100ms
active: true
bluetooth_proxy:
active: true
Don’t know why the entities became unavailable this morning, but will keep an eye on it and post back.
did a reinstall with the new GIT code last night, rebooted. my HA instance has not discovered anything yet.
Update:
The entities potentially became unavailable when I updated the Mode.
I was running the chlorinator on manual (which showed perfectly in HA). I then updated the Mode to Automatic, which sent the entities into Unavailable for about 20 seconds, after which, they represented their appropriate values again. I then updated the Mode to Off, which sent the entities into Unavailable. At this point, they would not return their proper values if I updated the mode, so I had to remove the integration and then re-add it to get the values back.
I found that my Bluetooth integration (connected to the hardware on my NUC) did not pickup the Chlorinator… might be a little too far away. I added the bluetooth proxy lines onto an existing ESPHome (ESP32) device and it picked it up straight away
@xarmoda, did you get a chance to experiment with putting you HA device closer to the chlorinator? Just for the sake of eliminating possibilities.
@Mikkaat, if you get a chance, try adding the chlorinator device to your history screen to see what it looks like over time.
Here’s what mine looks like. Note there are a few bits where it became unavailable:
yes. new code. no luck. its less than 10m from the chlorinator. I was going to test the bluetooth on the RPi with some other device as I have never used it.