Hi linux-bluetooth developers, I hope my question is not unsuitable for this mailing list. I have read in the archives of this mailing list that the Bluetooth mesh daemon needs exclusive access to a Bluetooth controller. If I understand that correctly (just to be clear), it means that when I only have one controller, I have to choose between either using mesh operations or "normal" Bluetooth operations (normal here meaning all operations that the regular Bluetooth daemon already performs). In my company we are now developing a Bluetooth mesh lighting solution by using the Bluetooth-mesh daemon in an embedded Linux environment (with only one Bluetooth controller attached via HCI). We have a custom mesh application that is using the mesh DBUS api to perform mesh operations. I am currently looking in to how we can additionally allow this application to perform other Bluetooth operations (i.e. acting as an observer, and in the future also as a central device). When you have time, I would be interested to hear your general thoughts about this topic. Whether or not you believe it is doable or if it perhaps already is a part of a long-term plan. I am also in general open to help contributing to the project. Thank you for your time, Isak
