node-red-contrib-lilitech 1.0.0

Node-RED nodes to control and monitor the devices of a Lilitech smart home headunit

npm install node-red-contrib-lilitech

node-red-contrib-lilitech

Node-RED nodes to control and monitor the devices of a Lilitech smart home headunit.

Every node works both ways: send a message to the node to command the device, and the node emits a message every time the device state changes (from a wall switch, the Lilitech app, a scenario, another flow...).

Requirements

• A Lilitech headunit with Node-RED enabled (Node-RED runs on the headunit itself).
• Node-RED 3.0 or later, Node.js 18 or later.

The headunit accepts connections only from the local machine: these nodes cannot control a headunit from another computer.

Install

From the Node-RED editor: Menu → Manage palette → Install, search for node-red-contrib-lilitech.

Or from the Node-RED user directory:

npm install node-red-contrib-lilitech

Nodes

headunit (configuration)

The connection to the headunit. The default address http://127.0.0.1:3000 is correct when Node-RED runs on the headunit.

light

Select the headunit and the light: the list is loaded from the headunit, and the node adapts to the light type.

Input

msg	Effect
payload: true / false / "on" / "off" / "toggle"	switch the light
payload: { "switch": true, "brightness": 80 }	write several items at once
topic: "brightness", payload: 50	write a single item
payload: { "color": { "r": 255, "g": 0, "b": 0 } }, or topic: "color" with "#ff0000", "255,0,0" or "{r:255,g:0,b:0}"	set the color

Output: one message per changed item, with msg.topic = item name (e.g. switchFeedback), msg.payload = value, msg.origin and msg.device.

Light type	Writable items
onOff	switch
dimmer	switch, brightness
tunableWhite	switch, brightness, temperature
rgb	switch, color, brightnessColor
rgbWhite	switch, brightness, color, brightnessColor
rgbTunableWhite	switch, brightness, temperature, color, brightnessColor

Each writable item has a ...Feedback item with the state confirmed by the device. brightness, brightnessColor and temperature are percentages (0-100). DALI lights with scenes enabled also accept scene (0-15). simulated is emitted when the presence simulator switches the light (the badge on the app card) and is shown in the node status.

environment sensor

Read only: the node has no input and emits a message every time a value of the sensor changes, with msg.topic = item name, msg.payload = value and msg.unit = unit of measure.

Sensor type	Items	Optional (enabled in the app)
temperatureSensor	temperatureValue (°C)
humiditySensor	humidityValue (%)
lightSensor	luminosity (lx)	solarRadiation (W/m²)
twilightSensor	twilight (true = night)
presenceSensor	presence
airQualitySensor	coTwo (ppm)	voc (mg/m³)
barometerSensor	pressureValue (hPa)
windSensor	windSpeed (km/h)	windDirection (°), windGusts
rainSensor	rainStatus	rainAmount, rainAmountRelative (mm), rainAmountRelativeTimestamp
soilMoistureSensor	soilMoisture (%)	evaporation

Options:

• Send min/max statistics: numeric sensors also emit ...MinValue, ...MaxValue, ...MinTimestamp, ...MaxTimestamp (e.g. temperatureMaxValue).
• Send diagnostics (default on): sensorLoss, lowBattery, faultSignal, when the feature is enabled on the sensor.

security area

Arms and disarms a security area and emits its state.

Input

msg	Effect
payload: "arm" / true / "on"	arm the area (with the exit time, if delayed arming is enabled)
payload: "disarm" / false / "off"	disarm the area
payload: "patrol"	start the patrol (internal logic areas with patrol enabled, area armed)
payload: { "areaControl": "arm" }	same as above

Commands sent from Node-RED do not ask for the PIN, even when the area requires it in the app.

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.origin and msg.device.

Item	Value
areaStatus	disarmed, unready, forceable, exiting, armed, forced, patrol, entering, alarm, tamper
memory	true when the area went in alarm since it was last armed
history	names of the sensors that triggered the last alarm
areaControl	last command (arm, disarm, patrol...) sent by the app, by other nodes or by the headunit

The Output option controls areaControl: not emitted with Area state only (default), emitted with Area state and commands.

electronic

Read only: emits the status of an electronic device (smartphone, laptop, tablet, watch, printer, scanner...) every time it changes, with msg.topic = isOnline and msg.payload = true (online) or false (offline).

actuator

Controls pumps, valves, sprinklers, faucets, servo valves and thermostatic valves, and emits their state.

Input

msg	Effect
payload: true / false / "on" / "off" / "toggle"	switch a pump, valve, sprinkler or faucet
topic: "proportionalDrive", payload: 60	set the opening of a proportional actuator (0-100 %)
payload: "open" / "close" / "stop" (or true / false)	drive a servo valve
payload: 21.5	set the setpoint of a thermostatic valve (4-30 °C, steps of 0.5)
payload: { "switch": true, "proportionalDrive": 60 }	write several items at once

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.unit (when it has one), msg.origin and msg.device.

Actuator type	Writable items	Read only
pump, valve, sprinkler, faucet	switch, proportionalDrive (proportional actuators only)	powerOffTimerAt
servoValve	drive (open, close, stop)	driveFeedback (open, opening, close, closing, stop, idle)
thermostaticValve	setpointTemperature (°C)	roomTemperature (°C), proportionalDriveFeedback (valve opening, %), battery (%)

Each writable item has a ...Feedback item with the state confirmed by the device. When enabled on the actuator in the app, every type also emits volumeValue / volumeRelative (l) with volumeRelativeTimestamp, openStatus and faultSignal.

automation

Controls shutters, sun blinds, awnings, curtains, gates, pedestrian gates, barriers, tilting doors, front doors and windows, and emits their state.

Input

msg	Effect
payload: "open" / "close" / "stop" (or true / false)	drive the automation
payload: "lock" / "unlock"	lock or unlock a front door with a smart lock
topic: "absolutePosition", payload: 40	move to a position (0-100 %)
topic: "absolutePositionFoil", payload: 30	tilt the slats (0-100 %)
payload: { "absolutePosition": 40 }	write one or more items at once

The commands follow the features enabled on the automation in the app:

Command	Available on
drive open	all
drive close	shutter, sunBlind, sunshadeAwning, curtain; the other types when closeable
drive stop	when stoppable
drive lock / unlock	frontDoor when lockable
absolutePosition	when positionable
absolutePositionFoil	when inclinable

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.unit (when it has one), msg.origin and msg.device. driveFeedback is one of open, opening, close, closing, stop, idle, locked, locking, unlocked, unlocking, block, alarm; positions come as absolutePositionFeedback / absolutePositionFoilFeedback. When enabled in the app the node also emits openStatus and faultSignal, and a lockable front door emits status (online / offline) and battery (%). simulated is emitted when the presence simulator moves the automation (the badge on the app card) and is shown in the node status.

Commands sent from Node-RED do not ask for the PIN, even when the automation is secured in the app.

notifier

Controls sirens, buzzers, flashes and status leds, and emits their state.

Input

msg	Effect
payload: true / false / "on" / "off" / "toggle"	switch the notifier on or off
topic: "test", payload: true	turn the notifier on for 5 seconds (only when testable)
topic: "maintenance", payload: true / false	exclude the notifier from the security areas (the alarms no longer turn it on)
payload: { "switch": false, "maintenance": true }	write several items at once

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.origin and msg.device: switchFeedback, test, maintenance and, when enabled on the notifier in the app, tamperSignal and lowBattery. switch is emitted only with Feedback and commands.

charger

Controls EV chargers and emits their state.

Input

msg	Effect
payload: true / false / "on" / "off" / "toggle"	switch a simple charger
payload: "play" / "pause" (or true / false, "toggle")	start or pause the charge of a smart charger
payload: "lock" / "unlock"	lock or unlock a smart charger
topic: "maxChargingCurrent", payload: 10	set the maximum charging current of a smart charger (1-16 A)

A smart charger accepts one item per message.

Charger type	Writable items	Read only
charger	switch	switchFeedback; when enabled in the app: power (W), energy and energyRelative (Wh), current (A), voltage (V)
smartCharger	command (play, pause), commandLock, maxChargingCurrent (A)	status, statusLock, chargingPower (kW), addedEnergy (kWh), chargingTime and sessionTime (s)

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.unit (when it has one), msg.origin and msg.device. Both types also emit overload, economy and green (energy management) and, when enabled in the app, faultSignal. status is one of disconnected, ready, charging, paused, scheduled, locked, lockedCarConnected, waitingForCarDemand, error... switch, command and commandLock are emitted only with Feedback and commands.

access control

Emits the access attempts on badge readers and keypads. The headunit checks the PIN or the badge and runs the action configured in the app; the node reports the result:

msg.topic	msg.payload	Also
access	granted / denied	msg.user (id, name) when the user is recognized, msg.reason for a denial (e.g. Pin blocked, User outside the allowed time window, Unidentified user)
exclusion	true / false	when excludible is enabled in the app
tamper	true / false	when tamperDetection is enabled in the app

The PIN and the badge read by the reader are never emitted.

Input (only when excludible is enabled): payload: true excludes the reader until it is enabled again and false enables it.

appliance

Controls dishwashers, washing machines, dryers, ovens, water heaters, fridges and the other appliances, and emits their state.

Input: payload: true / false / "on" / "off" / "toggle" switches the appliance (or { "switch": true }).

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.unit (when it has one), msg.origin and msg.device: switchFeedback, overload, economy and green (energy management) and, when enabled in the app, power (W), energy and energyRelative (Wh), current (A), voltage (V) and faultSignal. switch is emitted only with Feedback and commands.

energy management

Starts and stops the load control and emits its powers, energy flows and badges.

Input: payload: "play" / "stop" (or true / false, "toggle") starts or stops the controller. The rules (contracted power, margin, off-peak bands, green threshold) are configured in the app.

Controller type	Writable items	Read only
gridControl	command (play, stop)	status, gridPower (W), overloadBadge, economyBadge, gridProduction, gridToHouse
greenControl	command (play, stop)	status, gridPower, greenPower and housePower (W), overloadBadge, economyBadge, greenBadge, gridProduction, greenProduction, houseConsumption, gridToHouse, greenToHouse, greenToGrid

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.unit (powers), msg.origin and msg.device. overloadBadge is detach while the loads are detached, attach while they are reattached, idle otherwise; houseConsumption is 0 (none), 1 (grid), 2 (green) or 3 (both); the badges are null when the controller is stopped or the rule is disabled. command is emitted only with Feedback and commands.

irrigation

Starts and stops the irrigation controller and its programs, and emits their state.

Input

msg	Effect
payload: "play" / "stop" (or true / false, "toggle")	start or stop the controller: when stopped no program runs, not even the scheduled ones
program: "Garden" (or the id), payload: "play" / "pause" / "stop" / "toggle"	command a program
payload: { "programId": 1, "cmd": "play" }	the same, as an object (name instead of programId works too)
topic: "programsCmd", payload: "play"	command the program of an irrigation that has only one

A program can be commanded only while the controller is started. Programs, zones and durations are configured in the app.

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.origin and msg.device: status (play / stop), programRunning, programStartAt (next scheduled start, ISO date), programsRun (object with windy, rainy, override and programs: programId, name, status play/pause/stop, lastRun, totalDuration in ms, zones...), windy, rainy and override (seasonal adjustment, %, with msg.unit). programsRun is emitted only when it changes. command and programsCmd are emitted only with Feedback and commands.

hvac

Controls conditioners, fancoils, boilers, chillers, heat pumps, dehumidifiers, air purifiers, fans and vmc, and emits their state. The node offers only the items enabled on the hvac in the app.

Input

msg	Effect
payload: true / false / "on" / "off" / "toggle"	switch the hvac
payload: 22	set the temperature of a conditioner or fancoil (5-35 °C, step 0.5) or the humidity of a dehumidifier (%)
payload: "comfort" / "heat"	select a profile (comfort, economy, protection, standby, manual, chrono) or a mode (heat, cool, dry, fan, wind, auto) of a conditioner or fancoil
payload: { "switch": true, "setpointTemperature": 22, "fanSpeed": 2 }	write several items at once
topic: "fanSpeed", payload: 2	write a single item

Writable (feedback)	When
switch (switchFeedback)	conditioner and fancoil; the other types when powerable
setpointTemperature, thermoProfile, thermoMode (and their feedback), overrideRestore (true)	conditioner and fancoil, profiles and modes when enabled
setpointHumidity (setpointHumidityFeedback), 0-100 %	humidity control enabled
fanSpeed (1 to the number of speeds), fanAuto, fanEco, fanStrong, fanDirection (fixed, all, vertical, horizontal), with feedback	fan management enabled (no auto and direction on fans)
supplyFanSpeed, returnFanSpeed (and feedback), 0-100 %	supply / return fan management enabled

The headunit applies temperature and humidity only while the hvac is on. Changing the temperature outside the manual profile starts an override, restored after overrideTime or with overrideRestore. Override time, profile temperatures and the chrono schedule are configured in the app.

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.unit (°C, %, ms), msg.origin and msg.device. Besides the feedbacks: roomTemperature, thermoStatus (off, idle, heat, cool, dry, fan, inhibit, standby), overrideFeedback, overrideTime (ms), overrideTimeAt, chronoSetpoint, roomHumidity, humidityStatus, deliveryTemperature / returnTemperature / acsTemperature / pressureValue on boilers, chillers and heat pumps, and faultSignal, each when enabled in the app. The commands are emitted only with Feedback and commands.

socket

Controls simple and measurable sockets and emits their state.

Input

msg	Effect
payload: true / false / "on" / "off" / "toggle"	switch the socket
topic: "restoreEnergy", payload: true	reset the relative energy, like the reset button of the app
topic: "restorePower" / "restoreCurrent" / "restoreVoltage", payload: true	reset minimum and maximum of that measure

The resets are available only for the measures enabled on the socket in the app. The power off timer is configured in the app.

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.unit (when it has one), msg.origin and msg.device: switchFeedback, overload, economy and green (energy management), simulated (switched by the presence simulator) and, when enabled in the app, energy and energyRelative (Wh), power / powerMin / powerMax (W), current / currentMin / currentMax (A), voltage / voltageMin / voltageMax (V) and faultSignal. switch is emitted only with Feedback and commands.

metering sensor

Emits the measures of single and three phase energy meters and of volume, pressure, level and temperature sensors, and resets the relative energy of the energy meters.

Input (energy meters only)

msg	Effect
topic: "activeEnergyRelativeLaReset", payload: true	reset the relative energy of a single phase meter (or of phase 1), like the reset button of the app
topic: "activeEnergyRelativeLbReset" / "activeEnergyRelativeLcReset" / "activeEnergyRelativeTotalReset", payload: true	three phase meters: reset phase 2, phase 3 or the total

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.unit (when it has one), msg.origin and msg.device.

Type	Items
singlePhaseEnergyMeter	activeEnergyAbsoluteLaValue, activeEnergyRelativeLaValue (Wh) and activeEnergyRelativeLaValueTimestamp (last reset); when enabled in the app activePowerLaValue (W), reactivePowerLaValue (var), apparentPowerLaValue (VA), powerFactorLaValue, voltageLaValue (V), currentLaValue (A), frequencyLaValue (Hz)
threePhaseEnergyMeter	the same items for La, Lb and Lc, plus activeEnergyAbsoluteTotalValue, activeEnergyRelativeTotalValue, activeEnergyRelativeTotalValueTimestamp and totalActivePowerValue (W, with active power enabled)
volumeSensor, pressureSensor, levelSensor, temperatureSensor	volumeValue (m³), pressureValue (bar), levelValue (m), temperatureValue (°C)

When enabled in the app the node also emits sensorLoss, lowBattery and faultSignal, shown in the node status like the badges of the app card. Energies and powers are in Wh and W, as sent by the headunit (the app shows kWh and kW); thresholds and energy cost are configured in the app.

security sensor

Emits the state and the alarms of a security sensor (contacts, volumetric, barrier and shock sensors, flood, smoke, fire and gas detectors, panic buttons, line, key and float switches) and excludes it, tests it or puts it in maintenance like the app.

Input

msg	Effect
topic: "exclusion", payload: true / false	exclude / include the sensor (only with excludible enabled in the app; the exclusion timer is set in the app)
topic: "testing", payload: true / false	test mode: the sensor does not trigger the alarm
topic: "maintenance", payload: true / false	maintenance: the sensor is ignored

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.origin and msg.device: input (true = open / activated), trigger (true each time the sensor triggers its armed area), armed, exclusion, testing, maintenance and, when enabled in the app, tamper, sensorLoss, lowBattery, faultSignal, masked, weak, petDetected and maxAlarmsReached.

presence simulator

Starts and stops a presence simulator and its programs, and emits its state.

Input

msg	Effect
payload: "play" / "stop" (true / false, "toggle")	start / stop the simulation
program: "Evening" (or the program id), payload: "play" / "stop" / "toggle"	command that program (the simulation must be started)
payload: {"programId": 1, "cmd": "play"}	the same, as the app sends it

msg.program can be omitted (with topic: "programsCmd") when the simulator has only one program. Programs and simulated devices are configured in the app.

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.origin and msg.device: status (play / stop), programRunning, programStartAt (next scheduled start) and programsRun (the programs with their status, decoded as an object and emitted only when it changes). command and programsCmd are emitted only with Feedback and commands. The devices moved by the simulation emit simulated on their nodes.

system

Read only: emits the values of the clock or of the weather, with msg.topic = item name, msg.payload = value and msg.unit (when it has one). The headunit sends them every minute: the node emits an item only when it changes.

System type	Items
clock	sunrise / sunset (true at sunrise / sunset, false a minute later), night (true from sunset to sunrise), sunriseTime, sunsetTime (e.g. "07:05")
weather	weather (clear, clouds, drizzle, fog, rain, thunderstorm, snow, ...), temperatureValue / temperatureMinValue / temperatureMaxValue / temperaturePerceived (°C), humidityValue (%), pressureValue (hPa), windSpeed / windGustsValue (km/h), windDirection (°), rainAmountHour (mm/h), rainStatus, uvIndex, airPollutionIndex (1 = good ... 5 = very poor), weatherAlerts, weatherAlertsEvent (array of alert names), city, sunriseTime, sunsetTime

Options:

• Send the current day and time every minute (clock): currentDayTime ({"day": 0, "time": "09:16"}, day 0 = Monday like the app scenarios), currentDay (0 = Sunday), currentHour, currentMinute.
• Send the daily and hourly forecast (weather): forecastDaily (8 days with weather, temperatureDay, temperatureMin, temperatureMax, pop) and forecastHourly (24 hours with weather, temperature).

The clock uses the time zone and the position of the headunit set in the app; the weather comes from the OpenWeather technology.

thermostat

Controls heat, cool and heat/cool thermostats (also the integrated "smart" ones) and emits their state. The node offers only the items enabled on the thermostat in the app.

Input

msg	Effect
payload: true / false / "on" / "off" / "toggle"	switch the thermostat (only when powerable)
payload: 21.5	set the temperature (5-35 °C, step 0.5; with the setpoint block enabled in the app, the base setpoint ± 3 °C)
payload: "comfort" / "heat"	select a profile (comfort, economy, protection, standby, manual, chrono) or, on heat/cool thermostats, a mode (heat, cool and, when enabled, auto, dry, fan)
topic: "overrideRestore", payload: true	end the override and go back to the profile temperature
payload: { "switch": true, "setpointTemperature": 21.5 }	write several items at once

The headunit applies the temperature only while the thermostat is on. Changing the temperature outside the manual profile starts an override, restored after overrideTime or with overrideRestore. Override time, profile temperatures, chrono schedule and fan are configured in the app.

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.unit (°C, %, ms), msg.origin and msg.device: switchFeedback, setpointTemperatureFeedback, thermoProfileFeedback, thermoModeFeedback, roomTemperature, thermoStatus (off, idle, heat, cool, auto, dry, fan, inhibit, standby), overrideFeedback, overrideTime (ms), overrideTimeAt, the valves (systemPrimaryValve, or systemPrimaryValveHeat / systemPrimaryValveCool on 4 pipes, and the same for the secondary system), chronoSetpoint, roomHumidity and faultSignal, each when enabled in the app. The commands are emitted only with Feedback and commands.

video surveillance

Video cameras: records a clip, like the REC button of the app, and emits the camera state and the recorded clips. Monitors have no items yet: for now the node supports only video cameras.

Input

msg	Effect
payload: true / "manual"	record a clip (only with loop recording enabled on the camera in the app; the clip stops by itself)
source: "Doorbell flow"	who started it, shown in the app history (default: the node name, or Node-RED)

A command received while a clip is being recorded is ignored by the headunit.

Output: one message per changed item, with msg.topic = item name, msg.payload = value, msg.origin and msg.device: status (online / offline) and, with loop recording, triggerRecording (manual, auto when started by an armed security sensor, idle when the clip is saved). When the headunit uploads a clip the node also emits topic: "clip" with the file name in msg.payload, msg.trigger (manual or auto) and msg.source. Live stream, recordings and PTZ stay in the app.

scenario

Starts and stops a scenario, like the play/stop button of the app, and emits its running state. The node is at the end of the palette, in a lighter orange to tell it apart from the device nodes.

Input

msg	Effect
payload: "play" / "stop" (true / false, "on" / "off")	start / stop the scenario
payload: "toggle"	start it if stopped, stop it if running

Like the play button of the app, a scenario can be started only with the manual control enabled in the app and when it is enabled; otherwise the node reports an error. Starting a scenario that is already running does nothing.

Output: one message each time the scenario starts or stops (and on deploy), with msg.topic: "status", msg.payload = run / stop, msg.running, msg.lastRun and msg.lastEnd (timestamps in milliseconds of the last execution start and end, null if it never ran), msg.enable, msg.inhibited (a condition of the scenario is not satisfied), msg.origin and msg.scenario (scenarioId, name, roomId). With Feedback and commands it also emits topic: "command" with the play / stop sent by the app or by other nodes. The node status shows e.g. Running · since 10:15 or Stopped · Last run 05/11 10:15, in yellow with · Inhibited when the scenario is inhibited.

Example flows are available in Menu → Import → Examples → node-red-contrib-lilitech.

License

MIT

Deploy

Login: npm login --auth-type=web

Publish: npm publish

Click on: https://flows.nodered.org/add/node and add node-red-contrib-lilitech