Tag Node (beta)

[zachowj]

Tag Node (beta)

Sends an output when Home Assistant receives a tag scanned event for a configured tag id.

• trigger from multiple tags
• only trigger if from a defined device

[ervede]

Awesome node!!
Within the properties (when editing the node) there are options to configure:

• Tag (tag_name)
• Devices (device_id)

My suggestion is to put user_id also to this list
With the expectation that when you block a user in HA it will also stop this user to enable the tag.

[zachowj]

How do you block a user in HA?

I could see adding a user as a possible condition to the node. I think it would need to follow the same conventions as tag_name and device_id do now. Where the user that scanned the tag would need to be on the user list.

What you looking for could be done but using a subflow or if it's a one-off API node to a switch node.

[jimmhead]

Great node, makes scanning tags so much easier.

My suggestion would be to have the option to work with any tag rather than defining the list of tags (similar to listening to all tag_scanned events, but with the tag name included)

I've got a series of nfc cards to play music, the tag name has everything included in it to play the correct album or playlist through node red so I don't need to set anything up for each new tag, however I currently have to add each tag to the list in the node to get it to work

[kocmocgim]

I don't see tag's name

[zachowj]

Does it fill in if you click on the Update Tag List?

[kocmocgim]

If i set a specific name for tag in home assistant

[zachowj]

I was under the impression that you couldn't create a tag in the UI without giving it a name.

I'll change it so if the name doesn't exist it will display the tag id.

[kocmocgim]

Thank you 👍

[webbson]

I would like it to be possible to allow any tags to be scanned, so that there is a simple way of getting the name of the card currently scanned.

Then I could replace my own function with this. Today I have to listen to tag_scanned event, then call the tag/list websocket and then filter out the correct tag from there to be able to show the name of the tag scanned.

[zachowj]

That was added in v0.35.0 and the tag name should exists in the eventData