Skip to content

Commit

Permalink
Merge pull request #208 from tzapu/patch-1
Browse files Browse the repository at this point in the history
update moving_avg from snippets to throttle_avg
  • Loading branch information
flaviut authored Sep 19, 2023
2 parents c0321f1 + 4dcb5c6 commit 86fd7d1
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -318,13 +318,13 @@ sensor:
power:
name: "Phase A Power Return"
id: phase_a_power_return
filters: [*moving_avg, *invert] # This measures energy uploaded to grid on phase A
filters: [*throttle_avg, *invert] # This measures energy uploaded to grid on phase A
- phase_id: phase_b
input: "B" # Verify the CT going to this device input also matches the phase/leg
power:
name: "Phase B Power Return"
id: phase_b_power_return
filters: [*moving_avg, *invert] # This measures energy uploaded to grid on phase B
filters: [*throttle_avg, *invert] # This measures energy uploaded to grid on phase B
- platform: template
name: "Total Power Return"
lambda: return id(phase_a_power_return).state + id(phase_b_power_return).state;
Expand Down Expand Up @@ -438,7 +438,7 @@ If the readings are significant outside of that, there may be a problem.

### I'm seeing zeros on certain current clamps

First off, you will want to remove all filters for that sensor. Replace `filters: [ *moving_avg, *pos ]`, etc, with `filters: []`.
First off, you will want to remove all filters for that sensor. Replace `filters: [ *throttle_avg, *pos ]`, etc, with `filters: []`.

If your data is hovering around 0, then you either don't have any load on that circuit or there's some other issue that hasn't come up before.

Expand Down

0 comments on commit 86fd7d1

Please sign in to comment.