# Troubleshoot BrewZilla

### Wifi, Registration and Telemetry Issues

<table data-full-width="true"><thead><tr><th>Problem</th><th>Solution</th></tr></thead><tbody><tr><td><strong>Cannot open Captive Portal</strong></td><td>Check that WiFi is active on your mobile device</td></tr><tr><td></td><td>Select <strong>KegLand RAPT XXXX</strong> network</td></tr><tr><td></td><td>Enter password '<strong>kegland1</strong>' </td></tr><tr><td><strong>Cannot see KegLand RAPT XXX in my list of available networks</strong></td><td>Navigate to <strong>Settings</strong> and <strong>Enable WiFI</strong></td></tr><tr><td></td><td>Unplug the device for 30 seconds, then plug it back in and refresh the list of networks on your mobile device</td></tr><tr><td></td><td>This may already be connected to WiFi. Check the IP (STA) in <strong>Diagnostics</strong>. If this is populated with an IP address that is <em>not</em> 0.0.0.0 then this is already connected</td></tr><tr><td>"<strong>Selected Network is not connected to the Internet</strong>" <strong>error</strong></td><td>Select the <strong>KegLand RAPT XXX</strong> network and choose "<strong>Forget This Network</strong>"</td></tr><tr><td><strong>Device does not connect to my WiFi network</strong></td><td>Check that your network is broadcasting a 2.4gHz signal</td></tr><tr><td></td><td>Non alphanumeric characters in the SSID or password can cause issues - change these to simple (letters and numbers <em>only</em>) characters</td></tr><tr><td></td><td>Ensure you are selecting the correct network and inputting the correct password for that network</td></tr><tr><td></td><td>The network <em>must</em> have a password – the device cannot connect to an unsecured network</td></tr><tr><td></td><td>The device may already be connected. Check the IP (STA) in <strong>Diagnostics</strong>. If this is populated with an IP address that is not 0.0.0.0 then the deviceis likely already connected</td></tr><tr><td></td><td>Reboot the device by unplugging for at least 309 seconds</td></tr><tr><td></td><td>Reboot your modem/WiFi router</td></tr><tr><td></td><td>Try connecting to a different WiFi network</td></tr><tr><td></td><td>Turn off any VPN or anything that can block an outgoing signal on the router</td></tr><tr><td></td><td>If the above do not work, see <a href="#using-phone-as-hotspot">Using Phone as Hotspot</a> below</td></tr><tr><td><strong>Cannot see a Validation Code</strong></td><td>Connect the device to your WiFi network</td></tr><tr><td></td><td>Update the firmware - select <strong>Check for OTA update</strong> in <strong>Settings</strong></td></tr><tr><td><strong>Error when Registering device</strong></td><td>Check that the device firmware is up to date - select <strong>Check for OTA update</strong> in the <strong>DIagnostics screen</strong></td></tr><tr><td></td><td>The <strong>Validation Code</strong> may have timed out. Reboot the device by unplugging it for at least 30 seconds, then plugging it back in. Log out of the <strong>RAPT Portal</strong> and log back in</td></tr><tr><td></td><td>If the above steps do not work, reboot the network that the device is connected to. Once the network has rebooted,  reboot the device by unplugging it for at least 30 seconds, then plugging it back in. Log out of the <strong>RAPT Portal</strong> and log back in. Note: if using a modem and seperate wifi roters, reboot the modem and then the wifi routers in that order. </td></tr><tr><td></td><td>A corrupt firmware install can prevent registration. This can happen if a firmware download is interrputed, for example. If the above steps do not allow registration, please refer to <a href="rapt-device-boot-loop-troubleshooting-and-recovery-mode">RAPT Device Boot Loop Troubleshooting &#x26; Recovery Mode</a> to rollback firmware to a good version, then update to the current version</td></tr><tr><td><strong>Determine whether your device is connected to Wi-Fi</strong></td><td>To check this navigate to <strong>Diagnostics</strong> and check that it shows your network’s IP address next to <strong>IP (STA)</strong> - in the form 192.168.XX.XXX or similar. You can also check the WiFi AP (Access Point ) the device is connected to and the current WiFi signal strength</td></tr><tr><td><strong>Determine whether your device is registered to the RAPT Portal</strong></td><td>If the message "<strong>Register your device by pressing the select button to enter the main menu, then selecting the "Register Device</strong>" item in the main menu" is displayed, this is <strong>not registered</strong>. Please follow the steps outlined in <strong>Register Device</strong></td></tr><tr><td><strong>Cannot update firmware | 5379 Error</strong></td><td><strong>This is a network issue. The OTA Firmware Update could not be validated or was incomplete</strong>. Ensure your device is as close as possible to the router. Check signal strength in <strong>Diagnostics</strong></td></tr><tr><td></td><td>Ensure you have a strong 2.4gHz WiFi signal (not just 5gHZ). Check your signal strength against <a href="#signal-strength">this table</a></td></tr><tr><td></td><td>Make sure there are no VPNs in use, or filters or other potential issues set up in the router that can block an outgoing signal</td></tr><tr><td></td><td>If issues persist, reboot the device and also the modem</td></tr><tr><td></td><td>If the above do not work, see <a href="#using-phone-as-hotspot">Using Phone as Hotspot</a> below</td></tr><tr><td><strong>Cannot update firmware | 28674 Error</strong></td><td><strong>This is a network issue. The OTA Firmware Update could not be validated or was incomplete</strong>. Ensure your device is as close as possible to the router. Check signal strength in <strong>Diagnostics</strong></td></tr><tr><td></td><td>Error 28674 is an <strong>error opening an HTTP connection</strong>. Check your modem or router settings. A VPN, Firewall or other setting may be blocking outgoing connections - this is a common reason for this error</td></tr><tr><td></td><td>Ensure you have a strong 2.4gHz WiFi signal (not just 5gHZ). Check your signal strength against <a href="#signal-strength">this table</a></td></tr><tr><td></td><td>If issues persist, reboot the device and also the modem</td></tr><tr><td></td><td>If the above do not work, see <a href="#using-phone-as-hotspot">Using Phone as Hotspot</a> below</td></tr></tbody></table>

#### SIgnal Strength

<figure><img src="https://570278281-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUqN4sW0x2s4yh6iiT8NN%2Fuploads%2FcIkcwG6pWuQKIzRzB7rI%2FSIgnal%20Strength.png?alt=media&#x26;token=3008cc79-402c-4fc4-931e-bae66e2efd74" alt=""><figcaption><p>SIgnal Strength Table</p></figcaption></figure>

### Using Phone as Hotspot <a href="#using-phone-as-hotspot" id="using-phone-as-hotspot"></a>

If updating the firmware persistently fails or throws an error, and all troubleshooting steps have failed, then try using your mobile phone as a Hotspot to resolve this.

Using the phone as a Hotspot will typically solve firmware update issues of this kind

1: It helps eliminate potential network or modem/router issues which can cause problems that can be hard to isolate and resolve

2: It can help eliminate signal strength or poor WiFi connection issues as the phone can be positioned right next to the RAPT device when in Hotspot mode.

To connect to the phone Hotspot and update the firmware there are a few steps to follow

1. On the phone, turn WiFi **OFF**. When troubleshooting firmware download or network issues, we do not want to use the same network thus the phone must be disconnected from the WiFi network in order to do this
2. Enable **Personal Hotspot** (sometimes just called Hotspot) on your phone. This is typically located under the WiFi or Network menu in the Settings menu of the phone. On IOS this is under **Settings**/**Personal Hotspot**. The menu names will vary on Android depending on device
3. Enable **Maximise Compatibility** (on IOS) or **2.4gHz Network Only** (on Android - again, this will have different names depending on device/OS). This will help minimise issues when connecting
4. Once **Hotspot** is enabled on the device, following the steps in [Getting Started](https://docs.rapt.io/equipment/rapt-can-filler/getting-started) to connect to the phone Hotspot
5. Once connected, navigate to Settings/Check for OTA update on the RAPT Device

### General Troubleshooting

<table data-full-width="true"><thead><tr><th>Problem</th><th>Possible Cause &#x26; Solution</th></tr></thead><tbody><tr><td><strong>Pump not working</strong></td><td>P<strong>ump is blocked.</strong> The most common reason for a BrewZilla pump to stop working is due to blockage. The pump is easily accessible so the head can be removed and cleaned/unblocked. To prevent pump blockages <strong>always use the top screen when mashing</strong> or elevate the recirc tubing above the grain bed. Using the ball valve to control recirc speed can also help. <strong>If the recirc tubing contacts the grain bed it is common to have grain 'sucked back' into</strong> the pump causing blockages. Refer to <a href="../brewing-with-rapt-gen-4-brewzilla#pump-cleaning-and-maintenance">Pump Cleaning and Maintenance</a> for more information</td></tr><tr><td></td><td><strong>Cavitation</strong>. Cavitation during the boil can cause an airlock in the pump. Cycle the pump on and off briefly to clear this.</td></tr><tr><td></td><td><strong>Not cleaned properly.</strong> If the pump is not thoroughly cleaned after every use then sticky wort build up can cause the pump to fail or stop working. Ensure that hot (~50°C) StellarClean PBW solution is recirculated for at least 10 minutes after every brew day to prevent sticky wort buildup.</td></tr><tr><td></td><td><strong>Check for blockages.</strong> To determine if the pump is faulty or blocked remove the pump head when the BrewZIlla is empty and cool enough to handle. Inspect inside the pump head for grain or hop matter and clean as required. If not blocked, check to see if the impeller is spinning freely - sticky work buildup may prevent this</td></tr><tr><td><strong>BrewZilla making a clicking noise in operation</strong></td><td><strong>This is normal.</strong> The elements are controlled by robust relay switching and thus clicking will be heard when the power is set to less than 100%</td></tr><tr><td><strong>Mash temperature is different to probe temperature</strong></td><td><strong>This is normal.</strong> Due to grain having a large thermal mass the grain bed will not respond to temperature changes as quickly as the free flowing wort near the elements. Use of a <a href="https://kegland.com.au/products/rapt-bluetooth-thermometer-20-to-300c-20cm-htc-probe">RAPT Bluetooth Thermometer</a> allows for precise and accurate control</td></tr><tr><td><strong>Temperature reading error</strong></td><td><strong>Calibration issue.</strong> Select the Forget Calibration option from Settings to restore default calibration settings. If this clears the error re-calibrate following <a href="../manual-operation-with-the-digital-controller#temperature-probe-calibration">this guide</a>. Ensure that the two calibration points are at least 20°C apart to minimise errors</td></tr><tr><td><strong>Temperature reading not correct</strong></td><td><strong>Calibration issue.</strong> Select the Forget Calibration option from Settings to restore default calibration settings. If this clears the error re-calibrate following <a href="../manual-operation-with-the-digital-controller#temperature-probe-calibration">this guide</a>. Ensure that the two calibration points are at least 20°C apart to minimise errors</td></tr></tbody></table>