version 1.11

What's Changed

• Better scan performance, faster hit, more stable operation
• MQTT improvements (last will, retain states)
• Web administration improvements
• Code structure changes
• Typo fixes, bugfixes

New Contributors

• @Goodwillson made their first contribution in #59
• And a big thanks and thumbs up to @Seinuh for beta tests!

Full Changelog: Please read the README.md for the release notes

version 1.10

What's Changed

• Some logging improvements for less dynamic string construction and destruction in runtime by @BalazsM in #40
• Webserver initialization cleanup by @BalazsM in #42
• Logging bugfix and improvements by @BalazsM in #43

New Contributors

• @BalazsM made their first contribution in #40

Full Changelog: 1.09...1.10

version 1.09

• bugfix #27

version 1.08

Bugfix:

• #27 javascript bug - still bug
• #29 MQTT reconnect fix
  Enhancements:
• #30 status string customization
• #31 custom client id

Typos and minor fixes

version 1.07

1.07

• #23 version is compiled to the HTML source directly, user always see the current version and GIT revision
• binary file name changed. it does not affect the update process but contains the revision number as well
• build code cleaning, htmlmin, jsmin, cssmin do not need anymore for the build process

1.06 (Breaking change)

Status message now is coming with the normal presence message (availability change).

MQTT message topic is also changed

Status message topic from this version is /blecker/status/[device-mac]

version 1.05

1.05

• #11 feature is implemented: Captive portal
• #18 issue is fixed, now MQTT tries to connect even if the username and password not defined. Somebody uses MQTT without user and password
• typo, minor issue fixes

version 1.04

• Webhook feature is implemented
• web administration page sections is separated better
• minor things and typos were fixed
• #14 fix already in

version 1.03

The main feature is the autodiscovery function for Home Assistant.
This release contains bug fixes, typo fixes as well.

version 1.01

• #2 has been solved: if you define observed devices in the web frontend then just that devices will be monitored and sent messages about their presence
• reboot timer introduced: it is actually a workaround. I experienced the ESP32 stuck after some days (network ping is okay, but web frontend and message sending are dead). The administrator can define a reboot time in hours (web frontend). After defined hours the ESP will reboot. It has no effect on presence detection. The format is a single number (integer): "1" or "2". You cannot use float numbers