Thanks...a link to the code that generates it is helpful, but I was hoping for a more understandable explanation of what's what. Tks.

Call me ignorant, but where can I go to understand what all this means:

110-110-0 s=0,c=1,t=1,pt=7,l=5,sg=0:43.0

110 is obviously the node id and in this case 43.0 is the reading, but where can I go to fully understand what all the other parts of the string refer to?

TIA

I've ordered a new W5100 module - this time the red mini W5100 board missing the SD Card slot to see if I have better luck. Still keen to see code for an ENC based MQTTClientGateway though, as this will take a while to arrive...

I downloaded and installed the development branch and got the MQTTClientGateway running on an UNO with a W5100 shield (that I'm suspicious of, in terms of its reliability). The sketch runs great for a while publishing data to Mosquitto on my Mac Mini, but then stops responding after a while. I'm pretty sure the cause of the problem is the ethernet shield as it bombs out when running other sketches - the webserver one for example.

I have a few of these ENC28J60 boards and I'd like to use one of those instead, but have had some problems.

http://www.aliexpress.com/item/ENC28J60-LAN-Ethernet-Network-Board-Module-for-arduino-25MHZ-Crystal-AVR-51-LPC-STM32-3-3V/1956963721.html

I notice in the MQTTClientGateway sketch that I should just need to comment out the one W5100 Ethernet.h library and substitute with the UIPEthernet.h one, but I tried that and had no joy. Does anyone have a working sketch based on the ENC28J60 that they could post, along with the wiring diagram to connect that board in along with any additional tweaks necessary to get it running on an Uno? Thanks in advance. Cheers.

I think my biggest challenge is understanding when to combine the additional sensor in the main loop or when to put it in another. The whole idea of interrupts is baffling to me too.

OK. I've got the gateway to compile and get the following:

Started!
0;0;3;0;9;read: 110-110-0 s=1,c=1,t=0,pt=7,l=5:13.2
0;0;3;0;9;read: 105-105-0 s=0,c=1,t=1,pt=7,l=5:70.0
0;0;3;0;9;read: 110-110-0 s=0,c=1,t=1,pt=7,l=5:58.3
0;0;3;0;9;read: 105-105-0 s=0,c=1,t=1,pt=7,l=5:69.9
0;0;3;0;9;read: 110-110-0 s=0,c=1,t=1,pt=7,l=5:58.2
0;0;3;0;9;read: 105-105-0 s=0,c=1,t=1,pt=7,l=5:70.0
0;0;3;0;9;read: 110-110-0 s=0,c=1,t=1,pt=7,l=5:58.3
0;0;3;0;9;read: 105-105-0 s=0,c=1,t=1,pt=7,l=5:69.9
0;0;3;0;9;read: 110-110-0 s=0,c=1,t=1,pt=7,l=5:58.2
0;0;3;0;9;read: 110-110-0 s=0,c=1,t=1,pt=7,l=5:58.3
0;0;3;0;9;read: 105-105-0 s=0,c=1,t=1,pt=7,l=5:69.8
0;0;3;0;9;read: 110-110-0 s=1,c=1,t=0,pt=7,l=5:13.3
0;0;3;0;9;read: 110-110-0 s=0,c=1,t=1,pt=7,l=5:58.5

I can ping the MQTTClinetGateway from another machine and I've confirmed Mosquitto is running OK with a series of pub/subs from other machines/devices and that side of things is working perfectly fine.

I'm not seeing any of the above gateway readings publish to my broker. Thoughts?

Cheers.

@TD22057 said:

@John-Connolly You may want to the try the client gateway from this thread: http://forum.mysensors.org/topic/524/mqtt-client-gateway
It's a real MQTT client (point it at your Mosquitto broker) which I find easier to understand than the pseudo-broker that the MQTT gateway uses.

That's EXACTLY what I need/want! Thanks! I'll give it a shot the second the new kit arrives from AliExpress...which is taking its time.

I've just built the MQTT gateway as I'm planning to replace the serial one I have in place currently, since I understand MQTT/IP comms a lot better than I do serial. I've built it but I can't connect to it with an MQTT client like MQTT Spy or the command line MQTT tools. I can ping it, but it won't let me connect in other ways.

I've built the gateway with a W5100 shield (which I just don't trust) and messed around with the pin assignments/SOFTSPI etc - I can see the gateway receiving the sensor updates if I open serial monitor. I had a similar issue with some basic webserver tests with that W5100 shield. I should throw it away.

I'm waiting for some new ethernet modules (ENC28J60-based) and will give it another go then. The next step will be to get it bridged to Mosquitto on my Pi. I'll be back...

Scratch that...I figured it out. In the rules file, I needed to add a extra comma after the first chunk of mapping. As it stood, I presume it failed to process the whole rule, as there was a syntax error (missing comma) which mean't the 'list' of mappings were incomplete. Added a comma and all was right once again.