Because your tado° X device is a Thread device, it uses your Alexa Echo device as the "Thread Border Router" to stay on your network. Your Node-RED Matter Controller can piggyback right onto that network: [2]
Open your Alexa App.
Go to your tado° X device settings, look for Other Ecosystems (or Pairing Mode), and generate a Matter Pairing Code.
Note: You must act quickly, as these setup codes usually expire within a few minutes.
In Node-RED, drag out Sam's Device Management node.
Choose your Matter Controller config node (ensure it's running on the same IPv6 network/subnet).
Select the Commission Device method, paste the pairing code you got from Alexa, and give the device a label (e.g., tado_sensor).
Deploy the flow. Once commissioned, your Node-RED controller acts as a secondary ecosystem. [1, 2, 5]
Once commissioned, you can stop polling and use standard Matter Subscriptions to let the tado° X broadcast updates to Node-RED automatically whenever the climate changes: [1, 5]
Drag out a Read / Subscribe Attribute node from Sam's palette. [1]
Select your newly paired tado_sensor from the dropdown list.
Target the following clusters:
Temperature Measurement Cluster (0x0402) ➔ Attribute: MeasuredValue (0x0000).
Relative Humidity Measurement Cluster (0x0403) ➔ Attribute: MeasuredValue (0x0000).
Set the node to Subscribe mode. [1]
Temperature Scaling: Matter reports raw temperature values multiplied by 100. If the node outputs a payload of 2150, that means it is exactly 21.5°C. You will need a simple Change or Function node to divide the raw incoming msg.payload by 100 before writing it to your CSV spreadsheet.
Humidity Scaling: Matter reports relative humidity multiplied by 100. A payload value of 5530 represents 55.3% humidity. [6]
Once you pass those payloads through a quick mathematical division block, you can pipe them right into a standard file node to build your local CSV download log.