I already discribed the problem in full here:
opened 07:44PM - 19 Oct 24 UTC
### The problem
after flashing a "good" ie., working config for a fingerprint s… ensor i get the `[E][component:082]: Component fingerprint_grow is marked FAILED` error after connecting to the device:
![image](https://github.com/user-attachments/assets/3a9e0e8e-a282-4da7-962f-ddba48c693b8)
The yaml config was this:
```yaml
esphome:
name: xxx
friendly_name: xxx
esp8266:
board: d1_mini
# Enable logging
logger:
level: VERY_VERBOSE
ota:
- platform: esphome
password: "xxx"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "xxx"
password: "xxx"
captive_portal:
uart:
rx_pin: D1
tx_pin: D0
baud_rate: 57600
fingerprint_grow:
sensing_pin: D2
on_finger_scan_invalid:
- homeassistant.event:
event: esphome.xxx
on_finger_scan_matched:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
confidence: !lambda 'return confidence;'
on_finger_scan_unmatched:
- homeassistant.event:
event: esphome.xxx
on_finger_scan_misplaced:
- homeassistant.event:
event: esphome.xxx
on_enrollment_scan:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
scan_num: !lambda 'return scan_num;'
on_enrollment_done:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
on_enrollment_failed:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
api:
encryption:
key: "xxx"
actions:
- action: enroll
variables:
finger_id: int
num_scans: int
then:
- fingerprint_grow.enroll:
finger_id: !lambda 'return finger_id;'
num_scans: !lambda 'return num_scans;'
- action: cancel_enroll
then:
- fingerprint_grow.cancel_enroll:
- action: delete
variables:
finger_id: int
then:
- fingerprint_grow.delete:
finger_id: !lambda 'return finger_id;'
- action: delete_all
then:
- fingerprint_grow.delete_all:
```
![image](https://github.com/user-attachments/assets/8c8e4898-7bdb-496b-8269-d53236e26cdf)
### Which version of ESPHome has the issue?
2024.10.0
### What type of installation are you using?
Home Assistant Add-on
### Which version of Home Assistant has the issue?
2024.10.3
### What platform are you using?
ESP8266
### Board
D1 Mini
### Component causing the issue
TFT AS608
### Example YAML snippet
```yaml
esphome:
name: xxx
friendly_name: xxx
esp8266:
board: d1_mini
# Enable logging
logger:
level: VERY_VERBOSE
ota:
- platform: esphome
password: "xxx"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "xxx"
password: "xxx"
captive_portal:
uart:
rx_pin: D1
tx_pin: D0
baud_rate: 57600
fingerprint_grow:
sensing_pin: D2
on_finger_scan_invalid:
- homeassistant.event:
event: esphome.xxx
on_finger_scan_matched:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
confidence: !lambda 'return confidence;'
on_finger_scan_unmatched:
- homeassistant.event:
event: esphome.xxx
on_finger_scan_misplaced:
- homeassistant.event:
event: esphome.xxx
on_enrollment_scan:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
scan_num: !lambda 'return scan_num;'
on_enrollment_done:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
on_enrollment_failed:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
api:
encryption:
key: "xxx"
actions:
- action: enroll
variables:
finger_id: int
num_scans: int
then:
- fingerprint_grow.enroll:
finger_id: !lambda 'return finger_id;'
num_scans: !lambda 'return num_scans;'
- action: cancel_enroll
then:
- fingerprint_grow.cancel_enroll:
- action: delete
variables:
finger_id: int
then:
- fingerprint_grow.delete:
finger_id: !lambda 'return finger_id;'
- action: delete_all
then:
- fingerprint_grow.delete_all:
```
### Anything in the logs that might be useful for us?
```txt
INFO ESPHome 2024.10.0
INFO Reading configuration /config/esphome/xxx.yaml...
INFO Starting log output from xxx using esphome API
INFO Successfully connected to fingerprint-haustur @ xxx in 0.037s
INFO Successful handshake with fingerprint-haustur @ xxx in 2.651s
[21:42:50][I][app:100]: ESPHome version 2024.10.0 compiled on Oct 19 2024, 18:27:49
[21:42:50][C][wifi:600]: WiFi:
[21:42:50][C][wifi:428]: Local MAC: 30:83:98:9E:29:CB
[21:42:50][C][wifi:433]: SSID: [redacted]
[21:42:50][C][wifi:436]: IP Address: xxx
[21:42:50][C][wifi:439]: BSSID: [redacted]
[21:42:50][C][wifi:441]: Hostname: 'xxx'
[21:42:50][C][wifi:443]: Signal strength: -57 dB ▂▄▆█
[21:42:50][V][wifi:445]: Priority: 0.0
[21:42:50][C][wifi:447]: Channel: 9
[21:42:50][C][wifi:448]: Subnet: 255.255.255.0
[21:42:50][C][wifi:449]: Gateway: xxx
[21:42:50][C][wifi:450]: DNS1: xxx
[21:42:50][C][wifi:451]: DNS2: 8.8.4.4
[21:42:50][C][logger:185]: Logger:
[21:42:50][C][logger:186]: Level: VERY_VERBOSE
[21:42:50][C][logger:188]: Log Baud Rate: 115200
[21:42:50][C][logger:189]: Hardware UART: UART0
[21:42:50][C][uart.arduino_esp8266:118]: UART Bus:
[21:42:50][C][uart.arduino_esp8266:119]: TX Pin: GPIO16
[21:42:50][C][uart.arduino_esp8266:120]: RX Pin: GPIO5
[21:42:50][C][uart.arduino_esp8266:122]: RX Buffer Size: 256
[21:42:50][C][uart.arduino_esp8266:124]: Baud Rate: 57600 baud
[21:42:50][C][uart.arduino_esp8266:125]: Data Bits: 8
[21:42:50][C][uart.arduino_esp8266:126]: Parity: NONE
[21:42:50][C][uart.arduino_esp8266:127]: Stop bits: 1
[21:42:50][C][uart.arduino_esp8266:131]: Using software serial
[21:42:50][C][fingerprint_grow:537]: GROW_FINGERPRINT_READER:
[21:42:50][C][fingerprint_grow:538]: System Identifier Code: 0x0000
[21:42:50][C][fingerprint_grow:539]: Touch Sensing Pin: GPIO4
[21:42:50][C][fingerprint_grow:541]: Sensor Power Pin: None
[21:42:50][C][fingerprint_grow:546]: Idle Period to Sleep: Never
[21:42:50][C][fingerprint_grow:548]: Update Interval: 0.5s
[21:42:50][E][component:082]: Component fingerprint_grow is marked FAILED
[21:42:50][C][captive_portal:089]: Captive Portal:
[21:42:50][C][mdns:116]: mDNS:
[21:42:50][C][mdns:117]: Hostname: xxx
[21:42:50][V][mdns:118]: Services:
[21:42:50][V][mdns:120]: - _esphomelib, _tcp, 6053
[21:42:50][V][mdns:122]: TXT: friendly_name = xxx
[21:42:50][V][mdns:122]: TXT: version = 2024.10.0
[21:42:50][V][mdns:122]: TXT: mac = xxx
[21:42:50][V][mdns:122]: TXT: platform = ESP8266
[21:42:50][V][mdns:122]: TXT: board = d1_mini
[21:42:50][V][mdns:122]: TXT: network = wifi
[21:42:50][V][mdns:122]: TXT: api_encryption = xxx
[21:42:50][C][esphome.ota:073]: Over-The-Air updates:
[21:42:50][C][esphome.ota:074]: Address: xxx.local:8266
[21:42:50][C][esphome.ota:075]: Version: 2
[21:42:50][C][esphome.ota:078]: Password configured
[21:42:50][C][safe_mode:018]: Safe Mode:
[21:42:50][C][safe_mode:019]: Boot considered successful after 60 seconds
[21:42:50][C][safe_mode:021]: Invoke after 10 boot attempts
[21:42:50][C][safe_mode:022]: Remain in safe mode for 300 seconds
[21:42:50][C][api:140]: API Server:
[21:42:50][C][api:141]: Address: xxx:6053
[21:42:50][C][api:143]: Using noise encryption: YES
[21:42:52][VV][scheduler:225]: Running interval '' with interval=60000 last_execution=607898 (now=667898)
```
### Additional information
_No response_
But I will paste the rought problem here again:
after flashing a “good” ie., working config for a fingerprint sensor i get the [E][component:082]: Component fingerprint_grow is marked FAILED
error after connecting to the device:
The yaml config was this:
esphome:
name: xxx
friendly_name: xxx
esp8266:
board: d1_mini
# Enable logging
logger:
level: VERY_VERBOSE
ota:
- platform: esphome
password: "xxx"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "xxx"
password: "xxx"
captive_portal:
uart:
rx_pin: D1
tx_pin: D0
baud_rate: 57600
fingerprint_grow:
sensing_pin: D2
on_finger_scan_invalid:
- homeassistant.event:
event: esphome.xxx
on_finger_scan_matched:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
confidence: !lambda 'return confidence;'
on_finger_scan_unmatched:
- homeassistant.event:
event: esphome.xxx
on_finger_scan_misplaced:
- homeassistant.event:
event: esphome.xxx
on_enrollment_scan:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
scan_num: !lambda 'return scan_num;'
on_enrollment_done:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
on_enrollment_failed:
- homeassistant.event:
event: esphome.xxx
data:
finger_id: !lambda 'return finger_id;'
api:
encryption:
key: "xxx"
actions:
- action: enroll
variables:
finger_id: int
num_scans: int
then:
- fingerprint_grow.enroll:
finger_id: !lambda 'return finger_id;'
num_scans: !lambda 'return num_scans;'
- action: cancel_enroll
then:
- fingerprint_grow.cancel_enroll:
- action: delete
variables:
finger_id: int
then:
- fingerprint_grow.delete:
finger_id: !lambda 'return finger_id;'
- action: delete_all
then:
- fingerprint_grow.delete_all:
nickrout
(Nick Rout)
October 19, 2024, 7:55pm
2
How do you know it is “good”.
Edwin_D
(Edwin D.)
October 19, 2024, 8:04pm
3
Others got this error when using the wrong pins:
still new to ESPhome. been trying to get the config below to compile and I get the error “fingerprint_grow is marked FAILED”.
see screenshot. using the GROW R503 fingerprint sensor with esp32. I am sure I have something wrong in my config, just have not been able to identify what it is as I have been reading through the documentation. would love any input. thanks.
esphome:
name: fingerprint
friendly_name: FingerPrint
esp32:
board: esp32dev
framework:
type: arduino
# Enable l…
Have you checked you used the right documentation for the board, and that your D1 is an actual D1? This is one of the most faked boards around, boards that have little or nothing in common with the real version.
I do not get any errors and is is 100% compliant with the example from the eso home website
I bought a AZdelivery module from amazon. so its not an “original” D1 but it works exacly like one. The ESP8266 Module is real. I have also done multiple other projects with exactly the same board and they all worked flawlessly. I also used the same pinout as for all other projects.
nickrout
(Nick Rout)
October 20, 2024, 7:23pm
6
Try swapping rx and tx.
Also, is it something to do with D0 being high at boot?
Why not use the RX and TX pins, which are designed for UART?