9 Commits

Author	SHA1	Message	Date
geeksville	1e86365167	MITM_BOND supposedly doesn't have the problem mentioned in #266 ... (and it is good / more secure anyways - the old code was just based on the example docs)	2020-07-19 15:01:15 -07:00
geeksville	d9e93f3944	Try turning my software update service back on... ... Now that I've fixed a couple of nasty esp32-arduino bugs	2020-06-22 10:06:35 -07:00
geeksville	60470211e5	expose battery level via the standard BLE battery service	2020-06-22 10:04:26 -07:00
geeksville	fda98bbf58	oops BLE auth should not change	2020-06-14 15:52:06 -07:00
geeksville	2c8d152885	Use old style (pre BLE 4.2) pairing, it seems more reliable	2020-06-14 15:30:21 -07:00
geeksville	8a1754efe8	leave the software update service off for now - no one is using ityet	2020-06-13 11:36:45 -07:00
geeksville	d5deb49d20	use executeDelete to prevent leaking BLE handles	2020-06-13 11:05:13 -07:00
geeksville	a8d4b5479d	don't start the BLE update service for now - the android side isn't ready	2020-06-12 15:48:24 -07:00
geeksville	5ec5248fe4	complete ble ota move	2020-05-14 14:22:11 -07:00