Releases: rednblkx/HomeKey-ESP32
v0.4.1
0.4 - Features, fixes and a new look
First of all i just want to thank anyone that showed interest in this thing i made, as of now repository has 455 stars ⭐, a massive increase from the 200ish on the last release which feels absolutely insane for the little project i just made out of spite of Apple, so thank you, it means a lot ♥️ .
I've also rewrote part of the wiki, please take a look and let me know what you think.
What's Changed
- Reorganized WebUI and added a splash of color to it
- Added WebUI Authentication (Basic - Digest)
- Added a separate section on the WebUI for triggers, old HomeKey Events and GPIO Actions have been moved here and more properly labeled with a short description
- HomeKit/HomeKey GPIO Trigger (old GPIO Actions) now has an optional momentary state used on a successful HomeKey authentication (#102)
- Added Reboot, Reset HomeKit, Reset WiFi buttons on the WebUI
- Fixed setting timeouts for HomeKey/NFC Triggers (old Events)
- Added field to set the LWT topic on the WebUI(#81)
- Added HomeKey color preview on WebUI(#114)
- Configurable RGB values for the Neopixel
- Payload for the NFC/HK MQTT Topic now includes a
"reader_id"
field unique per device - Minor fixes and optimizations
- NFC Tag Detection is now treated as
Auth Failure
- Added Pixel Type selector for Neopixel action
Known Issues
- WebUI is not accessible from Safari on macOS Ventura and higher or iOS 18
New Contributors
Full Changelog: v0.3.11...v0.4
Not backwards compatible, if for whatever reason you need to flash the previouse, this won't be possible.
Hotfix
What's Changed
- Fixed Custom States Persistance issue
Full Changelog: v0.3.1...v0.3.11
littlefs.bin
only included for posterity, no update to it.
v0.3.1 - Minor Update
What's Changed
- Configurable HomeKey Card Finish (color) from Web UI = Tan, Gold, Silver and Black
- Initialize nfcSuccessPin and nfcFailPin by @gficher in #69
- Implement NeoPixel status LED by @jess-sys in #73
- QoL things and minor fixes
New Contributors
Known Issues
- Not saving custom states, if using custom states better stay on previous version
Full Changelog: v0.3...v0.3.1
0.3 - Improvements, new stuff and a Discord server
I'll start this off by announcing that you can now find attached on these releases firmware binaries, you can find more information about them in the wiki.
- Implemented a simple web interface that includes all options previously in
config.h
and more - This release includes the new PN532 SPI Driver that was reworked to use ESP-IDF SPI Master APIs and some other improvements, this should solve the "Didn't find PN53x board" that can appear at times
- Added option to trigger a GPIO Pin on HomeKey Success or Fail, should address #57
- Added option to trigger a GPIO Pin when interacting with the Lock from the Home App
- Improvements and optimizations
- Tested on ESP32-C3 and works about the same (firmware binaries attached below)
Additionally i have now launched a Discord server called "HomeKit Corner"(might rename it to "HomeKit Matters" or something to include Matter), this is where current and future projects will be discussed. This should help streamline communication and make it easier to answer questions and solve any issues, if you have any of that or just want to hangout you can join the server at the link below.
MQTT Custom States and Home Assistant Integration
- PicoMQTT library has been replaced by Espressif's MQTT IDF Component esp-mqtt
- HomeKey related functions have been isolated into a library located at HK-HomeKit-Lib
- Added
MQTT_HOMEKEY_ALWAYS_UNLOCK
andMQTT_HOMEKEY_ALWAYS_LOCK
options to the configuration - Implemented MQTT custom states, more info in the wiki here
- Now leveraging MQTT Discovery to integrate with Home Assistant and be able to control the lock from there
Important Note: This release removes the MQTT publishing of state to the MQTT_STATE_TOPIC
topic upon a successful HomeKey authentication, however not entirely, more information on this can be found in the wiki here
First Release
Hello everyone!
In order to better track changes over time for this project, i've decided to take advantage of the releases section of GitHub, this will also help me attach helpful information regarding the released version like added features and if any breaking changes were introduced that people updating should be aware of.
This is also were i will be publishing binaries when the web interface will be done, so you don't have to compile/recompile the whole thing.
Thank you for your support and all the engagement with this project!
Note: For the time being i will be marking the releases as pre-release since i still don't consider this as production-ready and also to lower expectations for the new people.