-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inkbird sensor disconnecting Similar to #109405 #137249
Comments
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) inkbird documentation |
Please post
Additionally, get everything into a good state, than enable the following debug logs : logger:
default: info
logs:
btsocket: debug
inkbird_ble: debug
bleak_retry_connector: debug
bluetooth_adapters: debug
bluetooth_auto_recovery: debug
habluetooth: debug When the problem happens again, post the logs and the timestamp of when the problem happens again |
I have setup the logger to capture the information and will post next time it shows as offline. The esphome code is:
I assume the mac address you are looking for is the Mac address shown in the Inkbird integration? |
Diagnostics from the Bluetooth config entry would be best. Thanks |
I have 4 restarts since I opened the issue. So far, it is back working. Not sure why? I'll leave this open for a couple of more days to see if it got fixed with a different change in either supervisor or core code. |
I have a feeling its an environmental issue as there haven't been any changes that would explain why it would stop or start working again |
When / if it happens again I will post the information. Not sure what an environmental issue is? Nothing has changed in the area that the sensors are located. |
environmental issue = something unique to your local environment that we wouldn't see in testing. Could be interference, hardware issue, etc. The logs still might give us a hint as to whats going on if you can get it to happen again, and just because it might be environmental, it doesn't mean we can't work around it with a software change (but sometimes its a configuration or hardware change that is needed) |
Just happened again on 2025.2 release Bluetooth Diagnostic attached |
It looks like the diagnostics are missing. There should be something in the logs, are you sure you have all the debug loggers enabled?
|
I had to leave before I left the json file above.
Logger: aioesphomeapi.reconnect_logic Can't connect to ESPHome API for office-esp32-bluetooth-proxy @ 192.168.1.82: Error while starting connection: Starting connection cancelled (APIConnectionCancelledError)
|
That looks like a cancellation problem. Can you send a full log? It seems the connection to the Bluetooth proxy is being dropped and reconnecting is being cancelled for some reason. |
I have since rebooted as I need this sensor. Next time it fails I will post the complete core logs. Do you also want a new json file as well? |
Yes please |
Since it looks like the esphome device might be part of the issue, please add |
Added this. I still don't understand why the issue only shows on a restart and goes away on a reboot.? |
Failed on a restart this morning. Had about 6 prior restarts with no issues. home-assistant_2025-02-09T15-50-16.126Z.log Bluetooth Json |
Which timestamp did it fail at? |
Also which Bluetooth mac failed this time? |
In the data seen 0.73s ago
|
So the name is corrupted
|
So it won't accept the advertising data once the name is corrupted because we no longer no what kind of device it is. |
Its likely either a bug in the device firmware or a problem with the radio that causes it to send a corrupt name, or some interference problem that happens to have the CRC pass. Once it sees the longer name it will always prefer the longer name as it doesn't know the longer name is corrupt |
A few things we could do to mitigate this problem:
|
Sadly neither of these are small changes so it will take some time to work around this issue |
Same Bluetooth: 49:42:08:00:46:DC as before. Not sure about time stamp. I grabbed the data as soon as it restarted with the sensor failure. I guess by the time I answered you had already figured this out. |
At least we know whats going on now. Sadly we can't fix the actual problem but we can work around it. It will take some time. |
The problem
The Inbird sensor disconnecting is back. Not sure if the Supervisor or Core is causing it. On a new update I lose the connection to one of my Inkbird sensors. A reboot always brings it back. Using ESPhome Proxy as my Bluetooth connection. The proxy is on line as it sees other Inkbird devices
What version of Home Assistant Core has the issue?
2025.2.0b7
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
Inkbird
Link to integration documentation on our website
https://www.home-assistant.io/integrations/inkbird/
Diagnostics information
Nothing in the logs. This issue keeps coming back.
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: