Mosquitto publish to AWS cannot publish

Installing and Using OpenWrt
1

Hi all,

I'm trying to publish on AWS console with mosquitto client.
I have 2 devices:

An OpenWrt board ( OpenWrt 15 ) and an Onion Omega 2 board ( OpenWrt 18.06 )

I'm following this tutorial: AWS mosquitto Onion Omega

I have installed on my OpenWrt 15 board:

libmosquitto - 1.4.10-1
libmosquitto-nossl - 1.4.10-1
mosquitto-client - 1.4.10-1
mosquitto-client-nossl - 1.4.10-1
mosquitto-nossl - 1.4.10-1

I think that the setup is ok, but if I try to publish something with

mosquitto_pub -t \$aws/things/XXXX/shadow/update -m '{"state": {"desired": {"temperature": 1 }}}' -q 1

I do not see anything on the AWS console and I don't get any error from the OpenWrt 15 board.

While with the Omega board it works.
The Omega board has installed:

libmosquitto-ssl - 1.5.9-2
mosquitto-client-ssl - 1.5.9-2
mosquitto-ssl - 1.5.9-2

Could it be that the oldest version of mosquitto that does not support the same config file?

How can I see the mosquitto log ?
I'm able to ping the AWS broker with the OpenWrt 15 board

Any suggestion?

Thanks

2

I would use the "-d" option, to get debugging messages, and see if there is any difference.

3

This is what I get:

First is OpenWrt_19 and then OpenWrt_15

root@OpenWrt_19:~# mosquitto_pub -d -t \$aws/things/xxxx/shadow/update -m '{"state": {"desired": {"temperature": 22 }}}' -q 1
Client mosq- sending CONNECT
Client mosq- received CONNACK (0)
Client mosq- sending PUBLISH (d0, q1, r0, m1, '$aws/things/xxxx/shadow/update', ... (44 bytes))
Client mosq- received PUBACK (Mid: 1, RC:0)
Client mosq- sending DISCONNECT
root@OpenWrt_19:~#


root@OpenWrt_15:~# mosquitto_pub -d -t \$aws/things/xxxx/shadow/update -m '{"state": {"desired": {"temperature": 22 }}}' -q 1
Client mosqpub/8038- sending CONNECT
Client mosqpub/8038- received CONNACK
Client mosqpub/8038- sending PUBLISH (d0, q1, r0, m1, '$aws/things/xxxx/shadow/update', ... (43 bytes))
Client mosqpub/8038- received PUBACK (Mid: 1)
Client mosqpub/8038- sending DISCONNECT
root@OpenWrt_15:~#
4

All i can think is that the old client is somehow incompatible with the server.

5

Yes probably it is.

Thanks