Home Assistant release with the issue:
0.99.2
Last working Home Assistant release (if known):
0.98.x
Operating environment (Hass.io/Docker/Windows/etc.):
Hassio on Raspberry Pi 3 B+
Component/platform:
SolatEdge CLOUD via API
Description of problem:
Upgraded to 0.99.2 yesterday and now SolatEdge sensors do not appear. configuration.yaml is unchanged
Problem-relevant configuration.yaml
entries and (fill out even if it seems unimportant):
Using default yaml, expect for specific API.
Traceback (if applicable):
Additional information:
Hey there @drobtravels, @scheric, mind taking a look at this issue as its been labeled with a integration (solaredge_local
) you are listed as a codeowner for? Thanks!
@DavidqStokes Could you please case to provide the requested data in the issue template? Thanks already! 👍
Home Assistant release with the issue:
0.99.2
Last working Home Assistant release (if known):
0.98.X
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
Solaredge
> Code:
> - platform: solaredge
> api_key: XXX
> site_id: XXX
> name: solaredge
>
Description of problem:
Solaredge entities are not available, no errors in logging (debug).
@frenck
I think this is about the online SolarEdge version
Mine SolarEdge (online) works still on 0.98.4
Did it work on 0.99?
If not perhaps take a look at the breaking changes in the release notes.
https://www.home-assistant.io/blog/2019/09/18/release-99/#breaking-changes
Yes, this is the online version which connects (or connected) to the SolarEdge API server. It worked perfectly under 0.98.4, but when I upgraded to 0.99.2 yesterday it was broken.
On further investigation, the defined sensors are not created and therefore cannot be used (which is a pity, because I was about to create some automations based on how much power was consistently being generated by my PV system.
Hopefully this is something that can be fixed.
David Stokes
On Sun, Sep 22, 2019 at 1:37 PM +0100, "scheric" notifications@github.com wrote:
@frenck
I think this is about the online SolarEdge version
Mine works still on 0.98.4
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
There was a breaking change in 0.99 and the solaredge integration became a component with platforms instead of just a sensor platform. So the config yaml needs to be updated. This was unfortunately not included in the release notes.
The docs have been updated though:
https://www.home-assistant.io/components/solaredge/#configuration
There was a breaking change in 0.99 and the solaredge integration became a component with platforms instead of just a sensor platform. So the config yaml needs to be updated. This was unfortunately not included in the release notes.
The docs have been updated though:
https://www.home-assistant.io/components/solaredge/#configuration
Thanks updated yaml and confirmed working. Still curious why the config checker doesn't flag the old configuration as error?
Okay - I tried this tonight and the new SolarEdge platform is working fine.
I edited my configuration.yaml to include the new platform, using the default configuration, removing the old sensors. This worked first time and pulled data from the SolarEdge API. The platform created the new sensors straight away.
However, the new sensors created by the new platform have a different entity name (the text '_pv' is no longer part of the enitity name), but it was easy enough to edit the entity names in the UI to get everything working again.
Even better, the template to convert from Wh (Watt hours) to KWh (Kilowatt hours) also works, which I couldn't previously get to work. (I may actually convert the lifetime generation outs to MWh (Megawatt hours).
I can now work on some automations to send my wife some messages to put the washing machine and dishwasher on when we have a nice sunny day (... not always, in the north of England).
Thanks for pointing me in the right direction
I also confirm, same problem in 0.99.3 and solution :-) all is fine.
Most helpful comment
Okay - I tried this tonight and the new SolarEdge platform is working fine.
I edited my configuration.yaml to include the new platform, using the default configuration, removing the old sensors. This worked first time and pulled data from the SolarEdge API. The platform created the new sensors straight away.
However, the new sensors created by the new platform have a different entity name (the text '_pv' is no longer part of the enitity name), but it was easy enough to edit the entity names in the UI to get everything working again.
Even better, the template to convert from Wh (Watt hours) to KWh (Kilowatt hours) also works, which I couldn't previously get to work. (I may actually convert the lifetime generation outs to MWh (Megawatt hours).
I can now work on some automations to send my wife some messages to put the washing machine and dishwasher on when we have a nice sunny day (... not always, in the north of England).
Thanks for pointing me in the right direction