Dasboard-ui chart x-axis shows only last few samples

Dashboard
1

I have basic line chart connected directly to mqtt topic. The chart is configured to show last 3 minutes or 900 points (the topic gets 5 messages per second).

Sometimes the chart works as expected, sometimes it shows only last 5-10 samples and I can't figure out the pattern. Clearing local browser storage does not help.

2

Hi @gdanov

What version of Node-red and Dashboard do you have?
It's probably a good idea for you to show us a snapshot of your screen, a sample of the data and an export of the flow.

3

here are the versions

Mar 23 13:56:35 pizerow Node-RED[5197]: 23 Mar 13:56:35 - [info] Node-RED version: v2.2.2
Mar 23 13:56:35 pizerow Node-RED[5197]: 23 Mar 13:56:35 - [info] Node.js version: v12.22.5
Mar 23 13:56:35 pizerow Node-RED[5197]: 23 Mar 13:56:35 - [info] Linux 5.10.92-v8+ arm64 LE
Mar 23 13:56:38 pizerow Node-RED[5197]: 23 Mar 13:56:38 - [info] Loading palette nodes
Mar 23 13:56:44 pizerow Node-RED[5197]: 23 Mar 13:56:44 - [info] Dashboard version 3.1.6 started at /ui

The UI looks like this, note the second chart x axis

[Album] imgur.com

data is stream of numbers, don't thin it has anything to do with the problem.

4

Hmm. Well it certainly only shows 10 discrete values over 2 minutes, which should be 600 data points.
Were there 600 data points in that period?

I wonder if it would make a difference if you experimentally add a small random number to each value, maybe between 0 and 0.1 just to make the data a bit more spikey.

5

I'm looking at the dashboard from several devices simultaneously. some work some not. This is ipad for example. I'd really appreciate if people who have no idea what could be the problem skip questioning basic things.

BTW the image preview shows a working chart. You need to click on the image to see the broken one at the bottom. Values are all zero, yes, but come in at 5Hz, guaranteed, checked and verified.

6

I'd really appreciate if people who have no idea what could be the problem skip questioning basic things

I'm really sorry for trying to help you. I shan't do it again.

7

You won't get very far if you respond to one of the key helpers on this forum in that manner.

It would have helped if you had told us that in the first place as it immediately says it is not a fundamental problem with the flows.

That suggests that it changes over time, rather than across devices or browsers. Which is it? To paraphrase your comment, I'd really appreciate if people who are asking questions would make sure they provide all the basic facts in a non-ambiguous way.

What do you see in the browser developer console when it is failing?

8

I expected people that have understanding how the chart works to give pointers where to look for the problem. Instead I get people stabbing in the dark and moralizing me. I could just as well read the code and not waste time here.

9

It is difficult to point to where the problem might be if you won't clarify exactly what the symptom is and don't respond to requests for further information.
Once you have worked out what the cause is please do feed back what you find so it can be improved.

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.