Closed MarkuBu closed 3 months ago
I have the same issue...
Same issue here
Same issue here. Does anyone have a workaround/solution? Thanx! BR, Ralf
Same issue here. Does anyone have a workaround/solution? Thanx! BR, Ralf
A workaround is to flash via direct-connected USB port. A pain, but better than nothing.
When I asked athom last week the size of the flash, they reported 2M - however as we're all finding it's detecting as 1M so the OTA method is failing as there's not enough space to store the update when flashing OTA.
The size increased with 5.0 so OTA upgrades have been failing ever since (ie. from 5.0 to 5.1, 5.0 to 5.2 and now 5.0 to 5.3). I can confirm 5.2->5.3 OTA also failing so just about to grab my ladder again :)
The workaround I did is that I took the original .yaml form Athom's GitHub page and took out the webserver component and it did flash OTA and works as good as ever. I never used the webserver anyway as I'm using it through Home Assistant.
Here is my code:
`esphome: name: "presence-sensor" friendly_name: "Presence Sensor"
esp8266: board: esp8285 restore_from_flash: true
preferences: flash_write_interval: 1min
logger:
api: encryption: key: "whoknows?"
ota: password: "whoknows?"
wifi: ssid: !secret wifi_ssid password: !secret wifi_password
captive_portal:
light:
i2c: sda: GPIO4 scl: GPIO5 scan: true
uart: tx_pin: GPIO15 rx_pin: GPIO13 baud_rate: 115200
binary_sensor:
platform: status name: "Status"
platform: gpio pin: number: GPIO0 mode: INPUT_PULLUP inverted: true name: "Button" disabled_by_default: true on_multi_click:
platform: gpio pin: number: GPIO14 mode: input: true pullup: true name: "Pir Sensor" id: pir filters:
platform: gpio pin: number: GPIO12 mode: input: true pullup: true name: "mmWave Sensor" id: mmwave filters:
platform: template name: "Occupancy" id: occupancy device_class: occupancy lambda: |- if ( id(mmwave).state and id(pir).state) { return true; } else if (id(mmwave).state == 0) { return false; } else { return id(occupancy).state; }
sensor:
platform: uptime name: "Uptime Sensor"
platform: wifi_signal name: "WiFi Signal Sensor" update_interval: 60s
platform: bh1750 name: "Light Sensor" address: 0x23 update_interval: 5s
switch:
number:
platform: template name: Farthest Detection #Value range: 1.9 ~ 12m Default: 6 id: Farthest_Detection entity_category: config min_value: 1.9 max_value: 12 initial_value: 6 optimistic: true step: 0.1 restore_value: true unit_of_measurement: m mode: slider set_action:
platform: template name: Maintain Sensitivity #Value range: 0 ~ 9 Default Maintain sensitivity: 7 Default Trigger sensitivity: 5 id: Maintain_Sensitivity entity_category: config min_value: 0 max_value: 9 initial_value: 7 optimistic: true step: 1 restore_value: true mode: slider set_action:
platform: template name: Trigger Sensitivity #Value range: 0 ~ 9 Default Maintain sensitivity: 7 Default Trigger sensitivity: 5 id: Trigger_Sensitivity entity_category: config min_value: 0 max_value: 9 initial_value: 5 optimistic: true step: 1 restore_value: true mode: slider set_action:
platform: template name: Detection Delay #Confirmation delay Value range: 0 ~ 100 default 0.050 seconds. id: Detection_Delay entity_category: config min_value: 0.1 max_value: 60 initial_value: 0.1 optimistic: true step: 0.1 restore_value: true unit_of_measurement: seconds mode: slider set_action:
platform: template name: Fading Time #Fade-out delay Value range: 0.5 ~ 1500, default 15 seconds. id: Fading_Time entity_category: config min_value: 1 max_value: 300 initial_value: 15 optimistic: true step: 1 restore_value: true unit_of_measurement: seconds mode: auto set_action:
platform: template name: Blockade Time #Configure block time Value range: 1 ~ 255, default 1 seconds. id: Blockade_Time entity_category: config min_value: 1 max_value: 255 initial_value: 1 optimistic: true step: 1 restore_value: true unit_of_measurement: seconds mode: slider set_action:
button:
platform: factory_reset name: Restart with Factory Default Settings id: Reset entity_category: config internal: true
platform: template name: "Reset device" id: "factory_reset_device" entity_category: config on_press:
platform: restart name: Restart_esp id: restart_esp entity_category: config internal: true
platform: template name: "Restart_mmWave" id: "restart_mmwave" entity_category: config internal: true on_press:
platform: template name: Restart device entity_category: config on_press:
text_sensor:
time:
Thanks for the work around. I forked the repo, removed the web server config and changed the link in the config yaml to the new repo
https://github.com/MarkuBu/athom-configs/blob/main/athom-presence-sensor.yaml
substitutions:
name: athom-presence-sensor-xxxx
friendly_name: Presence
packages:
Athom_Technology.Presence_Sensor: github://MarkuBu/athom-configs/athom-presence-sensor.yaml
esphome:
name: ${name}
name_add_mac_suffix: false
friendly_name: ${friendly_name}
api:
encryption:
key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
Since this is just a work around and not a solution I leave this issue open
Thanx at all for working on workarounds!!! 👍🏻
I was able to OTA from 5.3->5.4
Mee too. Needed some retries and restarts of the devices, but finally worked: OTA -> 5.4
The size increase was fixed in 5.4.
Great, thanks. But I think I will continue without the Webserver. I just don't need it.
The problem
I have several Athom presense sensors. Since the update to ESPHome 2024.5.1 or .2 I can't update the firmware. Latest installed version is 2024.5.0
Maybe I missed .1, so I'm not sure if .1 or .2 caused the issue at first
Which version of ESPHome has the issue?
2024.5.2
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2024.5.4
What platform are you using?
ESP8266
Board
Athom presense sensor PS01
Component causing the issue
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response