hAP be³ Media - can't start Thread border router (otbr)

Hardware: hAP be³ Media (MA53UG+HbeH), RouterOS 7.23.3

App: otbr (image docker.io/openthread/otbr), freshly installed + Cleanup + Update performed, same error before and after. Goal: run otbr to join running Thread network (HA on external raspberry, existing TBR is Apple TV)

Symptom: otbr-agent crashes on every startup, before any Join/Form attempt on a Thread network:

otbr-agent[93]: [NOTE]-AGENT---: Running 0.3.0
otbr-agent[93]: [NOTE]-AGENT---: Thread version: 1.4.0
otbr-agent[93]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0
otbr-agent[93]: 00:00:00.008 [C] Platform------: otPlatRadioSetMacKey() at radio.cpp:964: InvalidArgument

Result: otbr-web starts but reports "OpenThread daemon is not running", and the REST port (8081) never opens. The built-in Thread radio is correctly detected (/dev/ttyACM0 shows up as an available HW device in the app config), so this looks like a mismatch between the built-in RCP firmware and this otbr-agent build over how the MAC key is set (possibly a "key ref" vs. plaintext key handling issue on the RCP side — not sure, would appreciate input from someone closer to the firmware).

Happy to provide the full syslog output or test further if that helps track it down.

How did you install otbr? Manually or using the "app" feature of ROS? Did you go through the app setup wizard before?

Using the App menu in Winbox. Used the setup to define storage (a freshly formatted USB drive), bridge and router address.

(Bear in mind I received the router only this Monday, and I am a newbie in Mikrotik stuff - I hope Claude.ai which I used to help me configure the thing has not been hallucinating too much :wink: )

offtopic

Rest assured. It probably WILL have ...

Problem with AI models is they need time and lots of data to assess what is probably the most correct thing. And this device is too new and ROS changes so often, it usually invents stuff.
You can however instruct Claude (and other AI models) to NOT invent stuff and explicitly ask you if something is not clear.
That should help.

/offtopic

Why folks waste thier time with Artificail Imbecile instead of just reading the mfg's docs I will never understand . . . It's like asking the drooling kid with the helmet for help when you already have instructions.

Maybe, the answer came to me...

Nowadays everyone, probably, has to be as beautiful and talented
as the photos retouched by Artificial Intelligence,
and in person, expectations are high...
and even the slightest flaw, which you wouldn't even notice because it's a perfectly normal human being,
actually makes you vomit from the betrayed expectation...

So admitting you don't know something is like being out of touch,
and therefore, since Artificial Intelligence doesn't judge you,
but rather reassures you and is addictive,
that's why people are increasingly stupid and dependent on this AI
that's destroying the world by taking away electricity and drinking water.

I doubt the issue is AI not understanding. Rather there is a bug...

I'd try upgrade to the "testing" channel. I suspect there are some fixes, or at least that's easy to do.

I'll just vote "laziness and low expectations" . . . :slight_smile:

Update: Same behaviour with RouterOS and RouterBOARD aligned at 7.24rc3

I understand that there are still few units of hAP be3 in the field, but has anyone successfully deployed the otbr app/container?

I am sure Mikrotik has done that. We don't know what you actually want to achieve and which steps you exactly already made? We only have your AI generated troubleshooting output.

I wasn't able to get OTBR running on my be³ Media hAP either. The logs show the exact same error.

Maybe 'cus the docs ain't written with new users in mind!
Was that a one click APP/ MikroTik added ?

Hello,

Sorry for the inconvenience. This seems to be the current issue: Version sha-86431d2 breaks communication with HA Connect ZBT-2: InvalidArgument · Issue #13471 · openthread/openthread · GitHub
It is going to be resolved.

Excellent - Thanks! I will mark the discussion as resolved when the new image is available.

The image was updated, and after repull, everything started working for me.

This image is built specifically for continuous integration (CI/CD) and simulated testing environments. It is not intended or optimized for real-world or production use.

For production deployments, please use openthread/border-router.

Why does ROS use "otbr" then?

Indeed. The router is indeed an excellent "all-in-one" machine for me.