zigbee uint24 format used with power metering cluster

[PleKy01]

PROBLEM DESCRIPTION

When trying to set reporting threshold, if attribute is of type uint24 (0x2A) then tasmota refused it with following error:

zbSend { "device":"0xf530", "endpoint":"0x01", "cluster":"0x0702", "config":{"0702/0400%2a":{"ReportableChange":1}}}
RESULT = {"ZbSend":"Unsupported attribute type '0702/0400%2a' 0x2A"}

similar issue for uint48 was solved adding the type in Tasmota drivers:
https://github.com/arendst/Tasmota/pull/20992

TO REPRODUCE

zbSend { "device":"0xf530", "endpoint":"0x01", "cluster":"0x0702", "config":{"0702/0400%2a":{"ReportableChange":1}}}

EXPECTED BEHAVIOUR

sending report config request to the device

Thanks for your help

[sfromis]

AFAICT, attribute type uint24 is supported as 0x22, but 0x2A is instead int24. If uint24 is what you want, try with %22 instead, but signed int24 is indeed not included in the supported types. Of course, signed values would be "unusual" for a threshold value.

[PleKy01]

Hello sfromis,

Thanks for your quick answer, you're right, my mistake it was signed int.
At first it may looks weird, but I guess it is to handle production (negative) values.

anyway, do you know if it is possible to by-pass this to request a reporting change for an int24 signed attribute?

BTW, I'm also looking for additional documentation for readconfig and maybe other commands for zbsend (not in main doc )

Thanks again

[sfromis]

Well, did it work sending the threshold as unsigned? Where did you see that it was supposed to be signed?

I suppose that @s-hadinger could add int24 to xdrv_23_zigbee_5_2_converters.ino if needed.

[PleKy01]

I saw it on vendor doc.
I've tried this:
ZbSend { "device":"0xf530", "endpoint":"0x01", "cluster":"0x0702", "config":{"0702/0400%22":{"Min":3600, "Max":43200, "Change":25}}}
No error from Tasmota or device, but still getting values every minute.
I was able to change CurrentSummationDelivered (also known by Tasmota), and no longer receiving updates every minutes.
So I guess device has not accepted the order.

[s-hadinger]

I have added support for 0x2A (int24) type in #24334 but I can't test it. Can you try and confirm it solves your problem?

[PleKy01]

Hello @s-hadinger ,

I can test it, will a nightly/latest be built tonight ?

Thanks

[sfromis]

Yes, it should be there within an hour.

[sfromis]

A new dev build has now been rolled out.

[PleKy01]

I have upgraded to nightly of the 13.
I was able to send the order:
ZbSend { "device":"0xf530", "endpoint":"0x01", "cluster":"0x0702", "config":{"0702/0400%2a":{"Min":61, "Max":3600, "ReportableChange":1}}}
No Error from Tasmota.

But I don't know if it has been understood by the device.
When I request the config I've got this:
ZbSend {"Device":"0xf530", "Cluster":0x0702, "ReadConfig":"1024"}

Before doing the config got:
{"fp_cuisine":{"Device":"0xF530","Name":"fp_cuisine","ReadConfig":{"0702/0400":{"MinInterval":1,"MaxInterval":61,"ReportableChange":null}},"Endpoint":1,"LinkQuality":145}}

After the ZbSend, got:
ZbSend {"Device":"0xf530", "Cluster":0x0702, "ReadConfig":"1024"} 19:24:00.305 CMD: Grp 0, Cmd 'ZBSEND', Idx 1, Len 58, Pld -99, Data '{"Device":"0xf530", "Cluster":0x0702, "ReadConfig":"1024"}' 19:24:00.307 ZIG: guessing endpoint 1 19:24:00.308 ZigbeeZCLSend device: 0xF530, endpoint:1, cluster:0x0702, cmd:0x08, send:"000004" 19:24:00.310 ZIG: ZbZNPSent 24020230F500000000000001000001020710301E0600101008000004 19:24:00.316 MQT: stat/zbbridge-p/RESULT = {"ZbSend":"Done"} 19:24:00.360 ZIG: {"ZbZNPReceived":"640200"} 19:24:00.375 ZIG: {"ZbZNPReceived":"45C430F500"} 19:24:00.424 ZIG: {"ZbZNPReceived":"4480000110"} 19:24:00.476 ZIG: {"ZbZNPReceived":"44810000020730F501010091009B71ED0000070810098B00000430F51D"} 19:24:00.477 ZIG: {"ZbZCLReceived":{"groupid":0,"clusterid":"0x0702","srcaddr":"0xF530","srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"LinkQuality":145,"securityuse":0,"seqnumber":0,"fc":"0x08","frametype":0,"direction":1,"disableresp":0,"manuf":"0x0000","transact":16,"cmdid":"0x09","payload":"8B000004"}} 19:24:00.481 ZIG: ZbZCLRawReceived: {"0xF530":{"ReadConfig":{"0702/0400":{"Status":139,"StatusMsg":"NOT_FOUND"}},"Endpoint":1,"LinkQuality":145}} 19:24:00.491 MQT: tele/zbbridge-p/fp_cuisine/SENSOR = {"fp_cuisine":{"Device":"0xF530","Name":"fp_cuisine","ReadConfig":{"0702/0400":{"Status":139,"StatusMsg":"NOT_FOUND"}},"Endpoint":1,"LinkQuality":145}}
I need to check with vendor supported reporting values :(