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
Just in case somebody stumbles across the same problem...
I've just bought one of these which turned out to be a v2.1, managed to get it to connect and flashed via https://blakadder.github.io/bluetooth-proxies/. It showed up ok in HA under the ESPHome tab, but then wanted to be "Adopted" which failed with "At least one platform must be specified for 'ota'; add 'platform: esphome' for original OTA functionality" and even with adding the right bit in via "edit" I couldn't convince it to go.
So I created a new device, added in the config from https://github.com/blakadder/bluetooth-proxies/blob/main/gl-s10_v2.yaml and then:
api:
encryption:
key: pickone
ota:
platform: esphome
password: "pickone"
Compile, download as legacy and flash with ESPHome-Flasher. That worked ok and let me adopt the device with the key I had added into the config. Might be worthwhile adding at least the OTA bit in to prevent the process in HA from getting stuck?
The text was updated successfully, but these errors were encountered:
Just in case somebody stumbles across the same problem...
I've just bought one of these which turned out to be a v2.1, managed to get it to connect and flashed via https://blakadder.github.io/bluetooth-proxies/. It showed up ok in HA under the ESPHome tab, but then wanted to be "Adopted" which failed with "At least one platform must be specified for 'ota'; add 'platform: esphome' for original OTA functionality" and even with adding the right bit in via "edit" I couldn't convince it to go.
So I created a new device, added in the config from https://github.com/blakadder/bluetooth-proxies/blob/main/gl-s10_v2.yaml and then:
api:
encryption:
key: pickone
ota:
password: "pickone"
Compile, download as legacy and flash with ESPHome-Flasher. That worked ok and let me adopt the device with the key I had added into the config. Might be worthwhile adding at least the OTA bit in to prevent the process in HA from getting stuck?
The text was updated successfully, but these errors were encountered: