# Change node not working as expected!
**URL:** https://discourse.nodered.org/t/change-node-not-working-as-expected/54011
**Category:** General
**Created:** [19 November 2021 20:14 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011 "2021-11-19T20:14:35Z")
**Posts on this page:** 11
**Page:** 2
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [21 November 2021 08:48 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/21 "2021-11-21T08:48:49Z")
> [@zenofmud](#):
>
> Add a `mqtt-in` node (subscribing to the topic)
Presumably with Output set to parsed JSON?
---
### Author:  [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [21 November 2021 09:32 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/22 "2021-11-21T09:32:12Z")
Before I try that, just noticed that disconnecting the change & debug node from the flow, still results in a debug msg, how can that be???
EDIT
> [@zenofmud](#):
>
> Send the output of the 'Switch Garden Alert' to a `mqtt-out` node (with an appropriate topic)
And with output set to parsed json, and I get nothing out.
Checking the broker with MQTT Explorer shows that the message never reached the broker.
(replacing the contrib node with an inject node shows that the MQTT side is working)
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [21 November 2021 09:45 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/23 "2021-11-21T09:45:24Z")
What type of deploy are you doing? Try doing a full deploy.
---
### Author:  [@Bobo](https://discourse.nodered.org/u/Bobo)
#### Post date: [21 November 2021 09:48 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/24 "2021-11-21T09:48:02Z")
> [@Paul-Reed](#):
>
> Before I try that, just noticed that disconnecting the change & debug node from the flow, still results in a debug msg, how can that be???
Regarding oddities in the debug node (not providing any output, when there was actual output for example) I thought I was either losing my mind (which happens regularly anyway) or the node I had created was misbehaving. Now there appears to be a potential third option.
Further investigation needed.
---
### Author:  [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [21 November 2021 10:11 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/25 "2021-11-21T10:11:24Z")
> [@zenofmud](#):
>
> What type of deploy are you doing?
I was doing a 'modified nodes' deploy, but I've now selected full deploy, and it appears to have cleared the issues.
Good call Paul đ
I suppose that it still leaves the issue of why this happened in the first place...
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [21 November 2021 11:00 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/26 "2021-11-21T11:00:14Z")
I always (ummm most of the time) do a âmodified flowsâ deploy. Less than the full deploy but does more than the âmodified nodesâ deploy.
My guess is that it didnât clean up/create all the wires to the other nodes in the flow.
@knolleary @dceejay any thoughts about that?
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [21 November 2021 11:00 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/27 "2021-11-21T11:00:43Z")
In retrospect a page refresh before trying the full deploy might have been interesting.
---
### Author:  [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [22 November 2021 09:27 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/28 "2021-11-22T09:27:11Z")
Is this the expected result of using 'modified nodes' deploys?
It seems strange that the nodes were deployed, but the wiring wasn't?
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [22 November 2021 09:44 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/29 "2021-11-22T09:44:29Z")
No, that is not expected.
Changing a node's wiring is absolutely considered a modification.
I haven't had a chance to try reproducing it. It would be good to know if anyone else can.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [22 November 2021 09:45 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/30 "2021-11-22T09:45:22Z")
> [@Paul-Reed](#):
>
> Is this the expected result of using 'modified nodes' deploys
No. Any wiring changes should be deployed too. Something went wrong somewhere. If it happens again then it would be interesting to open the editor in another browser or another PC to see whether the flows file was not updated correctly or whether it was the browser end that was confused. Possibly if it were the file then keep a copy of the flows file before doing anything else, then do a full deploy (after a trivial change, a move of an unrelated node maybe) and the compare the two files. Along with screenshots of course.
---
### Author:  [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [6 December 2021 09:45 UTC](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011/31 "2021-12-06T09:45:35Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
[Previous page](https://discourse.nodered.org/t/change-node-not-working-as-expected/54011.md?page=1)