You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have an allotment with a couple of sheds which I want contact sensors on. The allotment has WiFi and is covered by ESPHome ble-proxies on ESP32 dev boards. My first shed has a device which I sourced from AliExpress and it's been perfect since installation. I ordered a second unit from Amazon UK and it refuses to "stick" in Home Assistant - on restart it disappears. Assuming this was a faulty unit I ordered a second and it does exactly the same.
To Reproduce
Wake the device
Pair to Home Assistant
Confirm the device is reporting data
Restart Home Assistant - devices disappear
Additional context
Firmware versions of the devices:
The original device which is working is on: 20230522-134711/v1.0.6@9b614a29
The second and third devices which are not working was on the same version but is now on: 20240408-184602/v1.0.16@716b307b (both updated using the Shelly BLE Debug app)
So I traced this back to a completely unrelated issue. Another integration had written a corrupt line to the device registry and it made the file effectively read-only meaning ANY integration added disappeared after a restart.
Describe the bug
I have an allotment with a couple of sheds which I want contact sensors on. The allotment has WiFi and is covered by ESPHome ble-proxies on ESP32 dev boards. My first shed has a device which I sourced from AliExpress and it's been perfect since installation. I ordered a second unit from Amazon UK and it refuses to "stick" in Home Assistant - on restart it disappears. Assuming this was a faulty unit I ordered a second and it does exactly the same.
To Reproduce
Additional context
Firmware versions of the devices:
Home Assistant version data:
ESPHome version data:
Attached screencap of the end to end journey:
https://github.com/user-attachments/assets/405ac2a9-1d8a-491e-9ddf-5cb7045d795c
Debug log:
Removed for now as it seems to contain nothing relevant to BTHome.
The text was updated successfully, but these errors were encountered: