#Setup

1 messages · Page 1 of 1 (latest)

dense spoke
#

Okay, but what is your goal exactly. I’m still not sure what you want to accomplish. Ofc you can just install the otbr using their setup scripts and manually interact with the Python matter server or something else. But again really depends on what you want to accomplish. In the end it’s probably best and easiest to just use the hasOS implementation and make your border router preferred.

lucid atlas
#

My full preference would be to use fully open sourced everything for everything. I've obviously limited options for that, with hardware, so I'm trying to get there with at least software

Right now, due to the issues I've hit, and how experimental Thread+Matter is with HA (and in general), I mainly want to know if anyone has done what I'm trying to do

#

In a perfect world, I want my RPi to be running HA Core, in docker, and communicating to OTBR and Matter Server also running there, also all in containers I've configured

#

Atm, I seem to be getting the same issues with hasOS as I was getting with Core, so I'd like to know if anyone had even done that either

dense spoke
#

The next thing is the networking. I Think you need to run with host networking for the otbr container.

#

The last thing is the matter Python server

#

Maybe start with one thing at a time and then ask for help with the specific problem.

#

Generally i would use the official repos, clone Them and make a docker-compose that uses the include docker files in the official repos and/or make your own docker file. Then you can always pull the official changes and dont have to maintain as much

#

Maybe also look into docker compose extends and include

#

They added include a few days ago, i Think it might be useful in this scenario

#

But generally it wont fix that you have 3 Home assistant otbrs showing

#

And so on.

#

You should probably just delete some of the border routers showing.

lucid atlas
#

Hmm hmm hmm hmm, you've given me a ton to think about there, really appreciated

lucid atlas
#

But that's the Dockerfile, not compose. I'll read up what you've sent on

dense spoke
#

For the matter server maybe just extend the existing compose.yml