Do you think this could be the reason for the problem with the frontend message box?
Pimatic from 0.9.51 updated to 0.9.53 with:
Thanks all for your great work!
@tobias-riesemann Excellent. Thanks for your feedback and for reporting!
Did you experience any anomalies when you restarted pimatic? I am just asking as some users on this thread experienced problems (CPU hogs). Which version of Node.js do you have installed, btw.?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Hi, i noticed no uncommon CPU issues whether during startup nore after pimatic is running on my Raspberry 1B.
CPU is about:
top - 09:19:21 up 32 days, 16:37, 1 user, load average: 0,19, 0,07, 0,07
Currently i’m using node v4.8.4
I also updated to 9.53. It seems (almost) everything to work. But I can also confirm the problem with the log display.
There is nothing displayed.
Sorry, for the late reply. As i now can see, the error log is empty.
I today updated from 0.9.48 to 0.9.53.
It worked very well, without producing any errors Thanks for that!
My config: Raspi 3B Node: v10.15.3
As I always do the updates from the frontend, I did at the same time the updates for:
pimatic-mobil-frontend (0.9.15 to 0.9.16)
pimatic-raspbee (0.0.10 to 0.1.5)
Wouldn’t it be a good idea to have there the possibility not to do all open updates at the same time?
I’m asking that in reference of maybe occuring errors while updating.
Doing the updates not all at the same time, might help to identify errors.
What do you think?
Thanks again for the super quality