.le.interval - in the course “Bluetooth Low Energy Fundamentals” (Lesson 3, Exercise 2), deprecation warning - “interval is deprecated.”

RE: .le.interval - in the course “Bluetooth Low Energy Fundamentals” (Lesson 3, Exercise 2), deprecation warning - “interval is deprecated.”

Hung Bui — Tue, 06 Jan 2026 12:17:17 GMT

Hi Daniel,

It's quite strange.
Could you try the attached project (v3.2.0).
I can see this on my UART log:

Advertising successfully started

Connected
                                                                     
Connection parameter updated
                                                  
Connection interval: 1.25 * 6 ms, latency: 0, timeout: 10 * 500 ms
            
Connection parameter updated
                                                  
Connection interval: 1.25 * 24 ms, latency: 0, timeout: 10 * 500 ms
           
Connection parameter updated
                                                  
Connection interval: 1.25 * 24 ms, latency: 0, timeout: 10 * 42 ms

If you still see the issue with this code, you may need to capture a sniffer trace so we can check what exactly happen over the BLE communication.
devzone.nordicsemi.com/.../1830.peripheral_5F00_lbs.zip

RE: .le.interval - in the course “Bluetooth Low Energy Fundamentals” (Lesson 3, Exercise 2), deprecation warning - “interval is deprecated.”

IoT-Dani — Tue, 30 Dec 2025 14:19:19 GMT

For the first one, shame on me, I was not on the right tab. I work with SDK v3.2.0.

Regarding the callback, I can print out other parameters which are not 0.

I work with an nRF52840dk. Can you suggest another sample that I can run on my board?

RE: .le.interval - in the course “Bluetooth Low Energy Fundamentals” (Lesson 3, Exercise 2), deprecation warning - “interval is deprecated.”

Hung Bui — Tue, 30 Dec 2025 13:37:25 GMT

Hi Daniel,

Which SDK you are using ? Could you try switching to v3.2.0 ?
As far as I can see in the tab for 3.2.0 in the dev academy course we have updated it to interval_us .

Regarding le_param_update callback, could you print out other parameters ? Could you try to test with one of our sample, for example peripheral_power_profiling. Quite strange that you see interval= 0.