Integration is unstable about remeha_home HOT 9 CLOSED

Definitely agree on the unavailability part. Especially the past couple of days. But I'm not sure it is the integration.
I think the Remeha home servers are to blame.

My theory is that somehow one of the Remeha server instances goes haywire on older login tokens.
Then the integration checks every minute for a status update. If you're lucky you get a valid login and all is ok or else you get a login timeout and the entities become unavailable.

Re-installing the integration did help for me.
Probably resetting login tokens.

Edit: reinstall solution didn't last long..

from remeha_home.

Same issues here, the entities created by the integration become unavailable every now and then and all of a sudden they are available again.

from remeha_home.

I have configured an Uptime Kuma (https://github.com/hassio-addons/addon-uptime-kuma) watcher.
The URL i'm watching is: https://api.bdrthermea.net/ and expected response (as I don't do the right request or authenticate) is a 404. But in about 15% of the cases it failed with a "getaddrinfo EAI_AGAIN api.bdrthermea.net".

from remeha_home.

I have traced the URI and got some more addresses to check.
It seems the API runs Azure.

https://bdriotprdapim.azure-api.net/
https://bdriotprdapim-westeurope-01.regional.azure-api.net

Are now added to the monitor.

from remeha_home.

I have traced the URI and got some more addresses to check. It seems the API runs Azure.

https://bdriotprdapim.azure-api.net/ https://bdriotprdapim-westeurope-01.regional.azure-api.net

Are now added to the monitor.

This are the errors I’m getting:
Error requesting remeha_home data: Cannot connect to host api.bdrthermea.net:443 ssl:default [Try again]
Error requesting remeha_home data: Cannot connect to host remehalogin.bdrthermea.net:443 ssl:default [Try again]

from remeha_home.

Today I was keeping a close eye on the integration and found something I would not expect. When HA reports the thermostat to be unavailable, the app on mobile works fine, including changing the set point. That is not what would have expected.

from remeha_home.

Is anyone here using the AdGuard addon for homeassistant? I think that changing the setting described here fixed my issues.

from remeha_home.

I am using AdGuard indeed, I have disabled the "use private reverse DNS resolvers".
Let's see if it changes anything.

I have this setting now active for 15 minutes and already see some differences. The DNS response time is 100-150 ms, compared to 2 seconds. And overall CPU load on the hassio server is way down.

from remeha_home.

It looks like the integration is now stable.

from remeha_home.