Node-red-contrib-led does not show properly the dashboard

Dashboard
1

Hi eveyone,
I start this thread because I have a problem in my dashboard after installing the node-red-contrib-led.
My node-red is running in localhost in port 1881,using that using that "node-red -p 1881 -u c:/node-red-1881"
I just included two nodes:
image

However the dashboard only shows the led:
image
The version of Node-Red and Dashboard which is running in port 1881 is:
image

In another Node-Red running in port 1880 which was installed some time ago shows the dashboard is as follows:
image
The version of Node-Red and Dashboard which is running in port 1880 is:
image

The dashboard version are different, the 1881 has the 3.0.4 version and the 1880 has the 2.19.4 version.
If someone has or had the same problem than me, please share your proposal!!!

THANKS

2

Your last image does not show up.

Since you have two installs of NR, did you just update the dashboard in one of them?
You can use the palette manager to update the older one.

Are the button and led on the same tab? Providing your flow would manke it easier to determine.

3

Please post the output from the browser console that you posted on your earlier thread. It shows a websocket connection issue.

4

Yes, the button and led are on the same tab. The button is enable. If I remove the led node from the flow and Deploy it, the dashboard shows the message below:

image
image851×658 16.4 KB

It says there is nothing to show, however the button node is on flow and it is not shown in dashboard.

As Colin request, please see enclosed the output from the browser when I update the Node-red:

JQMIGRATE: Migrate is installed, version 3.3.0
DevTools failed to load source map: Could not load content for http://127.0.0.1:1884/vendor/purify.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
red.min.js:16 Node-RED: 1.2.6
red.min.js:16 Versions
red.min.js:16 Projects disabled
2DevTools failed to load source map: Could not load content for http://127.0.0.1:1884/gridstack.min.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

And this is the output when I reload the dashboard in browser:

DevTools failed to load source map: Could not load content for http://127.0.0.1:1884/ui/js/angular-chart.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
app.min.js:530 Rendered http://127.0.0.1:1884/ui/css/app.min.less successfully.
app.min.js:530 CSS for http://127.0.0.1:1884/ui/css/app.min.less generated in 501ms
app.min.js:530 Less has finished. CSS generated in 501ms
app.min.js:150 You are using the ngTouch module. 
AngularJS Material already has mobile click, tap, and swipe support... 
ngTouch is not supported with AngularJS Material!
(anonymous) @ app.min.js:150
e @ app.min.js:470
invoke @ app.min.js:66
(anonymous) @ app.min.js:68
r @ app.min.js:29
fb @ app.min.js:68
c @ app.min.js:43
Wc @ app.min.js:43
Ee @ app.min.js:42
(anonymous) @ app.min.js:372
e @ app.min.js:20
t @ app.min.js:20
setTimeout (async)
(anonymous) @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
fire @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
ready @ app.min.js:20
B @ app.min.js:20
app.min.js:135 GET http://127.0.0.1:1884/ui/loading.html 404 (Not Found)
(anonymous) @ app.min.js:135
s @ app.min.js:130
(anonymous) @ app.min.js:128
(anonymous) @ app.min.js:162
$digest @ app.min.js:174
$apply @ app.min.js:177
(anonymous) @ app.min.js:43
invoke @ app.min.js:66
c @ app.min.js:43
Wc @ app.min.js:43
Ee @ app.min.js:42
(anonymous) @ app.min.js:372
e @ app.min.js:20
t @ app.min.js:20
setTimeout (async)
(anonymous) @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
fire @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
ready @ app.min.js:20
B @ app.min.js:20
websocket.js:88 WebSocket connection to 'ws://127.0.0.1:1884/ui/socket.io/?EIO=4&transport=websocket&sid=diz6qELchQ0BFaHPAAAM' failed:

I have updated the dashboard to 3.0.4 version in my older Node-Red running in 1880, and it works Ok showing the button and led, so the version of dashboard is not the problem:
image

This is the output of dashboard which is running well in port 1880:

DevTools failed to load source map: Could not load content for http://127.0.0.1:1880/ui/js/angular-chart.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
app.min.js:530 Rendered http://127.0.0.1:1880/ui/css/app.min.less successfully.
app.min.js:530 CSS for http://127.0.0.1:1880/ui/css/app.min.less generated in 504ms
app.min.js:530 Less has finished. CSS generated in 505ms
app.min.js:150 You are using the ngTouch module. 
AngularJS Material already has mobile click, tap, and swipe support... 
ngTouch is not supported with AngularJS Material!
(anonymous) @ app.min.js:150
e @ app.min.js:470
invoke @ app.min.js:66
(anonymous) @ app.min.js:68
r @ app.min.js:29
fb @ app.min.js:68
c @ app.min.js:43
Wc @ app.min.js:43
Ee @ app.min.js:42
(anonymous) @ app.min.js:372
e @ app.min.js:20
t @ app.min.js:20
setTimeout (async)
(anonymous) @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
fire @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
ready @ app.min.js:20
B @ app.min.js:20
app.min.js:135 GET http://127.0.0.1:1880/ui/loading.html 404 (Not Found)
(anonymous) @ app.min.js:135
s @ app.min.js:130
(anonymous) @ app.min.js:128
(anonymous) @ app.min.js:162
$digest @ app.min.js:174
$apply @ app.min.js:177
(anonymous) @ app.min.js:43
invoke @ app.min.js:66
c @ app.min.js:43
Wc @ app.min.js:43
Ee @ app.min.js:42
(anonymous) @ app.min.js:372
e @ app.min.js:20
t @ app.min.js:20
setTimeout (async)
(anonymous) @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
fire @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
ready @ app.min.js:20
B @ app.min.js:20
app.min.js:530 Rendered http://127.0.0.1:1880/ui/css/app.min.less successfully.
app.min.js:530 CSS for http://127.0.0.1:1880/ui/css/app.min.less generated in 171ms
app.min.js:530 Less has finished. CSS generated in 172ms

Thanks for your help!

5

What version of node-red-contrib-ui-led do you have running on both NR’a?

6

Now I have the same version for both NR'a, the version 0.4.11
The output of browser of version working well is:

DevTools failed to load source map: Could not load content for http://127.0.0.1:1880/ui/js/angular-chart.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
app.min.js:530 Rendered http://127.0.0.1:1880/ui/css/app.min.less successfully.
app.min.js:530 CSS for http://127.0.0.1:1880/ui/css/app.min.less generated in 410ms
app.min.js:530 Less has finished. CSS generated in 411ms
app.min.js:150 You are using the ngTouch module. 
AngularJS Material already has mobile click, tap, and swipe support... 
ngTouch is not supported with AngularJS Material!
(anonymous) @ app.min.js:150
e @ app.min.js:470
invoke @ app.min.js:66
(anonymous) @ app.min.js:68
r @ app.min.js:29
fb @ app.min.js:68
c @ app.min.js:43
Wc @ app.min.js:43
Ee @ app.min.js:42
(anonymous) @ app.min.js:372
e @ app.min.js:20
t @ app.min.js:20
setTimeout (async)
(anonymous) @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
fire @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
ready @ app.min.js:20
B @ app.min.js:20
app.min.js:135 GET http://127.0.0.1:1880/ui/loading.html 404 (Not Found)
(anonymous) @ app.min.js:135
s @ app.min.js:130
(anonymous) @ app.min.js:128
(anonymous) @ app.min.js:162
$digest @ app.min.js:174
$apply @ app.min.js:177
(anonymous) @ app.min.js:43
invoke @ app.min.js:66
c @ app.min.js:43
Wc @ app.min.js:43
Ee @ app.min.js:42
(anonymous) @ app.min.js:372
e @ app.min.js:20
t @ app.min.js:20
setTimeout (async)
(anonymous) @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
fire @ app.min.js:20
c @ app.min.js:20
fireWith @ app.min.js:20
ready @ app.min.js:20
B @ app.min.js:20
app.min.js:530 Rendered http://127.0.0.1:1880/ui/css/app.min.less successfully.
app.min.js:530 CSS for http://127.0.0.1:1880/ui/css/app.min.less generated in 168ms
app.min.js:530 Less has finished. CSS generated in 168ms
7

Just to backup a bit…

  1. you are running both versions on the same windows_NT machine, correct?
  2. what steps did you take to install the two versions?
  3. can you provide the initial start up log for both occurrences up till it says:
    13 Oct 10:44:33 - [info] Starting flows
8

Hello,

  1. Yes, I am running both versions on the sam windows.

  2. I installed the first one executing the command below as global (I followed the steps described in nodered.org):

npm install -g --unsafe-perm node-red

It was installed automatically in port 1880. This is the Node-Red which works properly with node node-red-contrib-led.

To add the second instance in port 1881, I read some tutorials about how to install multiple instance of Node-Red in Windows 10. I created a new folder in C: directory under the name "c:\node-red-1881", after that I executed the command below:

node-red -p 1881 -u c:/node-red-1881

I am not sure if it is the proper way of installing more than one instance.
3. the log for Node red in port 1881 which is not working well:

C:\Users\usuario>node-red -p 1881 -u c:/node-red-1881
13 Oct 22:43:45 - [info]

Welcome to Node-RED
===================

13 Oct 22:43:45 - [info] Node-RED version: v1.2.6
13 Oct 22:43:45 - [info] Node.js  version: v14.15.1
13 Oct 22:43:45 - [info] Windows_NT 10.0.14393 x64 LE
13 Oct 22:43:48 - [info] Loading palette nodes
13 Oct 22:43:51 - [info] Dashboard version 3.0.4 started at /ui
13 Oct 22:43:51 - [info] Settings file  : c:\node-red-1881\settings.js
13 Oct 22:43:51 - [info] Context store  : 'default' [module=memory]
13 Oct 22:43:51 - [info] User directory : c:\node-red-1881
13 Oct 22:43:51 - [warn] Projects disabled : editorTheme.projects.enabled=false
13 Oct 22:43:51 - [info] Flows file     : c:\node-red-1881\flows_PQCETEYMA2.json
13 Oct 22:43:51 - [info] Server now running at http://127.0.0.1:1881/
13 Oct 22:43:51 - [warn]

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

13 Oct 22:43:51 - [info] Starting flows
13 Oct 22:43:51 - [info] Dashboard version 3.0.4 started at /ui
13 Oct 22:43:51 - [info] Started flows

And the log for version running in port 1880 working well:

C:\Users\usuario>node-red
13 Oct 22:46:17 - [info]

Welcome to Node-RED
===================

13 Oct 22:46:17 - [info] Node-RED version: v1.2.6
13 Oct 22:46:17 - [info] Node.js  version: v14.15.1
13 Oct 22:46:17 - [info] Windows_NT 10.0.14393 x64 LE
13 Oct 22:46:20 - [info] Loading palette nodes
13 Oct 22:46:24 - [info] Dashboard version 3.0.4 started at /ui
13 Oct 22:46:25 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
13 Oct 22:46:25 - [info] Settings file  : C:\Users\usuario\.node-red\settings.js
13 Oct 22:46:25 - [info] Context store  : 'default' [module=memory]
13 Oct 22:46:25 - [info] User directory : \Users\usuario\.node-red
13 Oct 22:46:25 - [warn] Projects disabled : editorTheme.projects.enabled=false
13 Oct 22:46:25 - [info] Flows file     : \Users\usuario\.node-red\flows_PQCETEYMA2.json
13 Oct 22:46:26 - [info] Server now running at http://127.0.0.1:1880/
13 Oct 22:46:26 - [warn]

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

13 Oct 22:46:26 - [info] Starting flows
13 Oct 22:46:26 - [info] Started flows

Thanks!!!

9

Here my conclusion and solution, although I do not know the reason.

I have created a new instance in port 1882, however in this case I created the new folder directly inside users folder as follows: C:\Users\usuario\node-red-1882 instead of C:\node-red-1881

After that change I solved my problem. But I do not know why, sure someone can explain the main reason.

Thanks Colin and zenofmud!!

10

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