Latest Dashboard 2.0 Release - v1.23.0

Dashboard
1

v1.23.0 has been released.

The update features a number of updates from both FlowFuse and external contributors (many thanks @BartButenaers @cgjgh)

You can see the changelog here: Release v1.23.0 · FlowFuse/node-red-dashboard · GitHub

It should be available in the Node-RED palette within the next 30 mins :slight_smile:

7 Likes
2

Simply wish to say thank you to everyone who contributes to this work in any way.

You are all good people. In case you wondered.

3

[details="Hiding because post was incorrect"]
I think I broke my flow by updating .

[{"id":"6dc976ae24d7954c","type":"inject","z":"7c54d6845755357a","g":"6d8b208b1b6b2294","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":760,"y":160,"wires":[["fee6dbba5fa443fd"]]},{"id":"fee6dbba5fa443fd","type":"function","z":"7c54d6845755357a","g":"6d8b208b1b6b2294","name":"Show Alert","func":"msg.payload = {\n    groups: {\n        show: ['PAGE1:INFORMATION'],\n     }\n}\nreturn msg;\n","outputs":1,"timeout":0,"noerr":0,"initialize":"","finalize":"","libs":[],"x":950,"y":200,"wires":[["de718b82f35f0369","6cdae832241ac5e0"]]},{"id":"dc5b408ce9f08930","type":"function","z":"7c54d6845755357a","g":"6d8b208b1b6b2294","name":"Hide Alert","func":"msg.payload = {\n    groups: {\n        hide: ['PAGE1:INFORMATION'],\n     }\n}\nreturn msg;","outputs":1,"timeout":0,"noerr":0,"initialize":"","finalize":"","libs":[],"x":960,"y":240,"wires":[["de718b82f35f0369"]]},{"id":"de718b82f35f0369","type":"ui-control","z":"7c54d6845755357a","g":"6d8b208b1b6b2294","name":"","ui":"0aa5ac292a3ec726","events":"all","x":1140,"y":240,"wires":[["6e3d323e4a1332df","e081b3d77c38857c"]]},{"id":"0aa5ac292a3ec726","type":"ui-base","name":"My Dashboard","path":"/dashboard","appIcon":"","includeClientData":false,"acceptsClientConfig":["ui-notification","ui-control","ui-form","ui-text-input","ui-number-input","ui-file-input","ui-button","ui-button-group","ui-radio-group","ui-slider","ui-switch","ui-text","ui-table","ui-chart","ui-gauge","ui-markdown","ui-template","ui-tabulator"],"showPathInSidebar":true,"navigationStyle":"temporary","titleBarStyle":"fixed","showReconnectNotification":true,"notificationDisplayTime":"1","showDisconnectNotification":true}]

I had this in the SHOW / HIDE function, now it is not working

msg.payload = {
    groups: {
        show: ['PAGE1:INFORMATION'],
     }
}
return msg;

msg.payload = {
    groups: {
        hide: ['PAGE1:INFORMATION'],
     }
}
return msg;
4

Ah, I tested every single feature before release (due to there being a lot of component updates) but this might be one I missed. I cannot remember if we have e2e tests for dialogs either to avoid regressions in this area (something we will need to add if it turns out we broke dialogs).

Could you try using the ID of the group instead of PAGE:GROUP and let me know if that solves your issue in the short term?

Also, are your page and group names really UPPERCASE? I am wondering if we have made the matching more strict.

5
Hiding because post was incorrect 
{
    "groups": {
        "show": [
            "INFORMATION"
        ]
    }
}

this rectified it.

from original

msg.payload = {
    groups: {
        show: ['PAGE1:INFORMATION'],
     }
}
return msg;
6

yes they are uppercase.

7

I don't understand.

after correcting the flow, and reverting back to old syntax to see if problem recurs, it doesn't

now my old flow also is working OK.

puzzled.

EDIT

I uninstalled the 1.23.0 and installed 1.22.1 and then tested. working ok
again installed 1.23.0 and it DID NOT WORK for first time, but i used the node-id to Show/Hide once and again the older started working.
am not understanding the issue

8

That feels like a browser caching issue. Did you try a ctrl-f5 to force a cache refresh?

I have raised an issue before about Node-RED not following W3C guidelines on the use of case sensitive URL's.

The change was rejected as being potentially breaking to old installations which is OK I guess. However, in my view, it should be a setting with new installations defaulting to case sensitive but existing installations not.

For UIBUILDER users, choosing a custom web server for UIBUILDER (a simple setting of a new port number in settings.js) gets you W3C compliant case sensitive URL's.

9

Just upgraded and the number input node seems to be malfunctioning. Goes a bit weird (significant figure seems to disappear in the dashboard) when using 0.1 as the step value in the range parameters.

This is a bit of a deal breaker for me. Any way to drop back to previous version?

Cheers

10

Could you please raise an issue with steps to reproduce your issue.

To install an older version you can run npm i @flowfuse/node-red-dashboard@1.22.1 in your node-red user directory (typically ~/.node-red)

11

Thanks for that Steve. Downgrading wasn't quite that simple as there was an audit problem and I held my breath whilst doing and npm audit fix --force. Downgrading to the previous version seems to have rectified the number input node issue I was having. I will raise the issue.

Thanks

12

Unfortunately that is a bad idea. You might have broken something by forcing later versions of dependencies. The audit warnings would only have been warnings, you could have ignored then.

13

Are you talking about the Slider node? I am not seeing any problem with that, can you export the failing node and paste it here please?
[Edit] and post a screenshot showing what problem you are seeing.

14

Oh well we live and learn. I think I got lucky as everything seems to be functioning correctly (so far anyway). I have a spare SSD with an up to date backup for just such occasions as I have been caught out like this before.

15

It was the dashboard 2 number input node. Can't really provide any screen shots as I have gone back to an earlier version of the dashboard 2, sorry.

16

Link to github issue.

No need, since you did not use -g it will only have affected the local install of the nodes. If you go to your .node-red folder and remove the node_modules folder and the file package-lock.json, then run
npm install
it will re-install them as they should be.