Designer Project Query

Opens Lutron Designer .hw/.ra3 project files via Docker SQL Server and queries the project database. No VM or Designer app needed.

Prerequisites

• Docker running (container lutron-sql2022 auto-starts on first use)
• Project file path (e.g., ~/Downloads/share/gs.hw)

Opening a Project

bash
1npx tsx tools/designer-project.ts open <project-file>
2npx tsx tools/designer-project.ts status   # check if already open
3npx tsx tools/designer-project.ts close    # close when done

Only one project can be open at a time. Check status first.

Key Queries

CCA Address Map (the primary use case)

This is the complete CCA device inventory with on-wire zone bytes. The CCA zone byte seen in state report packets (byte 5) = AddressOnLink - 1.

sql
1SELECT
2  ln.AddressOnLink as LinkAddr,
3  ln.AddressOnLink - 1 as CCA_Zone,
4  s.PropertyAddress as PropAddr,
5  d.SerialNumber as Serial,
6  d.SerialNumberState as Paired,
7  d.ModelInfoID as ModelID,
8  cs.Name as Station,
9  a.Name as Area,
10  z.Name as Zone,
11  z.ControlType as CtrlType
12FROM tblLinkNode ln
13JOIN tblControlStationDevice d ON d.ControlStationDeviceID = ln.ParentDeviceID
14LEFT JOIN tblControlStation cs ON cs.ControlStationID = d.ParentControlStationID
15LEFT JOIN tblArea a ON a.AreaID = cs.ParentID
16LEFT JOIN AllZonesWithAssociatedDevice zd ON zd.device_id = d.ControlStationDeviceID
17LEFT JOIN tblZone z ON z.ZoneID = zd.zone_id
18LEFT JOIN tblShortFormPropertyAddressMap s ON s.ParentDeviceID = d.ControlStationDeviceID
19WHERE ln.LinkType = 11
20ORDER BY ln.AddressOnLink

Processor / Link Master

sql
1SELECT ln.AddressOnLink, ln.IsLinkOwner, ln.IsLinkMaster, ln.LinkType
2FROM tblLinkNode ln
3WHERE ln.IsLinkOwner = 1 OR ln.IsLinkMaster = 1

CCX Devices (Thread, link type 40)

sql
1SELECT
2  ln.AddressOnLink as LinkAddr,
3  d.SerialNumber as Serial,
4  d.SerialNumberState as Paired,
5  d.ModelInfoID as ModelID,
6  cs.Name as Station,
7  a.Name as Area
8FROM tblLinkNode ln
9JOIN tblControlStationDevice d ON d.ControlStationDeviceID = ln.ParentDeviceID
10LEFT JOIN tblControlStation cs ON cs.ControlStationID = d.ParentControlStationID
11LEFT JOIN tblArea a ON a.AreaID = cs.ParentID
12WHERE ln.LinkType = 40
13ORDER BY ln.AddressOnLink

All Zones with Areas

sql
1SELECT
2  z.ZoneID, z.Name as Zone, z.ZoneNumber, z.ControlType,
3  a.Name as Area
4FROM tblZone z
5LEFT JOIN tblArea a ON a.AreaID = z.ParentID
6ORDER BY a.Name, z.SortOrder

Free CCA Addresses

Addresses 0-5 are reserved (repeaters/master). Processor is typically at 255. Find gaps:

sql
1SELECT ln.AddressOnLink FROM tblLinkNode ln
2WHERE ln.LinkType = 11
3ORDER BY ln.AddressOnLink
4-- Compare against available range 6-254
5-- Next free = MAX(AddressOnLink) + 1 from occupied set

Preset/Scene Assignments

sql
1SELECT
2  p.PresetID, p.Name as PresetName,
3  pa.ZoneID, z.Name as ZoneName,
4  pa.Level, pa.Fade, pa.Delay
5FROM tblPreset p
6JOIN tblPresetAssignment pa ON pa.PresetID = p.PresetID
7JOIN tblZone z ON z.ZoneID = pa.ZoneID
8ORDER BY p.PresetID, pa.ZoneID

Address Architecture

Three different address spaces coexist:

• AddressOnLink = device's position on the CCA RF link. Assigned during pairing. TDMA scheduling uses this.
• CCA zone byte = AddressOnLink - 1. This is what appears in CCA state report packets at byte 5 (with bit 7 sometimes set for alternate components on the same device).
• PropertyAddress = sequential LEAP integration property ID. Used by the LEAP API for zone addressing. NOT related to the on-wire CCA value.

Tool Commands Reference

bash
1npx tsx tools/designer-project.ts open <file>        # Open project
2npx tsx tools/designer-project.ts query "<sql>"       # Run SQL
3npx tsx tools/designer-project.ts tables [filter]     # List tables
4npx tsx tools/designer-project.ts describe <table>    # Show schema
5npx tsx tools/designer-project.ts dump <table> [N]    # Dump rows
6npx tsx tools/designer-project.ts close               # Close project
7npx tsx tools/designer-project.ts status              # Check state
8npx tsx tools/designer-project.ts save <output>       # Save modified (needs VM)

Key Tables

ModelInfoID Reference

Model info is stored in the Designer reference library (SQLMODELINFO.MDF), not in the project DB. The ModelInfoID in tblControlStationDevice is an opaque foreign key into that library. To resolve model numbers, either:

• Cross-reference against known IDs from previous sessions
• Open the VM and query the reference DB via mcp__designer-db__query