# Lattice1 WiFi Troubleshooting {% hint style="info" %} Here are the conditions for your Lattice1 to be able to connect to your network: * The Lattice1's WiFi module uses **2.4GHz** only - 5 GHz SSIDs will NOT show up on the device. You can try creating a separate 2.4 GHz-only network. * The supported encryption types are **WEP, WPA/PSK** and **WPA2-PSK.** * Your network's **name (SSID)** has to be shorter than **32 characters**. * Same goes for the **WiFi password**, also has to be **<32 characters**. {% endhint %} ## Troubleshooting ### A. Network not showing up on the Lattice1 {% hint style="danger" %} **The network you wish to connect cannot be set up to operate on 5 GHz only!**\ **Please make sure the conditions above are met before continuing.** {% endhint %} So, your network works on 2.4 GHz, uses one of the supported encryption types and the SSID is not too long. What now? #### 1. Refresh the list The first step here would be to refresh the page with available networks several times and going through all the pages - the scan sometimes does not capture every wifi network, especially in a location where there may be many other networks interfering. We have also seen a very small number of cases where the network's SSID showed up on its own after some time. #### 2. Try power cycling Try power cycling both your Lattice1 and your router. Unplug your Lattice1, unplug your router, let them both sit for 1 minute and plug them both back in. Your router may take some time to restart and renew internet access. When your router comes back alive, refresh the list of available networks on the Lattice1 and you should see yours. #### 3. Create a dedicated 2.4 GHz network (if you don't have one already) If this doesn't help, try turning autoswitching off (in case your router switches between bands with the same SSID) and create separate SSIDs for 2.4 GHz and 5 Ghz. If that's a pain, you can configure a 2.4 GHz guest network with an alternate SSID (you should be able to find out how in your router's manual). {% hint style="info" %} You can also try [**connecting manually via SSH**](https://docs.gridplus.io/lattice1-guides/connect-to-wifi-using-ssh). This requires an Ethernet connection. {% endhint %} ### B. "Unable to connect" error on a network your device can see #### 1. Try a 2.4 GHz phone hotspot Let's check if you can connect to another network to make sure the problem is not with the Lattice1's WiFi module. Please create a 2.4 GHz mobile hotspot and try connecting to it. If you can connect to your hotspot, the problem is most likely with your network's configuration. {% hint style="success" %} By default, your phone hotspot will most likely be on 5 GHz and this invisible to the Lattice. To turn on 2.4 GHz, look around for a "**Maximize compatibility**" option in hotspot settings. {% endhint %} If you haven't yet, also try connecting via Ethernet to see if your Lattice can get online at all. #### 2. Once again, make sure your network meets the conditions for a successful connection If you can connect to a 2.4 GHz phone hotspot, please go into your router settings and: * Make sure the encryption type used is one of these: WEP, WPA-PSK and WPA2-PSK * Make sure your SSID and WiFi password are shorter than 32 characters * Check if your **router** is not blocking the Lattice from accessing the internet * Check if your **firewall** is not blocking the Lattice from accessing the internet * Try turning **UPnP** on if it's off * Etc. Different router models have different settings, try searching for something obvious that could be a problem, something preventing the Lattice from connecting {% hint style="info" %} Router settings can usually be accessed by typing the router's IP address into the address bar on your browser (the IP itself should be on the router sticker) and using login credentials provided by your ISP, or by using a web app provided by the router's manufacturer. You should be able to find a guide on how to access your router settings in your router's manual - if you can't find it, try obtaining it from your ISP. {% endhint %} #### 3. Reset your Lattice's router If everything else fails, you can opt to reset the device router. You can do that by going to **System Preferences → Security & Privacy → Reset Router**. Please note this will change the **Device ID** you use to connect to apps. After your reset the router, power cycle the device and let it sit for 5-10 minutes before attempting to connect again. {% hint style="success" %} The steps above will resolve 99% of WiFi issue cases we've seen. {% endhint %} ### C. Other options #### 1. Change the Lattice IP address A very rare issue can be a cause of connection problems - the device can use the same subnet as your router - this means both the Lattice and your router have the same IP address. If this is the case, the two devices will overlap and this will cause the device to behave erratically - random disconnects, spotty connection, requests not being sent back to apps they were requested from, etc. This only happens if your router's IP address is **192.168.3.1** (this is the default Lattice IP address) - the ideal solution here is to change either the IP address of the Lattice1 or the router. Below you can find a guide on how to change the Lattice IP. First, you'll have to make sure you can connect to the device - since we're troubleshooting WiFi, your best bet here is connecting **via Ethernet**. Once your device is on your network, you will then [**SSH into your device**](/lattice1/lattice1-guides/how-to-communicate-with-your-lattice1-via-ssh.md) and use the following commands: ``` uci set network.wlan.ipaddr=192.168.9.1 uci commit network /etc/init.d/network restart ``` The **new IP address** from the first line can be whatever you want as long as it's unique within your network - we have used `192.168.9.1` as a general placeholder, but it's of course usable. After you change the Lattice IP, power cycle the device and try connecting again. {% hint style="info" %} Please note that if you ever reset the Lattice's router after changing the IP manually, you will have to re-do this as the IP will revert back to the default `192.168.3.1`. {% endhint %} #### 2. Just wait... We have seen a fair amount of WiFi issues over the years, and when everything else fails, one thing that has worked for some of our clients in the past was just **waiting** and trying again after some time. For usually unknown reasons, their networks suddenly showed up on their devices, or they were able to connect despite getting multiple errors before - without any changes to their network setup. So, just wait and try connecting again in a couple of hours. If that doesn't help, leave both your Lattice and your router unplugged overnight and give the Lattice another chance in the morning. #### 3. Use a WiFi2Ethernet adapter If you can connect the device via **Ethernet,** get it online and ready to sign transactions, but connecting via cable is not a viable long-term solution for you (your router is in another room, etc.), you can try getting a WiFi2Ethernet adapter such as [**this one**](https://www.iogear.com/product/GWU637/). #### 4. Contact GridPlus and/or a networking expert Feel free to join [**our Discord**](https://discord.gg/gridplus) or [**open a ticket**](https://gridplus.io/contact/) if you still can't connect after trying everything in the guide above. We'll do our best to help you. Also, consider consulting a networking expert in your area, there's only so much we can do without physical access to your location. {% hint style="success" %} **But definitely get in touch with us first and we'll see what we can do.** {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.gridplus.io/lattice1/lattice1-wifi-troubleshooting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.