Update CHANGELOG. Add note on Data Format 2 and 4 to README.

ttu · Oct 11, 2019 · ccbc4e7 · ccbc4e7
1 parent 9992e5b
commit ccbc4e7
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,6 +1,7 @@
 ## Changelog
 
 ### [Unreleased]
+* Fix usage of bt_device parameter when opening the BLE connection
 
 ## [0.13.0] - 2019-07-01
 * Fix hcitool subprocess closing

diff --git a/README.md b/README.md
@@ -215,6 +215,12 @@ Example data has data from 4 sensors with different firmwares.
 }
 ```
 
+##### Note on Data Format 2 and 4
+
+There is no reason to use Data Format 2 or 4.
+
+Original reasoning to use the URL-encoded data was to use _Google's Nearby_ notifications to let users to view the tags without the need to install any app. Since the _Nearby_ has been discontinued there isn't any benefit in using Eddystone format anymore.
+
 ##### Logging and Print to console
 
 Logging can be enabled by importing `ruuvitag_sensor.log`. Console print can be enabled by calling `ruuvitag_sensor.log.enable_console()`. Command line application has console logging enabled by default.