Suggestion for changing "Messages".

[droiddk]

Hello

Suggestion:
Change the ”Messages” on the ”System” tab.

Had a break-down today, no connection between logger and Meteobridge and this was all “Messages” gave me:
logger (08.12.2016 12:17:37): 10.10.17.103's 2nd request on port 22222 declined.
logger (08.12.2016 12:17:38): 10.10.17.103's 2nd request on port 22222 declined.
And so on…

The same during normal operation, this is all I can see under messages:
logger (08.12.2016 16:42:49): connection on port 22222 closed.
logger (08.12.2016 16:42:49): 10.10.17.103's request on port 22222 accepted.
And so on...

Maybe another solution when Meteobridge is used as remote-bridge for weathersoftware?

Second, any news about Meteostick and evaporation, sent you (Boris) a email about this some time ago?

Regards

[droiddk]

Up.

[droiddk]

I was hoping this was fixed with the latest release:
"summarizes repeating entries from the logger process in the messages section of "System" tab."

But its not :/

Regards

[admin]

Identical lines generated from logger process following directly one by one should be suppressed now.
Can you please post an example where it is not working that way?

[droiddk]

Can you please post an example where it is not working that way?

logger (11.02.2017 15:37:04): connection on port 22222 closed.
logger (11.02.2017 15:37:04): 10.10.17.34's request on port 22222 accepted.
logger (11.02.2017 15:37:09): connection on port 22222 closed.
logger (11.02.2017 15:37:09): 10.10.17.34's request on port 22222 accepted.
logger (11.02.2017 15:37:15): connection on port 22222 closed.
logger (11.02.2017 15:37:15): 10.10.17.34's request on port 22222 accepted.
logger (11.02.2017 15:37:20): connection on port 22222 closed.
logger (11.02.2017 15:37:20): 10.10.17.34's request on port 22222 accepted.

Regards

[YJB]

I see more or less the same on meteohub with the logger process:

logger (18.12.2016 08:02:55): disconnect station 0 (RFXCOM): response without data
logger (18.12.2016 08:03:25): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:03:55): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:04:25): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:04:55): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:05:25): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:05:55): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:06:25): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:06:55): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device

[admin]

Can you please post an example where it is not working that way?

logger (11.02.2017 15:37:04): connection on port 22222 closed.
logger (11.02.2017 15:37:04): 10.10.17.34's request on port 22222 accepted.
logger (11.02.2017 15:37:09): connection on port 22222 closed.
logger (11.02.2017 15:37:09): 10.10.17.34's request on port 22222 accepted.
logger (11.02.2017 15:37:15): connection on port 22222 closed.
logger (11.02.2017 15:37:15): 10.10.17.34's request on port 22222 accepted.
logger (11.02.2017 15:37:20): connection on port 22222 closed.
logger (11.02.2017 15:37:20): 10.10.17.34's request on port 22222 accepted.
Regards

It does not filter out that, because it is not two identical lines following each other.
That is how it is designed.

[admin]

I see more or less the same on meteohub with the logger process:

logger (18.12.2016 08:02:55): disconnect station 0 (RFXCOM): response without data
logger (18.12.2016 08:03:25): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:03:55): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:04:25): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:04:55): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:05:25): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:05:55): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:06:25): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device
logger (18.12.2016 08:06:55): station 0 (RFXCOM), can't write baud rate toggle word "F025" to device /dev/ttyUSB0: No such device

So far I did not implement this for Meteohub. These kind of repeats will be suppressed in Meteobridge only.

[droiddk]

It does not filter out that, because it is not two identical lines following each other.
That is how it is designed.

But it should...I only sees that in my messages, warnings are left out. Maybe a option for disabling messages like that? Or another tab.