Support for Bluetooth LE notifications?

Hi, I'm new to Pycom devices - I've had a couple of LoPy dev boards for a week or two and they seem great. I'm looking to use them in a commercial project that requires BLE notification support.

I have programmed a LoPy to advertise a BLE service and characteristic with Read, Indicate & Notify properties. (Bluetooth server / peripheral)

I am testing the connection using generic BLE apps (BLE Scanner for Android & LightBlue Explorer for iOS) to connect to the LoPy and read the values. The apps can connect and read the values from the LoPy, and the apps appear to show that I can successfully subscribe to notifications. However, it seems that the notification isn't triggered from the LoPy when the value changes. What I'd expect to see is that once the mobile app registers for notifications then any subsequent change in value on the LoPy side would trigger the new value to be sent to the mobile app, but only manually triggered reads seem to be working.

Is sending notifications from a Bluetooth LE client supported yet? I can't find any reference in the docs or forum.

It looks like the missing functionality (i.e. not supporting BLE notifications when running as a BLE server) may be linked to the soon-to-be-implemented BLE characteristic descriptors. Hopefully BLE server-side notifications will work once the descriptor functionality has been implemented - although that hasn't been made clear yet.

The above code running on a LoPy advertises a BLE service and characteristic with Read, Indicate & Notify properties. The LoPy is acting as the Bluetooth server / peripheral in this case. The value of the characteristic will be changed every few seconds.

Connect to the Lopy using a BLE app on a smartphone (e.g. BLE Scanner for Android or LightBlue Explorer for iOS).

Test that manually triggering a read value works - it should

Press the button on the app to subscribe to notifications. Expected: Every update in value on the LoPy should be notified to the app. Actual: No value updates are notified to the app. Only manually triggered reads seem to work.