Cannot connect to mqtt3.thingspeak.com
I have created a mqtt device in thingspeak, allocated a channel for pub and sub. I noted down the credentials for connection when the device was created. I tried to connect using the host mqtt3.thingspeak.com port 1883 and the supplied credentials(user name and password). I tried with node red (mqtt node) and also mqtt lense but still cannot connect. Would appreciate advice some advise. Thanks
댓글 수: 6
시간 내림차순
Thank Chris for the suggestion; I did tried couple of desktop client (mqtt lense and mqttspy) cannot connect for both; However when I try mqtt x, it connected. Not sure on the right track, It would appears that thingspeak need the unique clint id(which is the same as user name) and mqtt x is the only desktop client that allow entering the Client id (others are auto generated) and in nodered, you cant enter the client id and I want to get node red to work.
Is there anyway to get thingspeak to ignore clint id?
Cheers,
Ken
MQTTLense is no longer supported (I tried to install it to test if I could change client ID), and MQTTSpy seems to have a client ID in the configurations scripts I found here.
There is no way to get ThingSpeak to ignore the client ID. I'm pretty sure others on the forum have reported sucessful Node Red integration with ThingSpeak, but I havent done it myself.
Thanks Chris,
You are correct, I managed to connect to thingspeak via nodered after looking at the configaration a bit more. All good now. Appreciated.
Cheers,
Ken,
NZ
Ken,
Thanks for letting us know! Can you give us any more hints on what it took to make it work?
Also are you in New Zealand? "NZ"
-Christopher
Hi Chris,
Most nodered user seems to prefer the "nodered thingspeak node" to connect to thingspeak (which uses the thingspeak api) and is very easy to use but only allow for one feed at a time.
I wanted to try mqtt connection as it allows mutiple feeds with one transmission. The issue with my initial nodered mqtt setup was that I could not find the "client id" in the security tab in the nodered mqtt node (which only accept user name and password), so I assume that client id cannot be set. However, I found later that I can enter the client id in the connection tab. That was the problem (user).
Yes, I live in Auckland, New Zealand, a tinkerer and keen sailor
Cheers,
Ken
NZ
참여하려면 로그인하세요
