Networking Issues about snapmaker2-controller HOT 4 OPEN

2. When connected to wifi the device keeps going unreachable. It claims to be still connected to the wifi (and still prompts to "disconnect" if previously connected to luban) but does not respond to pings (or connection requests from Luban). Or, more confusingly, will respond (ping) to one device but not the other device (e.g. will not respond to a ping from the router but will respond to a ping from my laptop or vice versa).

I have exaclty the same issue since the update from Luban 3 to 4 and update from the Snapmaker 2.0 A250 firmware to the latest version. The Snapmaker has 4 meters distance to the WiFi Access Point and there is no wall or other objects in between. I'm not able to print directly from the PC anymore. I have to copy the files to the USB and then plug the USB in the Snapmaker. Could we please investigate furter to solve this for all?

from snapmaker2-controller.

+1 for this feature (forget Wifi).
Also, please show MAC address on Settings -> About Machine.

These two are very important when you are using MAC address filtering.

from snapmaker2-controller.

Another vote for forget-wifi. MAC addr would be nice.

There's a common new-machine workflow that goes something like this:

1. connect to the wide-open guest Wifi network, troubleshooting as necessary
2. connect to the secure Wifi network once step 1 succeeds

When doing this on the Snapmaker, any problems (bad password, timeouts) with the secure network cause a default connection to the guest network. If all computers are on the secure network, Luan etc cannot connect to the Snapmaker.

Another problem with the controller wifi setup is that selecting a protected network requires re-entering the password every time. Maybe that should be the long-press option when a password has already been stored.

UPDATE: Just a quick follow-up. I disabled the guest network so that the snapmaker controller would be forced to connect to the password-protected network. The controller was unable to do so, which makes me wonder:

a) if the initial setup uses different connection code, which is able to handle WPA
b) if the initial setup failed to connect, but reported success
c) if the controller is incapable of connecting to WPA-protected networks
d) if the controller does not support long passwords (~ 30 characters)

from snapmaker2-controller.

I have my WiFi router standing 2 meters above Snapmaper 2.0, and machine can't even find my wireless networks, but finds networks from my neighbours. This ticket wasn't even answered within over two years. This is unacceptable.

Maybe we all should fill a support issue to stop being ignored by snapmaker support?

from snapmaker2-controller.