-
Notifications
You must be signed in to change notification settings - Fork 13
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
Support for R503 FPS and watchdog #18
Comments
#19 Pull request created. |
#20 Pull request created (Updated an if condition). |
Turns out when the WiFi access point switches channels or the microcontroller loses connection to the AP, there isn't a reconnection strategy in the code for WiFi. Only MQTT reconnect is implemented. The current watchdog solution works as a reconnection strategy but can be done using the native WiFi library. Will take a look into this. Reference: |
IMG_3631.-.Trim.mp4Been stable for the last month. Closing this issue. |
Issue #18: R503 FPS LED WDT ESP32
The adafruit fingerprint library supports FPM10A (optical) and R30x/R50x (Capacitive) Fingerprint sensors. However, the Capacitive fingerprint sensors (FPS) do not support the following function:
The above line throws "Unknown Error" on Serial Monitor via switch-case logic.
but instead use
The R-series FPS have an LED ring around the sensor that can be used to indicate various states via
I have also noticed that certain microcontrollers (ESP32xx family) get stuck and do not publish mqtt messages, even though broker and wifi are available. I am yet to ascertain the issue via logs as this bug appears only when microcontroller is on power (for an extended period of time - days) and not connected to a system for serial monitor. Currently using a watchdog to raise a hardware interrupt and reboot the device on such a scenario.
Hardware WatchDog Timer - ESP32xx Stuck WiFi
The text was updated successfully, but these errors were encountered: