MyController.org

[TD22057]

@jkandasa said:

@TD22057 The current MQTT gateway supports only limited features and a big drawback is we cannot use it directly on internet as it does not have any security option and limited to number of connections

For this reason I'm implementing MQTT broker support in MyController server. Here we can connect our mysensors gateway (serial/Ethernet) to MyController. Connect all our MQTT client to MyController with authentication

https://github.com/mycontroller-org/mycontroller/issues/7

I'm sure I'm not understanding something, but isn't that a lot more complicated than it needs to be? Why isn't MyController just an MQTT client that connects to an existing broker? So Arduinos <-> MQTTClientGateway <-> Mosquitto <-> MyController. If MyController subscribes to the MS messages from the broker and publishes command messages to the broker, everything works fine. Security and everything else is already handled by the existing broker software (Mosquitto).

[jkandasa]

@TD22057 said:

I'm sure I'm not understanding something, but isn't that a lot more complicated than it needs to be? Why isn't MyController just an MQTT client that connects to an existing broker? So Arduinos <-> MQTTClientGateway <-> Mosquitto <-> MyController. If MyController subscribes to the MS messages from the broker and publishes command messages to the broker, everything works fine. Security and everything else is already handled by the existing broker software (Mosquitto).

@TD22057 MyController supports MQTT gateway(connects with existing broker) also but with limited feature. The current MQTTClientGateway doesn't support firmware upgrade and some other features which is required to use all the features in MyController. So if we use Serial/Ethernet gateway we can use all the features from MyController at the same time I do not want to restrict people with MyController, So if I provide MQTT broker they can connect all their clients with MyController.

[bpair]

@jkandasa Great. I just tried it. I used send on the activity board and it appears to be doing what i meant by Receive. Of course once you fix that "bug" it may not work like that anymore.

But I did see the data on the chart.

[jkandasa]

@bpair said:

@jkandasa Great. I just tried it. I used send on the activity board and it appears to be doing what i meant by Receive. Of course once you fix that "bug" it may not work like that anymore.

But I did see the data on the chart.

@bpair As I mentioned on the bug, that's all users wish they can disable/enable payload option. After the fix also still you can feed your data via action board (if you enabled send payload option). I hope for now your requirement fulfilled.

[bpair]

Thanks. Everything looks very good.

[artur]

Good afternoon. tell me why issue such a mistake?
Good afternoon. tell me why issue such a mistake?
I understand that the resulting package is less, but I use the default gateway mysensors MQTT.
help solve this problem.

2015-10-27 22:47:52,574 DEBUG [MQTT Call: MC] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:84] Message Received, Topic:[MyMQTT/20/0/V_LIGHT], PayLoad:[1]
2015-10-27 22:47:52,576 ERROR [MQTT Call: MC] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:92] Exception,
org.mycontroller.standalone.mysensors.RawMessageException: Unknown message format, Topic:MyMQTT/20/0/V_LIGHT, PayLoad:1
        at org.mycontroller.standalone.mysensors.RawMessage.<init>(RawMessage.java:62) ~[mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener.messageArrived(MqttCallbackListener.java:85) ~[mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.eclipse.paho.client.mqttv3.internal.CommsCallback.handleMessage(CommsCallback.java:354) [mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.eclipse.paho.client.mqttv3.internal.CommsCallback.run(CommsCallback.java:162) [mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
2015-10-27 22:47:55,114 DEBUG [MQTT Call: MC] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:84] Message Received, Topic:[MyMQTT/20/0/V_LIGHT], PayLoad:[0]
2015-10-27 22:47:55,115 ERROR [MQTT Call: MC] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:92] Exception,
org.mycontroller.standalone.mysensors.RawMessageException: Unknown message format, Topic:MyMQTT/20/0/V_LIGHT, PayLoad:0
        at org.mycontroller.standalone.mysensors.RawMessage.<init>(RawMessage.java:62) ~[mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener.messageArrived(MqttCallbackListener.java:85) ~[mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.eclipse.paho.client.mqttv3.internal.CommsCallback.handleMessage(CommsCallback.java:354) [mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.eclipse.paho.client.mqttv3.internal.CommsCallback.run(CommsCallback.java:162) [mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
2015-10-27 22:48:33,356 DEBUG [MQTT Call: MC] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:84] Message Received, Topic:[MyMQTT/3/255/V_SKETCH_NAME], PayLoad:[EgHumBarTemBat_v2]
2015-10-27 22:48:33,358 ERROR [MQTT Call: MC] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:92] Exception,
org.mycontroller.standalone.mysensors.RawMessageException: Unknown message format, Topic:MyMQTT/3/255/V_SKETCH_NAME, PayLoad:EgHumBarTemBat_v2
        at org.mycontroller.standalone.mysensors.RawMessage.<init>(RawMessage.java:62) ~[mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener.messageArrived(MqttCallbackListener.java:85) ~[mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.eclipse.paho.client.mqttv3.internal.CommsCallback.handleMessage(CommsCallback.java:354) [mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.eclipse.paho.client.mqttv3.internal.CommsCallback.run(CommsCallback.java:162) [mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
2015-10-27 22:48:33,377 DEBUG [MQTT Call: MC] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:84] Message Received, Topic:[MyMQTT/3/255/V_SKETCH_VERSION], PayLoad:[2.2 19.10.2015]
2015-10-27 22:48:33,378 ERROR [MQTT Call: MC] [org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener:92] Exception,
org.mycontroller.standalone.mysensors.RawMessageException: Unknown message format, Topic:MyMQTT/3/255/V_SKETCH_VERSION, PayLoad:2.2 19.10.2015
        at org.mycontroller.standalone.mysensors.RawMessage.<init>(RawMessage.java:62) ~[mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.mycontroller.standalone.gateway.mqtt.MqttCallbackListener.messageArrived(MqttCallbackListener.java:85) ~[mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.eclipse.paho.client.mqttv3.internal.CommsCallback.handleMessage(CommsCallback.java:354) [mycontroller-standalone-0.0.2-alpha5-single.jar:na]
        at org.eclipse.paho.client.mqttv3.internal.CommsCallback.run(CommsCallback.java:162) [mycontroller-standalone-0.0.2-alpha5-single.jar:na]

[jkandasa]

@artur said:

Good afternoon. tell me why issue such a mistake?
Good afternoon. tell me why issue such a mistake?
I understand that the resulting package is less, but I use the default gateway mysensors MQTT.
help solve this problem.

Log message says that you are using MyController 0.0.2-alpha5(mycontroller-standalone-0.0.2-alpha5). This version of MyController supports only for MySensors-1.6 dev branch. And the MQTT format should be MY_MQTT_TOPIC_PREFIX/NODE-ID/SENSOR-ID/CMD-TYPE/ACK-FLAG/SUB-TYPE

Refer this for more details: https://github.com/mycontroller-org/mycontroller/issues/33

[artur]

what is the point to move to 1.6 when gateway may only client?

[jkandasa]

@artur said:

what is the point to move to 1.6 when gateway may only client?

@artur Not only gateway will be client, we have other features like Get node details without reboot(via I_PRESENTATION), ping status for node(heartbeat), MQTT full support (supports all the commands, you can do firmware update also), like we have many features available in 1.6. Anyhow we have to support all the features once 1.6 released. Hence I started implementing 1.6 features slowly one by one.

[artur]

certainly it sounds tempting, but I just could not find in the examples, see only MQTT client initially.
https://github.com/mysensors/Arduino/tree/development/libraries/MySensors/examples
I realized 1.6 is still in development?

[jkandasa]

@artur said:

certainly it sounds tempting, but I just could not find in the examples, see only MQTT client initially.
https://github.com/mysensors/Arduino/tree/development/libraries/MySensors/examples
I realized 1.6 is still in development?

@artur Yes, 1.6 is in development branch. you can find MQTT client here

[artur]

and who will MQTT broker?

[jkandasa]

@artur said:

and who will MQTT broker?

You are right! I misunderstood something here! I believe I have to create code for MQTT broker with MyController

http://forum.mysensors.org/topic/2285/mqtt-broker-support-in-mysensors-1-6