Vendor_TZE204_cjbofhxw ModelTS0601 - Ampermeter from Matsee #6934

sajikur · 2023-04-28T11:04:55Z

https://forum.phoscon.de/t/matsee-plus-smart-meter-with-ct/3453/4

https://zigbee.blakadder.com/QS-Zigbee-S05-EC.html

Ampermeter from Matsee Model TS0601

Product name: Ampermeter from Matsee.
Manufacturer: Vendor_TZE204_cjbofhxw .
Model identifier: ModelTS0601.
Device type : Please remove all unrelated device types.
- Other: Amperometer

Screenshots

Basic

Identify

Alarms

Device Temperature

Groups

Scenes

On/Off

Level Control

Color Control

Simple Metering

Diagnostics

Other clusters that are not mentioned above

Mimiix · 2023-04-28T11:19:25Z

Missing screeenshot of atleast the full cluster list.. Please add all.

sajikur · 2023-04-28T11:49:22Z

Hi, thank you for answer. Could you tell me what is the panel you mean?

Mimiix · 2023-04-28T11:59:36Z

The list of clusters under the node on the gui.

sajikur · 2023-04-28T12:07:53Z

It's correct?

Mimiix · 2023-04-28T12:12:22Z

Now we are still missing screens for groups and scenes cluster

sajikur · 2023-04-28T12:20:56Z

well, It's all? Sorry for my little experience in this kind of request

Mimiix · 2023-04-28T12:55:17Z

All good , thanks :)

sajikur · 2023-04-28T13:11:28Z

All good , thanks :)

Thank you!

sajikur · 2023-05-12T12:02:41Z

hi, any news?

Mimiix · 2023-05-12T12:11:16Z

No dev has picked it up, so no news

BabaIsYou · 2023-05-16T19:26:52Z

https://zigbee.blakadder.com/QS-Zigbee-S05-EC.html

Is certainly not the right link ;-)

May be could try this DDF. Not quite sure about consumption BTW

{
	"schema": "devcap1.schema.json",
	"manufacturername": "_TZE204_cjbofhxw",
	"modelid": "TS0601",
	"product": "Ampermeter from Matsee plus",
	"sleeper": false,
	"status": "Gold",
	"subdevices": [{
			"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",
					"parse": {
						"fn": "zcl",
						"ep": 1,
						"cl": "0x0000",
						"at": "0x0001",
						"script": "tuya_swversion.js"
					},
					"read": {
						"fn": "zcl",
						"ep": 1,
						"cl": "0x0000",
						"at": "0x0001"
					}
				},
				{
					"name": "attr/type"
				},
				{
					"name": "attr/uniqueid"
				},
				{
					"name": "config/offset",
					"default": 0
				},
				{
					"name": "config/on"
				},
				{
					"name": "config/tuya_unlock"
				},
				{
					"name": "config/reachable"
				},
				{
					"name": "state/consumption",
					"parse": {
						"fn": "tuya",
						"dpid": 101,
						"eval": "Item.val = Attr.val / 1000;"
					},
					"read": {
						"fn": "none"
					},
					"default": 0
				},
				{
					"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",
					"parse": {
						"fn": "zcl",
						"ep": 1,
						"cl": "0x0000",
						"at": "0x0001",
						"script": "tuya_swversion.js"
					},
					"read": {
						"fn": "none"
					}
				},
				{
					"name": "attr/type"
				},
				{
					"name": "attr/uniqueid"
				},
				{
					"name": "config/offset",
					"default": 0
				},
				{
					"name": "config/on"
				},
				{
					"name": "config/reachable"
				},
				{
					"name": "state/lastupdated"
				},
				{
					"name": "state/current",
					"parse": {
						"fn": "tuya",
						"dpid": 18,
						"eval": "Item.val = Attr.val / 1000;"
					},
					"read": {
						"fn": "none"
					},
					"default": 0
				},
				{
					"name": "state/voltage",
					"parse": {
						"fn": "tuya",
						"dpid": 20,
						"eval": "Item.val = Attr.val / 10;"
					},
					"read": {
						"fn": "none"
					},
					"default": 0
				},
				{
					"name": "state/power",
					"parse": {
						"fn": "tuya",
						"dpid": 19,
						"eval": "Item.val = Attr.val / 10;"
					},
					"read": {
						"fn": "none"
					},
					"default": 0
				}
			]
		}
	]
}

BabaIsYou · 2023-05-22T23:33:10Z

hi, any news?

@sajikur any news from your side ?

sajikur · 2023-05-23T04:51:31Z

hi, any news?

@sajikur any news from your side ?

Unfortunately no new news. Too bad because the device is really very cheap compared to shelly and it's zigbee

BabaIsYou · 2023-05-23T09:28:26Z

Did you give a try to the provided DDF ?

sajikur · 2023-05-23T09:51:11Z

Did you give a try to the provided DDF

sorry for my incompetence. Could you explain me your post?
thank you

BabaIsYou · 2023-05-23T09:54:46Z

I think you could begin with this : https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet

sajikur · 2023-05-23T10:03:05Z

https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet

thank you, I'll try

Fix dresden-elektronik#6934

github-actions · 2023-06-14T01:59:42Z

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.

pdcmoreira · 2023-06-14T13:43:25Z

Also bought one of these.

Tried the DDF above and also tried creating one with some of the ids that appeared in the logs, but none of that worked.

There is an interesting thread about this device at the Z2M repo and in particular there seems to be a specific behavior to this (relevant comments 1 2):

It periodically polls for some "cloud connection status" through 0x25
The coordinator should send back the same payload with an extra 0x01 (which represents the "connected" status)
Only after it receives this "confirmation" it starts sending the actual power values

Is it possible to implement such behavior in a DDF?

Also, there's another interesting comment with some kind of pseudo-code (but the logic seems to make sense overall).

BabaIsYou · 2023-06-14T17:07:11Z

Saw it already, but as sajikur has naver mentionned a pairing issue, nor tested the DDF ... issue was staled ...

github-actions · 2023-07-06T02:08:39Z

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 · 2023-07-13T02:09:16Z

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.

haegar33 · 2023-08-08T15:08:04Z

So the conclusion is: there is no solution for this device and no working deConz implementation? Its a wide spread energy meter on Aliexpress now. In my NodeRed/Deconz setup its quickly recognized, but only as power plug. I tried the DDF mentioned above but no differenz

pdcmoreira · 2023-08-08T15:18:53Z

@haegar33 For now, I guess there is no working solution and I also stopped trying to make it work. Might try again soon.

Mimiix · 2023-08-08T15:21:11Z

So the conclusion is: there is no solution for this device and no working deConz implementation? Its a wide spread energy meter on Aliexpress now. In my NodeRed/Deconz setup its quickly recognized, but only as power plug. I tried the DDF mentioned above but no differenz

The proposed DDF was never tested.

While testing the DDF, you should see things in the rest api .

pdcmoreira · 2023-08-08T15:29:25Z

Hey @Mimiix what do you mean by this?

While testing the DDF, you should see things in the rest api .

haegar33 · 2023-08-08T15:40:38Z

Indeed there is change in the REST-API (but not visibile in Phoscon!)

"25": {
        "config": {
            "offset": 0,
            "on": true,
            "reachable": true
        },
        "etag": "6e74c7e73e4da6618383676044fa2343",
        "lastannounced": null,
        "lastseen": "2023-08-08T15:14Z",
        "manufacturername": "_TZE204_cjbofhxw",
        "modelid": "TS0601",
        "name": "Consumption 25",
        "state": {
            "consumption": 0,
            "lastupdated": "none"
        },
        "type": "ZHAConsumption",
        "uniqueid": "18:7a:3e:ff:fe:cb:0a:21-01-0702"
    },
    "26": {
        "config": {
            "offset": 0,
            "on": true,
            "reachable": true
        },
        "etag": "0cf7365295e68bbf806159e8e23bc409",
        "lastannounced": null,
        "lastseen": "2023-08-08T15:14Z",
        "manufacturername": "_TZE204_cjbofhxw",
        "modelid": "TS0601",
        "name": "Power 26",
        "state": {
            "current": 0,
            "lastupdated": "none",
            "power": 0,
            "voltage": 0
        },
        "type": "ZHAPower",
        "uniqueid": "18:7a:3e:ff:fe:cb:0a:21-

Ok, so some progress ;) But readings are always zero (Status last update = never)

Mimiix · 2023-08-08T15:40:55Z

The working of the DDF can only be determined by checking the rest api or websocket. Phoscon probably isn't showing anything as it needs to add support on its own.

Mimiix · 2023-08-08T15:41:27Z

This repo only provides support until the api itself .

haegar33 · 2023-08-08T16:17:47Z

ok applying the DDF gets a modified REST-api response, but this does not imply that the device is providing values with the defined "attributes" I see that @pdcmoreira and others have tried without success.
Looks like this is the first China device not working with my setup ;(
Thanks anyway! Haegar

haegar33 · 2023-08-09T10:37:42Z

Looking at a similar(?) device discussed here #7151 I changed the DDF entry for ''state/voltage'' as suggested and I get at least a reasonable answer back via REST:

   "lastannounced": "2023-08-09T09:12:33Z",
    "lastseen": "2023-08-09T10:21Z",
    "manufacturername": "_TZE204_cjbofhxw",
    "modelid": "TS0601",
    "name": "Power 26",
    "state": {
        "current": 0,
        "lastupdated": "2023-08-09T09:14:29.603",
        "power": 0,
        "voltage": 234
    },
    "type": "ZHAPower",
    "uniqueid": "18:7a:3e:ff:fe:cb:0a:21-01-0b04"
}

Smanar · 2023-08-09T14:55:22Z

If you have the GUI, you can take a look in logs with flag "info" and "ddf", you will return from the device (even not managed by deconz)

Because the DDF seem fine for me, you need to have the consumption too.

What have you changed on the original DDF to have voltage ?

haegar33 · 2023-08-10T08:41:51Z

I have changed:

        {
          "name": "state/voltage",
          "parse": {"fn": "tuya", "dpid": 6, "eval": "Item.val = (Attr.val[0] << 8) | Attr.val[1]) / 10;" },
          "read": {"fn": "none"},
          "default": 0
        },

thus reading from dpid 6. As I am not an expert in javascript bitfield decodings I could not get current or power. I will try the deCONZ GUI log file

Smanar · 2023-08-10T15:25:33Z

Hu ?
I have checked again, and the model _TZE204_cjbofhxw don't use the dpid 6 but the 20 for voltage ....

I will try the deCONZ GUI log file

Yeah pls, on deconz logs you will be able to see request from the device with "info", and the dpid used by it.

github-actions · 2023-09-01T01:46:38Z

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.

pdcmoreira · 2023-09-01T01:51:26Z

Please keep this open.

github-actions · 2023-09-23T01:44:41Z

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 · 2023-09-30T01:45:21Z

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.

sajikur added the Device Request label Apr 28, 2023

Mimiix added the Incomplete issue label Apr 28, 2023

Mimiix removed the Incomplete issue label Apr 28, 2023

BabaIsYou added a commit to BabaIsYou/deconz-rest-plugin that referenced this issue May 29, 2023

DDF - Add support for _TZE204_cjbofhxw Ampermeter from Matsee

9ec019d

Fix dresden-elektronik#6934

BabaIsYou mentioned this issue May 29, 2023

DDF - Add support for _TZE204_cjbofhxw Ampermeter from Matsee #7019

Closed

github-actions bot added the stale label Jun 14, 2023

github-actions bot removed the stale label Jun 15, 2023

github-actions bot added the stale label Jul 6, 2023

github-actions bot closed this as completed Jul 13, 2023

Mimiix reopened this Aug 8, 2023

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

github-actions bot added the stale label Sep 1, 2023

github-actions bot removed the stale label Sep 2, 2023

github-actions bot added the stale label Sep 23, 2023

github-actions bot closed this as completed Sep 30, 2023

Vendor_TZE204_cjbofhxw ModelTS0601 - Ampermeter from Matsee #6934

Vendor_TZE204_cjbofhxw ModelTS0601 - Ampermeter from Matsee #6934

Comments

sajikur commented Apr 28, 2023 • edited

Screenshots

Basic

Identify

Alarms

Device Temperature

Groups

Scenes

On/Off

Level Control

Color Control

Simple Metering

Diagnostics

Other clusters that are not mentioned above

Mimiix commented Apr 28, 2023 • edited

sajikur commented Apr 28, 2023

Mimiix commented Apr 28, 2023

sajikur commented Apr 28, 2023

Mimiix commented Apr 28, 2023

sajikur commented Apr 28, 2023

Mimiix commented Apr 28, 2023

sajikur commented Apr 28, 2023

sajikur commented May 12, 2023

Mimiix commented May 12, 2023

BabaIsYou commented May 16, 2023 • edited

BabaIsYou commented May 22, 2023

sajikur commented May 23, 2023

BabaIsYou commented May 23, 2023

sajikur commented May 23, 2023

BabaIsYou commented May 23, 2023

sajikur commented May 23, 2023

github-actions bot commented Jun 14, 2023

pdcmoreira commented Jun 14, 2023

BabaIsYou commented Jun 14, 2023

github-actions bot commented Jul 6, 2023

github-actions bot commented Jul 13, 2023

haegar33 commented Aug 8, 2023

pdcmoreira commented Aug 8, 2023

Mimiix commented Aug 8, 2023

pdcmoreira commented Aug 8, 2023

haegar33 commented Aug 8, 2023

Mimiix commented Aug 8, 2023

Mimiix commented Aug 8, 2023

haegar33 commented Aug 8, 2023

haegar33 commented Aug 9, 2023

Smanar commented Aug 9, 2023 • edited

haegar33 commented Aug 10, 2023

Smanar commented Aug 10, 2023 • edited

github-actions bot commented Sep 1, 2023

pdcmoreira commented Sep 1, 2023

github-actions bot commented Sep 23, 2023

github-actions bot commented Sep 30, 2023

sajikur commented Apr 28, 2023 •

edited

Mimiix commented Apr 28, 2023 •

edited

BabaIsYou commented May 16, 2023 •

edited

Smanar commented Aug 9, 2023 •

edited

Smanar commented Aug 10, 2023 •

edited