ZimaCube 7th Bay RGB lighting now has an official control protocol, so you do not need to flash CubeFX just to change colors or effects. The official firmware exposes an ESP32 Wi-Fi endpoint at 172.16.1.1 and accepts JSON commands for breathing, constant, and per-LED custom modes.
CubeFX remains an optional community firmware for users who want a different interface or deeper customization. If you prefer the stock firmware, use the official HTTP/JSON method and avoid reflashing the ESP32.
How the 7th Bay Lighting Works
The current 7th Bay LED protocol says the lighting controller is an ESP32 connected to a 13-LED WS2812B strip.
Connect to the Lighting Controller
The official firmware creates a Wi-Fi network named ZimaCube with the documented password homecloud. The controller is reachable at 172.16.1.1.
ping 172.16.1.1Set a Constant Color
{
"id": 2,
"data": [
{"h": 21, "s": 255, "v": 255}
]
}Send the JSON to the controller:
curl -X POST -H "Content-Type: application/json" -d @light.json http://172.16.1.1/postBreathing and Custom Modes
Mode 1 is breathing mode with adjustable speed. Mode 5 provides per-LED color/brightness control for all 13 LEDs. The official docs currently mark modes 3 and 4 as under development.
You Can Keep the Stock Firmware
This is the key change from the 2024 forum thread: official control documentation now exists. You can script the stock firmware without flashing a third-party image.
CubeFX Is Still an Optional Alternative
The community CubeFX project thread provides a custom firmware path for advanced users who intentionally want it.
OTA Firmware Updates
The ESP32 also exposes an OTA web interface. Do not upload unknown firmware binaries; keep a recovery copy and understand that custom firmware can change the protocol ZimaOS expects.
Use RGB for Status Automation
Because the control endpoint accepts JSON, you can map backup state, disk alerts, downloads, or local AI activity to colors from scripts without touching the storage subsystem.
The RGB control overview provides additional project context.
Convert HSV Values Before Sending JSON
The official protocol expects hue, saturation, and value on a 0โ255 scale. If your color picker uses degrees and percentages, convert those values before sending them to the ESP32.
Test One Simple Mode Before Automating
Start with constant-color mode and confirm the controller responds. Only then add scripts for backup status, disk alerts, or music effects. This separates network/protocol problems from automation logic.
Keep Automation Non-Critical
Use the LEDs as a visual convenience, not the only alert path for disk failures or backups. Hardware notifications should also exist in logs, email, monitoring, or another persistent channel.
FAQ
Do I need CubeFX to control the LEDs?
No. Current official firmware has a documented JSON/HTTP protocol.
How many LEDs are in the strip?
The official hardware docs specify 13 WS2812B LEDs.
Can I control each LED separately?
Yes, official custom mode supports per-LED HSV values.
Can I restore stock firmware after CubeFX?
Use the official OTA/firmware resources and confirm the correct hardware revision before reflashing.
