Data for not-connected inputs.

[sirtow]

I recently installed ver 2023.11.6 on new unit. I have some of inputs not connected to the clamps but I do see that those inputs report some usage around 100w.

Is it expected behavior? is there a way to set those inputs are not connected?

[sirtow]

I ended up adding a new entry under defaultfilters:

- &nullify 
    lambda: "return 0.0f;"

and then replacing the pos filter with nullify

[Cyphon00]

I took a slightly different approach.
Initially, I zeroed out any CTs that were not connected to the Vue2 (yet the sensors were still sending spurious data due to the electrical noise they were picking up).
I zeroed them using the multiply function and have provided an example of how I applied this to CT11-16.

Pay close attention to set the phase_id for each breaker by matching it to the phase/leg it connects to in the panel
      - { phase_id: phase_a, input: "10", power: { id: cir10, filters: [ *pos ] } }
      - { phase_id: phase_a, input: "11", power: { id: cir11, filters: [ *pos, multiply: 0 ] } } #Using  'multiply: 0' to set CT to 0W for any ununsed/unconnected sensors to stop noisy/erroneous power data.
      - { phase_id: phase_a, input: "12", power: { id: cir12, filters: [ *pos, multiply: 0 ] } } #Using  'multiply: 0' to set CT to 0W for any ununsed/unconnected sensors to stop noisy/erroneous power data.
      - { phase_id: phase_a, input: "13", power: { id: cir13, filters: [ *pos, multiply: 0 ] } } #Using  'multiply: 0' to set CT to 0W for any ununsed/unconnected sensors to stop noisy/erroneous power data.
      - { phase_id: phase_a, input: "14", power: { id: cir14, filters: [ *pos, multiply: 0 ] } } #Using  'multiply: 0' to set CT to 0W for any ununsed/unconnected sensors to stop noisy/erroneous power data.
      - { phase_id: phase_a, input: "15", power: { id: cir15, filters: [ *pos, multiply: 0 ] } } #Using  'multiply: 0' to set CT to 0W for any ununsed/unconnected sensors to stop noisy/erroneous power data.
      - { phase_id: phase_a, input: "16", power: { id: cir16, filters: [ *pos, multiply: 0 ] } } #Using  'multiply: 0' to set CT to 0W for any ununsed/unconnected sensors to stop noisy/erroneous power data.      

I soon realised that HA was still importing the zeroed CTs (CT11-16), resulting in graphs with a bunch of empty (and useless) datapoints from all those zeored sensors.
To fix this, I commented out CTs 11-16 in 2 locations (Power and Daily Energy), like so:

<...>
  - { platform: copy, name: "${Circuit10} Power", source_id: cir10, filters: *throttle_avg }
  #- { platform: copy, name: "${Circuit11} Power", source_id: cir11, filters: *throttle_avg }
  #- { platform: copy, name: "${Circuit12} Power", source_id: cir12, filters: *throttle_avg }
  #- { platform: copy, name: "${Circuit13} Power", source_id: cir13, filters: *throttle_avg }
  #- { platform: copy, name: "${Circuit14} Power", source_id: cir14, filters: *throttle_avg }
  #- { platform: copy, name: "${Circuit15} Power", source_id: cir15, filters: *throttle_avg }
  #- { platform: copy, name: "${Circuit16} Power", source_id: cir16, filters: *throttle_avg }
  - platform: template
<...>
  - { power_id: cir10, platform: total_daily_energy, accuracy_decimals: 0, restore: false, name: "${Circuit10} Daily Energy", filters: *throttle_time }
  #- { power_id: cir11, platform: total_daily_energy, accuracy_decimals: 0, restore: false, name: "${Circuit11} Daily Energy", filters: *throttle_time }
  #- { power_id: cir12, platform: total_daily_energy, accuracy_decimals: 0, restore: false, name: "${Circuit12} Daily Energy", filters: *throttle_time }
  #- { power_id: cir13, platform: total_daily_energy, accuracy_decimals: 0, restore: false, name: "${Circuit13} Daily Energy", filters: *throttle_time }
  #- { power_id: cir14, platform: total_daily_energy, accuracy_decimals: 0, restore: false, name: "${Circuit14} Daily Energy", filters: *throttle_time }
  #- { power_id: cir15, platform: total_daily_energy, accuracy_decimals: 0, restore: false, name: "${Circuit15} Daily Energy", filters: *throttle_time }
  #- { power_id: cir16, platform: total_daily_energy, accuracy_decimals: 0, restore: false, name: "${Circuit16} Daily Energy", filters: *throttle_time }

Hope that helps.

[sirtow]

Using existing multiply is much simpler than adding a new function route I took :), Thanks! .
As a side note, how/where did you define the ${Circuit11}?

[Cyphon00]

:) No probs.

I added those names when I was trying to figure out how to give the sensors a 'friendly' name (rather than "sensor.emporiavue2_ct09_power"). Turns out, that defining their name in the YAML isn't the way to do it, and it's done once they are in HA instead.
Either way, here's the code I added at the very start of the vue2 YAML. It's probably not necessary now, but I liked it/kept it so it's easy to update the sensor names in future, if needed.

# Define names for the circuits here. Easier than naming in HA
substitutions:
  Circuit01: "CT01"
  Circuit02: "CT02"
  Circuit03: "CT03"
  Circuit04: "CT04"
  Circuit05: "CT05"
  Circuit06: "CT06"
  Circuit07: "CT07"
  Circuit08: "CT08"
  Circuit09: "CT09"
  Circuit10: "CT10"
  Circuit11: "CT11"
  Circuit12: "CT12"
  Circuit13: "CT13"
  Circuit14: "CT14"
  Circuit15: "CT15"
  Circuit16: "CT16"
##