Zigbee2mqtt: Owon PC321 Z incomplete

Feature requests
,
1

Hello everyone,

I’m writing something about the Owon PC321-Z and I notice that on Gladys it is only partially recognized — how can we add all of its functions?

Screenshot of 2024-05-07 22-17-16
Screenshot of 2024-05-07 22-17-16441×535 15.4 KB

Whereas in Zigbee2MQTT :

{
    "current": 0.87,
    "current_l1": 0.56,
    "current_l2": 0.307,
    "current_l3": 0,
    "energy": 28.36,
    "energy_l1": 8.559000000000001,
    "energy_l2": 19.805,
    "energy_l3": 0,
    "linkquality": 149,
    "power": 45,
    "power_factor_l1": 1,
    "power_factor_l2": 0.75,
    "power_factor_l3": 0,
    "power_l1": -6,
    "power_l2": 53,
    "power_l3": 0,
    "power_reactive": 46,
    "reactive_energy": 21.857,
    "reactive_energy_l1": 2.036,
    "reactive_energy_l2": 19.821,
    "reactive_energy_l3": 0,
    "reactive_power_l1": 0,
    "reactive_power_l2": 46,
    "reactive_power_l3": 0,
    "voltage_l1": 230.8,
    "voltage_l2": 230.6,
    "voltage_l3": 230.6
}

Thanks in advance

1 Like
2

You need to submit a feature request for a developer to add them :+1:

1 Like
3

Thanks for the feedback @McFlyPartages, I’ve converted this post into a feature request!

1 Like
4

That’s not really a feature, is it? Because it’s just adding a device to Zigbee2mqtt?

5

If it’s to add the unknown features of this device to Gladys.
It’s not complicated to do.
I can’t promise anything because I don’t have much time at the moment, but I can put it aside. Unless someone starts before me…

1 Like
6

If there’s a how-to I’ll be willing to try, but like everyone else I’m short on time

7

A feature request = a development :slight_smile:

As soon as someone has to « work » (except for a bug, in which case it’s a GitHub issue), it should be put in this category :slight_smile:

Here’s an example of a PR for this kind of development:

All the developer documentation is here:

Live coding sessions are good examples too :slight_smile:

Knowing that the hardest part isn’t making the PR, the most time-consuming part is gathering the information and testing in real conditions to make sure everything works!

In this case, it will also be necessary to create new types of features, because we don’t handle « reactive_energy », etc.. I don’t even know what that is, I admit :sweat_smile:

1 Like
8

@pierre-gilles

That corresponds to the energy consumed by old appliances like fridges and washing machines that have RC circuits with capacitors and that cause a phase shift; it is measured and billed in industrial settings with three-phase and not to private households, so…

https://www.edf.fr/entreprises/faq-entreprises/facture/comprendre-gerer/quest-ce-que-lenergie-reactive

Reactive energy is measured separately by the Linky meter and is not transmitted to suppliers. It is therefore not taken into account for customer billing.
The main consumers of reactive energy are large consumers, notably in industry that use welding machines, induction and arc furnaces, asynchronous motors, transformers or fluorescent lamps. Under High Voltage tariffing, an excessively high reactive consumption leads to the application of a financial penalty by the distributor. The threshold is set by the value of the cos phi which must remain > 0.9. This value is indicated on each monthly bill, in the lower left corner

There you go… EDF owes more than just the lights! :rofl:

2 Likes
9

@pierre-gilles, I believe you told me about a JSON to provide? Isn’t that what I posted above?

Thanks in advance

10

@McFlyPartages No, you’re mixing that up with this thread :slight_smile:

1 Like
11

I understand better why I couldn’t find the message lol

1 Like
12

If you need any doc/info about this device, don’t hesitate to ask me. I had taken care of adding some metrics, in particular the power factor:

I should be able to find the attribute IDs knowing that this device sends some non-standard metrics.

1 Like