Henning von Bargen

Hmm... The timestamps of the messages coincide with this documentation: auto_purge boolean (optional, default: true) Automatically purge the database every night at 04:12 local time. So I think this is...

Both conditions are fulfilled here. Just a wild guess: I guess the reason is that one thread tries to write sensor data while another thread tries to purge the DB.

The component just provides sensor data and doesn't access the recorder DB directly. Besides, other users which do not use this component, described the same error in #64890.

This may be silly, but could this be caused by some kind of faulty caching? Maybe it's necessary to add http headers to avoid caching? I'm asking this because years...

Is this a possible duplicate of #135?

I am running this, too. I see several changes per day, which roughly seem to correspond with the heating phases for zone 1. 

@enthus1ast Did you manage to solve the umlaut problem in your fork? I'm new to nim, but I like it. My very first project should be a simple directory chooser...