Wooley Socket CK-BL702-SWP-01(7020) - can I get Power Information?

cyber5 · December 23, 2023, 11:57am

I am new to this ZigBee stuff, and bought the SonOff dongle before I realised that I already had a working Hue Hub and Zigbee LEDs that I installed 2 years ago. I had to make a decision then and unplugged the Hue and got going with ZHA.

I quickly realised I needed some hubs for battery sensors and bought some WOOLEY sockets that are advertised as having power information and are picked up by ZHA as CK-BL702-SWP-01(7020) - but as dumb switches, no power/energy information is forthcoming (the small-print does say that you need a specific hub to get this).

It MUST be possible with ZHA to get the energy data, but working it out from scratch is somewhat above my pay grade. I found the “clusters” config but every single stat in the ElectricalMeasurement cluster returrns “None”.

I did find the following link for zigbee2mqtt I think, and imagine I could use it to work with ZHA if I had the skills and experience. Anyone got a hint or a suggestion?

github.com/zigpy/zha-device-handlers

[New device support]: CK-BL702-SWP-01(7020)

opened 10:14PM - 09 Nov 23 UTC

gromgsxr

### Problem description shows as manufacture eWeLink CK-BL702-SWP-01(7020) avai…lable from amazon ebay ect https://www.ebay.co.uk/itm/314855773062 appears to be working in z2mqtt see here for info on the clusters https://github.com/Koenkk/zigbee2mqtt/issues/19334#issuecomment-1784120749 ### Solution description please add this device ### Screenshots/Video <details><summary>Screenshots/Video</summary> [Paste/upload your media here] </details> ### Device signature <details><summary>Device signature</summary> ```json { "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4742, maximum_buffer_size=127, maximum_incoming_transfer_size=242, server_mask=11264, maximum_outgoing_transfer_size=242, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)", "endpoints": { "1": { "profile_id": 260, "device_type": "0x0009", "in_clusters": [ "0x0000", "0x0003", "0x0004", "0x0005", "0x0006", "0x1000", "0xfc11", "0xfc57" ], "out_clusters": [ "0x000a", "0x0019", "0x0b04" ] }, "242": { "profile_id": 41440, "device_type": "0x0061", "in_clusters": [], "out_clusters": [ "0x0021" ] } }, "manufacturer": "eWeLink", "model": "CK-BL702-SWP-01(7020)", "class": "zigpy.device.Device" } ``` </details> ### Diagnostic information <details><summary>Diagnostic information</summary> ```json [Paste the diagnostic information here] ``` </details> ### Logs <details><summary>Logs</summary> ```python [Paste the logs here] ``` </details> ### Custom quirk <details><summary>Custom quirk</summary> ```python [Paste your custom quirk here] ``` </details> ### Additional information https://github.com/Koenkk/zigbee2mqtt/issues/19334#issuecomment-1784120749

I may have a play with zigbee2mqtt - it is still early days for me with just a few devices to play around with and I could switch. I will say the zigbee works remmarkably well. Startlingly well when I look at what is talking to what in the app and find that the presence detector in the kitchen is talking to the socket at the bottom of the garden, 30m away, not the socket in the bedroom directly above it.

macado75 · December 24, 2023, 11:38am

Did you get anywhere with this? I’ve just bought a bunch of these and i’m having the same issue with ZHA.

MaximumFish · December 25, 2023, 5:37pm

Just got a few of these and a Sonoff dongle for Christmas, and power monitoring seems like an essential feature for any smart plug so I’ll be watching this thread with interest - at least up until the cut-off for sending them back.

macado75 · December 26, 2023, 5:17pm

I raised an issue in GitHub for this but I’ve decided to return them to Amazon.

github.com/home-assistant/core

Woolley CK-BL702-SWP-01(7020) power monitoring entities not showing

opened 11:24AM - 24 Dec 23 UTC

macado75

integration: zha

### The problem I have recently purchased a few Woolley CK-BL702-SWP-01(7020) z…igbee power monitoring switches from Amazon. They are detected fine in ZHA but don't seem to show entities for the power monitoring features, just the switching functionality. Am I doing something wrong or are these devices not supoported? ### What version of Home Assistant Core has the issue? core-2023.12.3 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Zigbee Home Automation ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

Worth keeping an eye on if you’re planning on keeping them.

MaximumFish · December 27, 2023, 1:08pm

Thanks, I’d already found that issue and subscribed to it, just didn’t spot that it was you who’d made it! I’m currently torn as to whether to send them back as they’re at least useful as Zigbee routers and I’d imagine power monitoring will be added to ZHA eventually…

cyber5 · January 6, 2024, 7:36am

I too am using them as zigbee routers - I have quite a big area to cover and they have made a difference. I just use them on things where I am not that bothered about the power usage. And hope that someone much more able than me will fix the power monitoring one day.

Setting up zigbee2mqtt just seemed a step too far at the moment.

MaximumFish · January 6, 2024, 5:28pm

It’s already working in ZHA via the bug report above, we’re just waiting for it to get pushed to the main branch. Shouldn’t be too long now.