Hello
Since January 8th, the measurement of the CK-BL602-SWP1-01(182) (fw 1.3.1) in HA has stopped working again, only if the ewelink app is running on my phone. If I exit the app, the last measured data remains indefinitely. Again…
Since January 8th, the measurement of the CK-BL602-SWP1-01(182) (fw 1.3.1) in HA has stopped working again, only if the ewelink app is running on my phone. If I exit the app, the last measured data remains indefinitely. Again…
Your device CK‑BL602‑SWP1‑01(182) uses the BL602 chipset, and this model does not send power measurement data directly to the cloud, as far as I know.
The BL602 firmware only reports energy data to the eWeLink mobile app, and the app then forwards it to the cloud. So when the eWeLink app is closed, the device stops pushing measurement updates, and HA receives only the last cached value. This behavior is by design for BL602‑based devices and has been seen many times before.
t’s also worth noting that CoolKit likely changed something in their cloud API or backend around that time. We can’t say this with absolute certainty because CoolKit doesn’t publish changelogs for these internal updates, but the symptoms match what users have seen before when the cloud behavior changes.
To summarize:
SonoffLAN cannot fix this because the device simply doesn’t send the data. If you need stable, fully local energy monitoring, the only real solution is to flash the device with OpenBL602 (open‑source firmware), because BL602 cannot run ESPHome or Tasmota.
And since this is the eWeLink forum, you’re essentially knocking on the wrong door - the limitation comes from the device firmware itself, not from HA or eWeLink cloud.
Hello
Actually, there was no firmware update before the problem occurred and except for a similar problem at the beginning of last year - late update of the ewelink app -, since December 2022, 12 copies worked normally - including measurement - and 3 never measured
, so I don’t understand…
Since all its functions - including switching! - are handled via the cloud, I thought of a cloud-side problem…