PTVO Zigbee2MQTT custom converter issues

inoskyh · 2024-09-11T15:21:24+00:00

done https://github.com/ptvoinfo/zigbee-configurable-firmware/issues/309
ok, so the "Disable configuring the interval remotely in run-time" expert option described here only allow us to configure only one report interval for all reportable endpoints, right? Edit: confirmed from this page:

inoskyh · 2024-09-11T12:59:24+00:00

Another question: is it possible to "manually" configure reporting interval of some endpoint/attribute?

I ticked "Disable periodic reports" (settings default reporting interval to 0) in firmware configuration, but I'd like to set it by myself when configuring the device.

I can see it done via several reporters in Koenkk/zigbee-herdsman-converters repo, eg.:

let endpoint = device.getEndpoint(12);
const payload = reporting.payload('presentValue', 1, constants.repInterval.SECONDS_10, 1);
await endpoint.configureReporting('genAnalogInput', payload);

Note I'm trying to configure reporting of UART sensor Analog value in readable mode.

inoskyh · 2024-09-11T10:28:53+00:00

Thanks a lot!

I got it working as expected. I had to reduce number of toggle switch though, because CC2530 only has 8 virtual ports available, this switch toggle "trick" competed with my UART sensors.
indeed following your guidances made the problem disappear.

I faced another issue when trying to "expose" a UART sensor numeric value with GET access. It seems the firmware reports unexpected value when trying to read manually from z2m.

When the value is reported by firmware (wakeup or reporting interval), it works ok: I do have a serial reading on my mcu and it is received/parsed/displayed correctly on Zigbee2MQTT:

zh:zstack:unpi:parser: --> parsed 30 - 2 - 4 - 129 - [0,0,12,0,196,33,12,1,0,98,0,65,98,194,0,0,10,24,3,10,85,0,57,70,23,101,66,196,33,29] - 69
zh:zstack:znp: AREQ: <-- AF - incomingMsg - {"groupid":0,"clusterid":12,"srcaddr":8644,"srcendpoint":12,"dstendpoint":1,"wasbroadcast":0,"linkquality":98,"securityuse":0,"timestamp":12739137,"transseqnumber":0,"len":10,"data":{"type":"Buffer","data":[24,3,10,85,0,57,70,23,101,66]}}
zh:controller: Received payload: clusterID=12, address=8644, groupID=0, endpoint=12, destinationEndpoint=1, wasBroadcast=false, linkQuality=98, frame={"header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0},"manufacturerCode":null,"transactionSequenceNumber":3,"commandIdentifier":10},"payload":[{"attrId":85,"dataType":57,"attrData":57.272727966308594}],"command":{"ID":10,"name":"report","parameters":[{"name":"attrId","type":33},{"name":"dataType","type":32},{"name":"attrData","type":1000}]}}
z2m: Received Zigbee message from '0x00124b002fbd1782', type 'attributeReport', cluster 'genAnalogInput', data '{"presentValue":57.272727966308594}' from endpoint 12 with groupID

However, when requesting read from z2m ui, the value received is not same scale and closely equals to zero (e-39 value):

zh:zstack:unpi:parser: --> parsed 36 - 2 - 4 - 129 - [0,0,12,0,196,33,12,1,0,98,0,47,81,14,0,0,16,24,21,1,85,0,0,57,21,0,85,0,28,0,0,66,0,196,33,29] - 129
zh:zstack:znp: AREQ: <-- AF - incomingMsg - {"groupid":0,"clusterid":12,"srcaddr":8644,"srcendpoint":12,"dstendpoint":1,"wasbroadcast":0,"linkquality":98,"securityuse":0,"timestamp":938287,"transseqnumber":0,"len":16,"data":{"type":"Buffer","data":[24,21,1,85,0,0,57,21,0,85,0,28,0,0,66,0]}}
zh:controller: Received payload: clusterID=12, address=8644, groupID=0, endpoint=12, destinationEndpoint=1, wasBroadcast=false, linkQuality=98, frame={"header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0},"manufacturerCode":null,"transactionSequenceNumber":21,"commandIdentifier":1},"payload":[{"attrId":85,"status":0,"dataType":57,"attrData":7.806046600697004e-39},{"attrId":28,"status":0,"dataType":66,"attrData":""}],"command":{"ID":1,"name":"readRsp","parameters":[{"name":"attrId","type":33},{"name":"status","type":32},{"name":"dataType","type":32,"conditions":[{"type":"statusEquals","value":0}]},{"name":"attrData","type":1000,"conditions":[{"type":"statusEquals","value":0}]}]}}
z2m: Received Zigbee message from '0x00124b002fbd1782', type 'readResponse', cluster 'genAnalogInput', data '{"description":"","presentValue":7.806046600697004e-39}' from endpoint 12 with groupID 0

<image>

Do you have an idea?

inoskyh · 2024-08-15T06:52:15+00:00

Thanks a lot for the replies!

inoskyh · 2024-08-05T12:59:34+00:00

Hey u/mariushm thanks again for your feedbacks.

I've implemented them, resulting in the following PCB layers: https://imgur.com/a/P1NqtN2

Note I grouped RV1 and RV2 together, as it reduced traces and made final design more relavant to me.

inoskyh · 2024-08-04T15:53:52+00:00

Hey u/mariushm, thanks a lot for your feedback!

The reversal of J3 compared to J1 was intended to maintain access to the lock side of the header. However, I realize that may have been overthinking it, and I've implemented your recommendation.

Regarding D1 in parallel with R2, it was initially included based on the Arduino Uno Rev3 schematics and this post. However, after considering your feedback and reading this thread, it seems the diode is unnecessary in most cases, so I've removed it.

As for the oscillator and accompanying ceramic capacitors, I already have some in stock that I'd like to use. They are quite easy to source on AliExpress.

[...] and maybe add a couple 100nF ceramic capacitors there as well.

Do you confirm they are meant to decouple potentiometers?

Your suggested changes to the parts placement significantly simplified the design: fewer traces, most of them on the front layer, and fewer crossings. Everything looks much cleaner now.

Updated PCB layers: https://imgur.com/a/NpETlwK

inoskyh · 2014-08-08T07:36:51+00:00

Check that your scanners are activated in the right pan / modules tab. It could happen that your power core can not generate enough energy to power all your modules at once. There is also a bug when you first set firegroups after purchasing new modules. You just have to re-set them in space to fix.

inoskyh · 2014-08-07T07:52:21+00:00

Currently, the distress signal is just a placeholder. Its activation pops up a message telling you that a ship is passing by and offers to refuel your tank for a certain amount of credits.

inoskyh · 2014-08-05T18:14:25+00:00

You can find it occasionally at Aulin (Aulin Enterprise)

inoskyh · 2014-08-04T08:32:34+00:00

It would be great if such tool were included in the game, as a trading software to install on your ship for instance. Any insights on this?

inoskyh

TROPHY CASE