Unable to connect after access point conversion

Merlin246

Hello,

I recently changed by wifi settings to be an access point as I had a demonstration in an area where I could not connect to the available wifi. I am now back home and trying to restore it back to it's original configuration. I have removed the M552 S2 from the config file and replaced the original commands:

M550 P"ToolChanger" 					; Set machine name
M587 S"[network id]" P"[password]"		; WiFi Settings
M552 S1					                                ; Enable WiFi Networking
M586 P0 S1 								; Enable HTTP
M586 P1 S0 								; Disable FTP
M586 P2 S0 								; Disable Telnet

However there are some issues.

The wifi does not start automatically, I have to connect with a USB and use YAT to send the M552 S1 command, then the blue light starts blinking and then turns solid and I can connect to the IP
I cannot connect using the machine name, I've even tried typing out the http:// part as well. This worked fine before, never an issue.

I do not know what I am doing wrong, any help would be greatly appreciated.

Edit: including more information
Duet 2 Wifi
RRF: 3.3
Using the AngryIP scanner, it shows a green dot showing a device at that IP but n/a for the hostname.
The machine name shows at the top of the tab.

Update 1: I included a M552 S0 before the M550 command, the wifi connection now starts automatically. However the connect-by-name is still not working.

T3P3Tony

@merlin246 said in Unable to connect after access point conversion:

M587 S"[network id]" P"[password]" ; WiFi Settings

do not have M587 in config.g it is designed to be used one to add the wifi network.
so that command running is interfering with the M552 S1 so try removing it. (just see the update the M552 S0 is needed before the M587 so that explains that. Still remove the M587 as every time it runs it writes the the ESP flash unnecessarily)

Merlin246

@t3p3tony Thanks for the suggestion, will remove that.

It appears after restarting my laptop, I can now access the web interface using the machine name. No idea what networking black-magic happened but alas the problem has been resolved.