This is the best one I’m aware of:
Feasycom FSC-BP119
https://a.aliexpress.com/_EHiBgCU
Thanks. I was hoping to be able to get one with 5.3+ support, tho…
I tried a Bluetooth 5 dongle and it didn’t work well.
This is consistent with what’s detailed here: Bluetooth - Home Assistant
It seems like only Bluetooth 4 dongles with a specific chipset (CSR8510A10) work well in linux, and the ine I sent above is the only long range one.
Thanks, I’ll look around for the bp119 . Out of curiosity, do you remember if/when you tried bt5 adapter it was an ats2851 devices? There are some reports of compatibility with recent HassOS versions.
It was a RTL8761BU and it did work, just a lot worse (disconnections, slow to reconnect, hung ups…)
I also have a BCM20702A0 one which works well but required external drivers (and it is also v4)
I wonder if it might be worth putting something like this on the integration page or directly link to a clear tutorial as the actual pairing process might be the most complicated part of the entire setup
Hi there,
In regards to the new integration within HA and not within HACS, I wonder how to set temperature changes for certain times of the day. I understood this would be part of the new integration but realised in a different way?
Thanks for your help
Hi there,
I just wanted to highlight this tip, it saved two of my devices!
After changing hardware I needed to re-pair my TRV and two of them would pair but had no connection. Re-repairing after unpairing did not bring any improvement nor resetting the devices alone. Both needed to be done.
What helped me was this dual approach:
- reset the devices as per manual manufacturer homepage
- ensure nothing is left of the previous pairing within bluetoothctl by using the following commands ( I am not sure if the order matters and in which order exactly I used them):
cancel-pairing [dev MAC]
untrust [dev MAC]
disconnect [dev MAC]
remove [dev MAC]
Example:
cancel-pairing 00:1A:22:76:AB:CD
I hope this helps!
First of all thanks to your work for this integration.
I have trouble getting my eq3 devices connecting to home assistant and your integration.
I’m running a raspberry pi 4 and a bluetooth proxy on a «ESP32 NodeMCU Module WLAN WiFi Development Board | Dev Kit C V2». According to the log the proxy is up and running, e.g.
" [16:36:50][D][esp32_ble_tracker:116]: connecting: 1, discovered: 0, searching: 0, disconnecting: 0
[16:36:54][D][esp32_ble_client:191]: [0] [00:1A:22:06:F1:CB] ESP_GATTC_WRITE_CHAR_EVT
[16:36:54][D][esp32_ble_client:191]: [0] [00:1A:22:06:F1:CB] ESP_GATTC_NOTIFY_EVT
[16:36:56]lld_pdu_get_tx_flush_nb HCI packet count mismatch (0, 1)
[16:36:58]lld_pdu_get_tx_flush_nb HCI packet count mismatch (0, 1)
[16:37:00][W][esp32_ble_client:138]: [1] [00:1A:22:06:D4:9C] Disconnecting before connected, disconnect scheduled.
I can see ‘your integration’ trying to connect. The ‘Retries’ counter increments, when I open the device in the integration and press the ‘Fetch’ button in the diagnosis section.
Any idea, why I don’t see any data.
If you have updated the eq3 firmware, you’ll need to put the pairing information in the proxy
Just wanted to share that I gave a shot to the UGREEN USB 5.3 adapter with external antenna, and it seems to be a lot more reliable than the ESPHome BTProxy and with a long range. It’s currently handling without errors 8 EQ3 + 5 Xiaomi BLE Sensors, on a VM with Home Assistant OS (up to date as of today).
Do you know which chipset it has?
It should be an ats2851. It’s recognized as “Actions general adapter” (chip-ID: 10d7:b012)
Interesting, it’s listed in the Unsupported list.
Do you use home assistant OS?
There were some fixes on kernel 6.12, and Home Assistant OS was recently updated to 6.12 too. 
how many concurrent active connections can you manage?
I currently have 3 usb dongles for 8 eq3 devices and it is a bit of a pain (particularly because some require pairing and so need to be pinned to a specific device)
I’m lucky enough for having 8 eq3 all @ firmware 120, so no pairing is required. I have only this dongle (and no esp proxies) and everything seems to be working.
Is there a way to monitor the Connection slot allocation monitor?
I made the integration before it existed so it is probably not using the right API for the connection slot manager.
Unless you use the extra features (setting schedules, etc) you may want to try the core integration instead
One thing you could do to check how many open connections are held is to enable the debug entities (click configure and tick the debug entities checkbox on each device here: http://homeassistant.local:8123/config/integrations/integration/dbuezas_eq3btsmart)
Then you can open each of the devices (scroll down) and see how many of them show as connected
I just managed to downgrade a thermostat to an older version (no pin) via python scripts