Need FW downgrades for Kasa Smart Motion Switch ES20M(US) HW1.0 from FW 1.1.15 to 1.0.11 and 1.0.10
Need FW downgrades for Kasa Smart Motion Switch ES20M(US) HW1.0 from FW 1.1.15 to 1.0.11 and 1.0.10
Immediate Request:
Please provide verified links for the firmware files (versions 1.0.11 and 1.0.10) and the corresponding firmware programming software required to downgrade ES20M(US) devices. This downgrade is needed to resolve instability issues introduced with firmware 1.1.15.
Technical Observations
Firmware Version Details
- Firmware 1.1.15:
- Possible New Protocol (tss): Introduced in this release(?), leading to authentication failures (e.g., tp‑link email and password issues in Home Assistant) until a full device reset is performed.
- Legacy Protocols: Coexistence of standard tp‑link protocols and an alternate protocol (KLAP) observed during initial connections.
- Firmware 1.0.11(?)/1.0.10:
- These versions maintain stable API interactions with Home Assistant and do not include the tss protocol, thus avoiding the observed issues.
Quantitative Metrics and Testing Scenarios
- Scenario 1: Home Assistant Direct Control
- Action: 5–15 consecutive on/off toggles.
- Outcome: Device hangs or reboots, with a hang that lasts until manual reset and with an internal device initiated reboot (watchdog?) occurring approximately 60 seconds after connectivity loss.
- Protocol Behavior: Initial connection via python‑kasa reports a KLAP-related authentication failure, followed by a switch to port 9999 on subsequent attempts.
- Scenario 2: Mixed Control Environment (Home Assistant & Kasa App)
- Observation: Similar instability is recorded when Home Assistant monitors the state and the Kasa app is used for toggling.
- Scenario 3: Exclusive Kasa App Control
- Observation: Devices remain stable when controlled solely by the Kasa app, implying the API changes in firmware 1.1.15 primarily affect Home Assistant.
Additional Network Considerations
- tss Protocol Effects:
- Persistent authentication failures until a complete reset is performed on both ES20M devices.
- Some users report that disconnecting other network devices may temporarily resolve these issues; however, the absence of a dedicated power-off function complicates management of multiple devices.