In parallel I have deleted the current log file with the result that no new file has been created. No logging at all.
After a reboot the system started to build and fill the log file. Again, nothing related to the issue we've been discussing here.
This is how Unix works. When you delete a file opened by some program (Z-Way in your case), it is not deleted, but removed from the folder to become orphaned until all handles are closed. The Unix way to solve it is to send USR1 signal to the program. This will instruct the program to re-open log file. Good Unix programs follow this recommendations. Z-Way is doing it too. And logrotate is relying on this.
So, this is by design, but maybe a bit counterintuitive.
I am sad to hear that. My system is still running.
Have you been running Z-Way in debugging environment?
Fingers crossed that Poltos can find the root cause.
I did not have it under gdb. I think part of the issue is that it is too much for a Raspberry Pi 4B. Believe it or not, the system felt quicker with a five second polling than one second. I think I'm going to extend the time to say 2 seconds and see how it feels. Even just loading all of the rooms on the main node takes several seconds albeit the CPU usage doesn't show that.
As I remember (please correct me) OH is polling Z-Way and not vice versa. So this might be some other issue. Or Z-Way is configured to poll some HTTP devices. Please check your configuration.
The fix bug we discuss here is related to Z-Way doing HTTP request to other services.
I've had the issue. With all that particular instance is doing is a go between between the Z-Way nodes with Z-Wave devices and Home Assistant, I believe the issue has to be with the remote z-way app. Hopefully the updated version that uses WebSockets resolves the issue. It is much better than it was before though. So the changes made really helped.