Node Red Dashboard layout

I'm sure I'm missing something but can anyone advise.. Dashboasrd, I have a lot of dropdown boxes to put on a page and the order in which they position on the page seems to depend on when they were last updated.. I know how to adjust their width and height but not what order they appear in the page. I assume this applies to all the other dashboard elements. What am I missing?

The order is determined by the order they appear in the dashboard sidebar view. They should be fixed in order - but there have been a couple reports where that sometimes doesn't stick, but not sure the root cause of that.

If you drag them around in the tree view to reorder and then drag them back to the order you want they ought to sort themselves out and fix in place.


I tried to track that down a long time ago -- iirc, there are some ways (maybe copy/paste? or import an old flow?) that new ui nodes get created with their order property == 0. Dragging them around does indeed set that property correctly, but you cannot really know if you've reset all nodes properly.

I think a quick fix would be to check that the order property of all ui nodes matches their position in the dashboard sidebar -- at least when it is first drawn. Of course, if any nodes were found with order == 0, they would be updated, and the flow would have to be re-deployed...

Hi Nick - I found the sidebhar and treeview and dragging one of the controls around as you suggest appears to have done the trick for now, thanks for you help. Lastly I have loads of these - umpteen settings per day and same again at the weekend. What is now the right way to make these non-volatille?

What settings do you mean? If you are referring to the ordering, then you shouldn't have to do anything. It should honour the order you add the widgets in the first place, and honour any reordering you do via the sidebar. But like I said, there have been reports - including yours - of the ordering not sticking if you don't do any interaction with the sidebar.

And of course, you still need to click the Deploy button to save any changes you make.

Oh, nho, I meant values. I am making a thermostat and so I have several dropdown select boxes (I can just copy them) and each has 96 time/temperature settings, ie every 15 minutes. When we set the time zones to particular times and temperatures I need those values to stay put even after a power cycle.

Thanks for the help, Nick, after all that I'd completely forgotten I designed a complete stat back in January 2017 - thank goodness for the blog. Works in the current NR and dashboard no problems.

1 Like

Peter - there is now persistent storage in the global context - this can be setup to write to a file (with a named context so only some options have to go to a file (if you are worried about SD card wear) and others can still go to memory