| 25 Nov 2024 |
spacekitteh | sorta | 01:19:32 |
spacekitteh | if you wanna use python-matter-server, then OTBR is a dependency to get running AFAIK | 01:19:49 |
spacekitteh | or rather, if you want to use matter-over-thread | 01:20:43 |
spacekitteh | * (if you want to use matter-over-thread) | 01:20:50 |
@hexa:lossy.network | and you want to run thread for something else? | 01:21:23 |
spacekitteh | yeah i have a bunch of thread devices | 01:21:37 |
@hexa:lossy.network | I don't think we have any other openthread border router | 01:21:41 |
@hexa:lossy.network | * I don't think we have any other openthread border router packaged up | 01:21:48 |
spacekitteh | matter-server isn't a thread border router, is it? | 01:22:00 |
@hexa:lossy.network | https://github.com/home-assistant-libs/python-matter-server 🤷 | 01:22:11 |
spacekitteh | matter is a higher level protocol, like TCP; thread is the IP + PHY layer | 01:22:55 |
@hexa:lossy.network | yeah | 01:22:58 |
@hexa:lossy.network | same as WLAN, only a transport | 01:23:19 |
@hexa:lossy.network | the question is if it can handle an adapter that speaks thread | 01:23:51 |
spacekitteh | * matter is a higher level protocol, like TCP; thread is the IP + MAC+ PHY layer | 01:24:08 |
spacekitteh | kinda, WLAN is just the MAC + PHY, you don't have to have it running IP, afaik | 01:24:23 |
spacekitteh | whereas thread explicitly includes IPv6 | 01:24:43 |
@hexa:lossy.network | maybe packaging up https://github.com/openthread/ot-br-posix would be worthwhile? | 01:25:14 |
spacekitteh | yeah that's what i'm currently trying to avoid, by asking if anyone is running it already :P | 01:25:29 |
@hexa:lossy.network | I see | 01:25:46 |
spacekitteh | (specifically, avoiding the packaging it myself lmao) | 01:26:01 |
@hexa:lossy.network | ot-br-posix is what home-assistant uses | 01:28:17 |
@hexa:lossy.network | https://www.home-assistant.io/integrations/otbr/
https://github.com/home-assistant/addons/tree/master/openthread_border_router | 01:28:22 |
spacekitteh | yep | 01:28:27 |
@hexa:lossy.network | and there are no github hits for ot-br-posix, soooo 😄 | 01:29:01 |
spacekitteh | indeed :( | 01:29:10 |
@hexa:lossy.network | * and there are no github hits for ot-br-posix language:nix, soooo 😄 | 01:29:20 |
@hexa:lossy.network | $ ./result/bin/otbr-agent --help
Usage: ./result/bin/otbr-agent [-I interfaceName] [-B backboneIfName] [-d DEBUG_LEVEL] [-v] [--auto-attach[=0/1]] RADIO_URL [RADIO_URL]
--auto-attach defaults to 1
RadioURL:
forkpty-arg[=argument string] Command line arguments for subprocess, can be repeated.
spinel+hdlc+uart://${PATH_TO_UART_DEVICE}?${Parameters} for real uart device
spinel+hdlc+forkpty://${PATH_TO_UART_DEVICE}?${Parameters} for forking a pty subprocess.
Parameters:
uart-parity[=even|odd] Uart parity config, optional.
uart-stop[=number-of-bits] Uart stop bit, default is 1.
uart-baudrate[=baudrate] Uart baud rate, default is 115200.
uart-flow-control Enable flow control, disabled by default.
uart-reset Reset connection after hard resetting RCP(USB CDC ACM).
region[=region-code] Set the radio's region code. The region code must be an
ISO 3166 alpha-2 code.
cca-threshold[=dbm] Set the radio's CCA ED threshold in dBm measured at antenna connector.
enable-coex[=1|0] If not specified, RCP coex operates with its default configuration.
Disable coex with 0, and enable it with other values.
fem-lnagain[=dbm] Set the Rx LNA gain in dBm of the external FEM.
no-reset Do not send Spinel reset command to RCP on initialization.
skip-rcp-compatibility-check Skip checking RCP API version and capabilities during initialization.
| 01:38:57 |
@hexa:lossy.network | 🫣 | 01:39:01 |
uep | oops | 01:39:31 |