search

KaufHA / kauf-rgb-switch

Files for the KAUF RGB Wall Switch
21 stars 8 forks source link

ERROR Error binary size: Error: ESP does not have enough space to store OTA file #10

Open kg4iae opened 1 year ago

kg4iae commented 1 year ago

I installed the switch according to the instructions. It's working in Home Assistant and controlling the lights. I wanted to add the Rotate Color YAML. I made the change according to the docs, and Installed it.

I got it working. (Press the button and it cycles through the colors.)

Next I added the Entity of the light I want to control. That's when I get this error:

INFO Successfully compiled program. INFO Resolving IP address of kauf-rgbsw-e35c1d.local INFO -> 192.168.1.21 INFO Uploading /data/kauf-rgbsw-e35c1d/.pioenvs/kauf-rgbsw-e35c1d/firmware.bin (610624 bytes) INFO Compressed to 418818 bytes ERROR Error binary size: Error: ESP does not have enough space to store OTA file. Please try flashing a minimal firmware (remove everything except ota)

Here's my YAML (ESPHome) substitutions: name: kauf-rgbsw-e35c1d hass_light_entity: light.frontroomrgb packages: Kauf.RGBSw: github://KaufHA/kauf-rgb-switch/kauf-rgbs.yaml rotate_colors: github://bkaufx/kauf-rgb-switch/yaml-features/rotate-colors-sync-to-ha-light.yaml esphome: name: ${name} name_add_mac_suffix: false api: encryption: key: <--Removed--> wifi: ssid: !secret wifi_ssid password: !secret wifi_password

Please help.

bkaufx commented 1 year ago

I would get rid of API encryption. ESPHome added it by default but it takes up a ton of space and IMO is not that important. You'll have to remove and re-add to home assistant after flashing without API encryption (this shouldn't impact anything, all your entities should show back up with the exact same names and retain their history). If you want to keep API encryption then you'll probably have to flash over to a smaller intermediate firmware to update. Hopefully ESPHome will do this automatically at some point in the future.

bkaufx commented 1 year ago

Get rid of these lines in the yaml:

api:
  encryption:
    key: <--Removed-->
kg4iae commented 1 year ago

Thanks for the info. It fixed my problem.