Serial Gateway and MQTT Broker

[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:

[talhatec]

@jkandasa has the independent service been created? I would really love to see this feature. Im using Home Assistant for overall home automation. But I want to manage MySensors with MyController due to the better features to handle MySensor Nodes.

[jkandasa]

@talhatec Still I am working on this feature. I will update you once it gets ready.

[jkandasa]

@talhatec Thank you for your patience
Finally the first version of serial2mqtt adapter available and released for public. Kindly report issues if you find any on issues page

[Diego Baravalle]

@jkandasa Thanks very very much!

Awesome work!

:clap: :clap: :clap:

[talhatec]

@jkandasa Thank you very much, will give it a go over the weekend.

[talhatec]

@jkandasa The serial2MQTT adapter worked for a while, but then it started to fail. Looking at the logs, its not receiving the data from serial properly

2017-08-07 18:04:00,942 ERROR [Thread-1] [org.mycontroller.serial2mqtt.gateway.MessageMonitorThread:66] Exception on processing [RawMessage(gatewayId=null, data=%ﾍﾲￌￒ￲▒ￍﾞﾉ<*▒oﾰﾲￋﾛ￤▒0;255;3;0;9;TSF:MSG:READ,254-254-0,s=255,c=3,t=1,pt=0,l=0,sg=0:, subData=null, isTxMessage=false, networkType=MY_SENSORS, timestamp=1502125439421)],
java.lang.NumberFormatException: For input string: "%ﾍﾲￌￒ￲▒ￍﾞﾉ<*▒oﾰﾲￋﾛ￤▒0"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
        at java.lang.Integer.parseInt(Integer.java:569)
        at java.lang.Integer.valueOf(Integer.java:766)
        at org.mycontroller.serial2mqtt.gateway.MessageEngine.postOnMqtt(MessageEngine.java:53)
        at org.mycontroller.serial2mqtt.gateway.MessageMonitorThread.processRawMessage(MessageMonitorThread.java:63)
        at org.mycontroller.serial2mqtt.gateway.MessageMonitorThread.run(MessageMonitorThread.java:85)
        at java.lang.Thread.run(Thread.java:745)

[talhatec]

@jkandasa Not sure what the issue is, but the adapter seems to be working fine now. Ill leave it running for a day and see if the data issue reappears. I was trying to get HomeAssistant and myController to work off the same MQTT topics. maybe thats what cause the data issue.

[jkandasa]

@talhatec Are you seeing this error often?

[talhatec]

@jkandasa It seems to be stable now. Think that it was a one off issue. Ive now got both HomeAssistant and MyController working on the same MQTT in/out topics.

However, when a sensor calls back to the controller, both HomeAssistant and myController send out replies, and due to this, i think the messages clash, and the controllers endup sending it multiple times.

Have to think of a way to make only one respond to requests.

[jkandasa]

@talhatec

However, when a sensor calls back to the controller, both HomeAssistant and myController send out replies, and due to this, i think the messages clash, and the controllers endup sending it multiple times.

I do not know your preference about, which controller wants to response for your sensors request. Suppose you want MyController only on listen mode, you have to change MQTT Topic publish to some dummy topic on MyController gateway settings.