Add optimizer data to solaredge_local

[scheric]

Description:

Added sensors for optimizer data.

• Average optimizer temperature
• Average optimizer input voltage
• Average optimizer input current
• Average optimizer power (calculated with the above averages)

Added sensor for inverter temperature.

Info

This is all the data received by the API

maintenance.log
power_control.log
status.log
information.log

My to-do list:

• Update lib.
• Add sensors.
• Add debug info.
• Add proper units.
• Fix Cl.
• Waiting for feedback.

What to test

• What happens when no optimizes are connected.
• What happens when inverter is offline.
• What happens when something went wrong during setup.
• What happens when more then one inverter connected.
• What happens to the optimizer voltage when it is night.

Problems

The solaredge-local api only gives current input in integers.

help needed for

Possible stuff people want to see.

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

[scheric]

Should the units for current and voltage be added in const.py

[MartinHjelmare]

We shouldn't add units in homeassistant/const.py in this PR. That could be done in another PR if there are many integrations that use the same units.

[MartinHjelmare]

Looks good!

[MartinHjelmare]

Is it ready to merge?

[scheric]

Not yet program fails when there was a bad connection to the inverter.
If that happens everything goes to 0.

[scheric]

Not a functional problem but would anyone hate having these large numbers or should i round the values.

[MartinHjelmare]

We usually want to present the data as is from the device, but if the device sends data that isn't following best practices regarding significant figures, it's ok to round. Ie we shouldn't present numbers with false precision.

[scheric]

There are no errors anymore when the inverter is not available.
There are no errors when the sun is under.

[scheric]

I think it is ready to be merged

This is the final result:

[MartinHjelmare]

Good!