Problems with Node-Red on Edge IO after updating to version 3.1.3

I am having strange problems with Node-Red flows. Some Function nodes have errors like not recognizing msg, or functions like Buffer.

These worked fine under 1.3.5. Any suggestions (other than rolling back to 1.3.5)?
Thanks,

Guillermo

Hi Guillermo, thanks for reaching out and for flagging!

This is an issue with the listed types package not being installed. We’re looking into a fix, and I’ll update here to confirm when the fix will be released.

That being said, this should only be an issue for the editor/ui; it shouldn’t affect the runtime functionality (if you deploy those function nodes, despite the UI errors, they should still work as expected). Let me know if that’s not the case.

Thanks,
Kathy

Hi Kathy,

Thanks for the quick response.

In the meantime, I was attempting to recreate the problem in a VM I have with Node-Red installed. I was having issues because my Flow uses the Tulip-Tag node. Is that not available in any repositories? I only found the Tulip-API nodes.

Regards,

Guillermo

The tulip-tag nodes are currently only available on Edge Devices. The same functionality should be achievable using the tulip-machine-attribute nodes with a bit more overhead - the primary differences are authentication (you will need to create an api key and use its credentials), and that you’ll need to copy the target machine attribute’s machineId/attributeId into the Node-RED node, instead of doing the mapping on the Tulip side.

Hope that helps!

Hi Kathy,

Yes, that helps, thanks.

Are there any plans to release the tulip-tag nodes to enable running on more powerful hardware? I noticed that the tulip-machine-attribute nodes are being deprecated in favor of the tulip-tag nodes.

Hi Guillermo, we’ll continue to support and maintain the public API nodes, and there are no plans to remove them from Tulip edge devices. We just recommend using the tulip-tag nodes on Tulip devices over the machine attribute nodes since they have built-in authentication and it’s a more scalable solution for duplicating flows between devices - but you can definitely still safely use the api nodes on the device.

As for running tulip-tags on external hardware, there are plans for this (or at least something similar) later this year, but I don’t have a concrete timeline.

Best,
Kathy

Perfect, thank you for the clarification.

Regards,

Guillermo

Hi Guillermo,

Just as a follow up, the UI bug from your original post will be fixed in our upcoming point release OS56.4 (scheduled for next week).

Best,
Kathy

1 Like

Perfect, thanks for letting me know and for resolving it quickly.

Regards,
Guillermo