Replies: 8 comments 29 replies
-
HI @faanskit, cool that you have put in the work. First, I would like to warn all current users that if you switch, you will lose all history data in your energy dashboard when changing the consumption sensors! Having said that, I should tell you that I do not have any solar panels myself and set up this integration helping out a family member who had got solar panels without HA support as the new dongles have no local API. From there, I received some login details of other users who liked the integration, so I could reverse engineer the API to support their devices. So basically I am okay with you improving/maintaining this repository, but it has to be backward compatible. |
Beta Was this translation helpful? Give feedback.
-
I think it would be a good idea to just release this as a parallel integration because it's not backwards compatible. So from my understanding there is no support yet for a battery? |
Beta Was this translation helpful? Give feedback.
-
If you like I can send you the json data from the end points I use for sec and H1. Ps @robshot what I offered to Marcus also goes for you, if you want to co-maintain this integration |
Beta Was this translation helpful? Give feedback.
-
Ok got it. |
Beta Was this translation helpful? Give feedback.
-
With some help from @robshot, progress have been made to also support H1. A few more attributes to add, then it should be possible to test it on a live system. For now, simulated environment based on sniffed data for H1. R5 have been tested with my own plants. |
Beta Was this translation helpful? Give feedback.
-
@faanskit are you willing to share your code so i might be able to learn how you setup the UI integration ? |
Beta Was this translation helpful? Give feedback.
-
@robshot and @djansen1987, you are both added as collaborators to a new private repository. Add as custom_component. Settings->Integrations->Add integration-->eSolar Insert your credentials and sensors shall be populated. To get more sensors and additional data as attributes_ Have fun.... Limited support for a while; busy days ahead. |
Beta Was this translation helpful? Give feedback.
-
It's now in the open, tested with a Dual Plant R5 system and a Dual Plant R5+H1 system. No support for SEC. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I've made an extensive overhaul of this integrations, basically starting from scratch. Only a few lines of code remains intact from original.
I'd like to know if you want this work to be pushed as a PR, or if I keep it a separate (and competing) integration.
It is 100% breaking the current system, and no migration possible.
Today it only supports Inverters (since that is what I have), but it natively supports Multi-site, and it supports multiple inverters per site.
It is set-up via Add integration, so no more
configuration.yaml
. (Sorry for the Swedish in the screenshots, I also support translations as per standard HA framework)I has minimal amount of sensors, but support more information as attributes. In this example, two sites:
Two sensors per site : Status & Energy
Two sensors per inverter: Energy and Power
As you can notice, under the Power sensor you find PV and Grid data.
I intend to add the following before I consider releasing it:
(1) Configuration of [multiple] sites (enable/disable)
(2) Configuration of inverter sensors (enable/disable); the inverter information is kind of redundant unless you need details
(3) Configuration of inverter PV/Grid attributes (enable/disable); the WEB query slows down the system quite a bit
Of course I'd like to support SEC and H1 - but then I'd need some more information about them and someone to test. In essence, I'd like to login to eSolar site with someone else credential while designing and building the system.
In a roadmap I consider to move the Esolar API code to become a PIP libary ay PyPi. Already now the integration code is broken out from the home assistant code, but for now it resides in a local file.
Should I also get intel about how to use the APP API's (encoding unknown) I will change from WEB API to APP API as they are more rich than the WEB API's.
What do you think. Would it be worth pushing this, or do I keep it separate?
/Marcus
Beta Was this translation helpful? Give feedback.
All reactions