Inject nodes or anything using a set time schedule no longer works on my node red. Ive checked the system date, left the nodes running over a few days with no debug outputs.
Ive tried to install a few addons using crons and schedules, but these don't work either.
I'm not sure whats going on or how to debug this further. Any help on how I can fix this?
Have you tried restarting node-red?
Is it just scheduler nodes that are not showing debug output or are you seeing no debug output at all, even if you feed an inject into a debug node?
In a command window stop node red then start it again and copy/paste the full startup sequence here please. Copy/paste not screenshot.
After updating its working again. Now the times are out, but I can fix that 
okay so its now not working again. Ive tried restarting node red, checked the time zone is correct. Im running in docker, so not sure if thats related or not... But i has been working fine up until recently... Here is the log bellow:
28 Feb 02:46:15 - [info]
Welcome to Node-RED
===================
28 Feb 02:46:15 - [info] Node-RED version: v3.1.5
28 Feb 02:46:15 - [info] Node.js version: v16.20.2
28 Feb 02:46:15 - [info] Linux 6.1.21-v8+ arm64 LE
28 Feb 02:46:17 - [info] Loading palette nodes
28 Feb 02:46:21 - [info] Dashboard version 3.4.0 started at /ui
28 Feb 02:46:22 - [info] Settings file : /data/settings.js
28 Feb 02:46:22 - [info] Context store : 'default' [module=memory]
28 Feb 02:46:22 - [info] User directory : /data
28 Feb 02:46:22 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Feb 02:46:22 - [info] Flows file : /data/flows.json
28 Feb 02:46:22 - [info] Server now running at http://127.0.0.1:1880/
28 Feb 02:46:22 - [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 Feb 02:46:22 - [info] Starting flows
28 Feb 02:46:23 - [info] Started flows
28 Feb 02:46:23 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://localhost:1883
28 Feb 02:46:38 - [info] Stopping flows
28 Feb 02:46:38 - [info] [mqtt-broker:mqtt] Disconnected from broker: mqtt://localhost:1883
28 Feb 02:46:38 - [info] Stopped flows
28 Feb 02:46:38 - [info] Updated flows
28 Feb 02:46:38 - [info] Starting flows
28 Feb 02:46:39 - [info] Started flows
28 Feb 02:46:39 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://localhost:1883
28 Feb 02:47:29 - [info] Stopping flows
28 Feb 02:47:29 - [info] [mqtt-broker:mqtt] Disconnected from broker: mqtt://localhost:1883
28 Feb 02:47:29 - [info] Stopped flows
28 Feb 02:47:29 - [info] Updated flows
28 Feb 02:47:29 - [info] Starting flows
28 Feb 02:47:29 - [info] Started flows
28 Feb 02:47:29 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://localhost:1883
28 Feb 02:47:40 - [info] Stopping flows
28 Feb 02:47:40 - [info] [mqtt-broker:mqtt] Disconnected from broker: mqtt://localhost:1883
28 Feb 02:47:40 - [info] Stopped flows
28 Feb 02:47:40 - [info] Updated flows
28 Feb 02:47:41 - [info] Starting flows
28 Feb 02:47:41 - [info] Started flows
28 Feb 02:47:41 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://localhost:1883
28 Feb 02:50:12 - [info] Stopping flows
28 Feb 02:50:12 - [info] [mqtt-broker:mqtt] Disconnected from broker: mqtt://localhost:1883
28 Feb 02:50:12 - [info] Stopped flows
28 Feb 02:50:12 - [info] Updated flows
28 Feb 02:50:12 - [info] Starting flows
28 Feb 02:50:12 - [info] Started flows
28 Feb 02:50:12 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://localhost:1883
28 Feb 02:55:34 - [info] Stopping flows
28 Feb 02:55:34 - [info] [mqtt-broker:mqtt] Disconnected from broker: mqtt://localhost:1883
28 Feb 02:55:34 - [info] Stopped flows
28 Feb 02:55:34 - [info] Updated flows
28 Feb 02:55:34 - [info] Starting flows
28 Feb 02:55:34 - [info] Started flows
28 Feb 02:55:34 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://localhost:1883
28 Feb 02:56:14 - [info] Stopping flows
28 Feb 02:56:14 - [info] [mqtt-broker:mqtt] Disconnected from broker: mqtt://localhost:1883
28 Feb 02:56:14 - [info] Stopped flows
28 Feb 02:56:14 - [info] Updated flows
28 Feb 02:56:14 - [info] Starting flows
28 Feb 02:56:14 - [info] Started flows
28 Feb 02:56:14 - [info] [mqtt-broker:mqtt] Connected to broker: mqtt://localhost:1883
Edit: noticed the times are wrong in the logs which is odd. Also it seems to keep disconnecting an reconnecting there to the zigbee server... No idea why that is,....
Ok looks like it was a config issue in the docker compose file.
Solution is here:
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
