Matter device
Matter device| This function block makes the
controller available as a Matter bridge on the local network,
allowing it to be operated by Matter-enabled smart home systems such
as Amazon Alexa, Google Home, Apple Home or Home Assistant. Each block is one Matter device with the configured name; the device type (light, socket, dimmer, roller shutter, thermostat or sensor) determines the inputs and outputs of the block. The outputs of the dimmer and roller shutter types are compatible with the Block Light/Dimmer and Block Shutter/Blind function blocks — the KNX addresses of the actuator (switch/percent or long-time/short-time/ height) can be linked directly at the outputs. All blocks together appear as a single bridge that only needs to be paired with the smart home system once. The Matter connection runs in an auxiliary service that is started and supervised automatically by the runtime and is pre-installed on the controller. Note: This block requires controller image version 4.012 or newer. Important: Node-RED and Matter should not be enabled on the controller at the same time. Running both services together causes very high memory usage, which may reduce the service life of the SD card. |
Inputs |
||
| FG |
Enable |
Optional enable; if the input is not connected the
block is enabled automatically. While the block is disabled,
commands from the smart home system are ignored. |
| SS / SP / SH / TI / SI / KO / BW / FE |
Status values (depending on device type) |
Feedback of the actual state to the smart home
system (shown in the app); connect the status addresses of the
actuator here: Light/socket: SS = switching status. Dimmer: SS = switching status, SP = percent status 0-100%. Roller shutter: SH = height status 0-100% (100 = closed). Thermostat: TI = actual temperature, SI = current setpoint. Sensors: TI = temperature, KO = contact (1 = closed), BW = motion, FE = humidity 0-100%. |
Outputs |
||
| ST |
Status |
0 = Matter service not connected, 1 = connected but
not yet paired, 2 = paired with at least one smart home system. |
| TR |
Trigger |
When a command is received from the smart home
system, a positive edge is output here (pulse, automatically reset
after 3 seconds). |
| EA / PR / LZ / KZ / PH / SW |
Commands (depending on device type) |
Commands from the smart home system to the
building; connect the command addresses of the actuator here
(assignment as with the Block function blocks): Light/socket: EA = switch. Dimmer: EA = switch, PR = percent 0-100%. Roller shutter: LZ = long-time (0 = up, 1 = down), KZ = short-time (stops an active movement), PH = height percent 0-100% (100 = closed). Thermostat: SW = new setpoint. Sensors: no command outputs (status display in the app only). |
Parameters |
||
| Device name |
Name of the device in the smart home system (e.g. "Living room light"). Without a name the block is not offered as a device. Name changes are transferred to paired systems automatically. | |
| Device type |
Light, socket, dimmer, roller shutter, thermostat, temperature sensor, contact sensor, motion sensor or humidity sensor. The type determines the inputs and outputs of the block and how it is displayed in the app. | |
| Matter pairing |
Opens the pairing dialog (controller must be
connected): shows the pairing status, the pairing code and the QR
data. "Decommission" resets the bridge to factory state — all
connections to smart home systems are lost. Note: Pairing is only possible when the status output (ST) of the block is greater than 0 (Matter service connected). At status 0 the service is still starting or is unavailable (controller image version 4.012 or newer required). |
|
| Debug |
Outputs debug messages via the runtime (received commands, connection state of the Matter service). Active as soon as the parameter is enabled on at least one block. Default: off. | |
| Port |
Test option, only visible when debug is enabled: local TCP port between runtime and Matter service, default 8125. If debug is not active, the default port is always used. | |
The smart home device (e.g. Amazon Echo, Apple TV/HomePod, Google Nest Hub) and the controller must be in the same IP network (subnet). Pairing is started in the respective app:
Alexa: Devices → Add device → Other → Matter.
Important: An Amazon Echo device with Matter support is required;
a bridge can contain a maximum of approx. 80-100 devices.
Apple Home: Add accessory → More options.
Google Home: Add device → Matter device.
Then scan the QR code or enter the pairing code. Both are shown in the Studio in the pairing dialog of the block ("Matter pairing" parameter). Since the bridge uses a test vendor ID, the app shows a notice such as "Uncertified device" — confirm this notice, pairing then works normally.
The bridge only needs to be paired once; all blocks (including ones added later) automatically appear as devices of the paired system. Additional smart home systems can be granted access via the app of the already paired system (share device / pair with another service).
Matter uses mDNS (UDP multicast to 224.0.0.251, port 5353) for device discovery and UDP port 5540 for communication. Both only work on the local network: pairing and operation do not cross subnet boundaries and do not work over a VPN connection. Remote access is handled by the paired smart home system through its own cloud (e.g. Alexa app while away from home).
The bridge is not found during pairing.
The smart home device and the controller must be in the same subnet.
IGMP snooping or client isolation in the switch or access point can
block the multicast packets. Firewall: UDP 5353 and UDP 5540 must be
allowed.
Status output stays at 0.
The Matter service is not running. Check that the controller has image
version 4.012 or newer. The pairing dialog in the Studio shows the exact
cause of the error.
Devices appear twice in Alexa.
The same device is configured both via a "Matter device" block and via
an "Alexa (local)" block. Remove one of the two connections.
Room assignments are missing after decommissioning/re-pairing.
Decommissioning resets the bridge to factory state; the assignments in
the app are lost and must be set up again. With normal project changes
(adding/renaming devices) the assignments are retained.
This function uses third-party software (an open-source Matter library). The function can therefore not be guaranteed. Since the controller is integrated as an uncertified Matter device, this function is no longer available as soon as a manufacturer (Amazon, Google, Apple, etc.) discontinues support for uncertified devices.