I have cleared the browser cache, restarted chrome: same as before.
I tryed Edge, same result.
I don't rememeber how I installed node-red. Followed some suggestion on internet.
Here is the start and stop of node-red:
pi@webradio:~ $ node-red-stop
Stop Node-RED
Use node-red-start to start Node-RED again
pi@webradio:~ $ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.153.97: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.
Started Node-RED graphical event wiring tool.
16 Apr 19:15:06 - [info]
Welcome to Node-RED
===================
16 Apr 19:15:06 - [info] Node-RED version: v1.3.2
16 Apr 19:15:06 - [info] Node.js version: v14.16.1
16 Apr 19:15:06 - [info] Linux 4.19.66-v7+ arm LE
16 Apr 19:15:08 - [info] Loading palette nodes
16 Apr 19:15:10 - [info] Dashboard version 2.28.2 started at /ui
16 Apr 19:15:11 - [info] Settings file : /home/pi/.node-red/settings.js
16 Apr 19:15:11 - [info] Context store : 'default' [module=memory]
16 Apr 19:15:11 - [info] User directory : /home/pi/.node-red
16 Apr 19:15:11 - [warn] Projects disabled : editorTheme.projects.enabled=false
16 Apr 19:15:11 - [info] Flows file : /home/pi/.node-red/flows_webradio.json
16 Apr 19:15:11 - [info] Server now running at http://127.0.0.1:1880/
16 Apr 19:15:11 - [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.
---------------------------------------------------------------------
16 Apr 19:15:11 - [info] Starting flows
16 Apr 19:15:11 - [info] Started flows
16 Apr 19:15:11 - [info] serial port /dev/ttyS0 opened at 9600 baud 8N1
16 Apr 19:15:12 - [info] [mpd-server:82f7baca.793ed8] Connected to MPD server localhost:6600
16 Apr 19:15:12 - [info] [mqtt-broker:a7459cab.67a5] Connected to broker: GPort@mqtt://localhost:1883
^C
pi@webradio:~ $
Is this not possible? ? Should I go back to backup and the old node-red ??
var k = msg.payload
if (k===0) msg = {color:"#FFFF00",bgcolor:"black",icon:"fa-4x fa-spinner fa-pulse"};
if (k===1) msg = {color:"#00FF00",bgcolor:"black",icon:"fa-4x fa-download"};
if (k===2) msg = {color:"#FF0000",bgcolor:"black",icon:"fa-4x fa-upload"};
if (k===3) msg = {color:"#FF0000",bgcolor:"black",icon:"fa-4x fa-exclamation-triangle"};
/* 0=moving
1=closed
2=opened
3=error */
msg.payload = k;
return msg;
No need to change anything else but the contents of the function node.
It is not about like I know whats wrong but I have such methods running flawlessly years now so worth of try.
Maybe the ui_control only in message behaves not so nice for possible socket losses and re-connections.
The log looks as it should, no clues as to why the dashboard tab is missing. Can you check in the developer console in your browser to see if it shows any errors?
I will try check in the developer console in the browser! hotNipi your solution seems to work!! But I leave it till tomorrow and try then. Just to be 100%.
Now I have increased hope!!
Thank you for taking your time! ! !
hotNipi Sorry! Not better!
I have taken this out of developer consol in browser:
WARN:
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!
FAIL:
:1880/ui/loading.html:1
Failed to load resource: the server responded with a status of 404 (Not Found)
FAIL:
app.min.js:150
SideNav 'left' is not available! Did you use md-component-id='left'?
(anonymous) @ app.min.js:150
FAIL:
:1880/ui/socket.io/?EIO=3&transport=polling&t=NZUnBot:1
Failed to load resource: net::ERR_NETWORK_CHANGED
I think that suggests there is something odd about the network connection between the PC and the Pi. How are they connected? Are they on the same local network?
In a terminal on the Pi what does this command show? ip addr
Now I got "dashbord" in the dropdown menu ! ? ! ?
I chosed "dashboard", "site", "option" sade "click to show side menu". I chosed "Alwayes show side menu". Deploy. and chosed "click to show side menu". And I am back!!
I took another Pi and copy the simulator-flow to the "new" Pi. Where it works !! ! (Node-red v1.2.7). This hade the "dashboard" in the dropdown menu. When I go back to the first Pi, there it was, in the dropdown menu.
Ghosts ? ! ? I don't believe in ghosts! Or?
Edit: The "new" Pi is running "Buster"
