Looking at the docs: nrf/ug_thread_architectures.html
I see the note "This platform design is currently discontinued by nRF Connect SDK." for "Network co-processor (NCP)".
Is there any particular reason why, that I'm not understanding?
I'd think the NCP would be the better option over RCP for power-saving plus network availability reasons. But maybe I'm just viewing them incorrectly...
For NCP, I imagine my nrf52840 dongle living alone, next to a small PC, connected via a GPIO input interrupt, so when some action happens on the Thread network that requires the PC to wake up, the dongle can trigger the interrupt and send/receive whatever it needs to from something like home-assistant/node-red/chip-tool.
In fact, I think the PC wouldn't even need to be in the picture. home-assistant and chip-tool both have android applications.
The question here though would be whether or not a bluetooth connection could be made for the Matter communication from the smartphone to/from the dongle.
From what I can tell via matter/nrfconnect_android_commissioning.html, bluetooth is only used for commissioning. No clue why it can't be used for 6lowpan as well.
I know Espressif has got their esp-c6 in the pipeline. It's got all of the goodies (minus AI), including wifi, bluetooth thread. I don't know if Nordicsemi has something similar in your pipeline as well.
It'd be nice to communicate with all Matter devices wired or wirelessly (encrypted vs closed circuit), online or offline (home PC or remotely via smartphone). Ya know, cover every contingency.
Essentially looking for a low-power device that can remain live all of the time, communicate with all 802.15.4 devices (whatever the protocol) and basically be a gateway for the end-user.
Note to myself, I see home-assistant has an add-on for this sort of Matter stuff: github.com/.../addons-development
