Domoticz

Since the updates there have been changes to the logging.
The LOG_DEBUG information is not longer visible in the tab 'Status', but can be seen in the tab 'All'.
So far no problem, except that so much information is scrolling by.
When I use a string to filter, the filter does its work, but it looks like the invisible lines still are causing the visible lines to scroll very fast from the window. Sometimes so fast that I do not even have the time to select and copy the lines for review.
Is this a known issue?

Yes, this is as designed. The web log function has limited memory to save resources on smaller servers.
If you want to see more you have to log to a log file.

OK. Thank you.
I have to look for a workaround for that, when I do not want to have a separate Putty session to see the log next to working with the internal editor in browser, for which I do hot have to login to Ubuntu.
Still it is a bit strange to see that the text is pushed up by 'nothing'.
It would have been nice when everything goes to the log but only to the screen that what correponds with the filter in stead of 'hiding' it.

In the previous situation, the functionality may have been the same, but I did not notice that, because I always looked at tab 'Status', where all that device data does not appear. So for me this part is a step back.

It would have been nice when there was also a tab' 'Debug', because this LOG+_DEBUG information does not show up at 'Status' or 'Error'.
And because of the current design, it is also not visible in 'All', because it scrolls away sooner than I can read it in this 'live view'.
Is that perhaps an idea?

Meanwhile I am thinking of a 'ShowDebug' function that is called when 'level == dz.LOG_DEBUG', gets a 'tail' from the logfile, uses the 'marker' to 'grep' the debug information I want and then put it in a custom page for review. Or something like that.
This prevents additional login with putty, after which I still have to do it manually. But it does not sound entirely ideal either.

Edit:
First I started to turn off log level INFO at Setup - Hardware for MQTT, P1 meter etc. and see if that will give more acceptable result. It will limit the numer of lines passing by.

janpep wrote: ↑Sunday 21 July 2024 9:25 First I started to turn off log level INFO at Setup - Hardware for MQTT, P1 meter etc. and see if that will give more acceptable result. It will limit the numer of lines passing by.

Ahhh, I should have done this earlier . This gives more rest, and is much better workable.
I do not think I'm missing much meaningful information in the log now. Otherwise I can temporarily enable this INFO logging for hardware again.
Problem solved.