Closed TommyA52 closed 1 month ago
Have found out that as meshagent is a services it can be stopped att restarted by sudo systemctl restart meshagent. This seems to give some improvement. Startup time approx 5 minutes Still to long time for our need. Close this issue and write a new one in Meshagent issues
See above
Using a rpi zero W for connecting an industrial equipment to internet occasionally (for remote service). At power up the rpi starts a python script which open a local hotpot allowing the user to submit wifi ssid and password by a web interface. Then converts the rpi to a wifi client and tries to connect to Meshcentral. It works but take a long time (10-15 minutes or so) for the meshagent to connect. Understand that the reason is that meshagent increase the time between the attempts when it doesn’t succeed. How solve this? Have tried to kill the meshagent at startup and then let the python script start the meshagent again when connection is established but has not succeeded to get this working so far. Very thankful for help with this!