Update owon.ts

[weson-su]

The attribute instantaneousDemand and currentSummDelivered are reported together and cannot be parsed and displayed. Go back to the original processing mode for a moment.

[weson-su]

What can i do for this Lint error? Thanks

[Koenkk]

Could you explain a bit why the current code does not work?

[weson-su]

It works fine with External converters, but says "Some checks were not successful" when pulling requests.

Run pnpm run pretty:check

zigbee-herdsman-converters@20.28.0 pretty:check /home/runner/work/zigbee-herdsman-converters/zigbee-herdsman-converters
prettier --check .

Checking formatting...
[warn] src/devices/owon.ts
[warn] Code style issues found in the above file. Run Prettier with --write to fix.
 ELIFECYCLE  Command failed with exit code 1.
Error: Process completed with exit code 1.

[Koenkk]

I mean, can you explain why this change was needed in the first place? What doesn't work with the original code?

[weson-su]

The version used is 1.40.2-1, after adding the device, it can be paired normally, and the onoff report is working normally. The problem is that instantaneousDemand and currentSummDelivered data are not updated on the Dashboard. Using the sniffer to capture the packet, it was found that the Configreport function was successful and the device could report normally. However, both instantaneousDemand and currentSummDelivered were reported together in one packet.
Wonder if the data merge report is not well compatible with the modernExtend processing?

[Koenkk]

However, both instantaneousDemand and currentSummDelivered were reported together in one packet.

Could you provide the debug log of this?

See this on how to enable debug logging.

[weson-su]

There are two devices in Log, 0x3c6a2cfffed35097 uses External converters, which works normally, such as line3424 of log, Mqtt is also reported after Zigbee Report.
0x3c6a2cfffed3b4c4 is used online version, abnormal work, such as log line3417, Zigbee Report after MQTT did not report.
log.log

[Koenkk]

Could you provide your configuration.yaml and the external converter?

[weson-su]

configuration.yaml.txt
WPS403.js.txt
CB432.js.txt
To facilitate the upload of Attach files, the file name extension of ".txt" is added.

[Koenkk]

Could you also provide your devices.yaml file?

[weson-su]

devices.yaml.txt
Please check the attachment.

[Koenkk]

I think the divisor is missing:

• Can you check if it publishes values with the latest dev branch
• Could you provide the data/database.db entry of this device?
• Could you provide the debug log when configuring it via the z2m frontend? (yellow refresh button)

See this on how to enable debug logging.

[weson-su]

I have use the edge vesion. divisor is 1000.
log (4).log
database.db.txt

[Koenkk]

It seems it published sometimes now.

[2024-10-23 15:05:47] debug: 	z2m: Received Zigbee message from '0x3c6a2cfffed3b4c4', type 'readResponse', cluster 'seMetering', data '{"currentSummDelivered":4026,"instantaneousDemand":50}' from endpoint 1 with groupID 0
[2024-10-23 15:05:47] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x3c6a2cfffed3b4c4', payload '{"energy":4.03,"linkquality":153,"power":50,"power_on_behavior":"off","state":"ON"}'

I cannot explain why it doesn't work the other time though:

[2024-10-23 15:05:39] debug: 	z2m: Received Zigbee message from '0x3c6a2cfffed3b4c4', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":4025,"instantaneousDemand":74}' from endpoint 1 with groupID 0
[2024-10-23 15:05:46] debug: 	z2m:mqtt: Received MQTT message on 'zigbee2mqtt/bridge/request/device/configure' with data '{"id":"0x3c6a2cfffed3b4c4","transaction":"9n6pp-1"}'

[weson-su]

The one that published is' readResponse '. If it is' attributeReport ', it is not publish.

[Koenkk]

Is this always the case? Because both are there:

zigbee-herdsman-converters/src/converters/fromZigbee.ts

Line 739 in 854080d

type: ['attributeReport', 'readResponse'],

[weson-su]

Yes.Trying to find the problem has not been able to find any problem, but falling back to the previous version of the processing is no problem. So if you want to go back to the previous way of processing to use, is it possible?

[Koenkk]

I don't see why it would fix it, it also uses fz.metering now.