Hello all, I try to retrieve data from the Notification service of the Royal Netherlands Meteorological Institute (KNMI), but I do not have any experience with MQTT over Websockets and so this is quite new for me. Perhaps someone with more experience sees it immediately and can give a hint. The …

Try removing the :443 from the host name and set the port entry to 443

Thank you, Steve, for your quick response. Your suggestion to remove :443 after the host name and enter it in the port field does not work. As soon as you put :// in front of the host name, such as ws:// or wss:// the port entry field is disabled (greyed-out) I got the suggestion from: MQTT over …

It does work (I'm certain :thinking:) but I'm not in a position to try it out to show you. Will be home later. Hopefully someone will pop by with a quick how to before then. Note: you will need to send me (private message (click my avatar->message)) with details of your MQTT server if you want me t…

Are you able to try out the python example to see if that works?

Hello@Steve-Mcl I will send you the broker details in a PM. [Edit: Done] Hello @cymplecy Simon, thank you for jumping in. I think, you mean the python example at Notification Service . After a small modification of the script and inserting the CLIENT_ID and the TOKEN I got a positive result. I …

Great that you got that working - it verifies that your API key and all the other information is correct :slight_smile:

I think it defaults to 1883 if the port is not set , and the port cannot be set when using ws(s)://

If you need a temporary work around, you could set up a local broker. Talk to that over mqtt. Then get it to talk to the remote broker over websockets.

I have certainly had this working, though I don't have a working wss server at the moment. Looking at the server node setup I see that I entered the the port number in the same way you have, but it also shows as greyed out in the port field. I assume that I entered that field before filling in the…

MQTT over Websockets

General

FireWizard52 24 December 2023 18:55 9

Yes, as soon as you insert :// in front of the hostname, such as ws:// or wss:// the port field is disabled. Therefore I found the suggestion to add the port after the hostname.

See links above.

However playing with this gives not any results and it ends even in a crash of Node-RED.

Regards

Topic		Replies	Views
MQTT Broken URL and PORT General	16	3301	5 September 2018
Establishing a websockets-MQTT connection through Node-Red General	16	2883	14 November 2021
MQTT-In Not Connecting General	69	9053	7 November 2019
Websocket connection over MQTT Dashboard	2	962	24 May 2021
Error reading topics MQTT General	5	503	7 August 2019

MQTT over Websockets

Related topics