CK-BL602-W102SW18-01(226)
coolkit WIFI
Firmware: 1.2.1
Hardware: 226
I want to know if this WIFI power meter with CLAMP is bidirectional or not, for mojitorin a solar installation. It seems NOT to be bidirectional anf I want to know
And I see this device does not update power values in HA. I have heard ewelink cloud limit requests and I understand it but a dearh device without any value update… Another ewelink device not working…
Which Home Assistant integration are you using?
Power values not updating in HA doesn’t automatically mean eWeLink Cloud is rate-limiting anything. This particular device model has had HA support/update issues reported before. Bidirectional metering is a separate question and should probably be confirmed by eWeLink/CoolKit.
So before declaring it “another eWeLink device not working”, it might be worth establishing which part is actually not working. 
device not working means power value is never updated in HA. I have to open ewelink app or OFF/ON device for a value update. I have read this device perhaps does nopt send values to the cloud, onlyy send to the app, but the app is connected to the cloud. I do not understand
CK-BL602-W302SE10-01(181) firmware 1.2.0 a thermometer DOES UPDATE VALUE, but CK-BL602-W102SW18-01(226) firmware 1.2.1 power meter DOES NOT UPDATE VALUE, and both use BL602
Then I think we have different definitions of “device not working”. The device apparently works and reports a value. The issue is that HA doesn’t receive automatic updates.
BL602 is the MCU, not a guarantee that two completely different devices will behave identically.
A thermometer reporting temperature and a power meter reporting power are different devices, with different firmware and possibly different reporting mechanisms.
So we’re still missing the most basic piece of information: which Home Assistant integration are you using?
The fact that opening the eWeLink app triggers an update is useful information. “Another eWeLink device not working” is a conclusion, not a diagnosis.
Thanks. Two screenshots instead of one sentence. That’s an impressive level of data compression, almost ZIP.
I briefly considered replying with a drawing to keep the communication protocol consistent.
I assume that you’re using the Sonoff custom integration (SonoffLAN), version 3.13.1. That was the information I was asking for. 
In that case, I wouldn’t assume yet that the lack of automatic power updates in HA is caused by the device itself or by eWeLink Cloud. It may also be related to how this particular device is supported by the custom integration. It would therefore be worth checking the integration’s documentation and known issues first. If that doesn’t clarify the behaviour, asking the integration’s author whether this particular device is fully supported, especially its automatic power updates, would probably be the next logical step.
Sorry I thought images were more explicit. Problem seems to be device does not send data if app is closed.
Just to be clear, which app do you mean? The eWeLink app?
OK ewelink app (android)
Let’s clarify one more thing: with the eWeLink app open, does the power value in Home Assistant update automatically? And after closing the eWeLink app, does that same value stop updating?
Exactly
Thanks. That makes the behaviour clear.
SonoffLAN can use both LAN and cloud connections, and devices with supported LAN functionality can communicate locally without relying on the cloud.
So in this particular case, I think the best next step is to ask the SonoffLAN author whether power reporting for CK-BL602-W102SW18-01(226) is actually supported over LAN, and how this model is handled by the integration.
The fact that opening the eWeLink app makes the values update is certainly interesting, but it doesn’t by itself explain which part of the communication path is responsible. This is probably better investigated on the SonoffLAN GitHub than by guessing here.
Honestly, unless investigating this is the goal itself, I would just replace it with a Zigbee or Matter power meter with local reporting to HA. At some point troubleshooting costs more time than the device is worth.