open thread end device (FTD) to work with matter app like chip-lighting-app

[rajaram1606]

HI Everyone, currently I am seeing and experimenting that chip-lighting-app (matter app) is working in OTBR device using dbus communication between OTBR and chip-lighting-app. Is there any support to make it (that is, chip-lighting-app) to work with open thread end device (ot-cli-FTD or ot-daemon with rcp using nrf52840 usb dongle)?? Because I am seeing it is not supporting it and throwing dbus error while starting this app.

openthread: failed to read ExtendedAddress property: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name io.openthread.BorderRouter.wpan0 was not provided by any .service files

[jwhui]

DBus support is provided as part of ot-br-posix.

See the OTBR_DBUS CMake option:
https://github.com/openthread/ot-br-posix/blob/f5ec65bd9c3af13098540e6c7e1bb77286fd73e2/etc/cmake/options.cmake#L72C8-L72C17

[rajaram1606]

Hi Jonathan, Thanks for the reply. I am looking for support to make chip-lighting-app to work with ot-daemon through, for example, unix domain socket. ot-daemon already exposes /run/openthread-wpan0.sock file. But, how to enable openthread support in chip-lighting-app so that it communicates with ot-daemon thru this unix domain socket?? i am looking for support in openthread end device, not in OTBR device.

Here, i am using rasp-pi (ubuntu 24.04) with ot-daemon (with nrf52840 ot-rcp software flashed) and chip-lighting-app. openthread is working properly.

[jwhui]

As you noted, chip-lighting-app on Linux currently requires ot-br-posix dbus daemon.

If you want to modify chip-ligthing-app itself, I would suggest reaching out to project-chip developers.