Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add note to PJ-1203A #2734

Merged
merged 2 commits into from
May 4, 2024
Merged

add note to PJ-1203A #2734

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b0d9b60
add note to PJ-1203A
schauveau May 3, 2024
150a7f4
correct a syntax error and some minor changes
schauveau May 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion docs/devices/PJ-1203A.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,10 +24,17 @@ pageClass: device-page

<!-- Notes BEGIN: You can edit here. Add "## Notes" headline if not already present. -->

## Notes

<!-- Notes END: Do not edit below this line -->
### 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 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.

<!-- Notes END: Do not edit below this line -->

## Options
*[How to use device type specific configuration](../guide/configuration/devices-groups.md#specific-device-options)*
Expand Down
Loading