I am based out of the US, so I can’t speak from experience with regard to Australian network hardware, but it couldn’t hurt to set it to the correct jurisdiction. Conversely, since you mentioned that you had issues with Ethernet also, it might be an unrelated issue.
@jsimmonds brings up a good point about the administration panel of the router- checking to make sure the device is getting onto the WiFi at all is a good next step. Once we have that information, we can know if the problem is the network configuration or the account configuration. It may also be possible to perform a WiFi network scan (to check for devices on the network) using a tool such as Fing. If the device is at least online, it will show up on the network as
farmbot-wxyz or similar.
If the device is in fact on the WiFi network, it is possible to see device logs by visiting
0.0.0.0 is the IP address of the device (you can find the device IP using Fing or your router admin panel). The logs will stream in real-time.
Based on your screenshot, it looks like your device was recently online (2 months ago) with FBOS v11 (14 months old). You mentioned that you flashed the latest version (which is good), but I would double-check that the configurator screen says “14.4.1” when you open it, just in case the new version did not properly flash.
Depending on how much information was originally on your account, you could also consider performing an ACCOUNT RESET, as we have seen a very small percentage of users that had old/corrupt data on their web app account that prevented the bot from coming online. Depending on how much saved work you have, you may want to hold off on trying this until other troubleshooting means have been exhausted.
Please let us know if the router shows the bot on the network and we can go from there.