Home Assistant Tags

Blog
83

yup!! not doing that!!! :nauseated_face:

84

same here :slight_smile: , gonna use my smartwatch for now :slight_smile:
but thnx for sharing

1 Like
86

QUESTION: Fantastic project, and I want to do just the same. My understanding from the line of codes that I am reading is that the music comes from a Spotify account, right?

87

Same here. I can always scan tags in, Say, the Shortcuts app but after I create the automation and want to actually use the tag, it works MAYBE in 1 case out of 20. iPhone 11 Pro., iOS 14. Same in 12 and 13.

88

Looks great and you must be awfully busy now fulfilling all the orders. I ordered 15/9, any idea on when you can ship? Thereā€™s no contact info in the order confirmation so thatā€™s why Iā€™m posting here

89

So when you create an automation for a tag in the GUI, it generates something that looks like this:

  trigger:
  - platform: tag
    tag_id: xxxxxxxxxxxxxx
  condition: []
  action:

Thatā€™s different than the samples Iā€™ve seen where they use an event trigger.

Does the tag_id thatā€™s part of the trigger mean that itā€™s only going to process that particular tag id? Does it act as a filter at the trigger level do you donā€™t need some condition to make sure you have the correct tag id?

There doesnā€™t seem to be any documentation yet on that tag platform.

90

It will only trigger if that tag_id is scanned.

I agree that there is an inconsistency between the examples and the code created by the automation editor. Odd.

91

I canā€™t seem to find it now, but I think I read somewhere that tags created with the phone app cannot be read by the device created by @adonno. Am I remembering correctly or am I on crack?

92

That is correct. The stand alone reader (donā€™t know about all of them) cannot read all of the data on the tag for some reason. You can still use either, but your trigger id will be different with the tag reader than it is on the phone. I use NodeRed and its pretty easy to get identifying information for each tag into a switch block at least.

93

OK. Thank you for the info. I must be having another problem then. The reader I built is not getting anything from the tags I wrote with the phone. I wave the tag and nothing happens, but the phone reads them just fine. Unfortunately, I do not currently have another tag to test with. I guess Iā€™ll be hitting Amazon today. :slight_smile:

94

I had mixed luck with some tags. I know some are read only, some are write all you want, and some are write once. I had some issues with the sample cards that came with the NFC sensor that adonno used (I bought it off Amazon). A pack of cards also from Amazon all wrote and read fine though.

95

Ok. Maybe it is just those cards then. The ones I have been testing are the ones that came with the reader. I have some 215 sticker somewhere that I got to make amiibos for my kids. I need to find those, or just try an amiibo. lol

96

I would like to connect the lego dimensions portal via a separate raspberry pi to Hass, how would I go about to achieve this? Any ideas?

97

Hi, Just built this.

I can successfully read tags from it into HA.

I have also tried the HA APP on my phone, Samsung S9 running the companion app ver 2.5.0

When I scan these

20201007_094403
20201007_0944031441Ɨ1303 335 KB

my phone recognises them and it appears in HA as

 e6a334ef-dfc0-4797-a60a-c17f7662b063

When I scan the same card on the tagreader I get the serial number only, as stated in a previous post and is not an issue.

My problem is my phone is unable to read these

20201007_094414
20201007_0944141193Ɨ1399 321 KB

But my tagreader can, so what is the difference between the two?

98

The blue ones are probably 125KHz tags, while the cards are 13.5MHz tags. Iā€™ve not yet seen a phone with a 125KHz RFID reader.

1 Like
99

Same here, build my tag reader and seems to work. The supplied card and blue tag function as follows:

  • the card has a 4 byte ID and if I use it with the tag reader the 4byte id triggers the automation
  • on the same card I can write a full long tag with my phone (Xiaomi9Tpro), but the tag reader doesnā€™t recognise the written long id so the automation doesnā€™t start. But if I read the card with my phone the automation for the long id starts.

The blue tag isnā€™t recognised by the phone.

Me thinks the supplied card is old standard so Iā€™ll wait for the pack of new cards I ordered.

100

Tip for One Plus 5 owners (and maybe for other phones too):
Scanner is located at the camera. Thought my phone couldnā€™t scan NFC, but you really need to put the card at the correct position.

101

With Home Assistant 0.116 it should be possible to use an MQTT tag scanner.
Anyone tried to get it to work? I tried the example described here: https://www.home-assistant.io/integrations/tag.mqtt but I am not getting any results yet.

1 Like
102

My reader has suddenly stopped working, I have double checked my connections as this is my log.

INFO Reading configuration /config/esphome/tag_reader.yaml...
INFO Starting log output from 192.168.0.158 using esphome API
INFO Connecting to 192.168.0.158:6053 (192.168.0.158)
INFO Successfully connected to 192.168.0.158
[19:11:13][I][app:105]: ESPHome version 1.15.2 compiled on Oct  8 2020, 19:01:55
[19:11:13][C][wifi:443]: WiFi:
[19:11:13][C][wifi:303]:   SSID: [redacted]
[19:11:13][C][wifi:304]:   IP Address: 192.168.0.158
[19:11:13][C][wifi:306]:   BSSID: [redacted]
[19:11:13][C][wifi:307]:   Hostname: 'nfc_tag_reader'
[19:11:13][C][wifi:311]:   Signal strength: -66 dB ā–‚ā–„ā–†ā–ˆ
[19:11:13][C][wifi:315]:   Channel: 11
[19:11:13][C][wifi:316]:   Subnet: 255.255.255.0
[19:11:13][C][wifi:317]:   Gateway: 192.168.0.2
[19:11:13][C][wifi:318]:   DNS1: (IP unset)
[19:11:13][C][wifi:319]:   DNS2: (IP unset)
[19:11:13][C][spi:081]: SPI bus:
[19:11:13][C][spi:082]:   CLK Pin: GPIO16 (Mode: OUTPUT)
[19:11:13][C][spi:083]:   MISO Pin: GPIO5 (Mode: INPUT)
[19:11:13][C][spi:084]:   MOSI Pin: GPIO4 (Mode: OUTPUT)
[19:11:13][C][spi:085]:   Using HW SPI: NO
[19:11:13][D][rtttl:093]: Playback finished
[19:11:13][C][template.switch:058]: Template Switch 'NFC Tag Reader Buzzer Enabled'
[19:11:13][C][template.switch:058]:   Icon: 'mdi:volume-high'
[19:11:13][C][template.switch:059]:   Restore State: NO
[19:11:13][C][template.switch:060]:   Optimistic: YES
[19:11:13][C][template.switch:058]: Template Switch 'NFC Tag Reader LED enabled'
[19:11:13][C][template.switch:058]:   Icon: 'mdi:alarm-light-outline'
[19:11:13][C][template.switch:059]:   Restore State: NO
[19:11:13][C][template.switch:060]:   Optimistic: YES
[19:11:13][C][esp8266_pwm:022]: ESP8266 PWM:
[19:11:13][C][esp8266_pwm:023]:   Pin: GPIO15 (Mode: OUTPUT)
[19:11:13][C][esp8266_pwm:024]:   Frequency: 988.0 Hz
[19:11:13][C][fastled:019]: FastLED light:
[19:11:13][C][fastled:020]:   Num LEDs: 1
[19:11:13][C][fastled:021]:   Max refresh rate: 400
[19:11:13][C][logger:185]: Logger:
[19:11:13][C][logger:186]:   Level: DEBUG
[19:11:13][C][logger:187]:   Log Baud Rate: 9600
[19:11:13][C][logger:188]:   Hardware UART: UART0
[19:11:13][C][light:177]: Light 'NFC Tag Reader LED'
[19:11:13][C][light:179]:   Default Transition Length: 0.0s
[19:11:13][C][light:180]:   Gamma Correct: 2.80
[19:11:13][C][pn532:355]: PN532:
[19:11:13][E][pn532:360]: Wake Up command failed!
[19:11:13][C][pn532:367]:   CS Pin: GPIO0 (Mode: OUTPUT)
[19:11:13][C][pn532:368]:   Update Interval: 2.0s
[19:11:13][C][rtttl:017]: Rtttl
[19:11:13][C][captive_portal:169]: Captive Portal:
[19:11:13][C][ota:029]: Over-The-Air Updates:
[19:11:13][C][ota:030]:   Address: 192.168.0.158:8266
[19:11:13][C][api:095]: API Server:
[19:11:13][C][api:096]:   Address: 192.168.0.158:6053

Not sure if it is coincidental with the 0.116 update but
[19:11:13][E][pn532:360]: Wake Up command failed! seems to be the problem?

Regards,

103

Iā€™ve been working on setting up this board myself and every time I get this error it has been related to the power connection from the NFC chip to board. I know you said you already checked them but I would look again. Also make sure you are supplying 5v.