Skip to content
This repository was archived by the owner on Sep 11, 2024. It is now read-only.

Releases: formatBCE/ESP32_BLE_presense

0.1.0

25 Jul 15:59
3aa6d7f
Compare
Choose a tag to compare

Summary

Integration to ESPHome now done via custom_component. Big thanks to @whitty!

What's Changed

  • Use home assistant time component by @whitty in #2
  • Rework "header, library and lambda" into "esphome component" by @whitty in #5
  • Clean up and change README by @formatBCE in #6

New Contributors

  • @whitty made their first contribution in #2

Full Changelog: 0.0.6...0.1.0

Faster tag scanning

27 Aug 06:00
Compare
Choose a tag to compare
0.0.6

Changed scan parameters for faster scanning.

Refactoring configuration flow

29 Jul 20:47
Compare
Choose a tag to compare
  • Initial WiFi Access Point will have unique name.
  • Device now will have automatic setup request popping up (captive portal), when connecting to it's WiFi (at least for Android devices).
  • Soft AP IP address changed to 8.8.8.8 due to previous change.
  • Configuration flow is changed in the way that will produce less errors:
    • Initially, when device is in AP mode, only WiFi settings and device name are set;
    • After that, it tries to connect to WiFi in parallel, and if error, it will allow to revise settings;
    • After connecting to WiFi, MQTT can be set up;
    • If MQTT setup is incorrect, it will be shown on info page;
    • Info page allows to re-configure MQTT, or completely reset configuration.
  • Hiding passwords in input fields (were in plain text, bummer).
  • LED blinking is set up to represent current configuration status:
    • 2 times per second: device is in Access Point mode;
    • 1 time per second: WiFi configuration is done, but cannot connect to WiFi;
    • 1 time per 2 seconds: WiFi is connected, but no connection to MQTT server (or MQTT configuration needed);
    • constant light: device is working properly;
      • during this, short flash offs will indicate, that some beacon is found and data sent to MQTT server.
  • Introduced hard configuration reset. If something went terribly wrong, and there's no way to configure device (e.g. WiFi went down or changed password), you may reset configuration and return device to AP mode by resetting it by 5 consecutive restarts with less than 5 seconds in between.

MQTT timestamp for using in integration

25 Jul 00:13
Compare
Choose a tag to compare

Software version, removed bin from code.

24 Jul 00:15
Compare
Choose a tag to compare

0.0.1

23 Jul 23:50
Compare
Choose a tag to compare
UUIDs added