Node-Red issue; service node no longer triggered by Z2M button

In Node-Red, when pressing button 4 on a remote control, a switch node outputs:
{“action”:“on_4”,“action_group”:516,“battery”:100,“linkquality”:80}
The output of the node goes to a service node.
This service node gives “failed” and gives “InputError: Invalid action format: on_4”
This worked in the past but I guess due to a Node-Red integration upgrade, something changed.
Any advice to resolve this problem is highly appreciated!

Turn on “block input overrides” in the action node

4 Likes

Thanks Kermit, spend hours to fix it, without success. Can confirm that this was the ‘missing link’. THANKS!

Thank you very much! This fixed it to me as well.
But can you please elaborate? Why was this working without problems for so long? The update broke it, right? Was there anything about it in release notes? I guess I gotta start reading those before updates :smiley:

There was a recent change from domain and service to action inside HA. Call service nodes allow you to send a message to override the nodes settings. Before the change you would send the following in the payload position to override the node.

{
    "domain": "light",
    "service": "turn.on"
    ...
}

Now

{
    "action": "light.turn_on",
    ...
}

So the original paths sent were

payload.domain and payload.service

Now that has changed to

payload.action

Unfortunately the data sent when a button is triggered is in the position payload.action which wasn’t a problem before but now matches the override message, so we need to block it.