Clarification on "input" and "id"

[sockmonkey0223]

As I build my configuration, I just want to make sure my understanding is correct regarding "input" and "id".

Am I correct in assuming that the "input" refers to the actual physical port on the Vue, and that "id" is an internal label or reference?

e.g.
My HVAC compressor is on breaker or circuit number 36. I plug the CT into port 1 on the Vue. Hence:

• { phase_id: phase_a, input: "1", power: { id: cir36, filters: [ *pos, multiply: 2 ] } }
• { platform: copy, name: "HVAC Compressor Power", source_id: cir36, filters: *throttle_avg }
• { power_id: cir36, platform: total_daily_energy, accuracy_decimals: 0, name: "HVAC Compressor Daily Energy", filters: *throttle_time }

[flaviut]

You are correct :)

…

On Wed, Sep 6, 2023, 14:45 sockmonkey0223 ***@***.***> wrote: As I build my configuration, I just want to make sure my understanding is correct regarding "input" and "id". Am I correct in assuming that the "input" refers to the actual physical port on the Vue, and that "id" is an internal label or reference? e.g. My HVAC compressor is on breaker or circuit number 36. I plug the CT into port 1 on the Vue. Hence: - { phase_id: phase_a, input: "1", power: { id: cir36, filters: [ *pos, multiply: 2 ] } } - { platform: copy, name: "HVAC Compressor Power", source_id: cir36, filters: *throttle_avg } - { power_id: cir36, platform: total_daily_energy, accuracy_decimals: 0, name: "HVAC Compressor Daily Energy", filters: *throttle_time } — Reply to this email directly, view it on GitHub <#201>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHY2HLK7AEZHJ4HXJ3OVFDXZDACVANCNFSM6AAAAAA4NYRBOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[sockmonkey0223]

A couple more questions:

1. Is there any advantage to using 2 lines (per the example) vs 1 to create the sensor?

   • { phase_id: phase_a, input: "1", power: { id: cir2, filters: [ *pos, multiply: 2 ] } }
   • { platform: copy, name: "Range Power", source_id: cir2, filters: *throttle_avg }

   vs.

   • { phase_id: phase_a, input: "1", power: { name: "Range Power". id: cir2, filters: [ *throttle_avg, *pos, multiply: 2 ] } }

2. The readme says "Note the sliding_window_moving_average" but I don't see that in the example config. I've also seen other configs using moving_average. Which of the three are currently recommended?

[flaviut]

Is there any advantage to using 2 lines (per the example) vs 1 to create the sensor?

Yup! Context: #200, https://www.technowizardry.net/2023/02/local-energy-monitoring-using-the-emporia-vue-2/

Would suggest reading the blog post around "Previously, esphome would perform a 2.88s moving average, then integrate that value for energy consumption"--it explains it much better than I can.

In short, doing it this way leads to improved energy measurement accuracy.

Note the sliding_window_moving_average" but I don't see that in the example config

Fixed :)

Which of the three are currently recommended?

The main page will be always be updated to contain the best practices.