Dashboard 2 gauge linear mode dynmic properties

Dashboard
1

Using gauge linear nodewith ticks. Updating ticks via dynamic properties updates the number values, but the bar does not update the new tick values (1000->200, tick changes, but color bar does not change).

Node setting:

image
image801Ă—1096 15.8 KB

Result after dynamic update:
image

2

Known. Not a bug just not described how to do it properly. See here Using dynamic properties issue · Issue #9 · hotNipi/node-red-dashboard-2-ui-gauge-linear · GitHub

3

One downside is, that it is not possible to set the tick values and colors e.g once per day or so. If the page is reloaded, the static values are present until the values are set dynamically again. So the latest values set dynamically are not persistent.
Basically it would require to set the ticks, colors etc dynamically alongside with the payload value.

4

Whatever way it is, the thing you actually wanted is that it is actually in configuration what is proper at current moment. That moment is under your control and the dashboard gives to you all the tools to fire out the config when you need.

None of solutions can be perfect in that sense.

5

I wanted to point it out in case somebody else tries it out.
In the current status, whenever the page is loaded the ticks and color bars would need to be set again dynamically. In contrast, the actual value is stored. Let's say the value is written once per day, even after reload it would be visible. Only after a full deployment in node red it would be gone which is obvious.
So the current usecase for dynamic ticks and colors is rather limited. I just didn't expect it to behave like that..

6

You may try v0.1.6

7

I just updated to 0.1.6
I now get these crumbled ticks and NaN values, the bars seem to be fine:

image

On all bars the ticks are aligne to the left most position, except for the max tick, which is aligned to the far right.

The issue only seems to be with the dynamically set bars. The bars that are not using dynamic settings are still fine.

JFYI: I did not change anything to my workflow. Also after sending dynamic values again, nothing changes.

Thanks for looking into this. I wasn't expecting any change.

Edit:
I deployed my workflow again and even then the ticks are messed up, even without dynamically setting anything. But only to the gauges that previously used dynamic properties. I'm still trying to find out why or what the difference is here. Somewhat strange so far.

8

Thanks. Will look over. Something I did miss for sure

9

I just created a new gauge and connected that. Seems to work.
The gauges I used previously do not work.

Seems to be connected with the update somehow.

Edit:

I just only deployed again and the ticks are aligned to the left side again.
So it works with a new gauge after first deployment. But after second deployment of the workflow it gets mixed up.

Are you able to reproduce it? Otherwise I may set up a sample workflow.

10

I'm away but I'll look asap.

1 Like
11

No. It works for me as expected

12

I created a sample flow, can you check it?

13

Something is wrong, can't import the flow

image
image829Ă—554 24.6 KB

14

Exported again

15

Ok. problem exits. Reveals when updating min or max or both.
I think fixing it will introduce breaking change...

16

Would it help if I remove min/max from the dynamic setting for now?
I just added it to have everything in one place, but min and max do not change in my case currently.

17

It works if you dont change the min and max

18

Ok, right seems to work if min/max have never changed before. I'll try to restart node-red if that does not help for now I will exchange the nodes.
Thanks for the support.

1 Like
19

v0.1.7 available

1 Like
20

Working here. Thanks for the great update!

1 Like