TZ3000_gjnozsaz appears but only power and link quality - No power meter #5633

waazdakka · 2022-01-03T16:13:56Z

Describe the bug

The plug appears in deCONZ with all its capabilities, but values stay by default in the electrical mesurement and the simple metering panels

Steps to reproduce the behavior

Pair Tuya TZ3000_gjnozsaz TS011F plug to deCONZ
See them appear into deCONZ and succeed to use them (on / off)
Go to Status panel
See nothing changing in the electrical measurement and simple metering panels

Expected behavior

Obtain the consumption and other electrical values on deCONZ

Screenshots

Environment

Host system: Raspberry Pi 4
Running method: Home Assistant deCONZ Add-on
Firmware version: 26660700
deCONZ version: 2.13.04 / 18/12/2021
Device: ConBee II
Do you use an USB extension cable: no
Is there any other USB or serial devices connected to the host system? no

Mimiix · 2022-01-03T16:19:31Z

What if you click read?

If the values don't change, the device probsbly doesn't support it.

waazdakka · 2022-01-03T18:21:29Z

Hmm it's sold as power metering plug :'(
https://fr.aliexpress.com/item/1005003523027932.html

Mimiix · 2022-01-03T18:59:53Z

If you click read on the clusters, does it show power consumption? Make sure something is plugged in.

waazdakka · 2022-01-04T21:33:18Z

Nothing, it stays at zero and I have a device plugged in. In found some similar issue on Z2MQTT, don't know if it could be a related-issue? Koenkk/zigbee2mqtt#10487

Mimiix · 2022-01-04T22:05:32Z

That doesn't say anything about the device power metering

akinek · 2022-01-08T22:02:01Z

I have the same plug.

Smanar · 2022-01-09T10:00:11Z

Ok, so for you it seem working, can try with a DDF https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet
you have a sample here, used for most of plugs #5577

With text editor, just need to edit thoses lines, the modelid is probably the same (visible on basic clsuter).

    "manufacturername": "_TZ3000_w0qqde0g",
    "modelid": "TS011F",
    "product": "NAS-WR01B",
    "path": "/devices/neo/NAS-WR01B.json",

wlfrdssn · 2022-01-10T19:41:47Z

Ok, so for you it seem working, can try with a DDF https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet you have a sample here, used for most of plugs #5577

With text editor, just need to edit thoses lines, the modelid is probably the same (visible on basic clsuter).
    "manufacturername": "_TZ3000_w0qqde0g",
    "modelid": "TS011F",
    "product": "NAS-WR01B",
    "path": "/devices/neo/NAS-WR01B.json",

I am not that familiar to DDF (and kind of new to deconz). l don't get this to work. Ill changed the manufacturnam and got new entities in HA but with value unknown. Trying to understand what I am doing wrong but have no clue.

Smanar · 2022-01-10T20:55:31Z

I don't understand why you have 3 entities ?

All 3 are for the same device ? you can find the device JSON in phoscon / help / API Information.
The DDF don't look so bad
The status is other than "draft" ?
You have enabled DDF in the "control" tab ?
Can take "hot reload" in the menu of the DDF editor.
When you select "edit DDF" on the node, what is the path in the windows title ?
where have you saved the DDF ?

wlfrdssn · 2022-01-11T08:21:11Z

I don't understand why you have 3 entities ?

All 3 are for the same device ? you can find the device JSON in phoscon / help / API Information. The DDF don't look so bad The status is other than "draft" ? You have enabled DDF in the "control" tab ? Can take "hot reload" in the menu of the DDF editor. When you select "edit DDF" on the node, what is the path in the windows title ? where have you saved the DDF ?

No it aint the same. Ill got five plugs so there is nothing wrong there. But somehow I manage to get double up of all of them like power_28_2 and so on when i changed in the DDF and hot reloaded.

Oh thanks, I was trying to find where I could find the API JSON on a easy way.

"lastannounced": null,
    "lastseen": "2022-01-11T07:38Z",
    "manufacturername": "_TZ3000_gjnozsaz",
    "modelid": "TS011F",
    "name": "Consumption 27",
    "state": {
        "consumption": null,
        "lastupdated": "none"

I have been tested status draft and status silver.
DDF is enabled in control tab
Have tested hot reload

now its devices/smartplug.json
I am on a Windows machine and have tested to save the DDF in AppData/Local/Dresden..../deconz/devices~ and C:/Deconz/devices/...

Now I found something! In the API information I found that I have sensors named power 36,38,40,42 also and they got the power information! But I can't find the sensors in HA. Somehow they are doubled up and just the first one with no information Ill find in HA.

Mimiix · 2022-01-11T08:31:54Z

In the Control tab, is the Status you use for the DDF enabled? So if you have it set on "silver" , is silver also enabled in the control tab?

wlfrdssn · 2022-01-11T08:37:39Z

Hmm no clue on that one. In control I have set DDF to normal. DDF status is now draft.
How do I see if the status I have been chosen have DDF enabled in control tab?

Mimiix · 2022-01-11T08:40:43Z

If you have the DDF for the device set to "silver" make sure that "Silver" is also checked in the above screen.

wlfrdssn · 2022-01-11T09:09:21Z

Hmmm.. For me settings look like. Old version? Settings somewhere else?

Mimiix · 2022-01-11T09:10:07Z

Are you on the latest 2.13.4?

wlfrdssn · 2022-01-11T09:43:53Z

Nope. Im on 2.13.2. Now I updated and got the same setting as you. Still same problem.

I deleted the devices from deconz and connected them again. Now I only got one power and one consumption. Thanks for all the help.

Mimiix · 2022-01-11T09:51:09Z

So it's solved?

wlfrdssn · 2022-01-11T09:58:22Z

So it's solved?

Yep, its solved. Got the right information in HA now.

Mimiix · 2022-01-11T09:59:04Z

Can you make a PR With the DDF in bronze? Just so others can benefit this?

wlfrdssn · 2022-01-11T10:07:43Z

Can you make a PR With the DDF in bronze? Just so others can benefit this?

Ill can make a try later. Maybe I should rename it, Now its called smartplugtest.json :)
Is there any instruction how it should be set up to PR with DDf in bronze?

Mimiix · 2022-01-11T10:10:59Z

Just make sure the DDF is set to bronze. Then probably you should be able to go here:
https://github.com/dresden-elektronik/deconz-rest-plugin/tree/master/devices/tuya and click "Add file" and upload there ( i think).

Then it should make a PR.

karsie1994 · 2022-01-27T21:35:41Z

Ok, so for you it seem working, can try with a DDF https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet you have a sample here, used for most of plugs #5577
With text editor, just need to edit thoses lines, the modelid is probably the same (visible on basic clsuter).
    "manufacturername": "_TZ3000_w0qqde0g",
    "modelid": "TS011F",
    "product": "NAS-WR01B",
    "path": "/devices/neo/NAS-WR01B.json",
I am not that familiar to DDF (and kind of new to deconz). l don't get this to work. Ill changed the manufacturnam and got new entities in HA but with value unknown. Trying to understand what I am doing wrong but have no clue.

How did you fill the binding table? I have no idea how to fill the binding table or upload the DDF file to Deconz when running from within Hassio on a Rasp Pi 4.

Smanar · 2022-01-28T09:39:02Z

How did you fill the binding table?
I have no idea how to fill the binding table or upload the DDF file to Deconz when running from within Hassio on a Rasp Pi 4.

You can have an issue on HA for bind https://forum.phoscon.de/t/ddf-editor-how-to-drag-bindings/1351
But we can edit the file manualy for that, will see later, without the bind, values will be updated in HA when you read them in deconz.

To manage file on HA with docker #5459 (comment)

Else can use the editor and "pre-used" path.

github-actions · 2022-02-19T01:48:59Z

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

waazdakka · 2022-02-21T14:44:00Z

Hello!
Coming back to the subject, I didn't understand all the edit suggestions in deConz, not sure of what to edit 🙄 But is there any chance to be corrected in the future to allow users to get power information without editing DDF-thing? 😅

Smanar · 2022-02-21T17:39:15Z

But is there any chance to be corrected in the future to allow users to get power information without editing DDF-thing?

DDF will be added 1 by 1 on the deconz package. But for the moment only DDF submitted in PR have a chance to be in the deconz package.

nukleuz80 · 2022-05-12T08:23:46Z

Hi there,
i tried the DDF file from @De-k and now i get the measurement sensors.
It seems to work fine but the power in Watt is 0.

Do you have any suggestions for it?

Here a screenshot from ioBroker objects and API - they are identical to each other...

{ "config": { "on": true, "reachable": true }, "etag": "0bbbdee622e75c565a02da42c91c5a43", "lastannounced": "2022-05-12T07:47:01Z", "lastseen": "2022-05-12T08:21Z", "manufacturername": "_TZ3000_gjnozsaz", "modelid": "TS011F", "name": "Power 125", "state": { "current": 17, "lastupdated": "2022-05-12T08:21:28.521", "power": 0, "voltage": 233 }, "type": "ZHAPower", "uniqueid": "a4:c1:38:81:56:ec:63:9a-01-0b04" }

The value for power is updating every 90 seconds with "0".

Smanar · 2022-05-12T13:28:56Z

So it work fine but every 90s you have a 0 zero value that overwrite the good one ?

I can't make test on my side but some device use a "filter" feature

        {
          "name": "state/power",
          "refresh.interval": 360,
          "read": {
            "at": "0x0400", 
            "cl": "0x0702", 
            "ep": 2,
            "fn": "zcl"
          },
          "parse": {
            "at": "0x0400",
            "cl": "0x0702",
            "ep": 1,
            "eval": "if (Attr.val != -16777215 && Attr.val != 16777215) { Item.val = Attr.val; }",
            "fn": "zcl"
          },
          "default": 0
        }

Here someone check for -16777215, we can't use 0 as value, because you can have a 0 zero value, perhaps you can catch the bad value on logs ?

nukleuz80 · 2022-05-12T13:32:51Z

Hi @Smanar,

there is no other value than 0 (zero).
I have a light with 15Watt in the plug but the value is 0 when the light/plug is on.

So there is every 90 seconds a 0/zero value.

EDIT: So i will check the logs for other values...

Smanar · 2022-05-12T14:04:04Z

Ha nope, I have bad understand.
You don't something with more consumption to test ? Because the tension is working, and they are working same in the DDF.

Mimiix · 2022-05-12T14:30:17Z

Hi @Smanar,

there is no other value than 0 (zero). I have a light with 15Watt in the plug but the value is 0 when the light/plug is on.

So there is every 90 seconds a 0/zero value.

EDIT: So i will check the logs for other values...

What does the deCONZ Gui show in the respective clusters and attributes?

phwagner82 · 2022-05-19T17:37:31Z

Hi everyone!
what is the current status on this topic? I have the same problems with this type of plugs...
Hope you can fix this problem!
Kind regards

nukleuz80 · 2022-05-19T17:46:54Z

Hi @Smanar,

there is no other value than 0 (zero). I have a light with 15Watt in the plug but the value is 0 when the light/plug is on.

So there is every 90 seconds a 0/zero value.

EDIT: So i will check the logs for other values...

What does the deCONZ Gui show in the respective clusters and attributes?

Here is the cluster...

Smanar · 2022-05-20T15:28:22Z

So the value is 0 too on your capture, you haven't a more powerfull device to test with your plug to have a bigger vlaue ?

Smanar · 2022-06-10T17:00:16Z

{
  "schema": "devcap1.schema.json",
  "manufacturername": "_TZ3000_gjnozsaz",
  "modelid": "TS011F",
  "vendor": "_TZ3000_gjnozsaz",
  "product": "TS011F",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_ON_OFF_PLUGIN_UNIT",
      "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"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "state/alert",
          "default": "none"
        },
        {
          "name": "state/on"
        },
        {
          "name": "state/reachable"
        }
      ]
    },
    {
      "type": "$TYPE_CONSUMPTION_SENSOR",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0x0702"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/consumption",
          "refresh.interval": 300
        },
        {
          "name": "state/lastupdated"
        }
      ]
    },
    {
      "type": "$TYPE_POWER_SENSOR",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0x0b04"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/current",
          "refresh.interval": 300
        },
        {
          "name": "state/lastupdated"
        },
        {
          "name": "state/power",
          "refresh.interval": 30
        },
        {
          "name": "state/voltage",
          "refresh.interval": 300
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0006",
      "report": [
        {
          "at": "0x0000",
          "dt": "0x10",
          "min": 1,
          "max": 300
        }
      ]
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0702",
      "report": [
        {
          "at": "0x0000",
          "dt": "0x25",
          "min": 1,
          "max": 300,
          "change": "0x0000000A"
        }
      ]
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "cl": "0x0B04",
      "report": [
        {
          "at": "0x0505",
          "dt": "0x21",
          "min": 1,
          "max": 500,
          "change": "0x00000003"
        },
        {
          "at": "0x0508",
          "dt": "0x21",
          "min": 1,
          "max": 300,
          "change": "0x0000000F"
        },
        {
          "at": "0x050B",
          "dt": "0x29",
          "min": 1,
          "max": 300,
          "change": "0x00000003"
        }
      ]
    }
  ]
}

phwagner82 · 2022-06-15T18:02:54Z

@Smanar thank you very much for the file and description. The power metering is working, but only once.
the data will not be refreshed.
can i support you with some logs to fix the issue?
br
Philipp

Smanar · 2022-06-15T18:11:38Z

You have the issue on all return ? Power/ voltage / current/ consumption ?
Because the binding don't look so bad, and if the reporting don't working, the poll is enabled too in the DDF ...

If it s not working try to replace

        {
          "name": "state/power",
          "refresh.interval": 30
        },

by

        {
          "name": "state/power",
          "refresh.interval": 300,
          "read": {
            "at": "0x050b",
            "cl": "0x0B04",
            "ep": 1,
            "fn": "zcl"
          },
          "parse": {
            "at": "0x050b",
            "cl": "0x0B04",
            "ep": 1,
            "eval": "Item.val = Attr.val"
          }
        }

phwagner82 · 2022-06-15T20:08:55Z

yes, i have no data at all, only after restarting the deconz service or rebooting the whole HAOS Am Mi., 15. Juni 2022 um 20:11 Uhr schrieb Smanar ***@***.***

…

: You have the issue on all return ? Power/ voltage / current/ consumption ? Because the binding don't look so bad, and if the reporting don't working, the poll is enabled too in the DDF ... — Reply to this email directly, view it on GitHub <#5633 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOAL7RYOODQNQ4WY4RZLAPLVPIMGNANCNFSM5LFRDMUA> . You are receiving this because you commented.Message ID: ***@***.***>

nukleuz80 · 2022-06-16T04:59:39Z

So the value is 0 too on your capture, you haven't a more powerfull device to test with your plug to have a bigger vlaue ?

Now i have values with a more powerful device. I did. not use the file you posted. I think this was my issue...

😎

Smanar · 2022-06-16T17:02:31Z

@nukleuz80 so the DDF is working as it, without the change from here #5633 (comment) ?

phwagner82 · 2022-06-21T18:30:41Z

It doesn't work for me, the data is not updated.

Smanar · 2022-06-21T19:39:37Z

Value is updated in deconz ?
Can you check is the DDf is used ? with logs or just open the editor with right clic on the node then "edit DDF" and look at file and path on window title.

phwagner82 · 2022-07-04T11:27:35Z

Hi Smanar!
thank you very much for your fast response!
Yes, i am using the DDF. If i click on "Edit DDF" the window shows me the DDF file name i used.
I am using HomeAssistant OS and i cant use the file permanently. how can i find the right log files?

kind regards
Philipp

Smanar · 2022-07-04T14:58:19Z

Nothing is updated, consumption, power tension, current ...
Have you tried this modification #5633 (comment)

You device look exactly same than the captures in the first post ?

If you have the GUI, can use it for logs (you can't make copy/paste on HA but can make screen capture) then in deconz / help / debug view

phwagner82 · 2022-07-14T13:45:47Z

device a4:c1:38:a3:8e:06:bf:64 and a4:c1:38:c1:0c:c7:51:88 are the same

15:50:28:084 sub-device: a4:c1:38:3c:36:3e:7b:fa-01-0b04, has item: attr/type
15:50:28:086 sub-device: a4:c1:38:3c:36:3e:7b:fa-01-0b04, has item: attr/uniqueid
15:50:28:087 sub-device: a4:c1:38:3c:36:3e:7b:fa-01-0b04, has item: config/on
15:50:28:087 sub-device: a4:c1:38:3c:36:3e:7b:fa-01-0b04, has item: config/reachable
15:50:28:088 sub-device: a4:c1:38:3c:36:3e:7b:fa-01-0b04, has item: state/current
15:50:28:089 sub-device: a4:c1:38:3c:36:3e:7b:fa-01-0b04, has item: state/lastupdated
15:50:28:090 sub-device: a4:c1:38:3c:36:3e:7b:fa-01-0b04, has item: state/power
15:50:28:091 sub-device: a4:c1:38:3c:36:3e:7b:fa-01-0b04, has item: state/voltage
15:50:28:174 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: attr/id
15:50:28:174 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: attr/lastannounced
15:50:28:175 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: attr/lastseen
15:50:28:176 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: attr/manufacturername
15:50:28:176 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: attr/modelid
15:50:28:177 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: attr/name
15:50:28:177 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: attr/swversion
15:50:28:178 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: attr/type
15:50:28:178 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: attr/uniqueid
15:50:28:179 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: state/alert
15:50:28:179 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: state/on
15:50:28:180 sub-device: a4:c1:38:c1:0c:c7:51:88-01, has item: state/reachable
15:50:28:183 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: attr/id
15:50:28:184 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: attr/lastannounced
15:50:28:184 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: attr/lastseen
15:50:28:185 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: attr/manufacturername
15:50:28:186 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: attr/modelid
15:50:28:186 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: attr/name
15:50:28:187 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: attr/swversion
15:50:28:187 SQL exec failed: SELECT attr FROM sensors WHERE uniqueid = 'a4:c1:38:c1:0c:c7:51:88-01-0702' AND deletedState = 'normal', error: no such column: attr (1)
15:50:28:188 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: attr/type
15:50:28:189 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: attr/uniqueid
15:50:28:190 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: config/on
15:50:28:191 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: config/reachable
15:50:28:193 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: state/consumption
15:50:28:193 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0702, has item: state/lastupdated
15:50:28:197 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: attr/id
15:50:28:198 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: attr/lastannounced
15:50:28:198 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: attr/lastseen
15:50:28:199 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: attr/manufacturername
15:50:28:200 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: attr/modelid
15:50:28:201 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: attr/name
15:50:28:202 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: attr/swversion
15:50:28:203 SQL exec failed: SELECT attr FROM sensors WHERE uniqueid = 'a4:c1:38:c1:0c:c7:51:88-01-0b04' AND deletedState = 'normal', error: no such column: attr (1)
15:50:28:203 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: attr/type
15:50:28:204 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: attr/uniqueid
15:50:28:205 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: config/on
15:50:28:205 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: config/reachable
15:50:28:206 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: state/current
15:50:28:206 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: state/lastupdated
15:50:28:207 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: state/power
15:50:28:208 sub-device: a4:c1:38:c1:0c:c7:51:88-01-0b04, has item: state/voltage
15:50:28:309 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: attr/id
15:50:28:311 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: attr/lastannounced
15:50:28:311 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: attr/lastseen
15:50:28:312 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: attr/manufacturername
15:50:28:312 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: attr/modelid
15:50:28:313 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: attr/name
15:50:28:313 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: attr/swversion
15:50:28:314 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: attr/type
15:50:28:315 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: attr/uniqueid
15:50:28:315 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: state/alert
15:50:28:316 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: state/on
15:50:28:316 sub-device: a4:c1:38:a3:8e:06:bf:64-01, has item: state/reachable
15:50:28:318 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: attr/id
15:50:28:319 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: attr/lastannounced
15:50:28:320 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: attr/lastseen
15:50:28:321 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: attr/manufacturername
15:50:28:322 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: attr/modelid
15:50:28:323 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: attr/name
15:50:28:324 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: attr/swversion
15:50:28:325 SQL exec failed: SELECT attr FROM sensors WHERE uniqueid = 'a4:c1:38:a3:8e:06:bf:64-01-0702' AND deletedState = 'normal', error: no such column: attr (1)
15:50:28:326 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: attr/type
15:50:28:327 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: attr/uniqueid
15:50:28:327 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: config/on
15:50:28:328 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: config/reachable
15:50:28:329 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: state/consumption
15:50:28:329 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0702, has item: state/lastupdated
15:50:28:331 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: attr/id
15:50:28:332 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: attr/lastannounced
15:50:28:333 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: attr/lastseen
15:50:28:334 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: attr/manufacturername
15:50:28:334 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: attr/modelid
15:50:28:335 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: attr/name
15:50:28:335 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: attr/swversion
15:50:28:336 SQL exec failed: SELECT attr FROM sensors WHERE uniqueid = 'a4:c1:38:a3:8e:06:bf:64-01-0b04' AND deletedState = 'normal', error: no such column: attr (1)
15:50:28:337 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: attr/type
15:50:28:338 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: attr/uniqueid
15:50:28:338 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: config/on
15:50:28:339 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: config/reachable
15:50:28:340 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: state/current
15:50:28:340 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: state/lastupdated
15:50:28:341 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: state/power
15:50:28:342 sub-device: a4:c1:38:a3:8e:06:bf:64-01-0b04, has item: state/voltage
15:50:28:452 a4:c1:38:3c:36:3e:7b:fa-01-0b04/state/current expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 142
15:50:30:254 a4:c1:38:3c:36:3e:7b:fa-01-0b04/state/current expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 113
15:50:31:256 a4:c1:38:3c:36:3e:7b:fa-01-0b04/state/current expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 95
15:50:33:016 a4:c1:38:a3:8e:06:bf:64-01-0b04/state/current expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 852
15:50:33:257 a4:c1:38:3c:36:3e:7b:fa-01-0b04/state/voltage expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 230
15:50:33:376 a4:c1:38:aa:7e:f3:c6:c2-01-0b04/state/voltage expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 231
15:50:34:007 a4:c1:38:a3:8e:06:bf:64-01-0b04/state/voltage expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 231
15:50:40:271 a4:c1:38:3c:36:3e:7b:fa-01-0b04/state/current expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 57

Attr.val; } --> 170
15:55:04:089 ZCL attribute report 0xA4C138A38E06BF64 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000
15:55:04:199 DEV: Poll Next failed to enqueue read item: state/voltage / 0xA4C1383C363E7BFA
15:55:04:698 DEV: Poll Next failed to enqueue read item: state/voltage / 0xA4C138A38E06BF64
15:55:04:700 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C1389DDE72113A
15:55:05:198 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C138AA7EF3C6C2
15:55:05:199 DEV: Poll Next failed to enqueue read item: state/voltage / 0xA4C138C10CC75188
15:55:06:198 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C1383C363E7BFA
15:55:06:698 DEV: Poll Next failed to enqueue read item: state/voltage / 0xA4C138A38E06BF64
15:55:06:700 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C1389DDE72113A
15:55:07:198 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C138AA7EF3C6C2
15:55:07:200 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C138C10CC75188
15:55:07:243 DEV Poll Busy /devices/0x588E81FFFEFF5ED6 APS-DATA.confirm id: 102, status: 0x00
15:55:07:277 58:8e:81:ff:fe:ff:5e:d6-01/state/on expression: Item.val = Attr.val --> true
15:55:07:282 DEV Poll Busy /devices/0x588E81FFFEFF5ED6 ZCL response seq: 114, status: 0x00
15:55:07:284 DEV Poll Idle enter /devices/0x588E81FFFEFF5ED6
15:55:08:030 a4:c1:38:a3:8e:06:bf:64-01-0b04/state/power expression: if (Attr.val != -32768 && Attr.val != 32768) { Item.val = Attr.val; } --> 165
15:55:08:039 ZCL attribute report 0xA4C138A38E06BF64 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000
15:55:08:198 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C1383C363E7BFA
15:55:08:697 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C138A38E06BF64
15:55:08:700 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C1389DDE72113A
15:55:09:049 a4:c1:38:a3:8e:06:bf:64-01-0b04/state/current expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 789
15:55:09:057 ZCL attribute report 0xA4C138A38E06BF64 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000
15:55:09:198 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C138AA7EF3C6C2
15:55:09:199 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C138C10CC75188
15:55:10:197 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C1383C363E7BFA
15:55:10:698 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C138A38E06BF64
15:55:10:736 DEV Poll Busy /devices/0xA4C1389DDE72113A APS-DATA.confirm id: 124, status: 0x00
15:55:10:771 DEV Poll Busy /devices/0xA4C1389DDE72113A ZCL response seq: 117, status: 0x86
15:55:10:772 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C1389DDE72113A
15:55:11:027 a4:c1:38:a3:8e:06:bf:64-01-0b04/state/power expression: if (Attr.val != -32768 && Attr.val != 32768) { Item.val = Attr.val; } --> 161
15:55:11:035 ZCL attribute report 0xA4C138A38E06BF64 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000
15:55:11:198 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C138C10CC75188
15:55:11:243 DEV Poll Busy /devices/0xA4C138AA7EF3C6C2 APS-DATA.confirm id: 129, status: 0x00
15:55:11:273 DEV Poll Busy /devices/0xA4C138AA7EF3C6C2 ZCL response seq: 118, status: 0x86
15:55:11:346 DEV Poll Busy /devices/0xA4C138AA7EF3C6C2 APS-DATA.confirm id: 132, status: 0x00
15:55:11:375 a4:c1:38:aa:7e:f3:c6:c2-01-0b04/state/power expression: if (Attr.val != -32768 && Attr.val != 32768) { Item.val = Attr.val; } --> 0
15:55:11:383 DEV Poll Busy /devices/0xA4C138AA7EF3C6C2 ZCL response seq: 119, status: 0x00
15:55:11:385 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C138AA7EF3C6C2
15:55:12:033 a4:c1:38:a3:8e:06:bf:64-01-0b04/state/current expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 772
15:55:12:042 ZCL attribute report 0xA4C138A38E06BF64 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000
15:55:12:231 DEV Poll Busy /devices/0xA4C1383C363E7BFA APS-DATA.confirm id: 140, status: 0x00
15:55:12:282 DEV Poll Busy /devices/0xA4C1383C363E7BFA ZCL response seq: 121, status: 0x86
15:55:12:324 DEV Poll Busy /devices/0xA4C1383C363E7BFA APS-DATA.confirm id: 143, status: 0x00
15:55:12:372 a4:c1:38:3c:36:3e:7b:fa-01-0b04/state/power expression: if (Attr.val != -32768 && Attr.val != 32768) { Item.val = Attr.val; } --> 8
15:55:12:378 DEV Poll Busy /devices/0xA4C1383C363E7BFA ZCL response seq: 122, status: 0x00
15:55:12:381 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C1383C363E7BFA
15:55:12:698 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C138A38E06BF64
15:55:12:700 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C1389DDE72113A
15:55:13:238 DEV Poll Busy /devices/0xA4C138C10CC75188 APS-DATA.confirm id: 150, status: 0x00
15:55:13:262 DEV Poll Busy /devices/0xA4C138C10CC75188 ZCL response seq: 124, status: 0x86
15:55:13:298 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C138AA7EF3C6C2
15:55:13:350 DEV Poll Busy /devices/0xA4C138C10CC75188 APS-DATA.confirm id: 154, status: 0x00
15:55:13:376 a4:c1:38:c1:0c:c7:51:88-01-0b04/state/power expression: if (Attr.val != -32768 && Attr.val != 32768) { Item.val = Attr.val; } --> 18
15:55:13:412 DEV Poll Busy /devices/0xA4C138C10CC75188 ZCL response seq: 126, status: 0x00
15:55:13:511 DEV Poll Busy /devices/0xA4C138C10CC75188 APS-DATA.confirm id: 156, status: 0x00
15:55:13:552 a4:c1:38:c1:0c:c7:51:88-01-0b04/state/voltage expression: if (Attr.val != 65535) { Item.val = Attr.val; } --> 233
15:55:13:557 DEV Poll Busy /devices/0xA4C138C10CC75188 ZCL response seq: 127, status: 0x00
15:55:13:559 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C138C10CC75188
15:55:14:282 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C1383C363E7BFA
15:55:14:698 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C1389DDE72113A
15:55:14:748 DEV Poll Busy /devices/0xA4C138A38E06BF64 APS-DATA.confirm id: 164, status: 0x00
15:55:14:765 DEV Poll Busy /devices/0xA4C138A38E06BF64 ZCL response seq: 128, status: 0x86
15:55:14:768 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C138A38E06BF64
15:55:15:200 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C138AA7EF3C6C2
15:55:15:661 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C138C10CC75188
15:55:16:032 a4:c1:38:a3:8e:06:bf:64-01-0b04/state/power expression: if (Attr.val != -32768 && Attr.val != 32768) { Item.val = Attr.val; } --> 157
15:55:16:040 ZCL attribute report 0xA4C138A38E06BF64 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x0000
15:55:16:198 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C1383C363E7BFA
15:55:16:698 DEV: Poll Next failed to enqueue read item: state/consumption / 0xA4C1389DDE72113A
15:55:16:699 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C138A38E06BF64
15:55:17:198 DEV: Poll Next failed to enqueue read item: state/consumption / 0xA4C138AA7EF3C6C2
15:55:17:698 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C138C10CC75188
15:55:18:198 DEV: Poll Next failed to enqueue read item: state/consumption / 0xA4C1383C363E7BFA
15:55:18:698 DEV: Poll Next failed to enqueue read item: state/consumption / 0xA4C1389DDE72113A
15:55:18:699 DEV: Poll Next failed to enqueue read item: attr/swversion / 0xA4C138A38E06BF64
15:55:19:198 DEV: Poll Next failed to enqueue read item: state/consumption / 0xA4C138AA7EF3C6C2
15:55:19:698 DEV: Poll Next failed to enqueue read item: state/consumption / 0xA4C138C10CC75188

Smanar · 2022-07-14T14:52:05Z

You are using the GUI to have logs ?

If yes, after some time, because atm there is the configuration part (busy error that are solved later), do you still have thoses lines

15:55:16:032 a4:c1:38:a3:8e:06:bf:64-01-0b04/state/power expression: if (Attr.val != -32768 && Attr.val != 32768) { Item.val = Attr.val; } --> 157
15:55:16:040 ZCL attribute report 0xA4C138A38E06BF64 for cluster: 0x0B04, ep: 0x01, frame control: 0x18, mfcode: 0x000
```0

github-actions · 2022-08-05T02:14:04Z

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

phwagner82 · 2022-08-08T19:30:46Z

yes, i am using the gui.

can i filter the log to get better logs?

Smanar · 2022-08-09T15:47:51Z

The 2 previous debug line are visible with "info" and "DDF"

The first one mean the device send the attribute value report or poll
The second one mean a report

And after some time, I don't think you still have this kind of error

15:55:11:198 DEV: Poll Next failed to enqueue read item: state/current / 0xA4C138C10CC75188

Values are visible on the GUI ? For exemple on the cluster 0x0b04 ?

github-actions · 2022-08-31T02:15:37Z

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

github-actions · 2022-09-07T02:17:50Z

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

waazdakka added the Bug report label Jan 3, 2022

This was referenced Jan 27, 2022

Tuya Smart Plug missing metering data (_TZ3000_cphmq0q7) #4838

Closed

New device: Tuya smart plug 16a #5334

Closed

github-actions bot added the stale label Feb 19, 2022

github-actions bot added the stale label Aug 5, 2022

github-actions bot removed the stale label Aug 9, 2022

github-actions bot added the stale label Aug 31, 2022

github-actions bot closed this as completed Sep 7, 2022

hubertgruber mentioned this issue Dec 19, 2024

TZ3000_5f43h46b #8070

Closed

1 task

TZ3000_gjnozsaz appears but only power and link quality - No power meter #5633

TZ3000_gjnozsaz appears but only power and link quality - No power meter #5633

Comments

waazdakka commented Jan 3, 2022

Describe the bug

Steps to reproduce the behavior

Expected behavior

Screenshots

Environment

Mimiix commented Jan 3, 2022

waazdakka commented Jan 3, 2022

Mimiix commented Jan 3, 2022

waazdakka commented Jan 4, 2022

Mimiix commented Jan 4, 2022

akinek commented Jan 8, 2022

Smanar commented Jan 9, 2022 • edited Loading

wlfrdssn commented Jan 10, 2022

Smanar commented Jan 10, 2022 • edited Loading

wlfrdssn commented Jan 11, 2022

Mimiix commented Jan 11, 2022

wlfrdssn commented Jan 11, 2022

Mimiix commented Jan 11, 2022

wlfrdssn commented Jan 11, 2022

Mimiix commented Jan 11, 2022

wlfrdssn commented Jan 11, 2022

Mimiix commented Jan 11, 2022

wlfrdssn commented Jan 11, 2022

Mimiix commented Jan 11, 2022

wlfrdssn commented Jan 11, 2022

Mimiix commented Jan 11, 2022

karsie1994 commented Jan 27, 2022

Smanar commented Jan 28, 2022

github-actions bot commented Feb 19, 2022

waazdakka commented Feb 21, 2022

Smanar commented Feb 21, 2022

nukleuz80 commented May 12, 2022 • edited Loading

Smanar commented May 12, 2022 • edited Loading

nukleuz80 commented May 12, 2022 • edited Loading

Smanar commented May 12, 2022

Mimiix commented May 12, 2022

phwagner82 commented May 19, 2022

nukleuz80 commented May 19, 2022

Smanar commented May 20, 2022

Smanar commented Jun 10, 2022 • edited Loading

phwagner82 commented Jun 15, 2022

Smanar commented Jun 15, 2022 • edited Loading

phwagner82 commented Jun 15, 2022 via email

nukleuz80 commented Jun 16, 2022

Smanar commented Jun 16, 2022 • edited Loading

phwagner82 commented Jun 21, 2022 • edited Loading

Smanar commented Jun 21, 2022 • edited Loading

phwagner82 commented Jul 4, 2022

Smanar commented Jul 4, 2022 • edited Loading

phwagner82 commented Jul 14, 2022 • edited Loading

Smanar commented Jul 14, 2022

github-actions bot commented Aug 5, 2022

phwagner82 commented Aug 8, 2022

Smanar commented Aug 9, 2022

github-actions bot commented Aug 31, 2022

github-actions bot commented Sep 7, 2022

Smanar commented Jan 9, 2022 •

edited

Loading

Smanar commented Jan 10, 2022 •

edited

Loading

nukleuz80 commented May 12, 2022 •

edited

Loading

Smanar commented May 12, 2022 •

edited

Loading

nukleuz80 commented May 12, 2022 •

edited

Loading

Smanar commented Jun 10, 2022 •

edited

Loading

Smanar commented Jun 15, 2022 •

edited

Loading

Smanar commented Jun 16, 2022 •

edited

Loading

phwagner82 commented Jun 21, 2022 •

edited

Loading

Smanar commented Jun 21, 2022 •

edited

Loading

Smanar commented Jul 4, 2022 •

edited

Loading

phwagner82 commented Jul 14, 2022 •

edited

Loading