BW-SHP15 Plugs: What does this mean: "No power sensor found for ..."

[iisworks]

I am seeing a lot of messages like:
No power sensor found for …
No consumption sensor found for

Blitzwolf BW-SHP15 Plugs (Tuya), and in the api values seem not to update any more.
Just upgraded to the new 2.14 Beta in Docker on Synology. Not using custom DDF yet, but it all started to happen after some (failed) attempts to get newer Tuya plugs working with DDF.

20:45:13:970 No power sensor found for 0x84FD27FFFECE7C45, endpoint: 0x01
20:45:13:971 ZCL attribute report 0x84FD27FFFECE7C45 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:45:18:600 Skip idle timer callback, too early: elapsed 572 msec
20:45:25:976 No power sensor found for 0x84FD27FFFECE7C45, endpoint: 0x01
20:45:25:977 ZCL attribute report 0x84FD27FFFECE7C45 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:45:26:154 Bind response success for 0x588e81fffed38ebc ep: 0x01 cluster: 0x0B04
20:45:28:633 Device TTL 2372 s flags: 0x7
20:45:28:976 No power sensor found for 0x84FD27FFFECE7C45, endpoint: 0x01
20:45:28:977 ZCL attribute report 0x84FD27FFFECE7C45 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:45:35:024 No power sensor found for 0x84FD27FFFECE7C45, endpoint: 0x01
20:45:35:024 ZCL attribute report 0x84FD27FFFECE7C45 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:45:37:215 Bind response success for 0x588e81fffeff604d ep: 0x01 cluster: 0x0B04
20:45:39:600 Skip idle timer callback, too early: elapsed 120 msec
20:45:40:990 No power sensor found for 0x84FD27FFFECE7C45, endpoint: 0x01
20:45:40:990 ZCL attribute report 0x84FD27FFFECE7C45 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:45:43:601 skip binding for attribute reporting of ep: 0x00 cluster 0x0001 (end-device might sleep)
20:45:43:995 No power sensor found for 0x84FD27FFFECE7C45, endpoint: 0x01
20:45:43:995 ZCL attribute report 0x84FD27FFFECE7C45 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:45:45:701 ZCL attribute report 0x84FD27FFFED24544 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:45:49:000 No power sensor found for 0x84FD27FFFECE7C45, endpoint: 0x01
20:45:49:000 ZCL attribute report 0x84FD27FFFECE7C45 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:45:50:605 No power sensor found for 0x84FD27FFFED24544, endpoint: 0x01
20:45:50:606 ZCL attribute report 0x84FD27FFFED24544 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:45:51:099 sensor 117 (lumi.sensor_motion): disable presence
20:45:51:205 emit event/tick: 0x00158d000530371f
20:45:51:275 	0x00158D000530371F force poll (2)
20:45:52:599 Skip idle timer callback, too early: elapsed 472 msec
20:45:52:700 Set sensor check interval to 1000 milliseconds
20:45:52:715 No consumption sensor found for 0x84FD27FFFECE99DC, endpoint: 0x01
20:45:52:716 ZCL attribute report 0x84FD27FFFECE99DC for cluster: 0x0702, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:45:55:683 ZCL attribute report 0x588E81FFFED38EBC for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
20:45:55:758 Bind response success for 0x588e81fffed38ebc ep: 0x01 cluster: 0x0B04
20:45:58:678 No consumption sensor found for 0x84FD27FFFECE7C45, endpoint: 0x01
20:45:58:678 ZCL attribute report 0x84FD27FFFECE7C45 for cluster: 0x0702, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
20:46:00:911 ZCL attribute report 0x00158D000461F3E0 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F

[Update] Had to restore the previous database to get things going again.

[Smanar]

@iisworks

No power sensor found for

You have this error message when deconz receive a Electrical Measurement request (from this cluster) but there is no sensor in the API that use this adress ( = the device that make this request have not sensor of this type in the API)

The device can be in the API as “light” device but not have ZHAPower sensor entry.

[iisworks]

So that means that the device pairing/description/config in deconz got corrupted?
I had this happen as described here:

Issue: Deconz becomes unresponsive when using DDF for Tuya TS011F Plugs

This has been going on for a while (2.13.3 - 2.14), seems to be related to DDF for Tuya plugs. I managed to collect some clues and a bit of logging. Deconz is running fine with 5 existing BW-SHP15 plugs (they report every few seconds), as long as I stay away from DDF. I have this DDF setting and no custom DDF files in use or loaded: [image] As soon as I enable Silver, the built-in NEO DDF is picked up and something happens that slows down deconz. I also see that the existing BW-SHP15 plugs do…

Like I said the only way to solve it was to restore the database. Or maybe removing + re-pairing all plugs would have helped but that was no option because all the automation involved in my 3rd party app would be broken.

[Smanar]

If the device is realy the “_TZ3000_mraovvmm” and have "TS011F " as model id, have 0x1002 as manufacture number, and have as mac adress start “0x84fd27”.

From the code the 2 sensors need to be created during the inclusion and can work without DDF.

If the sensor is created, it will be not deleted, except if you play with DDF (for exemple include the device using DDF, then disable DDF for exemple)