How Do I Recover My JellyFish System After a Cloud Server Outage?
- JellyFish cloud server experienced an outage (AWS-hosted backend)
- Controller lost its cloud session token during the outage and did not automatically re-authenticate
- App cache contains stale offline status that does not update after server recovery
Problem Description
JellyFish Lighting uses Amazon Web Services for its cloud backend. During rare outage events, all controllers lose cloud connectivity simultaneously. After the outage resolves, some controllers may require manual reconnection steps to re-establish their cloud link.
Symptoms
- All JellyFish lights in the home lost app control at the same time
- Cloud App shows all controllers as offline simultaneously
- Lights continue running stored schedules but cannot be changed remotely
- After outage resolves, controller stays offline in the app even though neighbors' systems recovered
- Cloud App login fails or shows a server error message
Recognize these? Here's what usually causes it.
Common Causes
- JellyFish cloud server experienced an outage (AWS-hosted backend)
- Controller lost its cloud session token during the outage and did not automatically re-authenticate
- App cache contains stale offline status that does not update after server recovery
- Controller needs a power cycle to force a new cloud registration after extended outage
Most fixes happen in the first 3 steps.
Never perform a factory reset in response to a cloud outage — this will erase all your zone and schedule configurations without solving the outage. Power cycling and app-level reconnection steps are always sufficient for outage recovery.
Tools & Requirements
Step-by-Step Solution
Schedules Run Without Cloud
One key advantage of the JellyFish system: scheduled lighting continues to run even when the cloud is down, because the controller stores and executes schedules locally. Your lights will still turn on and off at the correct times during an outage.
Local Control During Outage
During a cloud outage, you can still control your lights locally using the controller's front panel or by connecting directly to the controller hotspot via the Designer App. This gives you manual color and pattern control even without internet.
September 2023 Outage Was the Major Reference Event
JellyFish experienced a significant cloud outage in September 2023. The recovery steps above are based on the official guidance released after that event and remain the standard reconnection procedure.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
During an active cloud outage, your JellyFish lights continue running stored schedules without interruption. You can also control lights locally via the controller front panel or by connecting directly to the controller hotspot through the Designer App.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- JellyFish cloud server experienced an outage (AWS-hosted backend)
- Controller lost its cloud session token during the outage
- App cache contains stale offline status
- Controller needs a power cycle to force a new
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by JellyFish Lighting System owners.
SwitchBot RGBIC Neon Rope Light, 5M Matter-Certified Neon...
APPECK Smart RGBCW Outdoor Wall Lights 2 Pack, 1600LM Hig...
Lutron Deluxe Diva Smart Dimmer Kit for Caseta Lighting w...
As an Amazon Associate we earn from qualifying purchases.
Need More Help? JellyFish Lighting Support
Note: The contact information below connects you directly to JellyFish Lighting's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.