MQTT Publisher stopped working

[DrRob]

Hi,

I’ve been using MQTT Publisher for several years without issues. Yesterday I noticed that it has stopped working. I updated the firmware a few days ago, so the change may have occurred with that. It’s an RUTX11 on RUTX_R_00.07.13.1.

I have a client that sends messages such as “temperature” to topic “router/get”, and was previously receiving a reply on topic “router/(serial-no)/temperature”.

According to https://wiki.teltonika-networks.com/view/Monitoring_via_MQTT, my client should be sending messages to “router/(serial-no)/(parameter-name)”, so something has changed, I guess I’ve been using an old method, but if I do this:

mosquitto_pub \
    -h 192.168.32.1 -p 1883 \
    --cafile ca/ca.crt --cert ca/client.crt --key ca/client.key \
    -t 'router/get' \
    -m "myid"

in one terminal and this in another:

mosquitto_sub -v \
    -h 192.168.32.1 -p 1883 \
    --cafile ca/ca.crt --cert ca/client.crt --key ca/client.key \
    -t '#'

then I can see my query message appear on the subscriber side but there’s no reply from the router.

I’ve tried disabling and re-enabling MQTT Publisher, and I’ve tried rebooting – neither helped.

What am I doing wrong?

Thanks,
Rob.

[DrRob]

(I had to edit the message above – apparently you can’t use angle brackets in a post here…)

[DrRob]

I’ve realised that I made a mistake in the above – my test should have been:

mosquitto_pub \
    -h 192.168.32.1 -p 1883 \
    --cafile ca/ca.crt --cert ca/client.crt --key ca/client.key \
    -t router/get \
    -m id

and

mosquitto_sub -v \
    -h 192.168.32.1 -p 1883 \
    --cafile ca/ca.crt --cert ca/client.crt --key ca/client.key \
    -t '#'```

but I've tried that too, and it still doesn't work.

[DrRob]

No answer, so I figured out how to use the REST API instead, which is actually better because far more info is available via that route.