2018-12-04, 10:51 AM
You can still use mqtt and signalk, udp is so fast it's unlikely collisions will be an issue, mqtt is much slower. Also , mqtt sends data as text so display options are limited, the lovely gauges and dials in the KIP app aren't available for text, they need numeric data.
I've just set up 2 inputs into openplotter set up in the mqtt tab, no problems at all - sounds like you have created a loop somewhere.
MQTT is handy though, I'm slowly creating a generic esp sketch sending the data as signalk UDP but using mqtt for diagnostics from an ESP and for control for when the esp is mounted hidden away somewhere. Working well so far, but for data - signalk UDP works much better than mqtt, no need to waste resources changing mqtt data into signak.
I've just set up 2 inputs into openplotter set up in the mqtt tab, no problems at all - sounds like you have created a loop somewhere.
MQTT is handy though, I'm slowly creating a generic esp sketch sending the data as signalk UDP but using mqtt for diagnostics from an ESP and for control for when the esp is mounted hidden away somewhere. Working well so far, but for data - signalk UDP works much better than mqtt, no need to waste resources changing mqtt data into signak.