Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

esp-rfid v2 #605

Merged
merged 316 commits into from
Nov 2, 2024
Merged

esp-rfid v2 #605

merged 316 commits into from
Nov 2, 2024

Conversation

matjack1
Copy link
Collaborator

I think it's time to release a V2 for esp-rfid :)

We need a V2 as there are a few breaking changes on the MQTT interface, but I think it's much better now.

Apart from that, the update from V1 should just work, the old configuration will work on the V2 and the new stuff should default to settings that should keep the old configuration working. If anyone has problems upgrading let me know!

I have updated all the documentation and apart from a merge with stable and a changelog update we should be ready!!

@omersiar let me know what you think :)

frenchie71 and others added 30 commits September 7, 2019 22:04
ISR IRAM fix and compatibility with esp 2.2.3
adding compiled websources for Two Relays feature
Fix for #354 (platform setting breaks buildability)
…nly the first keypress is recognized

Copied code for decoding of Wiegand Keypad also to "OFFICIALBOARD" section to make it available there
Fixed the decoding of Wiegand Keypad #358
Added Eventhandler wifiOnStationModeGotIPHandler = WiFi.onStationModeGotIP(onWifiGotIP);
Added void to reconnect to MQTT Server when Wifi interface got an IP address
matjack1 and others added 27 commits April 9, 2024 16:24
Couple of small updates to rfid.esp and add more comments
Fix for NTP blocking loop if connection is blocked
- NTP works also on wifi reconnect
- event logs are highlighted correctly
- cleaned debug logging
Doesn't keep the door open for 10 seconds!
Fix opening door while disconnected
Access logs were missing a lot of access denied, which are now added and the UI was displaying only the role of the person trying the access, not the actual result.

So now we are logging the card, the role and the result of the opening.

For example a standard card could have failed because it has expired, it's disabled or it's outside of the opening hours. In all these cases we should add a line in the access logs saying that the person with the specific role had a denied access.
Fix access logs and visualization
This was affecting the user list and the user export
Fix pincode reading in websocket
commit 55d6801
Author: wasn-eu <info@wasn.eu>
Date:   Wed Jun 5 16:42:09 2024 +0200

    clean up
Using a SoftwareSerial to communicate with RDM6300 - take 2
@matjack1
Copy link
Collaborator Author

matjack1 commented Nov 2, 2024

Today is the day of v2!

@matjack1 matjack1 merged commit 36356dc into stable Nov 2, 2024
4 checks passed
@matjack1 matjack1 deleted the dev branch November 2, 2024 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.