Ctrlk
FiveM HostingCustomer SupportDiscord
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Smart Lights, Outlets & Buttons

Control RGB lights, smart outlets, and SwitchBot button pressers in each scene frame.

Smart Lighting requires the Pro version of Sonoran Studio and the Windows or macOS desktop app.

What are Smart Lights, Outlets & Buttons?

Sonoran Studio controls RGB light color and power, smart outlet on/off state, and SwitchBot Bot actions in each scene frame. With the FiveM, LSPDFR, and ER:LC integrations, you can build custom patterns for emergency lights, hazards, and turn signals. The same realtime Sonoran CAD and Radio events that power Studio widgets can trigger device sequences for transmissions, unit updates, calls, dispatch activity, and panic changes.

Supported Devices

Studio only lists devices that expose the controls required by the selected provider. A product having Wi-Fi, Bluetooth, Matter, Alexa, or Google Home support does not by itself guarantee compatibility.

Smart lights are third-party products. Their manufacturers may change or retire cloud and local APIs. Match the exact brand, family, and requirements below before purchasing.

Amazon links point to an exact product page when the model could be verified. Links marked Amazon search open a model-specific search; confirm the model or family shown below before ordering.

As an Amazon Associate, Sonoran Software earns from qualifying purchases.

Smart Lights

Wyze Color

Wyze connects through the Wyze cloud and requires the four account values shown in Studio.

Setup

  1. Add each color bulb or lightstrip in the Wyze app and confirm it is online.

  2. Open the Wyze developer console, sign in with the same account, and create an API key.

  3. In Studio, select Wyze Color and enter the Wyze email, password, key ID, and API key.

  4. Select Connect Wyze & find lights. The credentials are encrypted on this computer; use Re-login if they change.

Supported color bulbs:

Wyze Light Strip and Light Strip Pro are detected by the current integration and receive a single solid RGB color across the strip. Segment and effect control are not supported. Because Wyze does not publish device-control rate limits for this endpoint, use frame delays of 1,000 ms or longer for the most reliable sequences.

Official product references: Bulb Color A19 and BR30 and Light Strip / Light Strip Pro.

Philips Hue

Philips Hue uses the local Hue Bridge API. A Hue Bridge is required, including for products that can also connect over Bluetooth. Studio supports Hue lights that report full color controls; buy the White and color ambiance version, not White or White ambiance.

Setup

  1. Add the Hue Bridge and color lights in the Hue app and confirm every light works.

  2. Keep the Bridge and Studio desktop app on the same local network.

  3. Press the round link button on top of the Hue Bridge.

  4. In Studio, select Philips Hue, leave the optional fields blank, and select Connect Hue Bridge. Studio discovers the Bridge and creates a local API username. Advanced users may enter an existing Bridge IP and API username instead.

Compatible Hue families include color A19/BR30 bulbs, Lightstrip Plus and Gradient lightstrips, Play light bars, Go, Iris, Bloom, and Signe lights when paired to a Hue Bridge. Studio sets one color for the whole light and does not address gradient segments or entertainment areas.

The Hue API recommends approximately 10 light commands per second. Studio now queues Bridge writes at 100 ms intervals; use frame delays of at least 100 ms, and longer delays for large groups. See the official Hue rate-limit guidance and Hue Bridge overview.

Govee Wi-Fi

Govee connects through the official cloud API and requires a Govee API key. Studio only displays devices for which Govee reports both powerSwitch and colorRgb. This capability check is more reliable than assuming every product in a family supports the API.

Setup

  1. Add every light in the Govee Home app and confirm it is online over Wi-Fi. Bluetooth-only products cannot use this connection.

  2. Sign in to the Govee developer portal with the account that owns the lights and request an API key.

  3. In Studio, select Govee Wi-Fi, paste the API key, and select Connect Govee & find lights.

  4. Studio lists only devices whose API capabilities include both RGB color and power control, then loads the built-in scenes, DIY scenes, and snapshots Govee exposes for each compatible light.

API-verified examples from Govee's official supported-model list:

Many other Govee Wi-Fi products may appear automatically when the API reports both required capabilities. Bluetooth-only products are not supported. Scene availability varies by model, firmware, and the capabilities Govee exposes for that specific light. Lights without reported scene capabilities continue to use RGB color. RGBIC segment layouts, DreamView, music effects, and Govee device groups are not controlled.

Create and edit custom effects in the Govee Home app. Re-scan Govee in Studio after changing them. The frame editor displays a Govee scenes area containing the named built-in scenes, DIY scenes, and snapshots returned for each light. Select a scene card to add that light and scene to the active frame; select it again to remove it from the frame.

Govee scenes are per-device rather than account-level groups. Studio retrieves built-in scenes and DIY scenes through Govee's official scene endpoints, preserves the exact capability type, instance, and value returned for that light, and sends that tuple through the device-control API. This is important because Govee models can expose DIY scenes under different capability types.

Activating a scene powers the light on and then applies the selected effect. Govee does not expose a separate scene-off command. To replace an active effect, use another scene or a custom color in a later frame. Removing a scene card from a frame means Studio sends no command for that light during the frame; it does not turn the light off.

Govee permits 2 control requests per second per device and 12 per second per account. Turning a light on with a new color or scene requires two requests. Studio queues requests at 500 ms per device and 84 ms per account; use frame delays of 1,000 ms or longer for cloud reliability.

Nanoleaf

Nanoleaf uses its local OpenAPI on port 16021; no cloud account or hub is required. Enter the light's IP address or local hostname in Studio. In the Nanoleaf app, choose Connect to API, or hold the controller power button for 5–7 seconds, then select Pair & find Nanoleaf within 30 seconds.

Setup

  1. Put the Nanoleaf device and Studio desktop app on the same local network, then find the device IP in the Nanoleaf app or your router.

  2. Open the pairing window by choosing Connect to API in the Nanoleaf app or holding the controller power button for 5–7 seconds.

  3. In Studio, select Nanoleaf, enter the IP address or local hostname, and leave the token blank for first-time pairing.

  4. Within 30 seconds, select Pair & find Nanoleaf. Studio saves the returned local token; an existing token may be pasted when reconnecting.

Studio validates that the device reports RGB hue and saturation controls before adding it. Supported RGB families documented by Nanoleaf include:

Elements panels are not listed because they do not expose the RGB controls Studio requires. Studio controls one solid color for the entire device; panel layouts, per-panel colors, and effects are not controlled.

Nanoleaf's official OpenAPI recommends no more than 10 updates per second. Studio enforces a 100 ms interval per device. See the official OpenAPI overview, Light Panels OpenAPI, and Matter Wi-Fi OpenAPI model list.

LIFX

LIFX connects directly over the official local LAN protocol. No LIFX cloud token, account sign-in, or hub is required. Keep the Studio desktop app and the lights on the same local network, then select Scan local network for LIFX.

Setup

  1. Add the color lights in the LIFX app, update their firmware, and confirm they can display RGB colors.

  2. Keep the lights and Studio desktop app on the same local network. Guest Wi-Fi or client isolation must be disabled between them.

  3. Allow local UDP port 56700 through the computer firewall if discovery traffic is restricted.

  4. In Studio, select LIFX and then Scan local network for LIFX. No account, hub, address, or token is required.

Studio queries the vendor and product ID of every responding device and checks it against LIFX's official machine-readable product registry. A device is listed only when that exact product declares color: true. This covers the RGB versions of LIFX Color A19/A21/BR30/GU10 bulbs, Mini Color, Clean, Downlight, Z/Lightstrip, Beam, Tile, Candle Color, Neon, String, Ceiling, Spot, Path, PAR38, Tube, Luna, Mirror, and RGB outdoor families in the current registry.

Amazon links for registry-backed RGB families:

LIFX White, White-to-Warm, Day & Dusk, Filament, and Switch products are excluded because they do not declare RGB color capability. Unknown product IDs also remain hidden until their capabilities can be verified. Studio applies one solid color to the entire light; it does not address individual Beam, Tile, Candle, String, or lightstrip zones.

LIFX discovery and control use UDP port 56700. Studio requests an acknowledgement for every command and retries a missing acknowledgement once. LIFX warns clients against excessive LAN message rates but does not publish a numeric request ceiling, so Studio serializes commands per light. Start with frame delays of 100 ms or longer and increase the delay if Wi-Fi is congested. See the official LAN discovery guide, SetColor/SetPower messages, and packet header specification.

WLED

WLED connects directly to each controller's local JSON API. Studio requires WLED 0.13 or newer so it can verify that at least one segment reports RGB capability. Enter the controller's IP address or local hostname; separate multiple controllers with commas.

Setup

  1. Install WLED 0.13 or newer, configure the controller and LED output, and verify RGB colors from the WLED web interface.

  2. Open the WLED Info screen, WLED app, or router and copy the controller's IP address or .local hostname.

  3. In Studio, select WLED and enter the address. Separate multiple controllers with commas.

  4. Select Connect WLED controller. Studio verifies RGB capability and represents each controller as one light controlling all configured segments.

Studio treats each WLED controller as one light. A color update switches every configured segment to the Solid effect and applies the same RGB color and full brightness across those segments. Existing per-segment colors and effects are intentionally replaced while a Studio scene is active.

The linked controller appears on WLED's official compatible-controller list under Domestic Automation. WLED supports many other pre-flashed and DIY controllers, but the controller, power supply, strip voltage, data signaling, fusing, and wiring must all match. Follow WLED's hardware guidance rather than treating every product whose listing says “WLED” as equivalent.

The WLED API explicitly advises clients not to make requests in parallel. Studio puts all WLED discovery and control requests through one sequential queue and uses the one-call tt: 0 transition for immediate changes. Use frame delays of 100 ms or longer for reliable animations, especially with several controllers. See the official WLED JSON API and getting-started guide.

Smart Outlets

Wyze

Wyze connects through the cloud. Studio supports Wyze Plug and each independently exposed outlet on Wyze Outdoor Plug. Use the same Wyze email, password, key ID, and API key described above.

Govee

Govee connects through the official cloud API key. Supported outlet models are H5080, H5081, H5082, H5083, and H5086.

Shelly

Shelly works locally with Shelly Plus Plug US and Gen1, Gen2+, Gen3, or Gen4 devices that expose relay or switch outputs. Studio discovers Gen2+ devices through local mDNS. Enter an IP address or hostname for Gen1 devices. No hub or cloud connection is required. Device authentication must be disabled.

SwitchBot

SwitchBot supports Plug, Plug Mini (US), Plug Mini (JP), and Plug Mini (EU). It uses official OpenAPI v1.1. Enter the token and secret from Developer Options. An internet connection is required.

Button Pressers

SwitchBot Bot

Studio supports the SwitchBot Bot through SwitchBot's official OpenAPI v1.1. Configure the Bot's mechanical movement and operating mode in the SwitchBot app. The Bot must be connected through a SwitchBot Hub with Cloud Services enabled so it appears through the API.

  1. In the SwitchBot app, add the Bot, connect it to a Hub, and configure it as Press Mode, Switch Mode, or Custom Mode.

  2. Enable Cloud Services or Third-party Services for the Bot.

  3. Obtain the account token and secret from Developer Options in the SwitchBot app.

  4. In Studio, open Other, select SwitchBot, enter the token and secret, and select Connect SwitchBot & find Bots.

Studio reads the operating mode reported by each Bot before displaying it. Press Mode and Custom Mode provide a Press action. Switch Mode provides separate On and Off actions. If Studio cannot verify a Bot's mode, it does not list that Bot instead of risking an incorrect command.

Select the Bot and action for any frame just like a light or outlet. Studio sends the documented press, turnOn, or turnOff command when that frame runs. See SwitchBot's official Bot API reference.

Provider Timing Reference

Provider
Connection
Studio guard
Recommended frame delay

Wyze

Cloud

One combined action per light

1,000 ms or longer

Philips Hue

Local Hue Bridge

100 ms between Bridge writes

100 ms or longer; increase for large groups

Govee

Cloud

500 ms/device and 84 ms/account

1,000 ms or longer

Nanoleaf

Local network

100 ms/device

100 ms or longer

LIFX

Local UDP

Acknowledged commands, one queue per light

100 ms or longer

WLED

Local HTTP

One global sequential request queue

100 ms or longer

Shelly

Local HTTP

Direct on/off per outlet

100 ms or longer

SwitchBot

Cloud

Signed OpenAPI command per plug or Bot; 10,000 API calls/day account limit

1,000 ms or longer

Creating Device Sequences

Device sequences tell Studio which lights, outlets, or button pressers to use and how long each frame remains active. Each game or CAD/Radio widget event has its own saved sequence.

1. Choose a game source

Open Smart Lighting in the Sonoran Studio desktop app. Under Choose your game, select FiveM, LSPDFR, or ER:LC. The scene editor shows the persistent lighting states supported by that game, FiveM/LSPDFR gameplay moments when available, and the CAD and Radio widget events.

2. Connect your devices

Under Connect devices, choose your provider and follow the connection steps. After Studio discovers the devices, they are available in every scene and frame.

3. Select the event

Under Build event scenes, use Scene event to select the event family you want to configure, such as Emergency lights, Health threshold, Transmission started, Status changed, or Panic changed. When a family has multiple choices, Studio adds a second selector beside it. Every final event choice saves a separate sequence.

The grouped choices are:

  • Status changed: Any status, Available, Unavailable, Busy, En route, or On scene.

  • Transmission started / ended: My transmission, Other user transmission, or Any transmission. A configured scoped scene takes priority; otherwise Studio falls back to the matching Any transmission scene.

  • Radio emergency call: Ringing or Talking.

  • Panic changed: Started or Ended / cleared.

  • Health threshold: Drops below or Recovers above, with the 0–100 percentage box beside the selector.

No active game event is the fallback scene used when FiveM, LSPDFR, or ER:LC is not reporting another active game-lighting state. Panic active (continuous) is the persistent panic scene; Panic changed contains the optional one-shot start and clear scenes.

4. Build the frames

The first frame is created for you. Select smart lights with colors and power, smart outlets with on/off state, or SwitchBot Bots with their available Press, On, or Off action. When compatible Govee lights report scenes, a separate Govee scenes area appears below the device list. Select a built-in scene, DIY scene, or snapshot card to assign that specific light and effect to the active frame. Then set Delay to next frame in milliseconds.

Select Add frame to copy the selected frame, then change its devices, colors, states, or delay. Drag frame cards to reorder them. A sequence can contain up to 40 frames, and each frame delay can be between 50 and 60,000 milliseconds.

The Sonoran Studio lighting sequence editor showing three frames for a panic event
A three-frame panic sequence using different colors and lights in each frame.

Each frame can control a different set of devices. A light, outlet, or Bot not selected in a frame remains unchanged during that frame.

The Sonoran Studio frame editor with light selection, colors, and delay controls
Select the lights and colors for the active frame, then set the time until the next frame.

5. Test and save

Changes save automatically on this computer. Select Test once to play Frame 1 through the final frame one time before going live.

When a live game or unit-status state occurs, Studio loops that saved sequence until another state takes over. A gameplay-moment or CAD/Radio widget-event sequence plays once, holding each frame for its configured delay, and then resumes the newest active game or unit-status scene. A newer one-shot event replaces one already playing, while active panic lighting blocks unrelated events. Testing, direct light control, or another sequence cancels the sequence currently playing.

FiveM and LSPDFR Gameplay Moments

FiveM and LSPDFR report the same native-backed gameplay moments. Configure them under FiveM & LSPDFR moments in the scene selector. Each scene is optional and plays once when the transition occurs.

Scene event
When it runs

Weapon drawn

The player changes from unarmed to armed

Weapon holstered

The player changes from armed to unarmed; changing weapons emits holstered, then drawn

Player died

The player entity changes to dead

Player revived

The player entity changes from dead to alive

Travel · On foot

The player leaves a vehicle

Travel · Vehicle

The player enters a road or other non-air/non-water vehicle class

Travel · Aircraft

The player enters a helicopter or plane

Travel · Watercraft

The player enters a boat

Health threshold > Drops below

Usable player health crosses below the percentage you set

Health threshold > Recovers above

After low health, usable health crosses above the percentage you set

Set each percentage in the Threshold box shown beside the Health threshold event, or under Choose your game > Health event thresholds after selecting FiveM or LSPDFR. The defaults are Drops below 35% and Recovers above 50%. Studio requires the recovery value to be above the lower value, creating a gap that prevents rapid switching near one boundary. These settings apply to both smart-device scenes and Streamer.bot actions.

Player revived deliberately covers both respawns and framework revives. GTA's entity natives report dead versus alive, but do not identify which recovery flow a server or mod used.

CAD and Radio Widget Events

The Studio desktop app receives these events through the same authenticated realtime connection used by the overlay widgets. Configure any of them under CAD & Radio widget events in the scene selector.

Scene event
When it runs

Transmission started

My, another user's, or any radio transmission begins

Transmission ended

My, another user's, or any radio transmission ends

Radio channel changed

Your active Radio channel changes

Radio emergency call

An emergency call rings or someone talks on it

Radio tone

A tone plays in your Radio client

CAD tone

A tone addressed to your signed-in CAD client plays

Status changed

Any update or the selected CAD status becomes active

Call attached

You attach to a different CAD call

Attached call changed

The currently attached call updates

Call detached

You detach from the active CAD call

Call note

A dispatch notification is identified as a call note

Dispatch notification

Any other CAD dispatch notification arrives

Panic changed

A visible panic starts or ends / clears

Location-only unit updates do not trigger Status changed > Any status, preventing routine location refreshes from repeatedly interrupting lighting. Any status is a one-shot scene; a named status scene remains active until the unit status changes. Widget-event scenes are optional: an event with no saved frames leaves the current lighting scene unchanged.

Integrated Games

FiveM

FiveM can connect through the latest Sonoran CAD FiveM resource or through the standalone Sonoran Studio resource. The standalone option does not require a CAD community and sends only to the Studio desktop app on the player's computer.

Install the standalone resource

  1. Download the standalone FiveM resource.

  2. Extract the ZIP's [sonoran_studio] folder directly into the server's resources folder.

  3. Add exec @sonoran_studio/sonoran_studio.cfg to server.cfg.

  4. Remove any other line that starts sonoran_studio, including ensure sonoran_studio or an ensured parent folder. Only use the exec line above.

  5. Restart the server and keep the Sonoran Studio desktop app open while playing.

Do not run the standalone resource alongside the Sonoran CAD FiveM resource; both contain the Studio bridge and would report every event twice. The default desktop port is 9990. Players using a different local Studio port can run /setstudioport PORT in FiveM.

Automatic resource updates are enabled by default. Run sonoranstudio update in the server console to check immediately. If the resource reports an updater permission, helper, or folder-layout error, reinstall the complete ZIP and confirm that server.cfg uses only the bundled exec line.

FiveM scenes include emergency lights, turn signals, hazards, and the gameplay moments listed above. Sonoran CAD unit statuses, calls, Radio activity, and panic events remain available when the player is also signed into the corresponding Sonoran community.

LSPDFR

The Sonoran Studio LSPDFR plugin synchronizes emergency lights, left and right indicators, hazards, officer details, location, and callout activity through RAGE Plugin Hook. The plugin itself only connects to the Studio desktop app on your computer. When you are signed in, the desktop app sends validated overlay events through your authenticated Studio session.

You need LSPDFR, RAGE Plugin Hook, the Sonoran Studio Windows app, and Studio Pro or Sonoran One.

Install the plugin

  1. Download the LSPDFR integration.

  2. Close GTA V and RAGE Plugin Hook.

  3. Extract the ZIP into your Grand Theft Auto V folder. Confirm this file exists: Grand Theft Auto V\Plugins\SonoranStudio.LSPDFR.dll.

  4. Open RAGE Plugin Hook settings and enable Load all plugins on startup.

  5. Open the Sonoran Studio Windows app, go to Lighting, and select LSPDFR.

  6. Start GTA V through RAGE Plugin Hook and launch LSPDFR. Keep Sonoran Studio open while playing.

Supported lighting and overlay data

Feature
LSPDFR support

Emergency lighting

Emergency lights, left indicator, right indicator, and hazards

Gameplay moments

Weapon draw/holster, death/return, travel type, and configurable health lower/higher crossings

Unit HUD

LSPDFR persona name, agency, current street/area, and derived duty status

Attached Call

A locally generated call ID, callout name, and callout street/area after you accept it

Dispatch Notification

The callout name, message, and advisory when LSPDFR presents a callout

Radio Transmission

Not available from the native LSPDFR API

Panic

Not available from the native LSPDFR API

LSPDFR gameplay moments run the same one-shot scenes as FiveM. Its overlay updates can also run the Status changed, Call attached, Call detached, and Dispatch notification event scenes configured in Studio.

Studio derives the unit status from the LSPDFR callout lifecycle: Available while patrolling, En Route after accepting a callout, On Scene near the callout position, and Unavailable while off duty. LSPDFR does not expose the player's callsign/unit number, a postal code, or a standard call priority/response code through its native API. These fields remain blank or use your configured widget fallback. Set overlay location precision to Full to show LSPDFR street and area names; Postal only cannot show an LSPDFR location because no postal is available.

Callout packs control the metadata they expose. If a pack omits a friendly name, message, advisory, or position, Studio shows the remaining supported fields without inventing the missing value.

This support uses LSPDFR's documented callout lifecycle and functions from the official LSPDFR API project. Gameplay moments use GTA entity, weapon, ped, and vehicle natives through RAGE Plugin Hook's documented native invocation API, cross-checked against the CitizenFX GTA V native documentation. The callout field and handle patterns are also demonstrated by established open-source integrations including External Police Computer, ReportsPlusListener, and FirstResponseGPT.

The plugin sends changes only to 127.0.0.1:9990; it does not connect directly to a game server or expose a public port. If it does not load, open the RAGE Plugin Hook console with F4 and run LoadPlugin "SonoranStudio.LSPDFR.dll", then check RagePluginHook.log for a Sonoran Studio message.

ER:LC

Smart lighting for ER:LC reads the lighting and siren controller in the Roblox window. Sonoran CAD and Radio are not required.

Leave the ER:LC ELS controller visible while playing. On macOS, allow Sonoran Studio under Screen & System Audio Recording when prompted. Detection remains on your computer; screenshots are never saved or uploaded.

PreviousStream Widgets
NextStream Automations

Last updated

Was this helpful?