Loosing downstream messages from widget to node after deploy.

[beckflorian]

Current Behavior

I am working on a custom node with integrated widget. The Node and the Widget exchange information through a pub/sub model. When I (re)start nodered everything works fine. I send and receive messages via socket.
Now I change something in the flow and deploy.
After that I do not receive the downstream messages via socket any more.
When I reload the browser everything is fine again.

Expected Behavior

Deploying the flow should not change the message flow from the widget to the node.

Steps To Reproduce

This is my first issue...

I am working on an custom node with integrated widget.
https://github.com/beckflorian/ui-mainswitch.git

Currently i am working on (hopefully) the last major bug. I have done a lot of debugging... somehow I loose downstream socket connection after deploy...

When the state of the switch in the widget changes I emit a message to the server:

Client-Side code:

updateMainswitch(){
    console.info('downMainswitch' +  this.id + ': payload: ' + this.condition.mainSwitch)
    this.$socket.emit('downMainswitch' + this.id, this.id, { payload: this.condition.mainSwitch }))
},

console on client:
downMainswitch5ce8f224cea1234b: payload: 1

My server-side code:

onSocket: {
     // widget sends change of mainSwitch
    ['downMainswitch' + node.id]: function (conn, id, msg) {
        console.info('downMainswitch' + node.id + ' received:', conn.id, id, msg)
        setMainSwitch(msg.payload);
    },

console on server:
downMainswitch5ce8f224cea1234b received: 64_P1qA1L1UeAJMoAAAB 5ce8f224cea1234b { payload: 1 }

After Deploy:
Console on client shows the same output.
Console on Server: no output.

Is it a bug in my code or a bug in the dashboard?
Joepavitt sugested to open an isue on this...

Environment

• Dashboard version: 1.18.1
• Node-RED version: 4.02
• Node.js version: 22.5.1
• npm version: 10.8.2
• Platform/OS: The same on Raspbian with different versions od termux on android
• Browser: Firefox or Chrome

Have you provided an initial effort estimate for this issue?

I am not a FlowFuse team member