<font face="Arial, Verdana">Our scripts delete these config files if they see the ssid, try to connect and fail. The then assume it is a wrong password. I guess if the connection is not perfect or some timings are bad this might cause some problems. Did not think making a own wlan handling is so hard.</font>
One temporary solution would be editing
/usr/local/Repetier-Setup/ManageWifiAccess
after you have successfully connected. Comment line155
<font face="Arial, Verdana"># nmcli connection delete "$P1" ifname $WLAN &> /dev/null</font>
<font face="Arial, Verdana">whcih is the one responsible for the delete. If you see complete connect logic:</font>
<font face="Arial, Verdana"><div> connect)
prepareConnect
nmcli connection up "$P1" &> /dev/null
ret=$?
if [ $ret == 0 ] ; then
echo "OK"
else
nmcli connection delete "$P1" ifname $WLAN &> /dev/null
echo "Failed"
fi
;;
you see it starts the connection and if that fails it removes it. If I do not remove it and it would be invalid I also get into trouble since AP will always switch on/off as it tries to reconnect over and over again. Have to think how to solve both problems the same time. Maybe making a separate delete call and trying several times on networks that worked in past.
</span></font></div>