📋 Troubleshooting Guide: Node-RED Matter IPv6 Connectivity

Use this guide if the Node-RED Matter Controller network interface dropdown is blank, or if Matter-over-Thread devices show an ENETUNREACH error after an OS update or system migration.

🔍 Phase 1: Verify the Physical OS Network Interface

Run this command to check if the Raspberry Pi's Wi-Fi adapter has bound to a valid local IPv6 address:

ip addr show wlan0

• What to look for: A line starting with inet6 fe80::... scope link.

• If this line is missing, the Linux kernel has disabled IPv6 on the wireless card, preventing Matter discovery from initializing.

🛠️ Phase 2: Native Netplan Configuration (Debian Trixie)

Modern Raspberry Pi OS releases use Netplan to manage networking profiles. If IPv6 is missing, verify that dhcp6: true is explicitly enabled.

File Location: /etc/netplan/ (usually named 90-NM-xxxx.yaml or similar).

Let's look inside that folder to find your configuration file:

ls /etc/netplan/

You will likely see a file named something like 90-NM-xxxxxxxx.yaml or 01-netcfg.yaml. Open whichever .yaml file is in that folder using nano:

sudo nano /etc/netplan/*.yaml

Sanitized Configuration Template:

network:

  version: 2

  wifis:

    wlan0:

      renderer: NetworkManager

      match: {}

      dhcp4: true

      dhcp6: true

      access-points:

        "YOUR_SSID_NAME":

          auth:

            key-management: "psk"

            password: "REDACTED_WIFI_HEX_KEY"

          networkmanager:

            uuid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

            name: "netplan-wlan0-YOUR_SSID_NAME"

            passthrough:

              proxy._: ""

      networkmanager:

        uuid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

        name: "netplan-wlan0-YOUR_SSID_NAME"

Apply Changes Natively:

If you modify this file, never use the Tab key (only use spaces for indentation). Save the file and run the following to apply it:

sudo netplan apply

🌐 Phase 3: Thread Routing Verification

Modern network managers dynamically install the correct Thread routes broadcast by your Thread Border Router (e.g., Aqara M100). Check your active routing table to ensure it is parsing network data correctly:

ip -6 route show

• What to look for: A line mapping your Thread mesh prefix via your Border Router's link-local address, looking similar to this:
  fd9e:8866:ba70:1::/64 via fe80::56ef:44ff:fe8a:42db dev wlan0 proto ra ...

🔄 Phase 4: Cycle Node-RED Runtime

If network changes were made at the OS layer, the background Node-RED service must be restarted to re-scan the live network sockets:

sudo systemctl restart nodered

💡 Pro-Tip: Fixing a Stubborn Configuration Dropdown

If the wlan0 interface is physically present but still won't appear inside the Matter configuration node:

1. Click the Network interface + button to force-create a brand new Matter Controller config node.

2. Select wlan0 from that menu and click Add.

3. Give the node a placeholder name, click Done, and hit the main red Deploy button in the top right corner of Node-RED to initialize the cryptographic fabric.

This section documents exactly how your Aqara M100 hub, Alexa, and Node-RED share access to your Thread accessories like the Ikea SOMRIG/MYGGBETT button.

🔗 Understanding Matter Multi-Admin Commissioning

Matter introduces a feature called Multi-Admin Commissioning. This allows a single physical accessory—like the Ikea button—to connect securely to multiple smart home controllers (Alexa, Aqara M100, and Node-RED) at the exact same time.

                      ┌──► Alexa App (Ecosystem 1)

                       │

  [Ikea Button] ───────┼──► Aqara M100 (Thread Border Router)

 (Thread Device)       │

                       └──► Node-RED Controller (Ecosystem 2 via wlan0)

Unlike older smart home protocols where a device can only pair with one hub, Matter devices can be shared seamlessly across platforms without removing them from your existing smart home setup.

📝 Step-by-Step: Sharing a Device into Node-RED

Since your Ikea button is already paired with your Aqara M100 and Alexa, you must generate a temporary sharing token from one of those ecosystems to bring it into Node-RED.

1. Generate the Setup Code (From Alexa or Aqara App)

1. Open the app where the device is currently paired (e.g., the Alexa App).

2. Navigate to your Ikea Button device settings.

3. Look for an option named "Share with other services", "Other Assistants", or "Expose via Matter".

4. The app will generate an 11-digit numeric setup code (and a temporary QR code).

   • Note: This code is highly time-sensitive and usually expires within 3 to 15 minutes.

2. Bind the Code to Node-RED

1. Keep your Node-RED browser window open alongside the app.

2. Ensure your Matter Controller configuration node is deployed and listening on your validated wlan0 interface.

3. Pass the 11-digit setup code directly into the input of your Matter node as a text string payload:

msg.payload = "12345678901" 

4. 
   

5. Trigger the injection node.

3. Execution

Your Raspberry Pi Zero 2W will look up the Thread route via your Netplan configuration, securely reach out through the Aqara M100's Thread boundary, perform a cryptographic handshake with the Ikea button, and add it as a native device inside your Node-RED flow.

🔍 Troubleshooting Multi-Admin Failures

If the device fails to pair with Node-RED and throws an error:

• Check the Expiry: Ensure you injected the code into Node-RED before the timer ran out in the smartphone app. If it timed out, simply generate a fresh code and try again.

• Verify Routing: Run ip -6 route show to confirm that the Thread mesh prefix route (fd9e:...) is actively present in your Pi's routing table. Without it, the Pi cannot cross over the Wi-Fi network layer into the Thread mesh.

You can copy and paste this directly onto your site. If there are any specific payload layouts (like what data looks like when the Ikea button is single-pressed versus double-pressed) that you want to add to this guide, let me know!