Hello everyone, I am having really strange problem and i am not able to understand why is it happening. I am saving the MQTT credentials in settings.js process.env. I am using google cloud iot so i need a jwt to connect to broker. I am generating a JWT and saving it in settings.js using python c…

I just connected a real time clock to my Raspi. I hope it will work. after that i will try this .. thanks a lot for your help! :slight_smile:

Since MQTT is using TCP/IP, different implementations have different keep-alive configurations. If you were running your own MQTT broker (like I do, for example), this might not be an issue; but when using a public service, like an IoT cloud service, they might drop connections after some time out …

I am having problem only on first start every morning. Thats means for example if i switch off my raspberryPI and then come back again next morning and switch it on, It doesnt not connect. And now if i restart/Shutdown(2nd restart) it again then it works without any problem through out the day. Firs…

Got it... sorry, I misunderstood your original post. So, this is definitely not a TCP/IP connection timeout issue. ... and not being a public IoT cloud user, will drop off the discussion.

No problem. Thanks anyway :slight_smile:

[image] hsn548: getting everytime the new generated JWT How have you shown that? When you say it connects ok if you restart node-red are you just restarting node-red or running the script again too? Does node-red auto run on system start? If so it will be trying to start initially with the…

[image] Colin: How have you shown that? [image] I am also saving that generated JWT in a file and then comparing it with $(MQTT_JWT). [image] Colin: When you say it connects ok if you restart node-red are you just restarting node-red or running the script again too? I have a shell sc…

[image] hsn548: I have a shell script which run the script first and then run the node-red. I am running this shell script in systemctl. So first i do "systemctl stop shell.service" and then "systemctl start shell.service" So after it does not run and you restart that means it is running the …

echo "Waiting for python script to success!" while output=$(python3 jwt.py) [ "$output" != 'status=done' ] do echo "The python script did not output 'status=done', repeating..." sleep 1 done echo "Yay! python succeeded. Let's run node-red" sleep 10 node-red Thats my shell sc…

[image] Colin: So after it does not run and you restart that means it is running the shell script again, so refreshing settings.js again yes [image] Colin: If after it fails to connect you stop node-red, but then start it not using the service, so just running node-red in a terminal for …

Very odd. If you don't use the service file at all, but stop node-red, run the script to update settings.js and then manually start node-red does it work?

Node-RED

Node-RED Forum

Node-Red MQTT node doesnt connect on every first start every morning?

General

Colin 5 March 2020 09:36 17

Ah yes, good thinking. You could try adding
After=multi-user.target
to the [Unit] section of the systemd service.

1 Like

Topic		Replies	Views
Google IoT connection MQTT to Node-Red using JWT? General	1	305	26 April 2020
MQTT Time Out / Random Disconnect General	14	1493	12 March 2022
Beginner's problem: No connection to MQTT General	11	1616	26 February 2021
Error: Disconnected from MQTT broker General	23	1233	6 February 2022
Node-red mqtt-in node not working for aws iot General	16	2958	31 December 2019

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Node-Red MQTT node doesnt connect on every first start every morning?

Related topics