Serial Gateway and MQTT Broker

[jkandasa]

@Diego-Baravalle for now MyController will not push serial gateway messages to MQTT

[barduino]

@Diego-Baravalle

In theory you could use nodeJS to read from serial and push to MQTT.

From there you should be able to have 2 MQTT enabled controllers subscribing/publishing to broker.

That should be an interesting experiment

Cheers

[Diego Baravalle]

@jkandasa, @barduino

Thanks for your answers.

Use NodeJS is an interesting option.

[Frank C]

@jkandasa is there a future feature to push serial-gateway messages with MyController's build in MQTT? It would a great feature.

[jkandasa]

@Frank-C For now no plan

[gohan]

@Frank-C
It would be quite a redundant function because you can publish directly from the gateway if you use an ethernet shield, but it's not your case if I understood right

[jkandasa]

@Frank-C But I can write simple library to run independently to convert serial gateway messages to MQTT type. If you want.

[Frank C]

@jkandasa That would be fantastic if you could ? I think it would be a great feature :)

[jkandasa]

@Frank-C Yes, I can. but you have to run it as separate service. I will create a separate project for this work. I am not going to include this on MyController project.

[Frank C]

@jkandasa As a seperate service is okay, it would be very helpful. Thank you

[Diego Baravalle]

@jkandasa Perfect!

[FotoFieber]

Maybe this is enough for your requirement:
https://forum.mysensors.org/topic/4599/how-to-add-a-serial-device-to-use-in-node-red/10

[Frank C]

@FotoFieber Thanks for the suggestion, I got that working. I have had to change MyController to read an MQTT gateway. Problem now is MyController can't read the MQTT format of this script. Any suggestions or tips ?
MyController does such a great job with handling MySensors' data, it would be a pity to loose that functionality.

[FotoFieber]

@Frank-C
The script uses the serial protocol and should be compatible with the mysesnosrs mqtt-gateway. Are the pub/sub-topics set correct?

[Frank C]

@FotoFieber MyController is getting the MQTT msg, but doesn't like it's format, i've had continuous error msg like below:
2017-02-16 18:17:34,657 ERROR [Thread-4] [org.mycontroller.standalone.provider.mysensors.MySensorsProviderBridge:60] Unable to process this rawMessage:RawMessage(gatewayId=2, data=2;0;1;0;23;36, subData=mysensors/1/out/, isTxMessage=false, networkType=MY_SENSORS)
org.mycontroller.standalone.message.RawMessageException: Unknown message format, Topic:mysensors/1/out/, PayLoad:2;0;1;0;23;36
at org.mycontroller.standalone.provider.mysensors.MySensorsRawMessage.updateMQTTMessage(MySensorsRawMessage.java:114) ~[mycontroller-dist-standalone-0.0.3.Alpha2-single.jar:0.0.3.Alpha2]

MyController is set up with the correct topic, as seen in above Topic:/mysensors/1/out/ (i've also tried without the ending /).

[FotoFieber]

2;0;1;0;23;36 Is a correct message according to the serial API. I don't know anything about your controller...sorry

Maybe the controller needs the ; translated to / in the topic?

Have you tried to switch pub/sub topic?

[jkandasa]

@Frank-C Current approach of MyController on MQTT see only payload on message. Other data(nodeId, sensorIds, etc) from topic. Kindly create a request on MyController issue page. I will address this. If we address this I am not going to create separate service to parse serial-to-real-mqtt service type.

[Frank C]

@jkandasa Thanks for the follow up. I can see MyController is modifying the serial message into a customized MQTT msg (as you have said).
MyController works great with the serial so it would be good to keep that as is, and if we had an independent service to publish to a separate MQTT broker would be very helpful?

[jkandasa]

@Frank-C cool, we will go with independent service.

[Frank C]

@jkandasa :thumbsup: