search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.4k stars 30.3k forks source link

No active connection to BT sensor #79813

Closed Mariusthvdb closed 1 year ago

Mariusthvdb commented 2 years ago

The problem

having updated the Esphome add-on, and all the driver for the BT proxies to support an active connection, I expected (hoped) to see a close connection (good dBm) on a Govee temp/humidity sensor H5072/H5075 However, this is not the case. It only works ok on an M5stack wifi proxy, but 2 of the Olimex proxy boards dont connect at all.

Or, I should maybe say, the dBm doesnt go up from this, well maybe to -90:

Schermafbeelding 2022-10-07 om 14 13 40

it now seems to only connect to the main BT hardware in the MiniPC, where before, it did also connect to the BT extender I have installed and show something in the 60-70's (the miniP`c and the extender are a longer way from this device)

The Olimex is right next to it though, so Id expect to see low 30-20's, like on the M5stack

What version of Home Assistant Core has the issue?

2022.10.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Bluetooth Esphome

Link to integration documentation on our website

https://www.home-assistant.io/integrations/bluetooth https://www.home-assistant.io/integrations/esphome/

Diagnostics information

one of the Olimex boards: config_entry-esphome-244e3ecbb5a685ab468b53535898475b.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.esphome
Source: components/esphome/__init__.py:263 
Integration: ESPHome (documentation, issues) 
First occurred: 16:13:40 (32 occurrences) 
Last logged: 16:24:04

Name of device olimex-bluetooth-proxy-277564 changed to bluetooth-proxy-centraal, potentially due to IP reassignment
Name of device olimex-bluetooth-proxy-288d84 changed to bluetooth-proxy-aanbouw, potentially due to IP reassignment

Logger: aioesphomeapi.reconnect_logic
Source: runner.py:119 
First occurred: 16:13:40 (2 occurrences) 
Last logged: 16:13:40

Can't connect to ESPHome API for olimex-bluetooth-proxy-277564 @ 192.168.1.221: Server sent a different name 'bluetooth-proxy-centraal'
Can't connect to ESPHome API for olimex-bluetooth-proxy-288d84 @ 192.168.1.135: Server sent a different name 'bluetooth-proxy-aanbouw'

Additional information

related on the ESPHome https://github.com/esphome/dashboard/issues/329 ? on the devices adoption in the Dashboard, and still showing warnings in the log after successful adoption

aware the Loggins above are for the ESPHome, but probably related to this issue of not working Active connection?

Schermafbeelding 2022-10-07 om 16 29 47
homeassistant commented 2 years ago

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (bluetooth) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

bluetooth documentation bluetooth source (message by IssueLinks)

homeassistant commented 2 years ago

Hey there @ottowinter, @jesserockz, mind taking a look at this issue as it has been labeled with an integration (esphome) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

esphome documentation esphome source (message by IssueLinks)