mqtt activation

jidus

Hi,
I just activated mqtt on my dingz, but the broker doesn't seem to receive any messages. Do the Dingz switches have to be restarted to get the mqtt publishing messages?
As far as I understood, with FW 1.3.30, it's not possible yet to restart the Dingz with an API request. Is this correct, an if yes, is the restart only possible by cycling the Mains?

jidus

I restarted the Dingz and that was still not working. I checked the network traffic with Wireshark and I see packets sent by the Dingz to the broker. It means so that the problem is not on the Dingz side.

epi

I do not remember if I had to restart the button... but yes in 1.3.30 power cycle is the only way.

this is my service config as an example. maybe it will help 🙂
(I use http://mqtt-explorer.com/ to read queues from my mqtt server and test it...)

{
"mystrom": true,
"homekit": false,
"rest_api": true,
"panel": true,
"aws": true,
"discovery": true,
"udp_search": true,
"aws_notifies": false,
"ssdp": false,
"mdns": true,
"mdns_search": true,
"homekit_configured": false,
"cloud_ping": false,
"broadcast_period": 5,
"mdns_search_period": 60,
"remote_buttons": {
"enable": false,
"targets": {
"btn1": null,
"btn2": null,
"btn3": null,
"btn4": null,
"input": null,
"pir": null
}
},
"mqtt": {
"uri": "mqtt://dingz:dingz@192.168.x.y:z",
"enable": true,
"server.crt": null
}
}

jidus

In the mean time if found the problem. The issue was that the broker is running in WSL on Windows and the port used for the mqtt communication (1883) was not forwarded to WSL by default.