HEIMAN BW-SHP13 look a like is not showing powerconsumption

canedje commented 3 years ago

Device

Product name: The device name as shown on the product or package. BlitzWolf BW-SPH13
Manufacturer: As per deCONZ GUI Basic cluster._TZ3000_g5xawfcq
Model identifier: As per deCONZ GUI Basic cluster. TS0121
Device type : Please remove all unrelated device types.
- Light

Screenshots

I did order in the past from Banggood a Heiman Blitzwolf BW-SPH13 This worked good. I now did order again two devices. These ones are not showing power messaurement. If I look in the Deconz GUI I do see there is not Heiman as Vendor but:

If I look at the cluster infor there is power Measurement (See pictures above) In HA there is no power measurement My early one (BlitzWolf 1) has:

width=1442&height=373 22B68522-5F96-4884-A334-31252EA2D353

Mimiix commented 3 years ago

@marithpl I am starting to think yours is defective.

marithpl commented 3 years ago

I have 2 plugs, none of them doesn’t show power sensors. But I found wired behavior, when I remove a device from phoscon/deconz it's not removed from HA.

SebLz commented 3 years ago

I have 2 plugs, none of them doesn’t show power sensors. But I found wired behavior, when I remove a device from phoscon/deconz it's not removed from HA.

After doing that, have you tried to:

refresh device list + remove orphaned entries

Reload integration:

?

marithpl commented 3 years ago

I try this way. edit: nothing only single entity for switch appears.

Mimiix commented 3 years ago

I have 2 plugs, none of them doesn’t show power sensors.

Do they show in the rest api?

marithpl commented 3 years ago

"13": {
"etag": "86434a0dc2be1e8922e17ae5d38ad1c2",
"hascolor": false,
"lastannounced": null,
"lastseen": "2021-04-06T18:44Z",
"manufacturername": "_TZ3000_g5xawfcq",
"modelid": "TS0121",
"name": "Smart plug 13",
-"state": {
"alert": "none",
"on": true,
"reachable": true
},
"swversion": null,
"type": "Smart plug",
"uniqueid": "60:a4:23:ff:fe:61:d7:fd-01"
},
-"15": {
"etag": "ac7a27f3daaa4d4d870c360fdf4b4f3e",
"hascolor": false,
"lastannounced": null,
"lastseen": "2021-04-06T18:45Z",
"manufacturername": "_TZ3000_g5xawfcq",
"modelid": "TS0121",
"name": "Smart plug 15",
-"state": {
"alert": "none",
"on": true,
"reachable": true
},
"swversion": null,
"type": "Smart plug",
"uniqueid": "60:a4:23:ff:fe:5e:2a:db-01"
}

Only as lights. I try to remove them from deconz/phoscn, I've cleared orphaned devices in HA, plug it off from power socket and of course I try to pair it from sensor tab not from light tab.

Mimiix commented 3 years ago

"13": {
"etag": "86434a0dc2be1e8922e17ae5d38ad1c2",
"hascolor": false,
"lastannounced": null,
"lastseen": "2021-04-06T18:44Z",
"manufacturername": "_TZ3000_g5xawfcq",
"modelid": "TS0121",
"name": "Smart plug 13",
-"state": {
"alert": "none",
"on": true,
"reachable": true
},
"swversion": null,
"type": "Smart plug",
"uniqueid": "60:a4:23:ff:fe:61:d7:fd-01"
},
-"15": {
"etag": "ac7a27f3daaa4d4d870c360fdf4b4f3e",
"hascolor": false,
"lastannounced": null,
"lastseen": "2021-04-06T18:45Z",
"manufacturername": "_TZ3000_g5xawfcq",
"modelid": "TS0121",
"name": "Smart plug 15",
-"state": {
"alert": "none",
"on": true,
"reachable": true
},
"swversion": null,
"type": "Smart plug",
"uniqueid": "60:a4:23:ff:fe:5e:2a:db-01"
}

Only as lights. I try to remove them from deconz/phoscn, I've cleared orphaned devices in HA, plug it off from power socket and of course I try to pair it from sensor tab not from light tab.

How about the sensor api call?

marithpl commented 3 years ago

I can't find any thing in common with this plugs. Only motion/door/water sensors.

monotonytonytony commented 3 years ago

@marithpl try to unplug/plug the device from the socket.

That worked for me!! I got 6 of those when I first tried to add them by searching for light for the first one and did not worked.

Then I added the 5 others with sensor search and it worked but I could not add the first one with power sensor even after deleting and reset the plug with sensor search.

Then I saw @manup post so I just made clicked on sensor search and then unpluged and plugged the item and that WORKED!!

Note that the item was already added before (without the power sensor) and there was no need to reset the plug as well.

Pedder007 commented 3 years ago

Hi all, I'm sorry, but I can do here whatever I want (re-discover/re-pair, plug/unplug, switch with or without load, reset, ...), this first of my plugs, which I already paired formerly to my dev environment, is not delivering any measures to my prod environment. And I just verified again that this already happens while pairing it to my ConBee stick / deCONZ. I just took another new one of these plugs, firstly paired it as switch and secondly as sensor and this one again works great. The problem plug is already by Phoscon not discoverd as sensor, as the respective search process always ends without a result.

marithpl commented 3 years ago

Hi all, I'm sorry, but I can do here whatever I want (re-discover/re-pair, plug/unplug, switch with or without load, reset, ...), this first of my plugs, which I already paired formerly to my dev environment, is not delivering any measures to my prod environment. And I just verified again that this already happens while pairing it to my ConBee stick / deCONZ. I just took another new one of these plugs, firstly paired it as switch and secondly as sensor and this one again works great. The problem plug is already by Phoscon not discoverd as sensor, as the respective search process always ends without a result.

Same in my case When I pair as sensor. Device shows in Mesh Network via VNC and in Light menu but always ends without finding any decvice.

Mimiix commented 3 years ago

I've got this device today(new from the mail!) and updated to 10.4. Afterwards, added it (as a light) and it immediatly started working.
I have a DS218+ and running in a VM on Raspbian. Total nodes: 35. Conbee II without a extension cable (living on the edge!

In terms of reporting. it seems to be just as fast as the older SHP13 i own, which is the _TZ3000_3ooaz3ng. I removed it from my network and added it again. Same result, added fine.

So i have no clue what you are doing during pairing, but it seems that there's not a issue on the deCONZ side.

GoSpursGoNL commented 3 years ago

I also got two today. _TZ3000_g5xawfcq Both were easy to pair, but only one shows power measurements in Home Assistant. Deconz 2.10.04 / 3/14/2021 with latest firmware.

Not sure if it is relevant: the one that shows power measurements I tried adding via Phoscon on the switches page (nothing seemed to have happened, but when I went to the lights page afterwards, it was there). The one without power measurements I added via the lights page.

marithpl commented 3 years ago

I've got this device today(new from the mail!) and updated to 10.4. Afterwards, added it (as a light) and it immediatly started working. I have a DS218+ and running in a VM on Raspbian. Total nodes: 35. Conbee II without a extension cable (living on the edge!

In terms of reporting. it seems to be just as fast as the older SHP13 i own, which is the _TZ3000_3ooaz3ng. I removed it from my network and added it again. Same result, added fine.

So i have no clue what you are doing during pairing, but it seems that there's not a issue on the deCONZ side.

You gave me a hope. I spent 1 hour this evening to try again - no effects. I even try to go closer to Conbee, because it's on the attic. No luck :( Is a chance to docker version have this issue? As I see you have VM.

It's so frustrating... Where are you come from? I am able to send you one of plugs for testing...

Here is one of plug log from deonz, maybe will help:

2021-04-09 20:00:05 | stdout | 22:00:05:408 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
-- | -- | --
2021-04-09 19:55:07 | stdout | 21:55:07:025 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:54:25 | stdout | 21:54:25:844 Bind response success for 0x60a423fffe61d7fd ep: 0x01 cluster: 0x0006
2021-04-09 19:54:04 | stdout | 21:54:04:847 Bind response success for 0x60a423fffe61d7fd ep: 0x01 cluster: 0x0006
2021-04-09 19:51:37 | stdout | 21:51:37:089 0x60a423fffe61d7fd found group 0xFFF0
2021-04-09 19:51:37 | stdout | 21:51:37:088 verified group capacity: 255 and group count: 1 of LightNode 0x60a423fffe61d7fd
2021-04-09 19:50:08 | stdout | 21:50:08:635 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:45:10 | stdout | 21:45:10:245 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:40:11 | stdout | 21:40:11:866 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:35:13 | stdout | 21:35:13:484 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:30:15 | stdout | 21:30:15:154 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:25:16 | stdout | 21:25:16:954 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:25:16 | stdout | 21:25:16:758 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:22:32 | stdout | 21:22:32:804 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x60A423FFFE61D7FD (seems to be active)
2021-04-09 19:22:32 | stdout | 21:22:32:803 binding for cluster 0x0006 of 0x60A423FFFE61D7FD exists (verified by reporting)
2021-04-09 19:21:38 | stdout | 21:21:38:795 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
2021-04-09 19:20:33 | stdout | 21:20:33:648 0x60a423fffe61d7fd found group 0xFFF0
2021-04-09 19:20:33 | stdout | 21:20:33:646 verified group capacity: 255 and group count: 1 of LightNode 0x60a423fffe61d7fd
2021-04-09 19:20:18 | stdout | 21:20:18:419 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:20:16 | stdout | 21:20:16:433 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:20:13 | stdout | 21:20:13:255 device announce 0x60A423FFFE61D7FD (0x5067) mac capabilities 0x8E
2021-04-09 19:20:13 | stdout | 21:20:13:253 device announce 0x60A423FFFE61D7FD (0x5067) mac capabilities 0x8E
2021-04-09 19:20:13 | stdout | 21:20:13:252 new node - ext: 0x60a423fffe61d7fd, nwk: 0x5067
2021-04-09 19:20:13 | stdout | 21:20:13:249 APS-DATA.indication from unknown node 0x60A423FFFE61D7FD
2021-04-09 19:20:13 | stdout | 21:20:13:249 unknown node 0x60A423FFFE61D7FD (0x5067), lqi: 255
2021-04-09 19:15:34 | stdout | 21:15:34:368 MgmtLeave_rsp 0x60a423fffe61d7fd seq: 15, status 0x00
2021-04-09 19:15:34 | stdout | 21:15:34:368 APS-DATA.indication from unknown node 0x60A423FFFE61D7FD
2021-04-09 19:15:34 | stdout | 21:15:34:367 unknown node 0x60A423FFFE61D7FD (0x757F), lqi: 255
2021-04-09 19:15:12 | stdout | 21:15:12:710 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
2021-04-09 19:15:12 | stdout | 21:15:12:703     0x60A423FFFE61D7FD force poll (2)
2021-04-09 19:15:12 | stdout | 21:15:12:072 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
2021-04-09 19:15:12 | stdout | 21:15:12:062     0x60A423FFFE61D7FD force poll (2)
2021-04-09 19:15:11 | stdout | 21:15:11:461 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
2021-04-09 19:15:11 | stdout | 21:15:11:450     0x60A423FFFE61D7FD force poll (2)
2021-04-09 19:15:10 | stdout | 21:15:10:733 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
2021-04-09 19:15:10 | stdout | 21:15:10:724     0x60A423FFFE61D7FD force poll (2)
2021-04-09 19:14:55 | stdout | 21:14:55:403 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:14:53 | stdout | 21:14:53:411 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:14:41 | stdout | 21:14:41:483 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:14:39 | stdout | 21:14:39:700 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:14:39 | stdout | 21:14:39:649 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:14:28 | stdout | 21:14:28:519 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:14:28 | stdout | 21:14:28:323 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:14:26 | stdout | 21:14:26:553 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:14:26 | stdout | 21:14:26:493 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:13:47 | stdout | 21:13:47:049 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x60A423FFFE61D7FD (seems to be active)
2021-04-09 19:13:47 | stdout | 21:13:47:048 binding for cluster 0x0006 of 0x60A423FFFE61D7FD exists (verified by reporting)
2021-04-09 19:13:18 | stdout | 21:13:18:886 0x60a423fffe61d7fd found group 0xFFF0
2021-04-09 19:13:18 | stdout | 21:13:18:886 verified group capacity: 255 and group count: 1 of LightNode 0x60a423fffe61d7fd
2021-04-09 19:13:03 | stdout | 21:13:03:307 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:13:01 | stdout | 21:13:01:318 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:12:59 | stdout | 21:12:59:297 delay sending request 149 dt 0 ms to 0x60A423FFFE61D7FD, ep: 0x01 cluster: 0x0004 onAir: 1
2021-04-09 19:12:58 | stdout | 21:12:58:470 device announce 0x60A423FFFE61D7FD (0x757F) mac capabilities 0x8E
2021-04-09 19:12:58 | stdout | 21:12:58:469 device announce 0x60A423FFFE61D7FD (0x757F) mac capabilities 0x8E
2021-04-09 19:12:58 | stdout | 21:12:58:468 new node - ext: 0x60a423fffe61d7fd, nwk: 0x757F
2021-04-09 19:12:58 | stdout | 21:12:58:466 APS-DATA.indication from unknown node 0x60A423FFFE61D7FD
2021-04-09 19:12:58 | stdout | 21:12:58:465 unknown node 0x60A423FFFE61D7FD (0x757F), lqi: 255
2021-04-09 19:12:54 | stdout | 21:12:54:664 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:12:54 | stdout | 21:12:54:664 APS-DATA.indication from unknown node 0x60A423FFFE61D7FD
2021-04-09 19:12:54 | stdout | 21:12:54:663 unknown node 0x60A423FFFE61D7FD (0x6094), lqi: 255
2021-04-09 19:12:54 | stdout | 21:12:54:256 APS-DATA.indication from unknown node 0x60A423FFFE61D7FD
2021-04-09 19:12:54 | stdout | 21:12:54:255 unknown node 0x60A423FFFE61D7FD (0x6094), lqi: 255
2021-04-09 19:12:42 | stdout | 21:12:42:507 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:12:42 | stdout | 21:12:42:506 APS-DATA.indication from unknown node 0x60A423FFFE61D7FD
2021-04-09 19:12:42 | stdout | 21:12:42:506 unknown node 0x60A423FFFE61D7FD (0x6094), lqi: 255
2021-04-09 19:12:40 | stdout | 21:12:40:723 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:12:40 | stdout | 21:12:40:722 APS-DATA.indication from unknown node 0x60A423FFFE61D7FD
2021-04-09 19:12:40 | stdout | 21:12:40:721 unknown node 0x60A423FFFE61D7FD (0x6094), lqi: 255
2021-04-09 19:12:40 | stdout | 21:12:40:676 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
2021-04-09 19:12:40 | stdout | 21:12:40:675 APS-DATA.indication from unknown node 0x60A423FFFE61D7FD
2021-04-09 19:12:40 | stdout | 21:12:40:674 unknown node 0x60A423FFFE61D7FD (0x6094), lqi: 255
2021-04-09 19:05:50 | stdout | 21:05:50:048 max transmit errors for node 0x60A423FFFE61D7FD, last seen by neighbors 65 s
2021-04-09 19:05:50 | stdout | 21:05:50:047 0x60A423FFFE61D7FD error APSDE-DATA.confirm: 0xE9 on task
2021-04-09 19:05:39 | stdout | 21:05:39:493 max transmit errors for node 0x60A423FFFE61D7FD, last seen by neighbors 55 s
2021-04-09 19:05:39 | stdout | 21:05:39:492 0x60A423FFFE61D7FD error APSDE-DATA.confirm: 0xE9 on task
2021-04-09 19:05:29 | stdout | 21:05:29:042 0x60A423FFFE61D7FD error APSDE-DATA.confirm: 0xE9 on task
2021-04-09 19:05:19 | stdout | 21:05:19:946 0x60A423FFFE61D7FD error APSDE-DATA.confirm: 0xE9 on task
2021-04-09 19:05:10 | stdout | 21:05:10:443 0x60A423FFFE61D7FD error APSDE-DATA.confirm: 0xE9 on task
2021-04-09 19:05:00 | stdout | 21:05:00:948 0x60A423FFFE61D7FD error APSDE-DATA.confirm: 0xE9 on task
2021-04-09 19:04:49 | stdout | 21:04:49:944 0x60A423FFFE61D7FD error APSDE-DATA.confirm: 0xE9 on task
2021-04-09 19:00:21 | stdout | 21:00:21:273 ZCL attribute report 0x60A423FFFE61D7FD for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000

jimz011 commented 3 years ago

@marithpl wow that helped. I had one plug that I had lying around for months but all it did was being a switch.

I semi followed your steps and boom it works now... amazing!

Steps I took:

remove the plug from deconz
remove the deconz integration in HA
unplug the plug and replug it
start a light search in phoscon
press and hold the power button of the plug for about 10 seconds
it should now find the switch as a light
start a sensor search in phoscon
unplug and replug the plug
wait until it finds the sensor (took about 30 seconds here)
re-add the deconz integration in HA
done!

To check if it is in HA

open developer-tools
search for the entity that belongs to the plug (usually name of the switch that was set in phoscon)
click on the info button on the left of the entity name
click on the cogs at the top right of the popup
click on the RELATED tab
you should now see the integration name and 2 entities, the power entity will be something like sensor.power_76

Also make sure that you update the deconz firmware and the phoscon application!

Obviously I don't know if this will work for you guys, but it did for me thanks to @marithpl

marithpl commented 3 years ago

@jimz011 In my case it doesnt work. Removing of Deconz integration seems be so risky for me to lost all entitites. For some of them i changed entity id so a lot of automations, groups will stop working.

jimz011 commented 3 years ago

Ah that sucks, I used to do that as well, but I find deconz too unreliable giving the correct names every time when I add a device. Sometimes it will add the entity, but with the name it was given (rather than the name that I had set in phoscon).

So nowadays when I add a device in phoscon I give a name to the device first, assign it to a room/group and then add it to HA. It gives me the entity name I wanted (as this would be the same as the name defined in phoscon), but also the possibility to quickly remove/add deconz when needed. This was also very useful when I did a fresh install of HA after I switched to docker, since the names always stay the same, no automations were affected after switching to a new HA install.

Personally I would suggest doing the same. Changing entitynames in automations should be a quick job when using vscode and do a full HA folder search for the old entity name to swap them with the new one. If you have 30 devices, you'd only need to do this 30 times and then never again 🤣. But hey its just a suggestion which saved me a lot of time in the past (and still does every time I need it).

Pedder007 commented 3 years ago

Hi @jimz011, I tested your method without the point(s) 'remove/re-add the deconz integration in HA' and it works :+1 It seems to be, that the second un-pluging seems making the difference to what I tested before 😄 By doing this, Phoscon states (green bottom bar in the search window) a detection/connection also of the sensors, whereas they are not shown under sensors (but same with my other two plugs which are already working). I then switched to deCONZ GUI and was able to verify that the values are in there propperly 👍 After that I tried to get the plug propperly discovered into my HomeAutomation (Pimatic), but there it was still only discovered with the plug ID and not with the sensors IDs, which should normally (as with my other plugs) be available. However, I tested a bit around by manually configuring the sensor IDs and yet was able to identify the relevant ID for voltage, but not the rest (current, power, consumption). Also my two other plugs are using 2 sensor IDs (normally discovered by Pimatic as dezimal numbers), but I wasn't able to identify them in deCONZ (hex?). Do you have an idea how I maybe could evaluate the relevant IDs frome the deCONZ gui or from elsewhere? The IDs there are showing as following (0x0505 - 0x050B): grafik

PS. A complete de-coupling of my Pimatic setup from deCONZ is also not an option 😄

Pedder007 commented 3 years ago

Hi all, my last post seems having been a one-hit-wonder 🤣 Afterwards I tried to reproduce it, but the second step with the sensor detection never again ended with success (green bar in the respective Phoscon context-window). As I'm running also ioBroker, I implemented the respective plugin for deconz also there and now in minimum found the used sensor IDs, but wondered a bit about other things:

The device-ID related parameters look exactly similiar to those ones of the plugs which are working propperly:

But the sensor parameters definitly look other:

the data is not updated at all (the date here might be that one, when I firstly paired the plug to my dev environment)
current, power and voltage shows nonsens (in reality a small charging device was plugged into it, surely consuming something and running on >220V)
there is a temperatur value in, which I do definitely not have in the other plug's parameters and it also show nonsens (41°C)

Wondering here is, that via deCONZ gui I can read the values propperly (and also have no temperature in), but that they are not delivered propperly to two different systems via the rest-api, whereas this works propperly for two other devices/plugs of the same type, discovered and shown with the same name TS0121 and also manufacturer _TZ3000_g5xawfcq in Phoscon/deCONZ.

As I did spent now already hours into that issue, I will throw the device into the waste and simply order a new one.... 😄 ... or maybe use it elsewhere without measurements...

MauricioXavier13 commented 3 years ago

I fixed 2 of this devices only with switch doing the following: (Device previously added and online as a light, with some item connected to the socket/plug turned on)

In deconz:

Panels, Cluster Info, Basic
Reset Factory reset (Exec button)
Go to Phoscon, Add SENSOR (not light) And it turns green as a discovered sensor.

BoneheadFraggle commented 3 years ago

I installed one today. Added as a light in Phoscon. Sensors were added to Home Assistant, but didn't work. Added again as sensor in Phoscon. Sensors were added to Home Assistant again, this time they work fine (kind of).

Only thing I'm not that satisfied with is the update frequency. Seems to be once or twice a minute or so.

On | 22 | 47 | 08 | | 22 | 47 | 18 | | 10 Off | 22 | 47 | 57 | | 22 | 48 | 23 | | 26 On | 22 | 48 | 45 | | 22 | 49 | 32 | | 47 Off | 22 | 49 | 55 | | 22 | 50 | 29 | | 34 On | 22 | 51 | 10 | | 22 | 51 | 22 | | 12 Off | 22 | 52 | 30 | | 22 | 53 | 14 | | 44

Is it possible to change that to something more frequent, like ~5 s or 5% value change ?

Pedder007 commented 3 years ago

Hi @MauricioXavier13, you gave me new hope 👍, but further on no success here 😢 Tested the 'factory reset' already earlier, but afterwards always firstly learned the plug as light again and then tried as sensor.

Thus I now tried to learn it firstly as sensor, after the deCONZ reset, as you wrote.

But somewhere in deCONZ something is stored which leads to the fact, that allthough trying to learn the plug as sensor, in the background it is connected again as light (and the sensor learning stays w/o result). Depending on the way my exact steps have been (incl./or not deleting the device additionally in deCONZ), it also remembers to the old name (changed by me in Phoscon). The sensors are further on not detected/connected at all.

But seeing this, for me clearly says, that what ever one tries to delete/reset this plug, something stays in deCONZ or on the plug itself, which leads to that problem. Whatever it is, there is something which is not deleted propperly after once having already paired this plug.

Smanar commented 3 years ago

@Pedder007 When you are seing the value in the attribute page (voltage/current/power), can you try that:

Set phoscon in permit join (add new sensor)
Read again basic attribute on deconz (Cluster 0x0000, button "read")

But your problem is the power sensor is missing or the wrong values ?

Pedder007 commented 3 years ago

You are right @Smanar, I should have been more precise. Allthough the sensors are not detected (visible) in Phoscon, the values are in deCONZ. Please see below screenshoot. What at least doesn't work is, that I'm not able to get the values via the rest-api and following not in my Home Automation (Pimatic and also not in ioBroker), like it already works with 2 other of these plugs.

Smanar commented 3 years ago

So if you totaly miss the sensor entry, can try my previous procedure, it can trigger an inclusion, but without reseting the device (Some devices have "moving cluster" after the reset)

Pedder007 commented 3 years ago

You mean:

Set phoscon in permit join (add new sensor)
Read again basic attribute on deconz (Cluster 0x0000, button "read")

right? I tried already in parallel but it didn't work. To be precise:

stopped deconz headless
started deconz gui
went to the device
read the values
started Phoscon directly out of deconz gui
started sensor learning
read the values again in the deconz gui
but no 'green success bar' in Phoscon (> 1 minute search)

What are 'moving clusters'? - what I observed in former tests, that sometime the device comes back with a low number ID, where I might have deleted formerly an other device and in other cases it takes a high number ID ...

Pedder007 commented 3 years ago

A question, as I'm just reading about the current rest-api update (Longshot): Maybe this could solve these problems with the plug here? ' Support delete device and its REST resources @manup (#4736): The new deleteDevice(extAddress) function has following side effects:

Delete all related Sensor and LightNodes;
Delete device related entries from database;
Send ZDP Mgmt_Leave_req to device to remove it from network (also sleeping end-devices).

Coming with v2.11.0 this can be invoked from the GUI via Delete key or node context menu.'

Btw.: Great job you all together did there!!! 👍 👍 👍

Smanar commented 3 years ago

read the values again in the deconz gui

The values from basic attribute ? no the power mesurement.

For the moving clusters, I haven't find again the issue, but on another device (perhaps this one) the cluster 0x0B04 move, so the "device description" during the inclusion and some minuts after is not the same, and unfortunately deconz missing good information at start.

You can too try to resend commands presents on the first cirlcle on the node title (and when phoscon is in permit join), but don't make reset

And take a look on third app after to be sure, the "'green success bar" is not 100% perfect neither.

Pedder007 commented 3 years ago

sure 😅 read the values from the power measurement (shown in the screenshoot above) and they updated there (in the deconz gui). With third party app you mean my HomeAutom? - I did so, but they were still not able to discover the sensors (IDs), only the device ID And already described somewhere above, really wondering is, that ioBroker is discovering a temperature value from this device, always showing 41°C and a negativ power value:

Smanar commented 3 years ago

With third party app you mean my HomeAutom

Yep for exemple.

Have you something connected to consume power ?

Pedder007 commented 3 years ago

Yes, tried with and w/o load also formerly.

MauricioXavier13 commented 3 years ago

@Pedder007 , do you have some item connected to the plug consuming power? Yesterday with my procedure we fixed (me and some other guys in a forum) 7 plugs with this problem (no sensors).

In some cases we needed to insist and to keep trying the add sensor 2 or 3 times. But worked... Try also to read attributes between some steps.

But you don't need to delete or something similar. If the plug is represented in lights, just forget it. Just reset, do some read attributes and do ADD SENSOR.

Let some device working and consuming before. And then keep trying. 7 of 7 fixed yesterday! :)

Pedder007 commented 3 years ago

@MauricioXavier13, thanks for the additional hints! With 'If the plug is represented in lights, just forget it.', you mean simply to ignor that the plug is already there as light, right?

Pedder007 commented 3 years ago

Wow!!! that at least really worked!!! 😄 👍

One has really to insist and stay strong to get the sensor data also into the rest-api. It didn't work in the first round, I got the 'green bar' but still no sensor IDs further on via rest-api. I tried it again then, and in the second sensor scan ~4.x minutes, by clicking wild around in the device, reading the measurements, and also on/off and changing the load itself, once I again go the 'green bar' and now afterwards, I was also able to get the measurements into ioBroker and Pimatic 👍 Interesting is, that now, at least, deConz choosed also new IDs for the sensors (58. 59), which have never used before in my setup. Never saw such in all of my ZigBee devices and never treated one of them that rude 🤣

Thanks again @MauricioXavier13 and also @Smanar !!!

MauricioXavier13 commented 3 years ago

Sometimes they need time and retries! Good to hear that you solved it @Pedder007! 👍

Great!

marithpl commented 3 years ago

Sometimes they need time and retries! Good to hear that you solved it @Pedder007! 👍

Great!

My hero. I gave a last chance for this plug before throw them to trash. I clicked read attributes in Cluster Info and it works. Power consumption shows in HA. At the same time I turn on sensor search.

MauricioXavier13 commented 3 years ago

Sometimes they need time and retries! Good to hear that you solved it @Pedder007! 👍 Great!

My hero. I gave a last chance for this plug before throw them to trash. I clicked read attributes in Cluster Info and it works. Power consumption shows in HA. At the same time I turn on sensor search.

Well... as i can see always works for many people! I discovered this solution/fix yesterday and since that time we managed/helped to fix almost 10 plugs! It seems that is infallible... (taking in consideration some retries in some cases) 😄

GoSpursGoNL commented 3 years ago

@Pedder007 , do you have some item connected to the plug consuming power? Yesterday with my procedure we fixed (me and some other guys in a forum) 7 plugs with this problem (no sensors).

In some cases we needed to insist and to keep trying the add sensor 2 or 3 times. But worked... Try also to read attributes between some steps.

How do I get to that screen? I have selected the node and see 'no cluster detected' on the cluster info tab. Without other info nor buttons.

caro7372 commented 3 years ago

@Pedder007 , do you have some item connected to the plug consuming power? Yesterday with my procedure we fixed (me and some other guys in a forum) 7 plugs with this problem (no sensors).

In some cases we needed to insist and to keep trying the add sensor 2 or 3 times. But worked... Try also to read attributes between some steps.

But you don't need to delete or something similar. If the plug is represented in lights, just forget it. Just reset, do some read attributes and do ADD SENSOR.

Let some device working and consuming before. And then keep trying. 7 of 7 fixed yesterday! :)

You are absolutely right!! Tried long but now understand how to do this. Thanks very much.

MauricioXavier13 commented 3 years ago

@Pedder007 , do you have some item connected to the plug consuming power? Yesterday with my procedure we fixed (me and some other guys in a forum) 7 plugs with this problem (no sensors). In some cases we needed to insist and to keep trying the add sensor 2 or 3 times. But worked... Try also to read attributes between some steps.

How do I get to that screen? I have selected the node and see 'no cluster detected' on the cluster info tab. Without other info nor buttons.

Select the device in deconz. Right "circle" and Basic. Check Cluster Info in the Panels.

Screenshot_20210415-220830

MauricioXavier13 commented 3 years ago

@Pedder007 , do you have some item connected to the plug consuming power? Yesterday with my procedure we fixed (me and some other guys in a forum) 7 plugs with this problem (no sensors). In some cases we needed to insist and to keep trying the add sensor 2 or 3 times. But worked... Try also to read attributes between some steps. But you don't need to delete or something similar. If the plug is represented in lights, just forget it. Just reset, do some read attributes and do ADD SENSOR. Let some device working and consuming before. And then keep trying. 7 of 7 fixed yesterday! :)

You are absolutely right!! Tried long but now understand how to do this. Thanks very much.

Worked for you also? Oh great. Amazing!

GoSpursGoNL commented 3 years ago

Perfect, also works for me.

What I did:

previously already added as light. Showed up in Home Assistant, without power measurements.
Select the device in Deconz. Right "circle" and Basic -> click on 'exec' (not sure if this was necessary).
open Phoscon in second tab side by side with Deconz
in Deconz click on 'read'.
In Phoscon start a search for a new sensor
whist it is searching, start clicking 'read' button in ever couple of seconds in Deconz, start turning the switch (physically) on and off every couple of seconds. I had a desk light attached to it so that there would be actual power usage.
in my case Phoscon showed the green bar after 10-15 secnds or so at the first attempt
additional power usage entities appeared in HA directly if I remember correctly, but actual figures only started coming in after I had removed the device from the power socket and plugged it in again

MauricioXavier13 commented 3 years ago

Perfect, also works for me.

What I did:

previously already added as light. Showed up in Home Assistant, without power measurements.

Select the device in Deconz. Right "circle" and Basic -> click on 'exec' (not sure if this was necessary).

open Phoscon in second tab side by side with Deconz

in Deconz click on 'read'.

In Phoscon start a search for a new sensor

whist it is searching, start clicking 'read' button in ever couple of seconds in Deconz, start turning the switch (physically) on and off every couple of seconds. I had a desk light attached to it so that there would be actual power usage.

in my case Phoscon showed the green bar after 10-15 secnds or so at the first attempt

additional power usage entities appeared in HA directly if I remember correctly, but actual figures only started coming in after I had removed the device from the power socket and plugged it in again

Glad that works for you either! 🙂

userMak commented 3 years ago

@MauricioXavier13 thank you! I had one plug that I could not connect to HA and I did followed your instructions.

jreidel commented 3 years ago

Thank you guys!! It's finally working on all my BW-SHP13 plugs!!

MrMiracles commented 3 years ago

Well, I read all of above. Tried everything, accomplished something. I get "electrical measurement" (shows in HA as "power") working but "Simple metering" (which I think should be Consumption in HA) stays at 0 or "unknown". From the comments above it looks like you are all talking about not have both, right?

For clarification:

It shows up at HA:

Simple metering is 0 or 0x00 or whatever reading I should read here.

Power meter is doing fine

jimz011 commented 3 years ago

This might sound stupid, but try taxing the plug.

Make it use some power, this helped for me.

E.g. if a computer is plugged into it, start a game so that your device uses more power.

MrMiracles commented 3 years ago

Thanks, will let it run for a while. see if something happens. Update: You are an hero. Been busy with this for hours now and it just needed more power. 60+ watts did it for me. Now showing consumption as well. Thanks everyone here!

Pedder007 commented 3 years ago

That was the same here :-). Plugged a lamp on it, something >60W, and then suddenly got all measurements back. Voltage, currency, power and consumption. Reading this here all we should bill our efforts to the manufacturer 🤣

Pr0gr4mm3r commented 3 years ago

Perfect, also works for me.

What I did:

previously already added as light. Showed up in Home Assistant, without power measurements.

Select the device in Deconz. Right "circle" and Basic -> click on 'exec' (not sure if this was necessary).

open Phoscon in second tab side by side with Deconz

in Deconz click on 'read'.

In Phoscon start a search for a new sensor

whist it is searching, start clicking 'read' button in ever couple of seconds in Deconz, start turning the switch (physically) on and off every couple of seconds. I had a desk light attached to it so that there would be actual power usage.

in my case Phoscon showed the green bar after 10-15 secnds or so at the first attempt

additional power usage entities appeared in HA directly if I remember correctly, but actual figures only started coming in after I had removed the device from the power socket and plugged it in again

Great, this worked. Thanks @MauricioXavier13 👌

dresden-elektronik / deconz-rest-plugin

HEIMAN BW-SHP13 look a like is not showing powerconsumption #3788

Device

Screenshots