Hardcode clamp entity id into configuration #177
Unanswered
karpeychik
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Been playing with configuration for a while. I noticed a few things, but this is my first experience with ESPHome so I might be just doing something wrong. Would appreciate pointers.
- { phase_id: phase_b, id: vue2_breaker_cir_dishwasher, input: "1", power: { name: "Dishwasher", id: vue2_breaker_dishwasher, filters: [ *moving_avg, *pos ] } }
I would expect HA to get entity like
sensor.vue2_breaker_dishwasher
orsensor.vue2_breaker_cir_dishwasher
, but I get sensor.vue2_dishwasher. It seems like the entity id is always generated from lower casing the name. I'd like to future proof against something like a name change. I could introduce a template sensor but seems like would be better if I could just hardcode this.- { phase_id: phase_b, input: "1", power: { name: "Dishwasher", id: cir1, filters: [ *moving_avg, *pos ] } }
- { power_id: cir1, platform: total_daily_energy, accuracy_decimals: 0, name: "Dishwasher" }
Since names are the same the id would match and earlier sensor would be dropped. In my case I only see Wh sensor but no W sensor. Is this something compilation should be complaining about. (It might do this already and I don't know where to look).
Beta Was this translation helpful? Give feedback.
All reactions