PepperDash.Essentials.Plugins.Lutron.Quantum 3.0.0

Essentials Lutron Quantum Plugin

Device Config

Lutron Quantum

{
    "key": "lights1",
	"name": "Lutron QS",
	"type": "lutronQuantum",
	"group": "plugin",
	"properties": {
		"control": {
			"method": "com",
			"controlPortDevKey": "processor",
			"controlPortNumber": 1,
			"comParams": {
				"protocol": "RS232",
				"baudRate": 115200,
				"dataBits": 8,
				"parity": "None",
				"stopBits": 1,
				"softwareHandshake": "None",
				"hardwareHandshake": "None"
			},
			"tcpSshProperties": {
				"address": "",
				"port": 23,
				"username": "",
				"password": "",
				"autoReconnect": true,
				"autoReconnectIntervalMs": 10000
			}
		},
		"username": "admin",
		"password": "lutron",
		"integrationId": "1",
		"shadeGroup1Id": "11",
		"shadeGroup2Id": "12",
		"scenes": [
			{
				"name": "Lights Full",
				"id": 1
			},
			{
				"name": "Lights Med",
				"id": 2
			},
			{
				"name": "Lights Low",
				"id": 3
			},
			{
				"name": "Lights Off",
				"id": 0
			}
		]
	}
}       

Lutron QSE-IO

{
	"key": "qse-io1",
	"name": "Lutron QSE-IO",
	"type": "lutronQseIo",
	"group": "plugin",
	"properties": {
		"lightingDeviceKey": "lights1",
		"integrationId": "21"
	}
}

Bridge

{
	"key": "plugin-bridge",
	"uid": 11,
	"name": "Plugin Bridge",
	"group": "api",
	"type": "eiscApiAdvanced",
	"properties": {
		"control": {
			"tcpSshProperties": {
				"address": "127.0.0.2",
				"port": 0
			},
			"ipid": "A1",
			"method": "ipidTcp"
		},
		"devices": [
			{
				"deviceKey": "lights1",
				"joinStart": 1
			},
			{
				"deviceKey": "qse-io1",
				"joinStart": 71
			}

		]
	}
}

Lutron NWK Login Usage (nwk vs nwk2)

For all integrations with the Lutron QSE-CI-NWK-E, the nwk login should be used instead of nwk2.

Reason

The nwk user automatically terminates any existing session using the same login when a new connection is established. This behavior allows the system to recover from stale or orphaned sessions without requiring a reboot.

In contrast:

• The nwk2 user does not reliably replace existing sessions, which can lead to persistent "login: connection in use" errors if a previous session was not properly closed.

Important Note (Passphrase Prompt)

On first-time setup, logging in with either nwk or nwk2 may trigger a prompt to set a passphrase. The integration must handle this prompt correctly (e.g., respond "no" if not using a passphrase), otherwise the login process will remain incomplete and can lead to stuck sessions.

Conclusion

Standardizing on nwk ensures more reliable connection handling and prevents lockout conditions caused by stale Telnet sessions, provided the initial passphrase prompt is handled correctly.

Join Map

Lutron Quantum Lighting BridgeJoinMap

Digitals

Analogs

Serials

Lutron QSE-IO BridgeJoinMap

Digitals

Analogs

Serials

DEVJSON Commands

devjson:1 {"deviceKey":"lights1", "methodName":"PrintScenes", "params":[]}
devjson:1 {"deviceKey":"lights1", "methodName":"SelectScene", "params":[1]}
devjson:1 {"deviceKey":"lights1", "methodName":"MasterRaise", "params":[]}
devjson:1 {"deviceKey":"lights1", "methodName":"MasterLower", "params":[]}
devjson:1 {"deviceKey":"lights1", "methodName":"MasterRaiseLowerStop", "params":[]}
devjson:1 {"deviceKey":"lights1", "methodName":"ShadeGroupRaise", "params":[1]}
devjson:1 {"deviceKey":"lights1", "methodName":"ShadeGroupLower", "params":[1]}

devjson:1 {"deviceKey":"lights1", "methodName":"ResetDebugLevels", "params":[]}
devjson:1 {"deviceKey":"lights1", "methodName":"SetDebugLevels", "params":[2]}