Open kformosa opened 1 year ago
Use esp-idf instead for the framework type
I changed the platform to "ESP32" since I couldn't make that option work/compile. Still, after 7 days the same problem occurred. Had to reset the board and all good until 7 days pass.
I updated to the lastest ESPHome but still have the same issue: basically the 2 bluetooth devices being proxied via this ESP board return "NaN" to HA. Sometimes after just after 1 day up-time.
Resetting the board, fixes the issue until it returns.
Anyone else encountering same issue?
Got the same issue here - just need a restart switch in the bluetooth proxy YAML so I can automate a restart on the esp32 from HA.
The ESP32 Platform component should be configured to use the esp-idf framework, as the arduino framework uses significantly more memory and performs poorly with the Bluetooth proxy enabled. When switching from arduino to esp-idf, make sure to update the device with a serial cable as the partition table is different between the two frameworks as OTA Update Component updates will not change the partition table.
@bdraco would this be the same if I flashed directly from Tasmota to esphome?
@bdraco would this be the same if I flashed directly from Tasmota to esphome?
If you did tasmota to esphome you need to use the serial cable to flash it once as you likely have a tasmota partition table
@bdraco would this be the same if I flashed directly from Tasmota to esphome?
If you did tasmota to esphome you need to use the serial cable to flash it once as you likely have a tasmota partition table
I used a USB cable and chrome to flash from ESPhome website so not OTA - should that have wiped the tasmota partition table?
I used a USB cable and chrome to flash from ESPhome website so not OTA - should that have wiped the tasmota partition table?
yes
I flashed the board with the esp-idf framework using a cable over the weekend. Seems that the issue has been resolved. Thanks @bdraco
The problem
As in the title, I have a TTGO T-Relay board and flashed ESPHome. Been using ESPHome for a while and enabled the BLE tracker when it was available. But since around the .11 update, I am getting NaN in HA after roughly 5-7 days. I just restart the board (pressing Reset) and everything is back to normal - until 5-7 days when I run into the same issue. Still having the same issue with the .12 update.
Which version of ESPHome has the issue?
2022.12.3
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2022.12.8
What platform are you using?
ESP32
Board
TTGO T-Relay
Component causing the issue
BLE Tracker
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response