Solved the problem by adding the device via webSocket commands (without companion app) - directly with the BT adapter on the raspberry HA server.
First connect the OTBR to the matter server (command send by browser dev-tools):
var socket = new WebSocket("ws://10.0.0.54:5580/ws");
socket.addEventListener("message", (event) => {
console.log("Message from server ", event.data);
});
socket.addEventListener("open", (event) => {
console.log("WebSocket is open");
var message = {
"message_id": "1",
"command": "set_thread_dataset",
"args": {
"dataset": "0e080000000000020000000300000b35060004001fffc00208e2c27b4173cafbed0708fd17bea5b1ae2d0a0510a45ff34823c7f536ded24c37a2d83bd0030e68612d7468726561642d633961360102c9a6041048bdf2923fc3ae9c3ba5b2911568137d0c0402a0f7f8"
}
};
socket.send(JSON.stringify(message));
});
Second, pair e.g. eve energy with code:
var socket = new WebSocket("ws://10.0.0.54:5580/ws");
socket.addEventListener("message", (event) => {
console.log("Message from server ", event.data);
});
socket.addEventListener("open", (event) => {
console.log("WebSocket is open");
var message = {
"message_id": "2",
"command": "commission_with_code",
"args": {
"code": "03626027046"
}
};
socket.send(JSON.stringify(message));
});
Afterwards I could pair the eve door sensor - because the door sensor is only a child matter device and needs the eve energy first as a leader.
See also:
[("Thread border router required" with Eve and Matter)]