Mikrotik API doesn't accept reply !empty

Hardware
1

Hi,
I've recently updated my router OS to 7.18 and since the update has been performed I'm running an issue on NodeRed where it breaks it when the reply doesn't have data to reply.

I found the below on Mikrotik API docs.

Replies of commands which do not have any data to reply with, begin with !empty (introduced in RouterOS 7.18);

Anyone knows if it can be resolved or if it required NodeRed update to include this change on a next release.

Thank for your help.
Fred

2

Hi @Dasinho7

What are you using in Node-RED to interact with the Mikrotik API? Are you using the built-in HTTP Rquest node, or a contib node from the community that you've installed?

3

Hi @knolleary
I'm using Mikrotik node yes to send an API Raw command adding the command in payload. (see below an example of command which work under RouterOS 7.16.2 and block under 7.18.2.

msg.payload = ["/interface/bridge/port/print",
"?=interface=VLAN101"]
return msg;

4

Which specific node are you using? There are 3 listed on flows.nodered.org

Once you know which one you may need to raise an issue against the node to have it updated to match the latest MikroTik firmware.

The first in the list appears to have been updated most recently, but even that was over 3.5 years ago and the GitHub repo for the one ending in mikrotik3 points to the same place the mikrotik2 does.

All 3 appear to use the node-routeos package, which was last updated 4 years ago and is now marked as deprecated

5

Hi @hardillb

Thank you for your reply, I'm using node-red-contrib-mikrotik 0.7.0, I raised the issue on GitHub.
Thanks for the guidance.

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.