Multiple TAG reader support

Third party integrations AppDaemon
1

For my alarm system I use an NFC tag reader and the Alarmo Alarm panel integration and an ESPhome tag reader. This works almost perfect, but I want to use another tag reader at the backdoor. For nfc_tag_scanned this just works great. Both tag readers trigger an nfc_tag_scanned event which I handle in AppDaemon.

I also use a sound and RGB led on the ESPhome tag readers, but for that to work from Appdaemon, I need to know from which tag reader the nfc_tag_scanned event came from so i can send data (LED and sound) to the right tag_reader.

Does the nfc_tag_scanned even als contains the device_id where the event came from? I have searched the doc’s, but could not find anythibng (maybey I look in the wrong place

Regards, Harry

2

Hi,
Did you find a solution for this? I’m also currently trying to know what tag reader was used in my scenario.

3

Hi,
No did not find a solution yet, but temporarily send sound/ligth information to boh tag readers. For now this works great
Regards, Harry

4

I use multiple tag readers, and tags. (for music, but same issue in the end)

The trig is to make it a manual event, not a tag scan from the drop down.
You add the type “tag scanned” and ask it to match a tag and reader.
In my case 1 tag gets 2 readers, so I can use the tag on multiple places, but you can reverse that logic to a automation per reader instead of per tag.

To get the device, use the dev tools and listen to the event “tag scanned”

I use this piece of code:

triggers:
  - alias: Scanner Livingroom
    event_type: tag_scanned
    event_data:
      tag_id: xx-xx-xx-xx-xx-xx-81
      device_id: $device_id_1
    id: Livingroom
    trigger: event
  - alias: scanner kantoor
    event_type: tag_scanned
    event_data:
      tag_id: xx-xx-xx-xx-xx-xx-81
      device_id: $device_id_1
    id: Office
    trigger: event

In actions you can check for the Trigger-id :wink: