Giters

Tidone / homeassistant_eta_integration

Integration of ETA (Heating) sensors and switches to home assistant

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unknown error occured

Tomson124 opened this issue · comments

commented

I was switch from another ETA integration to this, but unfortunatly cannot get to work like I imagined.

I am on ETA-Integration 1.1.2
HomeAssistant: 2024.2.5
The Api version is 1.2
<api xmlns="http://www.eta.co.at/rest/v1" version="1.2" uri="/user/api"/>

grafik

commented

Hi,
This error may be caused by a general error in Home Assistant.
Please check the HA logs in Settings -> System -> Logs -> Load Full Logs (Einstellungen -> System -> Logs -> Vollständige Protokolle Laden) There may be a critical error unrelated to this integration.

If you can't find any error there you can update the integration to the latest version (1.1.3) and retry setting it up. On the first dialog box you can then enable verbose logging.

If the error still persists you can then go to Settings -> System -> Logs and click on Download Full Log. Please upload the file here or on Pastebin.

commented

Thanks for the quick answer.
I could not really see a unrelated problem in the logs, and after more testing I found that forcing the "old API version" does work, so it would appear the problem is related to the new API stuff... I did install the latest version for the Integration and for the pellet heater software itsself, too.
I did attach the log like you asked.
home-assistant_2024-02-29T22-36-48.965Z.log

commented

Thanks for the log.
It looks like the integration just suddenly stops querying the ETA endpoints after almost exactly 90 seconds, without throwing any kind of error.
That looks suspiciously like some kind of timeout.

I will do some tests and see if I can find the problem.

commented

Hi,
Unfortunately I can't reproduce the issue here.
According to your logs the integration just stops doing anything after some time without throwing any kind of error.
This leads me to believe that there is some external component which terminates the integration.
Home Assistant itself does not have this kind of feature, so I think that one of your other integrations interferes with the eta one.

If you want to help me pinpoint the problem you can do the following:

  • enable debug logging for everything (either in your configuration.yaml, or via a service call to logger.set_default_level, see the docs), try adding this integration again, and post the log here
    • make sure to reset the logging level to warning again at the end to avoid filling up your storage space with huge logfiles
  • or disable your other integrations one by one and retry adding this integration until you find out which integration interferes with this one

If not, you can force the old API version, which you already confirmed to be working. The only difference between the two API versions is how the sensors are discovered. So if all necessary sensors are discovered, you can just stay in old API mode.

commented

Thanks for the help and testing it.
I did some testing myself, but could not really figure out what causes it, but since the old API isnt that much different according to you, I will just use that since that works fine.