Control4 User Guide

1. Add the Driver

You require one instance of the Rithum Control4 driver in your project per physical Rithum Switch or Rithum Switch Pro.

There are two Rithum drivers for Control4 (see the bottom of the Control4 plugin release notes to download them).

• "Rithum Switch" driver - Use this if you have no need for the thermostat integration
• "Rithum Switch Thermostat" driver - Use this to take advantage of the thermostat features

Current driver version: 019.0. Requires Rithum Switch firmware 5.3.0+; the audio features additionally require the Control4 plugin 1.3.0+ on the switch.

⚠️ Upgrading from v18? The Thermostat driver is NOT a drop-in update — updating it in place can leave the Control4 processor unresponsive. See section 11: Upgrading from v18 before touching an existing installation. (The standard, non-Thermostat driver can be updated in place.)

The Thermostat driver has multiple proxies for the climate zones.

2. Add switch IP address

In the IP Network Connections tab, double click on the switch and enter an IP address for it.

NB: you must do this before attempting to setup the Rithum side, or the connection will not be established.

3. Select Lighting Loads

Next to the Lights option, press Select to then select which lighting loads to make visible to that Rithum Switch / Pro. You can simply select all loads, one or more rooms of loads, or select at the load level.

4. Advanced Lighting Scenes

Every scene from every Control4 Advanced Lighting Scene agent is pulled through to Rithum automatically — no selection or binding required. Toggle-capable ALS scenes track their on/off state on the switch.

• Use the ALS Scene picker + ALS Scene Second Label property to customise the second line of text shown under a scene's name (defaults to "Advanced Lighting").
• The list rebuilds automatically as agents change; the Refresh ALS Scenes action forces a rebuild if it ever looks out of date.

5. Set Custom Scene Names

For each switch, set a number of scenes (up to 5 per switch). Scenes have two Type options: 

1. Static - The Scene Name will pull through to Rithum as the top label (label 1) on the scene; label 2 will be the zone name that the switch is within in your project
2. Toggle - Set a "when off" label and a "when on" label, one of which will pull through to label 1 as necessary. The Scene Name will pull through as label 2.

Need more scenes, or the same scene on every switch? Use Global Scenes (next section) — they are shared project-wide and don't count against the per-switch limit.
 

6. Global Custom Scenes

Global Scenes are owned by the driver and shared across the whole project: define them once and they can be triggered from any paired Rithum Switch, with no per-switch configuration.

1. On any one driver instance, set Number of Global Scenes (up to 40).
2. Name each scene and choose its type (Static / Toggle) in the Global Scene properties — same labelling behaviour as per-switch scenes (section 4).
3. Trigger your automation from them as described in section 7.

Global Scenes appear on every switch's Scenes screen alongside that switch's own scenes.

7. Configure Scene Actions

Your senes can then be used to control almost anything in Control4, either as Button Bindings...

...or within Programming.

This applies to per-switch scenes (section 5) and Global Scenes (section 6) alike. Per-switch scenes expose their button-link connections on that switch's driver; Global Scene button links are created automatically on the master driver instance — bind keypads or attach programming to those, or use the scene activated/deactivated events in programming. Advanced Lighting scenes (section 6) need nothing here — they fire their agent's scene directly.

8. Rithum Stat

See this guide on Rithum Stat to understand how it works.

The Heat Actions (Heat On / Heat Off) and Cool Actions (On/Off, Low/Mid/High). Can be assigned in various places.

a) In Connections

b) In Programming

c) On the Rithum side as a trigger to any integration, which could be:

i) a relay directly controlled via Rithum (e.g. keep the call for heat outside of Control4)

ii) a Control4 scene. There's no real reason you would do this instead of configure it in Control4, but it's useful to understand for completeness

The Thermostat driver provides a Control4 thermostat proxy for every Rithum Stat zone: primary Heating and Cooling, Secondary Heating and Secondary Cooling, and a Hot Water (Switched) zone for schedulable on/off loads such as hot water, a towel rail, or a fan. The Hot Water/Switched zone is homeowner-schedulable from the switch.

Each zone has its own demand relay connection (plus fan-speed relays for the cooling zones) in the Connections tab — bind them exactly as for the primary zones. Heat/Cool scene trigger actions can be assigned for the secondary zones the same way as the primary ones (requires plugin 1.3.0).

9. Audio Zones — (new)

Expose Control4 audio rooms as audio zones on the Rithum Music screen: zone selection, transport (play/pause/skip), per-zone and group volume/mute, zone grouping, now-playing with artwork and streaming-service attribution badges (Spotify, TIDAL, TuneIn, etc.), and favourites. Each source also offers a "Now Playing" entry that routes that source into the zone (resuming sources that hold their own queue, such as Sonos).

1. Audio Zones — select which Control4 audio rooms to expose (up to 10).
2. Audio Sources — select which sources are offered inside the zones. All are selected by default. Recommended: deselect local media library sources such as My Music (DLNA) — local libraries can't currently be started from Rithum — start them from a Control4 Navigator.
3. Volume Step — how much each volume press changes the level.

Favourites. The favourites offered on Rithum are the Control4 favourites saved against each audio source (the Control4 Media Database). Radio station and music-service favourites can be started directly from a Rithum audio zone, even when the room is off.

• Starting content from Rithum is via favourites and presets only — catalogue browsing is a Control4 Navigator feature not available to third-party products.
• For third-party sources such as Sonos: set the source driver's Sync Favorites To Media Database property to On and make sure the driver is correctly associated with its device, or no favourites will appear for that source.
• Local libraries (legacy My Music): playback can only be started from a Control4 Navigator. Control4 has deprecated My Music; its DLNA-based replacement is expected to support favourites, at which point local content becomes startable from Rithum too.

Multi-room grouping. Grouping follows Control4 semantics — rooms are added to a live session: at least one zone in the group must be playing, and a room can only join a session its audio hardware can reach (e.g. a room can only join sessions its audio hardware supports — Rithum reports that zone as failed rather than hanging).

Spotify. Sessions started by a streaming app outside Control4 (e.g. Spotify Connect) cannot be controlled by Control4 — this applies equally to Control4's own apps. For full Spotify control from Rithum, use the Rithum Spotify Web Connect plugin, which is compatible with Control4 systems and runs alongside this integration.

10. Configure Rithum

You can now configure the Rithum side, just like any other integration. See this guide for more.

11. Upgrading from v18 — (new)

⚠️ The Thermostat driver is NOT a drop-in update from v18. The v19 driver adds new thermostat proxies, and updating it in place can leave the Control4 processor unresponsive. The standard (non-Thermostat) driver can be updated in place.

Migration flow:

1. Update the existing v18 Thermostat driver in place to 018.7 or later (safe — same proxies). This adds the Export Configuration action.
2. Run Export Configuration and copy the whole blob from the Configuration Export property (Ctrl+A, Ctrl+C).
3. Review or screenshot any Composer programming attached to the driver's scenes/events — deleting the driver deletes its events and the programming on them, and programming cannot be exported. Then delete the v18 driver, add the v19 driver, and set the switch IP again (section 2).
4. Paste the blob into Configuration Import (press Set), then run Import Configuration.
5. The Configuration Export box shows the import summary plus a STILL MANUAL checklist — re-bind the listed relay, room and scene button-link connections in Composer, then refresh navigators.

Per-switch scenes are capped at 5 in v19 (previously 10). Scenes 6–10 found in a v18 export are converted to free Global Scene slots automatically during import, name-deduped so global scenes import once across a multi-switch site; re-attach any keypad bindings or programming to the new Global Scenes (section 7).

If you need help migrating a larger project, or with consolidating scenes from several switches into Global Scenes, contact Rithum support and we will assist.