Yield node unresponsive

[ScheepersJohan]

Hi,

I have a flow where I want to add 2 the Yield node to, the first one did want to be connected, were unresponsive to be placed and connected on the flow. Eventual it responded.

The second Yield I can not eve drag onto the flow.

I have tried other nodes like Yaml ,Delay and they all work.

Any ideas??

[knolleary]

What module does the yield node come from? It isn't one I've ever seen.

Any errors in the browser console?

[ScheepersJohan]

I stopped and restarted.

pi@raspberrypi:~/.node-red $ node-red-start

Start Node-RED
 
Once Node-RED has started, point a browser at http://192.168.1.100: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.
1 Aug 12:22:32 - [info]
Welcome to Node-RED
===================
1 Aug 12:22:32 - [info] Node-RED version: v0.20.5
1 Aug 12:22:32 - [info] Node.js  version: v8.11.1
1 Aug 12:22:32 - [info] Linux 4.14.98-v7+ arm LE
1 Aug 12:22:36 - [info] Loading palette nodes
1 Aug 12:22:51 - [info] Worldmap version 2.4.1
Initializing chat-platform lib, you should see this only once
Running at: /home/pi/.node-red/node_modules/chat-platform Version: 1.0.9
01 Aug 12:23:00 - [info] RedBot version: 0.18.4 (node-red-contrib-chatbot)
1 Aug 12:23:10 - [info] Dashboard version 2.20.0 started at /ui
1 Aug 12:23:11 - [info] Settings file  : /home/pi/.node-red/settings.js
1 Aug 12:23:11 - [info] Context store  : 'default' [module=memory]
1 Aug 12:23:11 - [info] User directory : /home/pi/.node-red
1 Aug 12:23:11 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
1 Aug 12:23:11 - [info] Flows file     : /home/pi/.node-red/flows_raspberrypi.json
1 Aug 12:23:12 - [info] Server now running at http://127.0.0.1:1880/
1 Aug 12:23:12 - [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.
---------------------------------------------------------------------
1 Aug 12:23:12 - [info] Starting flows
Telegram Bot SignalOwl_2_bot will be launched, environment is development
No context provider specified for chatbot SignalOwl_2_bot. Defaulting to "memory"
1 Aug 12:23:18 - [info] Started flows
------ WebHooks for TELEGRAM----------------
http://localhost:1880/redbot/telegram/
1 Aug 12:23:19 - [info] [sqlitedb:5de16e9e.81da9] opened /home/pi/Documents/AquaData/db/aquadb.db ok
1 Aug 12:23:19 - [info] [sqlitedb:5de16e9e.81da9] opened /home/pi/Documents/AquaData/db/aquadb.db ok
1 Aug 12:23:19 - [info] [sqlitedb:5de16e9e.81da9] opened /home/pi/Documents/AquaData/db/aquadb.db ok
1 Aug 12:23:19 - [info] [sqlitedb:e69770b7.c3e7e] opened /home/pi/Documents/TTN gateway/Gateway request.db ok

The Yield node -

node-red-contrib-yield

This node sends messages passed from msg.payload separately down the flow. Simply puts the messages in an array and assign to msg.payload.

[knolleary]

And the browser console? If the node is misbehaving in the editor, then the browser log is the place to look.

[Steve-Mcl]

I've not used this yield node but it doesn't look too different to the built-in split node - if you can't get it working, you might want to look at that.

Ps, that yield node is over 4y old - might be abandoned. But you could raise an issue on its repo if you spot the issue.

[ScheepersJohan]

You drag it into the flow and the log show nothing.

I see it were update like 4 years last. May be I need to look for another node the split a array.

[Steve-Mcl]

@ScheepersJohan

May be I need to look for another node the split a array.

I have edited my post above. I did mean checkout the split node. Very similar functionality (as far as I can tell from the description)

[ScheepersJohan]

The strange thing is it is in another flow on the same Pi and it works.

[ScheepersJohan]

Thanks I will use the split node