Nope, upgrading to encrypted is still not fully working for me. I just tried adding encryption for one of my (wemos d1) devices and it is only partially working. I’m still seeing similar “Socket operation failed:…” error messages, and several of the features I have on the device are not working. For example, the device has an OLED that displays time, date, temp, and humidity… it also has a button for input, and a dfplayer for audio cues. After adding encryption the devices shows up in HA, and the time is showing properly, but the temperature and humidity aren’t working, and neither is the dfplayer or button. I assume this may be due to those functions requiring data from the HA api… but esphome maybe can send the date without interaction? I was able to OTA another fw (from the HA webui) without encryption enabled, and everything started working again.
On a related note, the HA integration did not ask me for an encryption key after the upload… just started working and logs showed encryption was in use. So they did get the string stuff fixed… so just the yaml edit is all that’s needed now.
Anyhow, just wanted to pop in and mention this here since it’s NOT fully ready for newbs yet. I’m not really nix apprehensive, but I have not tried hacking my .storage files yet… too much other things taking my time right now. Running esphome without encryption, at least until the devs sort this out, is no big deal I think for most users who are operating behind a firewall with only trusted clients. IMHO, this feature was just rushed out a bit too quickly/loudly… after all, it looks like there may be some difficult upstream issues to sort out according to this: