Back to JellyFish Lighting Guides
JellyFish Lighting

Why Are My JellyFish Lighting Schedules Not Working?

JellyFish Lighting GuideSmart Lighting
medium difficulty 10-20 minutes 41 views 1 found helpful Updated
This guide applies to: JellyFish Lighting JellyFish Lighting System (JellyFish Pro 2 Controller)
At a glance — most common causes
  • Conflicting schedules exist between the JellyFish Designer App and the Cloud App — they can override each other
  • Controller timezone is set incorrectly, causing schedule triggers to fire at wrong times
  • Schedule was saved to the Designer App only and not synced to the Cloud App
10-20 minutes9 solutions coveredmedium level

Expert Review & Technical Scope

DeviceJellyFish Lighting JellyFish Lighting System
Model CoverageJellyFish Pro 2 Controller
Fix Time10-20 minutes
DifficultyMedium
Required ToolsPhone with JellyFish Cloud App, JellyFish Designer App (to clear conflicting schedules)
Network / ProtocolWi-Fi / app-based troubleshooting context

Problem Description

Your JellyFish Lighting scheduled lighting events are not firing — lights do not turn on, change patterns, or turn off at the configured times. JellyFish schedules are managed differently between the Designer App and Cloud App, and running both simultaneously is the most common cause of schedule conflicts.

Symptoms

  • Lights do not turn on at the scheduled time
  • Lights do not turn off as scheduled and stay on all night
  • Scheduled pattern changes do not trigger
  • Schedule worked previously but stopped after an app update
  • Some schedules fire correctly while others do not
  • Schedules disappear or reset after power cycle

Recognize these? Here's what usually causes it.

Common Causes

  • Conflicting schedules exist between the JellyFish Designer App and the Cloud App — they can override each other
  • Controller timezone is set incorrectly, causing schedule triggers to fire at wrong times
  • Schedule was saved to the Designer App only and not synced to the Cloud App
  • Multiple overlapping schedule events are creating conflicts
  • Controller lost its time synchronization after an extended power outage
  • Schedule was accidentally set to a one-time date rather than a recurring pattern

Most fixes happen in the first 3 steps.

Warning

Clearing all schedules from the Designer App will remove them permanently from that app. However, schedules saved in the Cloud App are unaffected and will continue to work normally.

Tools & Requirements

Phone with JellyFish Cloud AppJellyFish Designer App (to clear conflicting schedules)

Step-by-Step Solution

1

Manage Schedules Only in the Cloud App

JellyFish officially recommends managing all schedules exclusively in the Cloud App. The Designer App is intended for initial installation and pattern design only. If you have schedules set in both apps, they can conflict and override each other unpredictably. Delete the Designer App from your phone after setup is complete and manage all ongoing schedules in the Cloud App only.

2

Switch to Sunrise and Sunset-Based Triggers

The Cloud App supports astronomical sunrise and sunset triggers that automatically adjust with the seasons. These are significantly more reliable than fixed-time schedules for exterior lighting. Replace fixed-time ON and OFF rules with a Sunset trigger for the on time and a Sunrise or fixed late-night time for off. This eliminates drift as days lengthen or shorten throughout the year.

3

Verify Controller Internet Connectivity

JellyFish schedules are cloud-executed, meaning the controller must have active internet access to receive and trigger scheduled events. Open the Cloud App and check the controller status. If it shows offline, schedules will not fire until connectivity is restored. Restart the controller by powering it off for 30 seconds and confirm it reconnects to the app before relying on scheduled triggers.

4

Test a Schedule 5 Minutes in the Future

After making any schedule changes, create a test schedule set to fire 5 minutes from the current time and watch the lights. This confirms the scheduling system is working before you rely on overnight or next-day schedules. If the test schedule fires correctly but your regular schedule does not, the issue is in the rule configuration — check AM versus PM, the correct days of the week, and that no override is active.

5

Delete and Recreate Problem Schedules

If a specific schedule consistently fails to trigger, delete it entirely from the Cloud App and recreate it from scratch. Do not edit an existing failing rule — delete it and build a new one. Corrupted or partially saved schedule entries can appear correct in the interface but fail silently. After recreating, run the 5-minute test to verify the new rule fires before saving it for daily use.

Quick Solutions

Delete Designer App Schedules to Prevent Conflicts
Verify Controller Timezone Setting
Check Schedule Recurrence Settings
Rebuild Conflicting Schedules

Still having issues? This is usually the deeper cause below.

Schedules that skip randomly are usually a daylight-saving holdover — delete and recreate the schedule to clear the corrupted entry.

Pro Tip

After resolving schedule conflicts, test by temporarily setting a schedule 5 minutes in the future and confirming it fires correctly. This confirms the scheduling system works before you rely on an overnight Off schedule.

Real-World Insight

Thermostat issues that keep returning are often caused by stale backup-battery memory holding old settings across power cycles without the user realising.

What Usually Goes Wrong
  • Conflicting schedules exist between the JellyFish Designer App and
  • Controller timezone is set incorrectly,
  • Schedule was saved to the Designer App only and
  • Multiple overlapping schedule events are creating conflicts
  • Controller lost its time synchronization

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.