log what comes with if you do node-red start
so it is given I will have to stop it first.
Hand on.
Ok this is what I get:
Note: MQTT machine is not visible so those errors are not anything to worry about.
me@me-desktop:~/.node-red$ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.0.6:1880
On Pi Node-RED works better with the Firefox or Chrome browser
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
To find more nodes and example flows - go to http://flows.nodered.org
Starting as a systemd service.
28 Mar 21:34:45 - [info]
Welcome to Node-RED
===================
28 Mar 21:34:45 - [info] Node-RED version: v0.19.4
28 Mar 21:34:45 - [info] Node.js version: v8.15.1
28 Mar 21:34:45 - [info] Linux 4.15.0-46-generic x64 LE
28 Mar 21:34:45 - [info] Loading palette nodes
28 Mar 21:34:45 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
28 Mar 21:34:45 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library
node-red-contrib-jktestEditableList - initialising module. Module Version: 0.1.1
node-red-contrib-jktestEditableList - loading module
28 Mar 21:34:46 - [info] Dashboard version 2.14.0 started at /ui
28 Mar 21:34:46 - [info] Settings file : /home/me/.node-red/settings.js
28 Mar 21:34:46 - [info] HTTP Static : /home/me/.node-red/public
28 Mar 21:34:46 - [info] Context store : 'default' [module=memory]
28 Mar 21:34:46 - [info] User directory : /home/me/.node-red
28 Mar 21:34:46 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
28 Mar 21:34:46 - [info] Flows file : /home/me/.node-red/flows_me-desktop.json
28 Mar 21:34:46 - [info] Server now running at http://127.0.0.1:1880/
28 Mar 21:34:46 - [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.
---------------------------------------------------------------------
28 Mar 21:34:46 - [info] Starting flows
28 Mar 21:34:46 - [info] [tcp in:MySensors Gateway] connecting to 192.168.1.20:5003
info: UIbuilder: Adding master vendor path url=/uibuilder/vendor/normalize.css, path=/home/me/.node-red/node_modules/normalize.css
info: UIbuilder: Adding master vendor path url=/uibuilder/vendor/jquery, path=/home/me/.node-red/node_modules/jquery
info: UI Builder - Version 1.0.8 started at /uibuilder
info: UI Builder - Local file overrides at /home/me/.node-red/uibuilder/uibuilder
28 Mar 21:34:46 - [info] UI Builder - Version 1.0.8 started at /uibuilder
28 Mar 21:34:46 - [info] UI Builder - Local file overrides at /home/me/.node-red/uibuilder/uibuilder
TypeError: Cannot read property 'global' of undefined
at site (/home/me/.node-red/node_modules/node-red-contrib-ui-level/ui-level.js:186:31)
at new LevelNode (/home/me/.node-red/node_modules/node-red-contrib-ui-level/ui-level.js:266:23)
at createNode (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/Flow.js:305:18)
at Flow.start (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/Flow.js:89:35)
at start (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/index.js:328:29)
at tryCatchReject (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:845:30)
at runContinuation1 (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:804:4)
at Fulfilled.when (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:592:4)
at Pending.run (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:483:13)
at Scheduler._drain (/usr/lib/node_modules/node-red/node_modules/when/lib/Scheduler.js:62:19)
28 Mar 21:34:46 - [info] Started flows
28 Mar 21:34:46 - [error] [function:build array (1)] TypeError: Cannot read property 'shift' of undefined
OK. this is something I need to investigate.
Ok.
Thanks.
I hope it isn't something at my end.
Just for a "last ditch effort", could you post a quick example of the least required flow to get it working?
One inject node with a value and the new node to display it?
(That is if my flow is not good enough.)
Place node into some group, default configuration should already work, give it a number with msg.payload and that's it. No tricks what so ever.
Ok.
Good. Just in case I am/was shooting myself in the foot.
I am sure you can agree I am quite good at doing that.
:wink
You could try to uninstall the ui-level node and reinstall. May and may not help.
I don have any not windows machine, cant test out really what's wrong, thus everything works on windows machine.
I've tried un-installing it and then putting it back.
But no reboot after/inbetween.
No change.
But I've tried FF, Chrome and Opera. All same result.
All local on this machine.
No big worry. I am just going through looking for new nodes that may be nice to use.
No immediate use/need for it to work.
Thanks.
What I may try is to un-install it and then install it from the CLI.
This is what I get:
me@me-desktop:~/.node-red$ npm install node-red-contrib-ui-level
npm WARN node-red-project@0.0.1 No repository field.
npm WARN node-red-project@0.0.1 No license field.
+ node-red-contrib-ui-level@0.0.6
added 1 package from 1 contributor and audited 1047 packages in 2.644s
found 13 vulnerabilities (5 low, 6 moderate, 1 high, 1 critical)
run `npm audit fix` to fix them, or `npm audit` for details
me@me-desktop:~/.node-red$
Alas still no luck.
I apply it to the flow with a simple inject node and it is still not working - as it were.
I published patch what might get it working for you, but it still not the correct solution.
Version 0.0.7
