unfortunately this sensor does not show up in the new energy section even with device_class and state_class defined. What do I need to do to get it seen?
for some reason i still don’t know 2018-8 are not working with my current configuration
after the update my supervisor api lost connection with my network at the point that can’t found any shelly device or even pull data of coronavirus integration
i start a new virtual machine and found all the shelly’s but at soon as i restore my backup, everything broke again
Hello,
I have an EFERGY integration taking every some minutes the energy consumption from a Clamp.
When I try to setup the new Energy by Home Assistant I cannot select the Energy device as source and therefore there is nothing to select.
What i am missing
Thanks.
The new statistics layout is really great! One minor request, would it be possible to display min/max or volatility without options to choose? So e.g. display temperature sensors x and y with mean and volatility, but only choose between x and y don’t display min/max options to choose.
I do not see Influx DB sensors as a source for the energy panel. Could it be that these sensors are currently not enabled to support the new statistical feature?
Tough Love comment.
Backward compatibility good. Breaking changes bad. We all know that. Some breaking changes may be unavoidable. Some are not.
For EXAMPLE – TP-Link Kasa Smart:
"The power and energy attributes from switch entities have been REMOVED and REPLACED by sensors. This applies to all five extra attributes about energy (current_power_w, total_energy_kwh, today_energy_kwh, voltage, current_a ).
Okay I get it. Adding the sensors is fine. I created these sensors way back when from attributes. But why was it deemed necessary to delete the attributes? Deleting the attributes forces users to make changes to their code. Leaving the attributes in place is a backward compatibility strategy at the expense of duplication. This one is especially painful since the integration will probably loose popularity with Home Assistant users moving forward due to TP-Link’s removal of the local API (unless the firmware update port is blocked at the router).
This is just an example. I can make these changes in less then an hour. But these types of unnecessary “breaking changings” are totally avoidable and only serve to propagate Home Assistant’s reputation for being “high maintenance” thus impeding it’s popularity moving forward.
There are lots of other examples but I’ve made my point.
Bottom line:
Backward compatibility needs to be a HIGH priority - or better yet, a “MUST” in the update strategy.
Pretty nice, but AVM FRITZ!Box Tools doesn’t work anymore. sensor.router disappeared, all tracked device become unknown (wich is a pain if you have automate most devices relaying on that), only up/downrates stay as they was. FRITZ!Box 7530 and no hints in log about that. Help pls.
Just updated to the recent version and now my TP-Link KP400 is in an unavailable state and no matter how many times i “reload” the integration or restart HA it never shows up. On previous version it still works.
I don’t have solar but I do track device usage and total usage of electricity. Got a couple of qs:
Is there a way, perhaps in the future, to allow the energy stat graph to include gas use as well as electricity? Perhaps with a seperate sidebar graphic of the ‘gas grid’? It’d be good to see together, e.g. to see where heating 1 room with an electric fire might be better than the gas central heating, etc. I could make a view of my own for most of this (not sure about the energy cost) - but wondered if it’d help others too. ie there are 22m gas central heating systems in the UK!
Can I add the energy dashboard to a view in another dashboard - my wall tablets dont have the sidebar showing by default and I’d love a quick way to navigate to the dash (and back) without side-swiping?