From b0d9b60f1cc5cfa61b5d4020143c6ab0c67011b6 Mon Sep 17 00:00:00 2001 From: "S. Chauveau" Date: Fri, 3 May 2024 13:47:33 +0200 Subject: [PATCH 1/2] add note to PJ-1203A --- docs/devices/PJ-1203A.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/devices/PJ-1203A.md b/docs/devices/PJ-1203A.md index ec527ce084b2..5d998d2a5965 100644 --- a/docs/devices/PJ-1203A.md +++ b/docs/devices/PJ-1203A.md @@ -24,10 +24,17 @@ pageClass: device-page +## Notes - +### Late Energy Flow Bug + +Some or all PJ-1203A suffer from a bug that causes the energy flow direction to be reported during the next cycle update. In parctice, that means that an incorrect direction is published during `update_frequency`frequency seconds after any transition between `producing` and `consuming`. +For each channel `x`, the option `late_energy_flow_x` attempts to solve that problem by delaying the publication of `power_x`, `current_x`, `power_factor_x` and `energy_flow_x` until the next update of `energy_flow_x`. +The attribute `timestamp_x` indicates when the power value was actually received from the device. This is typically `update_frequency` seconds before the publication time when the option `late_energy_flow_x` is enabled. It should be noted that this delay des not occur when the power value is zero because the energy flow datapoint is neither emited nor needed. + + ## Options *[How to use device type specific configuration](../guide/configuration/devices-groups.md#specific-device-options)* From 150a7f4ddbe5da28debd20b2f2e1557733c28aa0 Mon Sep 17 00:00:00 2001 From: "S. Chauveau" Date: Fri, 3 May 2024 15:58:44 +0200 Subject: [PATCH 2/2] correct a syntax error and some minor changes --- docs/devices/PJ-1203A.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/devices/PJ-1203A.md b/docs/devices/PJ-1203A.md index 5d998d2a5965..fef970fd71f3 100644 --- a/docs/devices/PJ-1203A.md +++ b/docs/devices/PJ-1203A.md @@ -32,7 +32,7 @@ Some or all PJ-1203A suffer from a bug that causes the energy flow direction to For each channel `x`, the option `late_energy_flow_x` attempts to solve that problem by delaying the publication of `power_x`, `current_x`, `power_factor_x` and `energy_flow_x` until the next update of `energy_flow_x`. -The attribute `timestamp_x` indicates when the power value was actually received from the device. This is typically `update_frequency` seconds before the publication time when the option `late_energy_flow_x` is enabled. It should be noted that this delay des not occur when the power value is zero because the energy flow datapoint is neither emited nor needed. +The attribute `timestamp_x` indicates when the power value was actually received from the device. This is typically `update_frequency` seconds before the publication time when the option `late_energy_flow_x` is enabled. It should be noted that this delay does not occur when the power value is zero because the energy flow datapoint is neither produced by the device nor needed to compute the sign.