adonno/tagreader

Simple to build/use NFC tag reader, specially created for Home Assistant

tagreader's Issues

The Buzzer doesn't beep when scan a tag

The buzzer play rtttl when API succesffully initialized.

The buzzer doesn't emit any sound when I scan any card. Maybe I missed something.

Status LED

More like a heads up than a Bug or a FR

ESPHome can use the build in LED of the D1 Mini as Status LED
Blinking is somethings is wrong like no wifi / HA API / Sensor connection
Off is everything is ok

status_led:
  pin:
    number: D4
    inverted: True

Did help me alot debugging and now in everyday use

Version with integrated battery

Hello Guys,
Does anyone already designed a case dir a portable Version with integrated Power source.
I would like to build a juke Box for my daughter.
Integrated would Like more nice than a Power Bank.

Best regards,
Dominik

Trigger the buzzer (with custom sounds) and / or set the light (with color) from HA

I just received my tag reader today. Thank you for this great project! 👍

I would like to know if you think it could be possible to use the Notify platform / a Service in HA to send specific commands to the device.
I think it could be great to be able make it beep with custom music notes that you could send as a message, or to use its LED as a light in HA.

Since the idea is to have this device bound to a room, I would use this to make distinct sounds to warn me about specific events or status.

A few ideas:

• Warning beep + red flash if I open the door to leave but some windows are open
• When I come home (based on motion sensor), the device beeps differently (or light up with a specific color) to tell me if my wife has already left her work or not.
• Reply based on status (1): I flash a badge to request a binary status, the reader answers with yes / no sound + green / red light.
• Reply based on status (2): I flash a badge to request the weather and the tag reader answers (from automation) with a color code (eg. red for rain, orange for chance of rain, white for snow, yellow for sunny...).
• Permanent light that changes color based on a associated sensor (e.g. ambient air status from green to red)

" Timed out waiting for readiness from PN532!"

Hello,
Changing the logger level to VERBOSE I can see the error message: "Timed out waiting for readiness from PN532!"
If I use VERY_VERBOSE I can see "A component took a long time in a loop() cycle"
Card reads do not work. If I hold the card over the NFC sensor for 5-10 seconds, eventually a read will come in.
I've double checked the wiring, proper soldering, etc, thats not an issue. I know the i2c version of this is still in the dev mode.
Do I have a bad board? I've tried with 2 different D1 minis, but only have the 1 PN532.
The hardware is in the 3d printed case from this repo.
My ESP board does not say AZ Delivery.
Thank You,

correct photo for I2C

sorry github is new for me. Find attached an correct picture:

Led won't turn off after first scan

Configured the set-up exactly as described, with my azdelivery D1 mini. When scanning, the led turns on (as configured in entity at home assistant). But it won't go off after scanning. Of course the other entity (just led) is turned off in Home Assistant.

RFID Card and NFC Phone | Inconsistent behaviour

Prerequisites
a. Wemos D1 mini
b. PN RFID 532
c. Card & tag, 13.56 MHz
d. master branch pn532_i2c

Use case
I want to use my Huawei Mate 20 Pro as an NFC Tag

What I did

1. Open Home Assistant Companion which is logged in at HA instance
2. NFC Tag option from Settings
3. Write Tag on White Card
4. Returning results

- platform: event
  event_type: tag_scanned
  event_data:
    device_id: 93d872ca49dfe4d7
    tag_id: ce1685b2-0bdf-4786-bea4-39caa49c4035

5. Fire event button

6. Check if ce1685b2-0bdf-4786-bea4-39caa49c4035 is displayed in Tags from configuration
   

7. Make the following automation in automation.yaml

- alias: "Huawei NFC Access"
  initial_state: True
  mode: single
  trigger:
  - platform: event
    event_type: tag_scanned
    event_data:
      device_id: 93d872ca49dfe4d7
      tag_id: ce1685b2-0bdf-4786-bea4-39caa49c4035
  action:
    - service: switch.toggle
      entity_id: switch.shelly_1pm

8. Reload automation
9. Swipe Huawei Phone

Expected results

1. The bulb must be switched on

Actual results

1. The bulb is not light on and a new entry is created in Tags
2. Huawei and White Card still have different identificators
   

More actions

1. Go To events and listen tag_scanned
2. Scan Huawei and White Card
   --> "device_id": bf45cac435a56ede5256ea83fed4f9c0 is the same for both.
   --> tag id is different than the id created with HA Companion
   --> device_id is different than the id created with HA Companion
   
   --
3. Go to automation and at device_id paste bf45cac435a56ede5256ea83fed4f9c0 value

New automation code excluded tag_id

- alias: "Huawei NFC Access Device ID"
  initial_state: True
  mode: single
  trigger:
  - platform: event
    event_type: tag_scanned
    event_data:
      device_id: bf45cac435a56ede5256ea83fed4f9c0
    #   tag_id: ce1685b2-0bdf-4786-bea4-39caa49c4035
  action:
    - service: switch.toggle
      entity_id: switch.shelly_1pm

4. Reload automation
5. Swipe White Card --> the bulb is switching ON
6. Swipe Huawei --> the bulb is switching ON
7. Check Tags from HA
   New Tag is created for Huawei
8. Swipe Huawei again
   New Tag is created for Huawei
   

Expected results
Huawei and White card should be considered one entity
When I write a new card

      device_id: 93d872ca49dfe4d7
      tag_id: ce1685b2-0bdf-4786-bea4-39caa49c4035

must be used in automation in order to make two entities to act as one

--
More Testing

1. Go To HA companion and read White Card
   --> results

- platform: event
  event_type: tag_scanned
  event_data:
    device_id: 93d872ca49dfe4d7
    tag_id: ce1685b2-0bdf-4786-bea4-39caa49c4035

2. Make the following automation

- alias: "Huawei NFC Access"
  initial_state: True
  mode: single
  trigger:
  - platform: event
    event_type: tag_scanned
    event_data:
      device_id: 93d872ca49dfe4d7
      tag_id: ce1685b2-0bdf-4786-bea4-39caa49c4035
  action:
    - service: switch.toggle
      entity_id: switch.shelly_1pm

3. Fire the event directly from the HA companion / Button Fire Event
   --> The bulb is switching ON and OFF
   --> Verify-in Tags if ce1685b2-0bdf-4786-bea4-39caa49c4035 was used == yes
4. Swipe Huawei in order to obtain the same result
   --> a new tag is created
   --> the bulb remains switched off

In conclusion
if I used Fire Event button directly from HA companion the phone trigger the action and in TAGS is used the device id which was created, but if I put the same values in the automation I am not able to obtain the same behavior

Errors when scanning tags

Hi,

I brought a tag reader pre-assembled from your store.

I've only just managed to get around to playing with this.

It connected to homeassistant perfectly however the tag reader will only scan intermittently. When it does scan also the following error is displayed in the log:

[16:04:34][D][pn532:159]: Found new tag '83-F4-57-03'
[16:04:34][D][rtttl:093]: Playback finished
[16:04:35][W][i2c:070]: Received NACK on transmit of address 0x24
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:35][W][pn532:099]: Requesting tag read failed!

Any suggestions. I've checked the wiring and everything looks fine. Full log below.

Richard

[16:03:35][D][main:118]: API is connected!
[16:03:35][D][rtttl:037]: Playing song success
[16:03:35][D][light:264]: 'TagReader 28aa56 LED' Setting:
[16:03:35][D][light:273]: State: ON
[16:03:35][D][light:277]: Brightness: 100%
[16:03:35][D][light:286]: Red=0%, Green=0%, Blue=100%
[16:03:35][D][light:289]: White Value: 0%
[16:03:35][D][light:296]: Flash Length: 0.5s
[16:03:35][D][api.connection:604]: Client 'Home Assistant 2021.1.1 (192.168.1.126)' connected successfully!
[16:03:35][D][rtttl:093]: Playback finished
[16:03:48]{d[I][logger:166]: Log initialized
[16:03:48][C][ota:366]: There have been 1 suspected unsuccessful boot attempts.
[16:03:48][I][app:029]: Running through setup()...
[16:03:48][C][esp8266_pwm:017]: Setting up ESP8266 PWM Output...
[16:03:48][C][fastled:010]: Setting up FastLED light...
[16:03:48][C][light:097]: Setting up light 'TagReader 28aa56 LED'...
[16:03:48][D][light:264]: 'TagReader 28aa56 LED' Setting:
[16:03:48][D][light:277]: Brightness: 100%
[16:03:48][D][light:286]: Red=100%, Green=100%, Blue=100%
[16:03:48][D][light:289]: White Value: 0%
[16:03:48][C][pn532:027]: Setting up PN532...
[16:03:48][D][pn532:042]: Found chip PN532
[16:03:48][D][pn532:043]: Firmware ver. 1.6
[16:03:48][C][wifi:033]: Setting up WiFi...
[16:03:48][D][wifi:324]: Starting scan...
[16:03:55][D][wifi:339]: Found networks:
[16:03:55][I][wifi:385]: - 'SHAYLOR' (FC:EC:DA:8A:48:D7) ▂▄▆█
[16:03:55][D][wifi:386]: Channel: 1
[16:03:55][D][wifi:387]: RSSI: -49 dB
[16:03:55][D][wifi:389]: - '💩' (FE:EC:DA:8A:48:D7) ▂▄▆█
[16:03:55][D][wifi:389]: - '' (0E:EC:DA:8A:48:D7) ▂▄▆█
[16:03:55][D][wifi:389]: - 'VM7752782' (40:0D:10:E6:CC:29) ▂▄▆█
[16:03:55][D][wifi:389]: - 'Virgin Media' (52:0D:10:E6:CC:29) ▂▄▆█
[16:03:55][D][wifi:389]: - 'VM5176461' (40:0D:10:91:E8:51) ▂▄▆█
[16:03:55][D][wifi:389]: - 'Virgin Media' (52:0D:10:91:E8:51) ▂▄▆█
[16:03:55][D][wifi:389]: - 'VM0677846' (48:D3:43:F2:4D:81) ▂▄▆█
[16:03:55][D][wifi:389]: - 'DIRECT-HPLAPTOP-HD6SA5KImsxI' (D0:C5:D3:7B:3C:7B) ▂▄▆█
[16:03:55][D][wifi:389]: - 'VM5176461' (C8:D1:2A:98:01:64) ▂▄▆█
[16:03:55][D][wifi:389]: - 'Virgin Media' (5A:D3:43:F2:4D:81) ▂▄▆█
[16:03:55][D][wifi:389]: - 'SKYD31A5' (24:A7:DC:DA:5B:72) ▂▄▆█
[16:03:55][D][wifi:389]: - 'VM3563805' (C0:05:C2:2E:BA:99) ▂▄▆█
[16:03:55][I][wifi:194]: WiFi Connecting to 'SHAYLOR'...
[16:03:56][I][wifi:457]: WiFi Connected!
[16:03:56][C][wifi:303]: SSID: 'SHAYLOR'
[16:03:56][C][wifi:304]: IP Address: 192.168.1.85
[16:03:56][C][wifi:306]: BSSID: FC:EC:DA:8A:48:D7
[16:03:56][C][wifi:307]: Hostname: 'tagreader_28aa56'
[16:03:56][C][wifi:311]: Signal strength: -51 dB ▂▄▆█
[16:03:56][C][wifi:315]: Channel: 1
[16:03:56][C][wifi:316]: Subnet: 255.255.255.0
[16:03:56][C][wifi:317]: Gateway: 192.168.1.1
[16:03:56][C][wifi:318]: DNS1: 192.168.1.126
[16:03:56][C][wifi:319]: DNS2: 1.1.1.1
[16:03:56][D][wifi:466]: Disabling AP...
[16:03:56][C][ota:029]: Over-The-Air Updates:
[16:03:56][C][ota:030]: Address: tagreader_28aa56.local:8266
[16:03:56][C][api:022]: Setting up Home Assistant API server...
[16:03:56][I][app:059]: setup() finished successfully!
[16:03:56][I][app:105]: ESPHome version 1.16.0-dev compiled on Oct 27 2020, 21:37:05
[16:03:56][C][wifi:443]: WiFi:
[16:03:56][C][wifi:303]: SSID: 'SHAYLOR'
[16:03:56][C][wifi:304]: IP Address: 192.168.1.85
[16:03:56][C][wifi:306]: BSSID: FC:EC:DA:8A:48:D7
[16:03:56][C][wifi:307]: Hostname: 'tagreader_28aa56'
[16:03:56][C][wifi:311]: Signal strength: -48 dB ▂▄▆█
[16:03:56][C][wifi:315]: Channel: 1
[16:03:56][C][wifi:316]: Subnet: 255.255.255.0
[16:03:56][C][wifi:317]: Gateway: 192.168.1.1
[16:03:56][C][wifi:318]: DNS1: 192.168.1.126
[16:03:56][C][wifi:319]: DNS2: 1.1.1.1
[16:03:56][C][i2c:028]: I2C Bus:
[16:03:56][C][i2c:029]: SDA Pin: GPIO4
[16:03:56][C][i2c:030]: SCL Pin: GPIO5
[16:03:56][C][i2c:031]: Frequency: 400000 Hz
[16:03:56][C][template.switch:058]: Template Switch 'TagReader 28aa56 Buzzer Enabled'
[16:03:56][C][template.switch:058]: Icon: 'mdi:volume-high'
[16:03:56][C][template.switch:059]: Restore State: NO
[16:03:56][C][template.switch:060]: Optimistic: YES
[16:03:56][C][template.switch:058]: Template Switch 'TagReader 28aa56 LED enabled'
[16:03:56][C][template.switch:058]: Icon: 'mdi:alarm-light-outline'
[16:03:56][C][template.switch:059]: Restore State: NO
[16:03:56][C][template.switch:060]: Optimistic: YES
[16:03:56][C][esp8266_pwm:022]: ESP8266 PWM:
[16:03:56][C][esp8266_pwm:023]: Pin: GPIO13 (Mode: OUTPUT)
[16:03:56][C][esp8266_pwm:024]: Frequency: 1000.0 Hz
[16:03:56][C][fastled:019]: FastLED light:
[16:03:56][C][fastled:020]: Num LEDs: 1
[16:03:56][C][fastled:021]: Max refresh rate: 400
[16:03:56][C][logger:185]: Logger:
[16:03:56][C][logger:186]: Level: DEBUG
[16:03:56][C][logger:187]: Log Baud Rate: 115200
[16:03:56][C][logger:188]: Hardware UART: UART0
[16:03:56][C][light:177]: Light 'TagReader 28aa56 LED'
[16:03:56][C][light:179]: Default Transition Length: 0.0s
[16:03:56][C][light:180]: Gamma Correct: 2.80
[16:03:57][C][rtttl:017]: Rtttl
[16:03:57][C][pn532:321]: PN532:
[16:03:57][C][pn532:333]: Update Interval: 1.0s
[16:03:57][C][pn532_i2c:041]: Address: 0x24
[16:03:57][C][captive_portal:169]: Captive Portal:
[16:03:57][C][ota:029]: Over-The-Air Updates:
[16:03:57][C][ota:030]: Address: tagreader_28aa56.local:8266
[16:03:57][C][api:095]: API Server:
[16:03:57][C][api:096]: Address: tagreader_28aa56.local:6053
[16:03:58][D][main:118]: API is connected!
[16:03:58][D][rtttl:037]: Playing song success
[16:03:58][D][light:264]: 'TagReader 28aa56 LED' Setting:
[16:03:58][D][light:273]: State: ON
[16:03:58][D][light:277]: Brightness: 100%
[16:03:58][D][light:286]: Red=0%, Green=0%, Blue=100%
[16:03:58][D][light:289]: White Value: 0%
[16:03:58][D][light:296]: Flash Length: 0.5s
[16:03:58][D][api.connection:604]: Client 'Home Assistant 2021.1.1 (192.168.1.126)' connected successfully!
[16:03:59][D][rtttl:093]: Playback finished
[16:04:00][D][pn532:159]: Found new tag '83-F4-57-03'
[16:04:02][W][i2c:070]: Received NACK on transmit of address 0x24
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][i2c:086]: Requesting 1 bytes from 0x24 failed!
[16:04:02][W][pn532:099]: Requesting tag read failed!

New tag ID gets created every time I scan my mobile device (Pixel 4)

Using the NFC tag / plastic card that came with the device works fine; it registers only once when scanning.

Using my Android device (Pixel 4); I am seeing a new tag generate each time I scan my phone to the tag reader. Is this expected behavior?

Unstable WiFi connection

The WiFi connection of the esp8266 to the network is unstable.
When connecting the pn532 module and after the setup of the module the WiFi connection and connection to the API stops & hangs often as evidenced by missing pings.

When the module is (physically) connected in HSU mode (or not setup) the connection is stable.

your "buy me a coffee link" is not working ;)

Tried to contact you on any other way, but couldn't find any contact data.
So I though I could open a case that can quickly be closed again 👍

Your link on https://github.com/adonno/tagreader to "buy me a coffee" is not working.
Update it, and I'll get you one ;)

Like your project! Thanks!

- Add condition to read only once every 5 seconds

tagreader/tagreader.yaml

Line 178 in 1f0f892

#TODO - Add condition to read only once every 5 seconds

HID iClass Badge Tag scans a different UID each time

Hello,

I just received the Plug-n-Play tag scanner from Adonno - Thank you!

While I will generally use it for normal tags (like the ones included), I was hoping to also be able to use my work badge, which is a HID iClass badge. Unlike HID Prox (125 kHz), the HID iClass badges are 13.56 mHz - therefore they are read by the scanner.

The problem is that I am getting a different UID each time I scan the badge. I assume this is likely because HID iClass works on a challenge/response type of security system. But is there any hidden field that can be read by the scanner that would be constant each time from a specific HID iClass badge?

Cannot buy a reader

It appears that your Cart may not be working correctly. When I select the item + colors of the reader, and then add to cart, it takes me to the Cart, which says it is empty.

Are there other ways of purchasing a reader?

rfidreader_tag_ko

when does this run?

- service: rfidreader_tag_ko
   then:
   - rtttl.play: "beep:d=8,o=5,b=100:b"

I thought it might work if the tag is disabled in home assistant but there is no option for this

Thanks a lot

ESPHome tag_scanned events

From 0.115.0 the Home Assistant ESPHome integration supports sending to the tag component directly.

home-assistant/core#40128
home-assistant/core#40130
home-assistant/core#40132

This will also be released as an action in ESPHome in a future release:

esphome/esphome#1281

pn532:
  ...
  on_tag:
    then:
      - homeassistant.tag_scanned: !lambda 'return x;'

Before that is released though in ESPHome, you can use:

pn532:
  ...
  on_tag:
    then:
      - homeassistant.event:
          event: esphome.tag_scanned
          data:
            tag_id: !lambda 'return x;'

Disable led and buzzer from code?

I'm have the NFC board and the Wemos D1 mini but not the LED and Buzzer. What alternations to the code do I need to make to test the scanning capabilities before I order the missing parts?

actually read contents of NFC tag

Hi,

thanks for this great little device.

Can this be used to actually transmit the contents of the NFC tag to home-assistant?

I would like to store Spotify URIs on the tags which then would be used to play the item. Currently this works via automation but it means that I would have to create an automation linking every tag id to a Spotify URI....

Thanks

Mqtt instead of homeassistant API

Thank you for this project.
Is It possibile use mqtt instead of homeassistant API?
Can you provide an example in case?
Thank you

Expose Ndef to act as a tag

PN532 should be able to expose the NDEF, this would make the tag reader a configurable tag with i.e.
wifi settings ...
or even maybe a dynamic game further down the line

Discord links in README.md don't work

The new discord links added by PR 36 don't work:

1. The badges just link to a static "Chat xx online" image and don't open discord

2. The discord link (https://discord.gg/ZsfSyj) under the Discord heading doesn't work for me. Is this the correct link?

STL printing in two colors

Do you have any recommendations on how to print your STLs in 2 colors? It looks like I need 2 parts to merge. Sorry, I'm really new to 3d printing, any help would be really appreciated!

Wiegand

Are there any future plans to integrate Wiegand protocol?

I have been playing around with https://github.com/esprfid/esp-rfid but this does not seem to be supported anymore.

Would be a "nice to have"?

No NFC Tag is reading

I Build everything like in the description but no tag arrived in Home Assistant NFC
i add tham vie Mobile but nothing happen when i use tham on the reader

Not an issue but a question

What software did you use to create ag_reader_schematics_v2.png
I have been looking for something usefull for some time.
If this question is not welcome here please delete

Thanks

Unable to order on website !

Sorry for noise as it's not directly relevant to code published here but as there is absolutely no contact info (email or form) on your website, how do I order the boxes you offer for the tagreader as your shop is not working in Firefox ! I keep adding products at cart, I get Product added message showing up but when I access cart it's always empty !

Thanks

Vincèn

Which WS2812 ?

The WS2812 offers following alternatives:

• SK6812 RGB WW
• WS2812B White
• WS2812B Black
• SK6812 RGB W
• SK6812 NWW

What are the differences, which one to use for my 1st reader?

Automatic Enable Buzzer and/or Led Light

Thanks for all your great work!
Is possible to enable directly in esphome code the buzzer and/or the light?
Because every time it reboot i need to reenable it on ha.
Thanks

NFC Tags not read

My setup does not read any NFC Tags. They simply do not show up in the "Tags" view in HA when I place them near the reader.
Bascially, the communication between the ESP and HA seems to work ok as I can turn on and off the LED via the Lovelace UI.
The PN532 seems to be powered on at least as the red LED is constantly on.

Any hints on how I could debug this?

Tag Reader generates a tag ID every time I scan my phone

Using the NFC tag / plastic card that came with the device works fine; it registers only once when scanning.

Using my Android device (Pixel 4); I am seeing a new tag generate each time I scan my phone to the tag reader. Is this expected behavior?

No scan after a few minutes

Hi,

I made the prototype and test it. everything is ok but after a few minutes i hear the buzzer and then no more scan can be done.
Like if it shutdown ou hibernate...

I have to launch the show logs on esphome flasher to wake up ... else nothing works

Could you help ?

Component Links Not Working

The Aliexpress links for the device components are invalid.

Can these be replaced with working ones?

tagreader on wifi but homeassistant not detecting them

I'm running latest homeassistant 1.117(?), I got two tagreaders, I configure them via their own access point and I can now see them on the network (can ping them) but homeassistant does not come up with a notification.

Any way to manually add the readers via Integration as I know their ips ?

Use Hardware spi

Esphome supports Hardware SPI why not use it?

the only thing you have to do is use the dedicated pins:

spi:
  clk_pin: D5
  mosi_pin: D7
  miso_pin: D6

then Esphome will use hardware SPI:

[12:00:12][C][spi:081]: SPI bus:
[12:00:12][C][spi:082]:   CLK Pin: GPIO14 (Mode: OUTPUT)
[12:00:12][C][spi:083]:   MISO Pin: GPIO12 (Mode: INPUT)
[12:00:12][C][spi:084]:   MOSI Pin: GPIO13 (Mode: OUTPUT)
[12:00:12][C][spi:085]:   Using HW SPI: YES

cs_pin can stay D3
buzzer can stay D8
but LED needs a new pin

D1+RC522

hi, thanks for your guidance. I already have an D1 and RC522. do you know how i can connect it to my esp? and the code in ESPHOME changes? thank you so much

Scan "transmission" intermittency

I'm still breadboarding this out so have simple and easy reconfiguration. I'm using a NodeMCUv2 running the tagreader.yaml as provided (although the name is rfid_one). Otherwise it is the standard setup.

Plug in the USB and the logs on HA show no scanning. Odd so i connect the serial monitor and see the output start reeling. I am scanning the tags fine. It is the connection to HA that is the problem. So I watch more and notice that it is connecting to HA for about 7 seconds at a time. It is then staying disconnected for 10 to 70 seconds. I'm in the same room as my wifi access point so its not interference or signal loss.

If there is a power saving mode so once a tag is scanned the system wakes up and then sends adding a delay to the process but functioning i'd be happy as it would have worked (albeit slowly).

Created a Remix of your case Cover

Hi, I remixed one cover of your 3D model cases.

One that has thinner space for the LED to show up better when using darker colors (like black icon). And one that has a thin grid to make the buzzer a little bit louder for those who need it.

The link is here.

Thanks!

Scanning an Android phone as a tag?

When using my android phone as a tag, and scanning it on the scanner, Home Assistant recognizes it as a different tag each time it's scanned.

Any tips on how to "lock down" just one tag id to my phone?

D1 Mini won't boot with PN532 power connected

Initially had same issue on a NodeMCU - then realised it was underpowered for the PN532.
Switched to a D1 Mini - but same, it won't boot to ESP Home when the power is connected.
Boots in fine when Power and GND disconnected - but then obviously can't wake the PN532

Any ideas?

Checked Cables and Pins.

Minimum power source / smallest power brick?

Got the tag reader but now wondering what's the smallest needed cable/power brick needed to drive this reliably ?

Any recommendations ?

Piezo buzzer volume is too low | INFO

There is any possibility to increase the volume of the piezo buzzer?

LED when writing

we should make use of the LED when the tag reader is in write mode.
The LED could be red to indicate that it will write.

turn off red LED on PN532

The red led on my PN532 is always on, while the WS2812 led works fine,
how to disable the led on the nfc reader board?

Put PN532 Switches in Images + Schematic to I²C

Hey,

Possibly like many others, the recent Home Assistant announcements brought me to your project. I literally just finished my first self-soldered tag reader 🥳 . Clearly lacking talent, the first device ended up in smoke, the second one had a buzzer for 2 seconds only before gravity decided that it will do well enough w/o it 🙈.

Disclosing that I am a total beginner I have a small feedback on documentation:

Please put the PN532 switches in your images + schematic to I²C.

AFAICT, the pictures used in the README.md still have the switches put to SPI, see:

• https://github.com/adonno/tagreader/blob/master/docs/cases.jpg
• https://github.com/adonno/tagreader/blob/master/docs/open-case.jpg

In the schematic, the switches are set to HSU, see:

• https://github.com/adonno/tagreader/blob/master/Schematics/tag_reader_schematics_v2.png

Of course, I read that the switches have to be put to I²C and afterwards I learned that this was introduced with release 4.0. But being new in that game, things easily overwhelm and I was unsure if the positions were correct. So any (visual) guidance is helpful.

In my particular case, PN532 wasn't scanning because I simply inverted the setting. Luckily only 2 options exist, hence I was able to solve the "problem" myself. But for future beginners to come, you might want to spare them efforts and headaches.

Thanks,
Martin

REQUEST: Beep when read

I heard an initialization beep from the unit, so I'm wondering if it can be made to beep when successfully read?

Don't scan nfc tag (Installed latest code using latest esphome dev)

Hi, as object tag reader doesn't scan anything. Anymore.
Old code and esphome (not dev and not beta work)
I alse listen to buzzer previous code when connect to ha sing a Jingle (after like 10 seconds)
With new code versione only a beep just connected (after like 0 second)
Anyone have this problem?
Thanks

Inform that NDEF will replace UID when present

Whenever a tag with a NDEF is scanned, check if there is an automation for that tag, and if so, replace the UID by NDEF in the automation

This is to avoid that a Tag would trigger 2 automations (one based on the NDEF another on the UID) at once. If users want to have a different action based on the device they use to read the tag, they will have to set it up by device.

Not sure if this should be managed on Home-Assistant side though

Need help to use your code with Arduino Uno + Ethernet Shield and Wiegand26 NFC reader

Hello

I can't use wifi to connect my NFC reader to Home-Assistant.
I would like to do it with Arduino Uno + Ethernet Shield but I don't know how to change the code to work with HA?
Could you help me how it works with ESPHOME to adapt for arduino uno and ethernet shield please?

Thanks a lot,

Regards

Ben

STEP Files

Hi,
could you share the step files in addition to the STLs? I'd like to modify the case to fit the RC522 reader.