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
HI Lewis, i get this error afte the latested update.
everything-presence-one-e01dc0 @ 192.168.1.142: Connection error occurred: everything-presence-one-e01dc0 @ 192.168.1.141: The connection dropped immediately after encrypted hello; Try enabling encryption on the device or turning off encryption on the client (Home Assistant 2024.7.4
This is my configuration in esp home, what do i need to change?
This is not an issue with the update. It's an issue with applying the update directly from GitHub when you have already configured it in the ESPHome add-on. When you add it to the ESPHome addon, it automatically adds an encryption key. Home Assistant uses this encryption key to communicate with the One.
When you install the update directly from GitHub instead of via the ESPHome addon, it will remove the encryption key. So home assistant is effectively trying to communicate with it using a password, while the device has no password.
Either remove and re-add to Home Assistant without the password, or flash again from ESPHome to add the password back
HI Lewis, i get this error afte the latested update.
everything-presence-one-e01dc0 @ 192.168.1.142: Connection error occurred: everything-presence-one-e01dc0 @ 192.168.1.141: The connection dropped immediately after encrypted hello; Try enabling encryption on the device or turning off encryption on the client (Home Assistant 2024.7.4
This is my configuration in esp home, what do i need to change?
substitutions:
name: everything-presence-one-e01dc0
packages:
Everything_Smart_Technology.Everything_Presence_One: github://everythingsmarthome/presence-one/everything-presence-one.yaml@main
esphome:
name: ${name}
name_add_mac_suffix: false
api:
encryption:
key: xxxxredactedxxxx
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
The text was updated successfully, but these errors were encountered: