Node with hidden wire --> X output node messages

Hi !

Sometimes, i have some bug with the wire of some nodes.
I use the latest version NR 2.2
The output wire of the node multiply the message (here 3 wires)

I don't know how it's happen (merging, deploy, copy paste ....) ?

If you have somes ideas...

Thanks in advance for your help !

PS : Debugger can help to see what happen :wink:

[
    {
        "id": "dbb85b569c600d88",
        "type": "exec",
        "z": "514053c7b34aa0bc",
        "command": "echo $HOME",
        "addpay": "",
        "append": "",
        "useSpawn": "false",
        "timer": "",
        "winHide": false,
        "oldrc": false,
        "name": "",
        "x": 920,
        "y": 1360,
        "wires": [
            [
                "aba38453d06cbbe4"
            ],
            [],
            []
        ]
    },
    {
        "id": "41215627dd511af0",
        "type": "inject",
        "z": "514053c7b34aa0bc",
        "name": "",
        "props": [
            {
                "p": "payload"
            },
            {
                "p": "topic",
                "vt": "str"
            }
        ],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "",
        "payloadType": "date",
        "x": 740,
        "y": 1360,
        "wires": [
            [
                "dbb85b569c600d88"
            ]
        ]
    },
    {
        "id": "aba38453d06cbbe4",
        "type": "debug",
        "z": "514053c7b34aa0bc",
        "name": "",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "false",
        "statusVal": "",
        "statusType": "auto",
        "x": 1130,
        "y": 1340,
        "wires": []
    },
    {
        "id": "8b57a776ae5311e1",
        "type": "exec",
        "z": "514053c7b34aa0bc",
        "command": "echo $HOME",
        "addpay": "",
        "append": "",
        "useSpawn": "false",
        "timer": "",
        "winHide": false,
        "oldrc": false,
        "name": "",
        "x": 920,
        "y": 1260,
        "wires": [
            [
                "0ab9500540f25909",
                "0ab9500540f25909",
                "0ab9500540f25909"
            ],
            [],
            []
        ]
    },
    {
        "id": "ca560554a48854a3",
        "type": "inject",
        "z": "514053c7b34aa0bc",
        "name": "",
        "props": [],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "x": 750,
        "y": 1260,
        "wires": [
            [
                "8b57a776ae5311e1"
            ]
        ]
    },
    {
        "id": "0ab9500540f25909",
        "type": "debug",
        "z": "514053c7b34aa0bc",
        "name": "",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": true,
        "complete": "payload",
        "targetType": "msg",
        "statusVal": "payload",
        "statusType": "auto",
        "x": 1185,
        "y": 1240,
        "wires": [],
        "l": false
    }
]

Looks like imilar issue as explained here.

The workaround to fix it when this happens is to delete the wire (which does not actually seem to do anything), then Deploy which will leave you with just the one wire.

Ok thanks for your reply.
Hope it will be fixed quickly

Thanks for the team
Regards.

A PR has been published and will be included in a patch release (hopefully) within the coming days.

For reference: the issue has been raised here: Duplicate wires between nodes with 2.2.0 Ā· Issue #3433 Ā· node-red/node-red Ā· GitHub

Perfect !
Thanks :grinning:

About a month ago I added a new (to me and NIB) LED strip controller and a Pico button for local control. It's had some goofy behavior and I just figured it was the controller but today I went looking to see why the sequence (flow, if you must) was producing double messages and found it was this issue. Now I wonder if I have it lurking somewhere else that I don't know about yet and I'd like some script, or such, to find if I do. Has anybody done this scan already? @Steve-Mcl ?

This issue has been handled and mitigated if you upgrade to version. 2.2.2. You won't need to do anything other than update and restart. You can, if you wish, do a browser refresh, full deploy to actually remove the duplicate wires in the flow file permanently (but it's not 100% necessary since they are removed in the runtime at load & won't cause the double message issue).

I've been on 2.2.2 since a few days after it was released and the sequence was deployed many times including some "fulls".