01-08-2025, 11:24 PM
Very happy with the afterburner but got stuck on getting remote controlling to work.
My setup is rasberry running mosquitto broker, connected to wifi-1 and afterburner connected on wifi-2, and the webbcontent on https://mrjones.id.au/afterburner/mqtt.html for access. I use a dyn-dns service for getting current ip to wifi-1 even if changing, and I use port forward on wifi-1 to the rasberry. One forwarding for tcp port and one for websocket.
I have managed to configure the afterburner to connect to the broker on the tcp port and I can subscribe and receive status topics from the afterburner using mosquitto_sub to the broker so that seem to be working fine working.
But I can not connect webbcontent to the broker on the websocket port.
Now doing a test setup on wifi-1 location without the afterburner and was thinking I should see successful connection status in the webbcontent and in mosquito broker log (all logs enabled) even though afterburner not connected(it and wifi2 is currently off-line when I'm testing), and even though no afterburner topics are pusblished. Correct?
I could verify that the brokers listener on the websocket port is working, by using python paho and creating a websocket connection to the dyn dns address with the port(3030) I forward to the websocket listener port (8000). And I can publish topics and subscribe to see them when subscribing on the tcp port (1883).
Both my test-subscriber, test-pubslisher, broker and the webb content are on same wifi wifi-1, but broker and test subscriber are on one machine while test publsiher and the webbcontent are on another machine.
I have mqtt user and pasword configured in broker. And I have put same in webbcontent dialog as in my test connection.
Webb content keeps trying to connect but fail.
In the webbcontent i see print Socket error AMQJS0007E Socket, and then it changes to Connection Timout
I can see the JS webbcontent fails on mqttws31.js:979 "this.socket = new WebSocket(wsurl, ["mqtt"]);", but I only see failed connection. Noting in the mosquitto broker log about the webbcontent trying to connect.
If I use chrome I get wss and if firefox ws, but looks same error.
Any ideas? Where am I thinking wrongly.
Best regards David in Sweden
My setup is rasberry running mosquitto broker, connected to wifi-1 and afterburner connected on wifi-2, and the webbcontent on https://mrjones.id.au/afterburner/mqtt.html for access. I use a dyn-dns service for getting current ip to wifi-1 even if changing, and I use port forward on wifi-1 to the rasberry. One forwarding for tcp port and one for websocket.
I have managed to configure the afterburner to connect to the broker on the tcp port and I can subscribe and receive status topics from the afterburner using mosquitto_sub to the broker so that seem to be working fine working.
But I can not connect webbcontent to the broker on the websocket port.
Now doing a test setup on wifi-1 location without the afterburner and was thinking I should see successful connection status in the webbcontent and in mosquito broker log (all logs enabled) even though afterburner not connected(it and wifi2 is currently off-line when I'm testing), and even though no afterburner topics are pusblished. Correct?
I could verify that the brokers listener on the websocket port is working, by using python paho and creating a websocket connection to the dyn dns address with the port(3030) I forward to the websocket listener port (8000). And I can publish topics and subscribe to see them when subscribing on the tcp port (1883).
Both my test-subscriber, test-pubslisher, broker and the webb content are on same wifi wifi-1, but broker and test subscriber are on one machine while test publsiher and the webbcontent are on another machine.
I have mqtt user and pasword configured in broker. And I have put same in webbcontent dialog as in my test connection.
Webb content keeps trying to connect but fail.
In the webbcontent i see print Socket error AMQJS0007E Socket, and then it changes to Connection Timout
I can see the JS webbcontent fails on mqttws31.js:979 "this.socket = new WebSocket(wsurl, ["mqtt"]);", but I only see failed connection. Noting in the mosquitto broker log about the webbcontent trying to connect.
If I use chrome I get wss and if firefox ws, but looks same error.
Any ideas? Where am I thinking wrongly.
Best regards David in Sweden