New to NodeRed but find it absolutely beautiful so far. This has been bugging me however, and I can't seem to get it to stop.. I think this is just a side-effect of selecting "a parsed JSON object" for the type of Output on my MQTT-in nodes, but this is required to do what I want, and I'd love to disable these errors which just clog up the the debug console:
They don't seem to cause a problem functionality wise with my flow, and would really just like them to be gone.
Subscribe to the same topic with the output set to string and connect a debug node. Find the messages that are not valid JSON and fix the source that is publishing the invalid data.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
The OpenJS Foundation | Terms of Use | Privacy Policy | OpenJS Foundation Bylaws | Trademark Policy | Trademark List | Cookie Policy
