Luxtronik - Possible to delete/empty logs to avoid "reboot"?

[noxx4life]

Hi everyone, I´m using this integration with Home Assistant to manage my heat pump and I´ve notice the behavior that when often change parameters or requesting status of any heat pump senor, the log file is growing fast. In a heat pump forum also other have experienced this and as result the heat pump is doing a restart if the log file is closed to reach its maximum file size, which is around 500kb. With a restart of the Luxtronik controller the heat pump avoid that it gets a out of memory exception and it also clears the log file with it.
The problem now is the restart itself, because not only the controller restarts, the whole heat pump does same, which in Winter can be an issue as during this time and until the heating starts again it can take some time. Also it is inefficient, looking at power consumption. You can see the reboot message in Error log as "Reboot detected Unexpected (Controller)".

Using the KD access you also see that Luxtronik controller logs so much stuff, which then results in a fast growing log file that results in a reboot. A normal user of a heat pump that does not use the websocket or this integration would never recognize it as with less requests the log will not grow much.

So I was asking myself if there is a possibility that logs can be cleared by any api of the heat pump before reaching the critical size? Is it possible to access this kind of level of the heat pump with the available options?

Happy to get feedback and start this discussion.

Best,
Chris

[AJediIAm]

So I was asking myself if there is a possibility that logs can be cleared by any api of the heat pump before reaching the critical size? Is it possible to access this kind of level of the heat pump with the available options?

Luxtronik manages the logs internally. There is no way to clear the logs.

Some people advise to limit the number of write actions to the heatpump since this can reduce the lifespan of the internal storage. I have no facts to back this up. Given the log behavior, it seems a good practice to follow.

In my case, the thermal mass of the floor heating fully absorbs frequent changes or a reboot. I limit adjustments based in energy price to hourly (and because I haven't figured out how to use the power limit functionality yet to consume surplus solar power).
Every house is different, but it might be worth it to try a more conservative approach to controlling your heatpump.

Feel free to share your use case so others can pitch in with alternatives.