This is not related to a problem. We could always write our own sensors, but the best thing would have been if this device does it all internally and then we can make use of the sensors the way we want.
How it is being handled doesn't have to be exactly the same as powersavers example. The most important is a sensor that makes it easy to understand if we have to reduce the current power usage to stay below a configured capacity threshold, and some information about how close or far away we are. Based on these sensors it should be easier to write automation's to turn off elements/entities with high power usage to stay below the configured threshold. And turn them back on again at the start of a new hour.
This should make it much easier to add capacity automation's for those who's not capable of writing their own sensors. I also think this would make the device more complete as a all-in-one power-metering-device.
This is not related to a problem. We could always write our own sensors, but the best thing would have been if this device does it all internally and then we can make use of the sensors the way we want.
I want pretty much the same sensors as these powersaver sensors provide: https://powersaver.no/examples/example-grid-tariff-capacity-part.html
How it is being handled doesn't have to be exactly the same as powersavers example. The most important is a sensor that makes it easy to understand if we have to reduce the current power usage to stay below a configured capacity threshold, and some information about how close or far away we are. Based on these sensors it should be easier to write automation's to turn off elements/entities with high power usage to stay below the configured threshold. And turn them back on again at the start of a new hour.
This should make it much easier to add capacity automation's for those who's not capable of writing their own sensors. I also think this would make the device more complete as a all-in-one power-metering-device.