Unit ('') does not match
See original GitHub issueon grouped energy sensors and on all power sensors, this is displayed in the statistics tab of developer
Must admit I didnt see this before, so probably because of updating to latest dev nightly 2022.5.0.dev20220407
I dont have classes set, nor units, believing the powercalc integration handles that?
main config I use is
powercalc:
energy_sensor_naming: '{} device energy'
power_sensor_naming: '{} device power'
and eg the groups mentioned are:
- platform: powercalc
create_group: Dining table
entities:
- entity_id: light.dining_table_lamp_1
- entity_id: light.dining_table_lamp_2
- entity_id: light.dining_table_lamp_3
- platform: powercalc
create_group: Terrace outdoors
entities:
- entity_id: light.terrace_spot_1
- entity_id: light.terrace_spot_2
- entity_id: light.terrace_spot_3
- entity_id: light.terrace_spot_4
as you can see the energy is correctly calculated for the group, its simply a matter of the missing unit
btw, I now notice also, that the grouped sensors dont carry the attribute integration: powercalc
, like all other power sensors do. (none of the energy sensors either, is that correct?)
Issue Analytics
- State:
- Created a year ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
f# iterating : The type 'unit' does not match the type 'char'
iter returns unit and is only used for the function's side-effects, which in this case don't exist. My guess is you probably want...
Read more >Solved: unit do not match - PTC Community
Hi,. This is an engineering stiffness problem where the stiffness matrix has different units for different elements. In Prime 6.0 it is possible ......
Read more >The unit of sensor.load_1m (None) does not match ... - GitHub
Hi @kdknigga you are absolutely right, it is caused by the correction of UoM in #56140. Unfortunately, there is currently no way via...
Read more >Error: This name does not match the unit name. [DO_COMBINE]
My code is as follows: program do_combine use decarrays implicit ... Error: This name does not match the unit name. ... if (iargc()...
Read more >Units do not match - SMath Studio
Hi idelarca1, hold the mouse pointer over Q.1yrpre, you can see that the sum is not possible, because S.pre is dimensionless while P...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Attribute integration is correct. That one is only set on power entity, not the group ones. Maybe I’ll will remove that one in the future as I only added it to make groups with the template sensor (and only select powercalc sensors that way). However since the last months powercalc has extensive possibilities to create groups, so this attribute is obsolete. But it certainly has nothing to do with the missing unit.
I have no clue yet, must be something HA internal.
When you still experience this issue in the coming week (when 2022.5 is progressing) I will have a look if I can reproduce.
Btw, here are the units set. This is according to HA developer documentation, and has always worked.
I have already made the change in #670. Has been merged into master.
I don’t think I am experiencing this issue. I have one light which gets unavailable sometimes (not sure why), but my other 22 lights are rock solid and never get unavailable. Also had this issue with the V1 api for that particular light. So I am not sure why you are experiencing an regression here with Hue API V2.
This is not something which can be solved in powercalc as I just act on state changes of the bound entity. When there are bugs in the hardware / api / integration (in this case Hue) it has to be solved there.