For some strange reason the Last 2 ESPHome updates have kicked my Konnected devices off WiFi and they had to be re-connected to my IoT WiFi ssid. This happens when ESPHome installs the firmware on them after the ESPHome Device Builder Add-on is updated. Anyone else with Konnected Alarm panel devices having this issue?
Are you saying ssid/pass were not saved?
Do you include that info in yaml file?
How do you reconnect them?
Correct. Both board revert back to their orig Konnected open Wi-Fi and I have to go back into the Konnected app and add them back to the IoT Wi-Fi. Never happened before over the years of having them setup in HA until the last 2 ESPHome releases but maybe something in an HA update changed things and I missed the notice?
What is yaml you are flashing?
Or
Specifically how is WiFi config in yaml?
The Kennected Alarm Panel boards are automatically added and the flashing of the firmware is updated thru ESPHome whenever it finds a new firmware and prompts me to update them. I have never edited the .yaml for either of the 2 boards and all the previous firmware updates have gone thru with no issues of WiFi being reset back to the factory WiFi SSID. 
The yaml used by esphome comes from konnected here
Cant give answer about wifi deleting but you have choice.
Continue as is and maybe wifi not delete again
edit yaml with correct file form konnected github and add wifi and know it will not delete again.
1 Like
Thank you for the help with this. So I would just edit this yaml with replacing the !secret with the correct info and save it for both devices and hopefully it won’t happen again?
On the main page of esphome dashboard there is secrets editor in upper right
Open that and add the secrets there like
wifi_ssid: “your ssid”
I use secret for
Ota_key
api_password
WiFi details
Any other secrets
Doing this hardcodes WiFi details in firmware so as long as firmware flashes it will be save or updated
You must install
Saving just updates the file not the device
I had no idea that was even there. Getting too old! The ssid was set to my old router/ap ssid. Thank you for walking me thru this issue. 