Closed heinemannj closed 4 months ago
I've made a quick and dirty review of your code.
My view:
My conclusion:
Sorry for the noise ...
Agree, battery charge and discharge automations based on solar forcast and energy prices are key. Don’t forget your carharger. It is way beyond the scope of this project and my skills to create a universal automation and/or implement various forcast and price prediction service, let alone maintain it.
You are looking at this time to raw Huawei Solar and PEES values which is helpful for debugging purpose. In addition you are on the way to integrate historical data - Very good.
But only looking into the past and to the future at the same time will safe our Earth and our money ...
From my perspective the most complex task:
A lot of different integrations to be synchronized ...
=>
Battery Charge-Discharge automation
is key!My approach: To be much close to the nameing conventions provided by @wlcrs huawei_solar and all other integrations I needs to synchronize:
It works as visible in above screenshoots!
For sure tons of bugs and a lot of improvement - but I need clear readable and short sensor names for proper debugging on all integration dependencies ...