Re: [DISCUSSION] Moving NimBLE to separate project

My thoughts: 1. Since the 1.4 release is coming up very quickly I would do this for 1.5 (personally). 2. I would choose 2a. 3. Seems a bit confusing to me to label nimBLE releases with same number as Mynewt releases. Why not just make the first stable release of nimBLE 1.0? Not a big deal

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

I think we’ve left enough time, and everybody has agreed. Let’s get on GitHub issues ASAP! On 23 Feb 2018, at 5:31, Fabio Utzig wrote: So, when is a decision going to be made? On Thu, Feb 8, 2018, at 11:15 AM, Miguel Azevedo wrote: +1 I strongly agree to track issues on github, the

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

So, when is a decision going to be made? On Thu, Feb 8, 2018, at 11:15 AM, Miguel Azevedo wrote: > +1 > > I strongly agree to track issues on github, the integration with > github issues and PRs is very good and there's a lot of people already > using it on other projects. > Thanks, > > Miguel

Re: BLEMESH PB GATT

Hi Aditya, Please use BLE_MESH_PB_GATT: 0 and BLE_MESH_GATT_PROXY: 0. But "0" should work too. What other settings do you have? You can use "newt target show " to show target settings. Best regards, Michał Narajowski 2018-02-23 13:17 GMT+01:00 Aditya Xavier : > Thanks for

Re: BLEMESH PB GATT

Thanks for quick reply ! With BLE_MESH_PB_GATT: FALSE and BLE_MESH_GATT_PROXY: FALSE, build fails for the app. Error: repos/apache-mynewt-core/net/nimble/host/mesh/src/proxy.c: In function 'proxy_send': repos/apache-mynewt-core/net/nimble/host/mesh/src/proxy.c:852:21: error: unused variable

BLEMESH PB GATT

Hi Mynewt Team, I have been going through and testing the BLEMESH sample app. Turning on only one device, which does not have BLE_MESH_GATT_PROXY & BLE_MESH_PB_GATT flag, still allows the Silicon Labs application to scan and connect to it. Correct me if am