Tesla Gateway or app offline?
Your Powerwall still works without internet, but you have lost app monitoring and remote control. The issue is usually WiFi band mismatch, router firewall port 1883 blocked, or Gateway lost network credentials. Follow these 6 diagnostic steps for Gateway 2 and Gateway 3.
Tell us your Gateway model, WiFi band (2.4GHz or 5GHz), whether you changed routers recently, and what LED colour you see. We diagnose your Gateway connection and firewall settings remotely.
Book Remote Diagnostic — from £75 → Tesla Powerwall hubIndependent — not affiliated with Tesla Inc.
⚡ Safety Warning
Do not open your inverter or interfere with DC cabling. Solar panels produce live DC voltage whenever exposed to light. Always use your DC isolator switch and contact a qualified solar engineer for hands-on fault diagnosis.
Step-by-step Gateway offline diagnosis
Work through these steps in order. Step 1 checks the physical LED. Step 2 covers WiFi band compatibility — the most common cause. Steps 3–6 cover reconnection methods, Ethernet, firewall port rules, and power cycling.
Look at the LED indicator on your physical Gateway unit. Solid green = connected and communicating with Powerwall. Flashing green = enabled but no communication with Powerwall — local connection issue. No light = no power to the Gateway — check your circuit breaker or wall outlet. On Gateway 3: green plus light blue = ready for initial commissioning. Flashing red = firmware update in progress — do not power off, wait for completion.
This is the #1 cause of Gateway offline issues. Gateway 2 supports 2.4GHz ONLY — not 5GHz. If your router defaults to 5GHz-only or has merged 2.4/5GHz bands, the Gateway cannot connect. Gateway 3 supports both 2.4GHz and 5GHz. If you recently changed routers, your new router may have different default band settings. Check your router admin panel and ensure 2.4GHz is available and your Gateway is connecting to it. Also verify signal strength — minimum 2-3 bars required. If the Gateway is too far from the router, move it closer or add a WiFi repeater.
Open the Tesla app and tap on your Powerwall. Go to Settings > WiFi. Select your home network and enter the password. Wait 2-3 minutes for the Gateway to reconnect to Tesla servers. If the Tesla app cannot reach your Gateway remotely, you can connect directly to the Gateway's local WiFi network: look for a network named TEG-xxx (where xxx is your unit's serial number, usually printed on the Gateway). Connect your phone to this network — no password required. Then open the Tesla app again — it will now see the local Gateway — and configure your home WiFi from there.
Tesla recommends configuring BOTH Ethernet and WiFi for maximum reliability. The Gateway will auto-select whichever connection is available and fastest. Use minimum CAT5 cable (CAT6 or CAT7 preferred). Verify the cable is fully seated in both the Gateway jack and your router port — push until you hear a click. If Ethernet still is not working, try connecting to a different port on your router — one port may be faulty. Inspect the cable for any visible damage or bent pins.
The Gateway uses the MQTT protocol on port 1883 to communicate with Tesla servers. Some routers block this port by default or after firmware updates. Log into your router admin panel and look for firewall rules or port blocking settings. Port 1883 must be open for outbound traffic. Also check if MAC address filtering is enabled — if it is, whitelist the Gateway's MAC address (usually printed on the unit or visible in the Tesla app). After any router firmware update or router change, power cycle both your router and the Gateway — turn them off for 30 seconds, then turn them back on.
Turn off the Gateway circuit breaker, wait 30 seconds, turn it back on. Allow 5 minutes for the system to fully reconnect and sync with Tesla servers. The LED should change from offline (no light or flashing) to solid green when successfully connected. If still offline after 5 minutes, press the Gateway reset button for 1 second — this resets WiFi settings without erasing your Powerwall configuration or historical data. Your Powerwall continues to operate normally even when the Gateway is offline — you lose app visibility and remote control, but backup power, solar charging, and self-consumption all work as configured. Contact STS for a remote diagnostic if it remains offline — we can check your router port rules, WiFi settings, and Gateway firmware.
Gateway offline vs Powerwall offline — why it matters
When your Gateway goes offline, the communication bridge between your home and Tesla servers is broken, but your Powerwall itself continues to operate independently. The battery system is designed to work in autonomous islanding mode — it detects local solar generation, powers your home, manages backup energy, and provides power cuts without needing internet or app instructions. All of this happens locally. The Gateway is just the remote monitoring layer. This is why your backup power works perfectly fine even when the app shows offline — the Powerwall never relied on cloud servers for its core functions.
The Gateway's job is to relay your system status to the Tesla app, allow you to change settings remotely, enable Storm Watch (UK Met Office weather integration), and push firmware updates. If the Gateway is offline, you cannot change settings from the app, you cannot see live power flows or battery SOC, and Storm Watch cannot auto-charge your battery before bad weather. But the Powerwall operates exactly as you configured it last — backup reserve stays set, self-consumption mode stays active, and the system keeps charging and discharging. STS diagnoses Gateway offline issues by checking your WiFi connectivity, router firewall rules, and Gateway firmware — independent of Tesla and your installer.
Gateway offline — common questions
Your Gateway has lost internet connection. Common causes: WiFi disconnected after you changed routers, port 1883 blocked by your router's firewall, your new router defaults to 5GHz but your Gateway is Gateway 2 (2.4GHz only), or a temporary Tesla server outage. The good news: your Powerwall still operates normally without internet. You lose app monitoring and remote control, but backup, solar charging, and self-consumption continue as configured on your local system.
The LED indicator tells you the Gateway's connection status. Solid green = connected and communicating with Powerwall and Tesla servers. Flashing green = enabled but not communicating with Powerwall — local connection issue. No LED = no power to the Gateway — check your circuit breaker. Flashing red = firmware updating — do not power off, wait for completion. Green plus light blue (Gateway 3 only) = ready for initial commissioning. If you see no LED but the Gateway has power, the LED itself may be faulty.
Standard method (if the Tesla app can reach your Gateway): Tesla app > Powerwall > Settings > WiFi > select your home network and enter the password > wait 2-3 minutes. If the app cannot reach your Gateway: connect your phone to the Gateway's local WiFi network (look for TEG-xxx, where xxx is your serial number) > open the Tesla app — it will now find the local Gateway > configure your home WiFi from the app. After you change routers, always power cycle both your router and the Gateway for at least 30 seconds to clear old network associations.
Yes — absolutely. The Powerwall operates completely independently of internet. Backup power works offline during outages, solar charging works without internet connection, and self-consumption discharges to your home as configured. Internet is only needed for: Tesla app monitoring and remote control, firmware updates and patches, Storm Watch (advance Met Office weather alerts to pre-charge before storms), and server-side analytics. If your Gateway is offline, all core battery functions continue uninterrupted. Your configured backup reserve, charging mode, and self-consumption mode remain active.
Three things usually happen when you change routers. First, WiFi credentials change — your old router's SSID and password no longer work, but the Gateway still has the old credentials stored in memory. Second, frequency band issue (Gateway 2 only) — if your new router defaults to 5GHz-only or merged 2.4/5GHz bands, Gateway 2 cannot connect because it only supports 2.4GHz. You must ensure 2.4GHz is available on your new router. Third, port 1883 blocked — your new router may have stricter firewall settings, and port 1883 (used for MQTT communication) must be open for outbound traffic. Fix: reconnect via the Tesla app or directly to the TEG-xxx local WiFi, confirm your router is set to 2.4GHz or has dual-band, and power cycle both devices for 30 seconds.
Gateway still offline after these steps?
If you have checked the LED status, verified your WiFi band (2.4GHz for Gateway 2), reconnected via the app, checked port 1883 in your router firewall, and the Gateway still remains offline — the issue may be a Gateway hardware fault, a router configuration problem, or a DNS issue. We review your WiFi settings, router firewall rules, and Gateway firmware remotely. Independent from Tesla and your installer.