You need support for it.
Can you share a Screenshot of the basic cluster?
You can’t. Energy measurements are not exposed by Phoscon, only via API.
Hi. I can see that it’s not possible at the moment. But that’s not the reason why I’m writing here. This is why this should be added to phoscom. Why shouldn’t display all the data that is available?
Ah it is showing in the api?
They should be exposed under sensors, not lights.
In deconz right click on the node. Edit DDF. Change the status from silver to gold.
Save and then remove and repair the device. It’s supported, just not tested.
Hi Mimiix
Can i do a similar thing for my device?
mine is only draft.
Your device is different.
I recommend opening a device request.
1 Like
Hi Mimiix
The Device has the same id as another device in your device list.
https://dresden-elektronik.github.io/deconz-rest-doc/devices/tuya/_TZ3000_typdpbpg_smart_plug_eu/
but the manufacture name has changed a bit, i guess its because this device is sold by many companies with there own name on it.
should i still open a new device case or how should i proceed?
Hi,
As the manufacturer name is different, we can not know for sure its the same device. Thats why you need to open a new device request.
So yes, you need to open an new device request.
Oh dear. Running from one issue (shitty hardware/Blitzwolf BW-SHP13 (_TZ3000_amdymr7l) reports ZERO current consumption regularly - #14 by bcutter) to to the other - the _TZ3000_j1v25l17 is not showing any kWh measurements.
I checked the DDF and it is set to Gold already (running deCONZ 2.25.3).
What can I do to make this device show kWh measurements?!?
This for sure is a special deCONZ only thing… 
same like
Looks like there was a typo in the DDF that got resolved.
Ah interesting. But I don’t think that’s the issue here.
- The referenced bug seems to have been introduced later. As mentioned, I’m running latest available (HA deCONZ addon user) deCONZ v2.25.3.
- 2.25.3 shipped DDF looks like this:
So the search goes on. Interestingly the 0702 contains this value which slowly increases. No idea why it does not update in HA.
Maybe it’s not a deCONZ but a HA deCONZ integration issue looking at the HA log:
15 raw should translate to 0.15 kWh, shouldn’t it?
When you clicked read, did it update in ha?
No. I’m restarting HA now to see if the “deconz does not generate unique IDs” errors disappear - and hopefully the entities’ value updates.
What does the API show?
lights:
{
"capabilities": {
"alerts": [
"none",
"select",
"lselect"
]
},
"config": {
"groups": []
},
"etag": "XXXXXXXXXXXXXXXXXX",
"hascolor": false,
"lastannounced": "2024-08-23T12:36:23Z",
"lastseen": "2024-08-23T14:10Z",
"manufacturername": "_TZ3000_j1v25l17",
"modelid": "TS011F",
"name": "XXXXXXXXXXX",
"state": {
"alert": "none",
"on": true,
"reachable": true
},
"swversion": "1.0.4",
"type": "Smart plug",
"uniqueid": "XXXXXXXXXXXXXXXXX-01"
}
sensors (power):
{
"config": {
"on": true,
"reachable": true
},
"ep": 1,
"etag": "XXXXXXXXXXXXXXXXX",
"lastannounced": "2024-08-23T12:36:23Z",
"lastseen": "2024-08-23T14:33Z",
"manufacturername": "_TZ3000_j1v25l17",
"modelid": "TS011F",
"name": "Power 115",
"state": {
"current": 598,
"lastupdated": "2024-08-23T14:33:52.733",
"power": 98,
"voltage": 241
},
"swversion": "1.0.4",
"type": "ZHAPower",
"uniqueid": "XXXXXXXXXXXXXXXX"
}
Anything suspicious here @Mimiix ?
Ah, here we go:
sensors/consumption:
{
"config": {
"on": true,
"reachable": true
},
"ep": 1,
"etag": "XXXXXXXXXXX",
"lastannounced": "2024-08-23T12:36:23Z",
"lastseen": "2024-08-23T14:38Z",
"manufacturername": "_TZ3000_j1v25l17",
"modelid": "TS011F",
"name": "Consumption 116",
"state": {
"consumption": 0,
"lastupdated": "none"
},
"swversion": "1.0.4",
"type": "ZHAConsumption",
"uniqueid": "XXXXXXXXXXXXXX-0702"
}
So why does the API report "consumption": 0, when the attribute has (currently) 29 stored?
What transforms the raw data to the API - the DDF?
Here’s the full DDF currently used (stock / default as of deCONZ v2.25.3):
{
"schema": "devcap1.schema.json",
"manufacturername": ["_TZ3000_nkcobies","_TZ3000_j1v25l17","_TZ3000_ynmowqk2"],
"modelid": ["TS011F","TS011F","TS011F"],
"product": "HG08673 LIDL SilverCrest smart plug with monitoring (DK, EU, FR)",
"sleeper": false,
"status": "Gold",
"subdevices": [
{
"type": "$TYPE_SMART_PLUG",
"restapi": "/lights",
"uuid": [
"$address.ext",
"0x01"
],
"items": [
{
"name": "attr/id"
},
{
"name": "attr/lastannounced"
},
{
"name": "attr/lastseen"
},
{
"name": "attr/manufacturername"
},
{
"name": "attr/modelid"
},
{
"name": "attr/name"
},
{
"name": "attr/swversion",
"parse": {"fn": "zcl:attr", "ep": 1, "cl": "0x0000", "at": "0x0001", "script": "../tuya/tuya_swversion.js"},
"read": {"fn": "zcl:attr", "ep": 1, "cl": "0x0000", "at": "0x0001"}
},
{
"name": "attr/type"
},
{
"name": "attr/uniqueid"
},
{
"name": "state/alert",
"default": "none"
},
{
"name": "state/on"
},
{
"name": "state/reachable"
}
]
},
{
"type": "$TYPE_POWER_SENSOR",
"restapi": "/sensors",
"uuid": [
"$address.ext",
"0x01",
"0x0b04"
],
"fingerprint": {
"profile": "0x0104",
"device": "0x0051",
"endpoint": "0x01",
"in": [
"0x0000",
"0x0B04"
]
},
"items": [
{
"name": "attr/id"
},
{
"name": "attr/lastannounced"
},
{
"name": "attr/lastseen"
},
{
"name": "attr/manufacturername"
},
{
"name": "attr/modelid"
},
{
"name": "attr/name"
},
{
"name": "attr/swversion",
"parse": {"fn": "zcl:attr", "ep": 1, "cl": "0x0000", "at": "0x0001", "script": "../tuya/tuya_swversion.js"}
},
{
"name": "attr/type"
},
{
"name": "attr/uniqueid"
},
{
"name": "config/on"
},
{
"name": "config/reachable"
},
{
"name": "state/current"
},
{
"name": "state/lastupdated"
},
{
"name": "state/power"
},
{
"name": "state/voltage"
}
]
},
{
"type": "$TYPE_CONSUMPTION_SENSOR",
"restapi": "/sensors",
"uuid": [
"$address.ext",
"0x01",
"0x0702"
],
"fingerprint": {
"profile": "0x0104",
"device": "0x0051",
"endpoint": "0x01",
"in": [
"0x0000",
"0x0702"
]
},
"items": [
{
"name": "attr/id"
},
{
"name": "attr/lastannounced"
},
{
"name": "attr/lastseen"
},
{
"name": "attr/manufacturername"
},
{
"name": "attr/modelid"
},
{
"name": "attr/name"
},
{
"name": "attr/swversion",
"parse": {"fn": "zcl:attr", "ep": 1, "cl": "0x0000", "at": "0x0001", "script": "../tuya/tuya_swversion.js"}
},
{
"name": "attr/type"
},
{
"name": "attr/uniqueid"
},
{
"name": "config/on"
},
{
"name": "config/reachable"
},
{
"name": "state/consumption",
"refresh.interval": 420,
"parse": {
"at": "0x0000",
"cl": "0x0702",
"ep": 1,
"eval": "item.val = 10 * Attr.val"
}
},
{
"name": "state/lastupdated"
}
]
}
],
"bindings": [
{
"bind": "unicast",
"src.ep": 1,
"cl": "0x0006",
"report": [
{
"at": "0x0000",
"dt": "0x10",
"min": 1,
"max": 360
}
]
},
{
"bind": "unicast",
"src.ep": 1,
"cl": "0x0702",
"report": [
{
"at": "0x0000",
"dt": "0x25",
"min": 1,
"max": 360,
"change": "0x0000000A"
}
]
},
{
"bind": "unicast",
"src.ep": 1,
"cl": "0x0B04",
"report": [
{
"at": "0x0505",
"dt": "0x21",
"min": 1,
"max": 360,
"change": "0x00000001"
},
{
"at": "0x0508",
"dt": "0x21",
"min": 1,
"max": 360,
"change": "0x00000064"
},
{
"at": "0x050B",
"dt": "0x29",
"min": 1,
"max": 360,
"change": "0x00000001"
}
]
}
]
}
The only difference compared to the current deconz-rest-plugin/devices/lidl/hg08673.json at master · dresden-elektronik/deconz-rest-plugin · GitHub I could spot is:
2.25.3:
"eval": "item.val = 10 * Attr.val"
latest on GitHub:
"eval": "Item.val = Attr.val * 10"
That’s not relevant at all and a wrong trail, isn’t it? Or is it the small “i” of “item.val”?
I’m starting to get a bit lost here after fiddling around with one device for 3 hours. 