Matter exposition

[bolfox]

Hi Max,

I’m testing the new Matter integration in KNX Ultimate (WONDERFUL ❤️) and I’m having some issues with device pairing. I would appreciate any advice or suggestions.

1. IKEA BILRESA button pairing issue

I’m trying to add an IKEA BILRESA wireless button. The device is correctly paired with a HomePod. I tried using the Matter pairing code generated by the Apple Home app, but I cannot get it connected to the Matter Controller node in Node-RED.

My setup:

Node-RED running in Docker on a Synology NAS
No firewall enabled
All required ports are open
I also tested with a Shelly plug that was already paired with Apple HomeKit, and that device is discovered and added immediately without any issues.

Is there anything specific required for Matter devices already paired with Apple Home / HomePod to be shared with Node-RED through KNX Ultimate?

2. SwitchBot Lock Ultra Matter integration

I also have a SwitchBot Lock Ultra connected through its Matter hub. The lock is visible and working correctly in Apple HomeKit.

I generated the pairing code through HomeKit and imported the hub into KNX Ultimate, but it only exposes the lock status. I cannot send commands to control the lock.

My goal is to control the lock through KNX.

3. Firmware updates for Matter devices

I would also like to understand how firmware updates are handled in a Matter setup.

For example, my IKEA devices currently receive firmware updates through Apple Home / HomeKit. If the device is also added to another Matter controller (such as KNX Ultimate), which system is responsible for managing firmware updates?

Thanks!

[Supergiovane]

Hi and thank you!
About point 3:

very few third-party controllers implement the OTA Provider role; it’s mostly the major ecosystems (Apple, Google, Amazon) that do it and they must be Matter certified (as for today). KNX Ultimate does not implement an OTA Provider, so it never participates in firmware delivery.

For your IKEA devices specifically: I’m not very familiar with IKEA, but I read somewhere that they’re Zigbee devices are exposed through the Dirigera bridge.
Bridged endpoints typically don’t expose Matter’s native OTA cluster the way a real Matter device would. the actual firmware update happens at the Zigbee level, managed by Dirigera/IKEA’s own OTA mechanism, not Matter’s OTA protocol. So even if Apple Home shows update status, it’s most likely just reflecting what Dirigera reports, not Apple acting as an independent OTA Provider for that device.

about other points, I’m still checking at it…

[bolfox]

Hi Max,

The IKEA button (and all the new IKEA Matter accessories) are Matter-native devices, so they don't require the Dirigera hub. They connect directly to the HomePod over Matter/Thread.

[Supergiovane]

Hi

About point 1:

your IKEA BILRESA works with Matter over Thread (not over IP). The border router (Homepod or similar) takes care of the communication between the IP and Thread network, but the Docker/Sinology must be able to handle IPv6 (Matter over Thread works by assigning an IPv6 address to the Matter over Thread devices).
Please be sure both Sinology and Docker running on it, handles IPv6.
So, just because Shelly works doesn't mean the container network is suitable for Matter-over-Thread. On Docker/Synology, the most likely causes are:

• container in bridge mode;
• IPv6 absent or disabled within the container;
• mDNS multicast not visible;
• IPv6 route to the HomePod's Thread network not propagated to the container;
• VLAN or multicast filtering between HomePod and NAS.

---

About point 2

Yes, i'm implementing all the Matter Devices/Clusters; it's a bit challenging to map that into KNX world, so i will proceed step by step.
Door Lock will be out later today or tomorrow morning ;-)

[bolfox]

Thanks Max,

I'm using UniFi with Vodafone FWA, and IPv6 is disabled by default. I'll check this part now...

The container has its own IP address; it's not bridged. mDNS is enabled, and there is no VLAN configured...

[Supergiovane]

Check Sinology and Docker as well.
The new version is already out.

[bolfox]

Ok, installed, thanks.

Every time I try to expose the input/output pin in the settings, it automatically goes back to "hide".

I'm trying to control the note from the pin as well :-)

[Supergiovane]

Hi
Really? Even if you drag a new node into the flow, instead of using an old one?

[bolfox]

[bolfox]

{"enc":true,"type":"error","data":{"name":"TypeError","message":"_Node.setNodeStatus is not a function","stack":"TypeError: _Node.setNodeStatus is not a function\n at knxUltimateConfigNode.node.addClient (/data/node_modules/node-red-contrib-knx-ultimate/nodes/knxUltimate-config.js:848:17)\n at setupDoorLockProfile (/data/node_modules/node-red-contrib-knx-ultimate/nodes/utils/matterControllerProfiles/doorLock.js:173:20)\n at setupMatterControllerProfile (/data/node_modules/node-red-contrib-knx-ultimate/nodes/utils/matterControllerProfiles/index.js:17:3)\n at new knxUltimateMatterControllerDevice (/data/node_modules/node-red-contrib-knx-ultimate/nodes/knxUltimateMatterControllerDevice.js:26:9)\n at Object.createNode (/usr/src/node-red/node_modules/@node-red/runtime/lib/flows/util.js:211:27)\n at Flow.start (/usr/src/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:261:54)\n at start (/usr/src/node-red/node_modules/@node-red/runtime/lib/flows/index.js:403:17)"}}

[Supergiovane]

Fixed both issues in the new version, out now.

[bolfox]

I have tried to re-add the Shelly Plug, but every time I receive this warning.

[bolfox]

IPv6:
Both the Synology and the HomePod receive an IPv6 address, but I can't find where it is being blocked.

[Supergiovane]

Check the Unifi wifi settings. Often, there is a multicast filtering here, or some "optimizations" da figa, that must be disabled.

[Supergiovane]

All issues should be fixed in 6.0.9 out now.

[bolfox]

I'm waiting for the Node-RED palette update to propagate. :-(

[Supergiovane]

6.0.10, sorry!

[bolfox]

Max, if I update it via npm, could it break my Node-RED palettes update system?

[Supergiovane]

Hmm… better not.

[bolfox]

Too late ahahhaahhah :-)

[bolfox]

OK, updated. It seems to be working now. It’s much better: I can now see the status below, and the debug output is coming from the output node.

I’m still not sure if it occasionally gets stuck on READ, as it stays with a grey status indicator.

[bolfox]

[bolfox]

I'm also trying to read the status from the input pin:
Error: Matter input requires clusterId and command or attribute
at knxUltimateMatterControllerDevice._inputCallback (/data/node_modules/node-red-contrib-knx-ultimate/nodes/utils/matterControllerProfiles/mappedEndpoint.js:148:69)
at /usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:214:26
at Object.trigger (/usr/src/node-red/node_modules/@node-red/util/lib/hooks.js:166:13)
at knxUltimateMatterControllerDevice.Node._emitInput (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:206:11)
at knxUltimateMatterControllerDevice.Node.emit (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:190:25)
at knxUltimateMatterControllerDevice.Node.receive (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:506:10)
at deliverMessageToDestination (/usr/src/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:824:40)
at Immediate._onImmediate (/usr/src/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:840:21)
at processImmediate (node:internal/timers:504:21)

I have triend with:

msg.clusterId = 6;
msg.attribute = 0;

return msg;

[bolfox]

When reboot the node

[bolfox]

This view is better because it shows the state as "unlocked", but after a few seconds the status disappears.

[Supergiovane]

node-red-contrib-knx-ultimate@6.0.11 is out.
Please see the Changelog.

[bolfox]

Hi Max, sorry, but during the week I have less time for experiments. 🙂

Anyway, it's been up and running for a few days now, and it seems to be working correctly without any issues.

I still can't get the IKEA Matter commands to work, on the Synology Docker and UniFi side, everything appears to be fine.

[Supergiovane]

Hi
Unfortunately, I have no Matter over thread devices to test with.