# "Error: Invalid action specified" from MQTT node
**URL:** https://discourse.nodered.org/t/error-invalid-action-specified-from-mqtt-node/67619
**Category:** General
**Created:** [12 September 2022 16:57 UTC](https://discourse.nodered.org/t/error-invalid-action-specified-from-mqtt-node/67619 "2022-09-12T16:57:36Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@hazymat](https://discourse.nodered.org/u/hazymat)
#### Post date: [12 September 2022 16:57 UTC](https://discourse.nodered.org/t/error-invalid-action-specified-from-mqtt-node/67619/1 "2022-09-12T16:57:36Z")
Hi, after upgrading from 2.0.4 to 3.0.2, I'm getting an error in Debug sidebar from an MQTT output node. This MQTT output node exists within a subflow template, which always worked before. Here's the message as it enters MQTT output, plus the error (when I click on the error's node source, it highlights MQTT node):
In case you are wondering what the incoming msg.action is about - that's just a property of the msg object that I added as part of my code. Maybe the property name "action" is conflicting with something else?
Is there any way I can revert to the previous behaviour, (without rolling back to previous version of Node-RED) as right now I can't turn my lights on 😛
(In seriousness, I do have other means of turning the lights on, just not as convenient!)
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [12 September 2022 17:11 UTC](https://discourse.nodered.org/t/error-invalid-action-specified-from-mqtt-node/67619/2 "2022-09-12T17:11:26Z")
Have a look at the help text for the node. `msg.action` now allows you to connect and disconnect dynamically.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [11 November 2022 17:11 UTC](https://discourse.nodered.org/t/error-invalid-action-specified-from-mqtt-node/67619/3 "2022-11-11T17:11:35Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.