Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No longer able to flash updated ESPHome versions: Error: Authentication invalid. Is the password correct? #39

Closed
louispires opened this issue May 22, 2024 · 3 comments

Comments

@louispires
Copy link

I flashed this well over a year ago, worked great until about August last year when the ESPHome firmware no longer flashed successfully via OTA.

Building .pioenvs/zigbee/firmware.bin
Creating esp32 image...
Successfully created esp32 image.
esp32_create_combined_bin([".pioenvs/zigbee/firmware.bin"], [".pioenvs/zigbee/firmware.elf"])
Wrote 0xdc2d0 bytes to file /data/build/zigbee/.pioenvs/zigbee/firmware-factory.bin, ready to flash to offset 0x0
======================== [SUCCESS] Took 380.16 seconds ========================
INFO Successfully compiled program.
INFO Connecting to 10.0.0.31
INFO Uploading /data/build/zigbee/.pioenvs/zigbee/firmware.bin (836304 bytes)
ERROR Error auth result: Error: Authentication invalid. Is the password correct?

I tried playing around with the OTA Password field etc. but nothing seems to have worked and I am now stuck on an old version

substitutions:
  name: zigbee
  device_description: "ZB-GW03 eWeLink Ethernet Zigbee Gateway based Zigbee Coordinator"

packages:
  zb-gw03:
    url: https://github.com/syssi/esphome-zb-gw03
    ref: main
    files:
      - packages/core.yaml
      - packages/status_led.yaml
      - packages/green_led.yaml
      - packages/i2c.yaml
      - packages/button_zigbee_reset.yaml
      - packages/mdns.yaml
    refresh: 0s

# Enable Home Assistant API
api:
  encryption:
    key: "bQ30ENXTK+FZ+8X5ryGB0HTzoulLftOS8fiyHzMUbpg="

ota:
  password: "a6c199f4e53f394834c47b3b5e0bbedb"

# Enable logging
logger:

wifi:
  ssid: !secret wifi_ssid_iot
  password: !secret wifi_password_iot

  manual_ip:
    static_ip: 10.0.0.31
    gateway: 10.0.0.1
    subnet: 255.255.255.0

Will probably need to sort this out soon due to the deprecation of the ezsp and seems like xsp1989 is busy attempting a new firmware build

Ideally, I would not like to resolder again and prefer to be able to do an OTA of some sort.

Any recommendations?

@syssi
Copy link
Owner

syssi commented May 22, 2024

You are on the right track. You have to find out the OTA password or key you have used last time to flash the device. Did you migrate to the encryption key already or did you flash the device using an OTA password last time? If you are unable to find out the password you cannot flash the device using OTA. Soldering to flash the ESP using an UART connection would be the only option I'm aware of.

@louispires
Copy link
Author

You are on the right track. You have to find out the OTA password or key you have used last time to flash the device. Did you migrate to the encryption key already or did you flash the device using an OTA password last time? If you are unable to find out the password you cannot flash the device using OTA. Soldering to flash the ESP using an UART connection would be the only option I'm aware of.

I had never added an OTA password, it just randomly one day stated that the password was incorrect.

That is when I started experimenting with adding a value and even attempting to set the password on boot:

on_boot:
    - lambda: |-
        id(my_ota).set_auth_password("New password");

Which also did not work for me...

@syssi
Copy link
Owner

syssi commented May 24, 2024

Do you agree to close the issue?

@syssi syssi closed this as completed Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants