Change log level of some logs to debug

[mvdwetering]

I had to analyze my HA logs for another issue and it was difficult due to the Omnik integration generating a lot of logging during the night.

I would suggest to change these logs level to debug to avoid polluting the logs when not needed. When needed for debugging one can easily enable debug logging for the integration to get them again.

I had this running for a couple of days and seems to work as intended.

[MarijnS95]

Some of these should not just serve as application debug, but as useful info when e.g. setting up the connection and getting a failed connection without details otherwise. It is hard to tell from the diff if this is now affected, but it looks like it.

[mvdwetering]

The errorhandling during initial connection setup is not impacted as that is all in config_flow.py.

Config entries will still be shown in the HA UI as having an error. It is just not spamming the log anymore.
The ConnectionError is most of the time not an error for this integration as it is expected to not being able to connect when there is no sun. Hence the desire to not have logging for things that are expected to happen.

When the more detailed info is needed you can just click the "Enable debug logging" in the integration and it will show again (including stack traces).

I could revert the AuthenticaitonError change as that is likely to be an actual error. I just included it because it seemed the same as the other line.

[robbinjanssen]

Maybe we should change this into a setting via config flow?

[mvdwetering]

Maybe we should change this into a setting via config flow?

Wouldn't that be almost the same as the Home Assistant "Enable debug logging" option?

Main difference would be that you can enable/disable it per config entry. "Enable debug logging" is for the whole integration so all config entries. Not sure how important that is.

[MarijnS95]

The errorhandling during initial connection setup is not impacted as that is all in config_flow.py.

Good to have that confirmed, that's where such errors are most helpful.

Config entries will still be shown in the HA UI as having an error. It is just not spamming the log anymore.

Do you mean shown as error while going through the config flow? Or does it show an error every night while the inverter is unreachable?

[mvdwetering]

Config entries will still be shown in the HA UI as having an error. It is just not spamming the log anymore.

Do you mean shown as error while going through the config flow? Or does it show an error every night while the inverter is unreachable?

I meant this part of the UI

However, looking back I am not sure why I mentioned it since it only gets in that state when the integration gets (re)loaded.

[klaasnicolaas]

That is because your inverter is currently off and therefore not available to collect data?

[robbinjanssen]

Since this is no longer needed, i'll close this PR.