Guide: Setting up and testing MQTT Client Gateway

[gregl]

I can see in mosquitto logs a subscription from the gateway

1452645694: mosquitto version 1.3.4 terminating
1452645694: Sending CONNACK to mysensors-1 (0)
1452645694: Received SUBSCRIBE from mysensors-1
1452645694: 	mygateway1-in/+/+/+/+/+ (QoS 0)
1452645694: Sending SUBACK to mysensors-1

So looks like i need to add an extra level to the message i send!
So i just tried sending a message to topic:

mygateway1-in/9/1/0/1/1

and now i can see in my serial outputs of both the mqttclient gateway and the relaysketch node the message received!
( but its not swithing my relay yet! )

@hek is this the correct MQTT formatting:
MY_MQTT_PUBLISH_TOPIC_PREFIX/FROM-NODE-ID/SENSOR-ID/CMD-TYPE/ACK-FLAG/SUB-TYPE

[gregl]

Ok got it... ( sorry for making mess of this discussion!)
If i publish to
mygateway1-in/9/1/1/0/2 and send message values of 0 or 1 it works.... ;-)

Hope this helps someone else!

Greg ;-)

[tante ju]

@hek
That thread does not directly touch on the issue I noticed, although that might be connected.

Some other questions:
Why is the topic structure as it is? I like my MQTT topics in hierarchical order. So, having different prefixes for send and receive (in and out) is not nice, but ok. BUt why is the ACK flag before the data type, which is usually linked to a value or variable in the sensor? I would consider ACK to be a sub-value of that one.

And is there a way to have more speaky names instead of numbers? So, the source does not have that option and as that gateway is now included in the library I only see the possibility of changing the source in the library, which will disconnect from updates. Not nice. What about an option of excluding gatewayTransportSend and incomingMQTT via define from the library and define then in the own sketch?

[moskovskiy82]

What is the correct way to run DHCP? Tried commenting out
#define MY_IP_ADDRESS
but that didn't help.

Also is it possible to use fqdn for the mqtt broker instead of the ip?

[gregl]

@moskovskiy82

I also tried to use DHCP and fqdn for mosqitto, but no luck....so I cant help but I too would like to know if its possible.

[hek]

@gregl

A PR was merged 5 days ago where you can specify
MY_CONTROLLER_URL_ADDRESS

https://github.com/mysensors/Arduino/pull/375

I haven't verified it myself yet though.

[mbj]

Finally I have the ESP8266 gateway running with Mosquitto and Openhab. Because the ESP8266 Gateway installation was painless and Mosquitto and Openhab the major problems I have posted some general info at this link in case anyone is interested, see http://forum.mysensors.org/topic/3005/switching-from-v1-5-mqtt-gateway-to-esp8266-mqtt-client-gateway.
(Sorry if this is the wrong procedure but found no way to add other tags to a message in this thread).

[gregl]

@hek
Thanks Hek - will give it a try soon!

[moskovskiy82]

I have been successfully running the MQTT client gateway receiving the data from sensors. Now build the first mysensors relay and would like to know if the MQTT client gateway can act as a transmitter?

I have assigned the nod id of 55 to the relay sensor and trying to send
mosquitto_pub -t mygateway1-in/55/1/0/0/3 -m "1"

But doesn't seem to help

[hek]

Yes, it should work as a transmitter as well. What does the log say on gateway and node?

[moskovskiy82]

Resolved. Power supply was the problem

[mbj]

@mbj said:

Finally I have the ESP8266 gateway running with Mosquitto and Openhab. Because the ESP8266 Gateway installation was painless and Mosquitto and Openhab the major problems I have posted some general info at this link in case anyone is interested, see http://forum.mysensors.org/topic/3005/switching-from-v1-5-mqtt-gateway-to-esp8266-mqtt-client-gateway.
(Sorry if this is the wrong procedure but found no way to add other tags to a message in this thread).

Do not know if this info is of any interest but my ESP8266 MQTT gateway (based on a NodeMCU board) has been running without hiccups for almost a month now. So it has been very stable. I have also made a very short test using a Wemos D1 Mini for the gateway and this one seemed to be working as expected as well (not very surprised but you never know until it has been tested :-)).

[DirkB19]

Hi,

I've uploaded the GatewayW5100MQTTClient.ino to a UNO with W5100.

I have changed IP adresses to my Mosquitto broker (on Raspberry Pi) as instructed.

However,
I don't see the gateway connecting to the Mosquitto (in the /var/log/mosquitto/mosquitto.log on RPI) and also I don't see anything in the serial monitor. I've got 10+ sensornodes that work well when using another gateway (to OpenHab).
What am I overlooking here ?

The same hardware UNO+W5100 worked before as MQTTgateway(+broker), so I'm guessing it's not the hardware?

Any help is appreciated.
Thanks,
DirkB

[gregl]

@DirkB19

Hi Dirk - did you change the MAC address ( these need to be unique too and it could have the same one "DEADBEEFFEED" as your existing GW )

[mbj]

@DirkB19 If you do not see anything in the serial monitor for the gateway then the problem must be with the gateway itself. Have you observed that there is a special #define MY_W5100_SPI_EN to uncomment when compiling for an Uno with the shield installed ? If not, you can try that.

[DirkB19]

@mbj said:

MY_W5100_SPI_EN

Sorry for this NOOB question, but where is this to be uncommented.
I don't see it in the gateway sketch ?
I use this sketch GatewayW5100MQTTClient.ino

[mbj]

@DirkB19

It is looking like this, just uncomment the #define - line:

// W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
//#define MY_W5100_SPI_EN 4

[DirkB19]

@mbj

Thanks for the help, but I'm still very confused because OK, I found the line to uncomment.
I uncommented, but still nothing on serial monitor.
So then I see lines below this in the sketch and I realize that my radio is wired as follows ;
SCK -- Pin 13
MISO -- Pin 12
MOSI -- Pin 11
CS -- Pin 6
CE -- Pin 5
?
But there's no Pins 14,15,16 to be found on my W5100/UNO ? So I'm very confused ...

#if !defined(MY_W5100_SPI_EN) && !defined(ARDUINO_ARCH_SAMD)
#define MY_SOFTSPI
#define MY_SOFT_SPI_SCK_PIN 14
#define MY_SOFT_SPI_MISO_PIN 16
#define MY_SOFT_SPI_MOSI_PIN 15
#endif

// When W5100 is connected we have to move CE/CSN pins for NRF radio
#define MY_RF24_CE_PIN 5
#define MY_RF24_CS_PIN 6

[martinhjelmare]

@DirkB19

In this case I think pin 14-16 are meant to be aliases for analog pins A0-A2.

Read the build page for the Ethernet gateway. You have to wire the radio in a non standard way in combination with the 5100.

But it's optional when using the shield. You could enable the SPI for that instead, like you were talking about a few posts up.

[mbj]

@DirkB19 The Arduino pinouts are, to say the least, confusing and it helps to look at one of the pinout sketches you can find on the net, for example http://marcusjenkins.com/wp-content/uploads/2014/06/ARDUINO_V2.png. So the pins are, as Martin said, (A0-A2) which must be exactly as you had them wired before if you had a "previous version" working MQTT Ethernet gateway. I have such a gateway (nowadays used as a spare) but built with a nano and a W5100 unit and it compiled and worked right away using the GatewayW5100MQTTClient.ino sketch from the development branch.

As you see nothing in the serial monitor there must be something else. Even if you upload the sketch to a completely barebone UNO without radio or anything else attached you will get a message in the serial monitor, in this case:

0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0-beta)
0;255;3;0;9;Radio init failed. Check wiring.

So if you see nothing at all there is something really basic wrong.
Presumably your sketch compiles OK so I assume you have exchanged all Arduino libraries to the libraries which belong to the Mysensors development branch.