I am using the ui-tabulator node in FlowFuse. It works well except it sends unnecessary messages to the log file. Here is an example. Is there a way to turn these off?
1/13/2025 8:44:04 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:44:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:09 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:09 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:09 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:09 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:09 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:09 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:24 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:45:44 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:46:04 AM No connected clients - message to ui-tabulator ignored
1/13/2025 8:46:04 AM No connected clients - message to ui-tabulator ignored
This warning indicates that you send messages to the node when there are no open clients, i.e. no created table objects. This means, for example, that if you send a setData message it will be discarded and when the client is opened the table will come up without this data.
If these messages annoy you I can do the following (on the next release):
- Add a new msg command which checks if there are open clients
- Give an option to suppress this reply via the
tbDoNotReplyflag
HI @omrid , thank you for the quick reply. I'm not sure I completely understand your explanation but I will go back to my flow and see if I can rework it so this message doesn't occur.
I see why this was happening now. To fix it, I put in a switch node to check for an empty array before continuing which appears to have stopped the warning messages. Thanks again for the explanation!
I'm trying to understand what you did, to see if there is an issue in the ui-tabulator node.
It looks like every ~20 seconds, you send 6 messages to the table, and they get discarded since there is no open dashboard page (so no table object).
What are these messages? why block empty arrays with a switch node instead of not sending them in the first place?
Just after I sent that reply I realized I do need to send an empty array to clear the table or use the clearData command. So I am modifying it to send the clearData instead of an empty array.
Yes, but the issue is that you are sending the message when there is no open dashboard client, (hence no table object which will receive the message). Which means that if the message has data, this data would be lost
The data comes from a database query. We are only interested in data from the most recent query.
OK, understood.
I will update the node so that the log message will only be issued when the debug flag is set.
