Remote end closed connection without response

[Kanecaine]

I regularly see the following error in the logs:

Logger: custom_components.hafas.sensor
Quelle: custom_components/hafas/sensor.py:122
Integration: HaFAS
Erstmals aufgetreten: 06:26:56 (10 Vorkommnisse)
Zuletzt protokolliert: 10:47:57
Couldn't fetch journeys for sensor.xxx_to_yyy: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

Otherwise, the integration works without any problems and the journey times are retrieved correctly.

[akloeckner]

I also see this occasionally and I would think, it's just the usual inevitable network drop-outs. In the end, we're doing lots of regular network request. Some of those are just bound to fail. Maybe decreasing the log level would be appropriate. At least for N happenings per some time interval.

Can you say roughly, how often it happens? From your log, I'd guess 10 times per 4 hours. So, every 20-30 minutes maybe.

I seem to have 26 warnings like that in 3 days, so one every three hours.

[Kanecaine]

Hm, hard to say. Two days ago it was actually 10 times in 4 hours. Since yesterday, however, I haven't had a single one of these entries. So it doesn't seem to be a regular occurrence.

[akloeckner]

Is this for the DB profile? Then, I fear, it will be permanent... See #21.

[Kanecaine]

Hi, yes it is the DB profile. It is a great pity to hear that it is a major problem that cannot be solved at the moment. But of course I understand that most contributors do this in their spare time and that such a fundamental change can be too big. Thanks anyway.