Monitor, Re-Authentication with Schluter API over time

[IngoS11]

After a few days the integration triggered the need for a re-configuration. Why this happened is not entirely clear, the log files in my production environment did not give a clue. I have increased the logging to monitor the problem.

[IngoS11]

So far, the authentication has held up. No issues in production. We will continue to monitor

[ryandkg]

Installed last night and after providing credentials, the integration started flawlessly.

By morning it needed re-configuration (ie login credentials for Schluter site).

I have set the logging level to:
homeassistant.components.schluter.climate: critical

[IngoS11]

@ryandkg I see this as well from time to time but have not yet figured out why that happens

[ryandkg]

@IngoS11 - I installed the recent update of this integration. Since then my Schluter thermostats have lost connection to the server twice, most recently last night.

When checking the logs I see the following error:

This error originated from a custom integration.

Logger: custom_components.schluter
Source: helpers/update_coordinator.py:322
Integration: Schluter DITRA-HEAT-E-Wifi (documentation, issues)
First occurred: 02:17:38 (1 occurrences)
Last logged: 02:17:38

Error fetching schluter data: Invalid Response: 503

Hope this is helpful in diagnosing the problem.

[IngoS11]

@ryandkg Yes this is still an issue. It happens on my production machine as well. I was suspecting something is wrong with the authentication but it looks like they are doing something on their end that causes a 503.

[nathaliea]

I also installed it but when I type my correct login and password it keeps saying Invalid username or password. Any suggestions?