There is something definitely up with the MQTT to SignalK converter.
I was able to replicate the function of the tab by convert all the data from the ESP to the SignalK in Node Red. The local MQTT server behaved fine with no issues. It has been running two days with no issues.
If you use the MQTT tab to covert the data(outside source) it seems to be fine for up to two items. But, if you exceed two conversions it seems to create a loop and causes the processor to go up to near 100%. The more conversions you add the sooner the problem happens.
At five conversions the problem would happen within 10-15 minutes.
I was able to replicate the function of the tab by convert all the data from the ESP to the SignalK in Node Red. The local MQTT server behaved fine with no issues. It has been running two days with no issues.
If you use the MQTT tab to covert the data(outside source) it seems to be fine for up to two items. But, if you exceed two conversions it seems to create a loop and causes the processor to go up to near 100%. The more conversions you add the sooner the problem happens.
At five conversions the problem would happen within 10-15 minutes.