I’ve refined my old project with a brand new device style.
This looks like a great project thank you so much for sharing! I have some of the old tag readers which I was going to use for a security project but never did it so I’ve going to convert them for this. I suppose the issue will be flashing the firmware and that those old card readers don’t have a button for Next etc. I wonder if I can use some of my Aqara buttons in the automation for Net, Play/Pause etc instead?
sure you can customize firmware for your tuners. Please check your esp chipset as this new version is “Made for ESPHome” program compatible and this program requires ESP32 chips. Most tagreaders I’ve seen are esp8266. This doesn’t have to be deal breaker for you and not having button and volume knob should make it possible to use old ones even with memory constraints. Thinking of it, I have one custom tagreader working on esp8266 so maybe I should make another yaml just for these old tagreaders. Right now, your on your own, unfortunately.
I’ve just pushed changes to make this firmware compatible with Adonno tagreader so you can switch to this automation and start using MAss library with NFC discs/cards
Let me know if it works for you.
Thanks so much for this - will try tonight!!!
Very nice project!
I had a NFC Tag reader and music in home assistant working 5 years ago or so.
But the custom music service that allow google music back then did break and I did not want to build something on a flaky third party system again and ditched the project.
Now I am looking into it again.
I have one of Adonnos tag readers around.
I want to play playlists with my google homes when reading the tag.
I just setup home assistant to mount my music from my NAS.
That way YouTube Music can not break my setup.
But now I am not sure if I should stick with the build in Home Assistant Media or use Musik Assistant for my local media.
What is your recommendation/opinion on this?
Music Assistant is purpose built around music services and players. In case you’d like multiroom audio, that might be your only option if you’re not willing to invest in Sonos or other dedicated players. And it’s pretty good with mixing sources like local nas and streaming services. I don’t think HAss has ambition to be on par with services provided by MAss. But if you don’t need music catalog and library it might be total overkill for you. While I’m using Sonos and don’t have local music files, MAss with its library is a bit too much for me as I’d rather use ‚favorites’ in streaming services or physical cards with TagTuner 
On the other hand, MAss can be used as integration glue for all your sources and players. So it’s up to you to decide on usage scenarios.
December update:
D1-Custom version based on ESP32 D1 mini with only 16mm high
new blueprint, with shuffle options
This is fantastic. I’m in the process of building 2 to use for my kid’s room and basement so he can choose songs himself.
One thing I am trying to implement into your blueprint (I’m struggling to get the correct syntax) is a max volume entity to the Volume Up action. My kid likes to crank the volume of speakers and I’m trying to prevent his ears from being blown away! I’ve created a max volume input number helper that I was planning to change the value of with another automation based on the time of day. In your blueprint. I’ve added a “max_volume” input
max_volume:
name: Maximum Volume
description: Input number helper that sets the maximum allowed volume
selector:
entity:
filter:
- domain:
- input_number
I know all I need to do is add another condition to the Volume Up action, but I’m not sure what I need to call. I’ve tried the code below but am getting an error in my log and my TagTuner will not do volume up anymore. Would you have any thoughts on this?
- condition: template
value_template: '{{ state_attr(states[trigger.entity_id], "volume_level") | float < states(max_volume) | float }}'
Edit: I’ve set my max volume helper to be between 0 and 1 with a 0.01 step increase.
I would leave the blueprint as it is. This way you can update it any time without loosing compatibility. You want a separate automation with trigger player volume greater then your max and action set volume to max. This should do the trick every time. I also have automations for volume lowering like after 30mins of player idle, set volume to decent levels like 25 or so. This way I never come back to overblown audio. Try that and let me know.
I have tried this way, but have found it isn’t as reliable or reactive as I would like. It seems to sometimes miss that it was turned up or if the knob keeps getting turned, it seems to get missed and the volume just sits way too high. I figured if I was able to add it to the tag tuner automation, then it would only work if the volume was below my threshold. The other reason for including it in the tag tuner automation is one of my tag tuners is connected to a soundbar that is also hooked to the tv. I would like to be able to turn it up and down (ignoring the max threshold) with the remote.
I’ve made volume limiter part of the TagTuner blueprint
Try this import
Thanks! I finally got around to trying to use it. I was previously using your pre-shuffle blueprint. Now that I’ve updated, I get an error stating I’m “Missing input massplayer”. I’m using Sonos and Spotify so I shouldn’t have to enter the Music Assistant player right?
just set the same player there. There is no good way of doing MAss and http/Sonos players in this blueprint.
I’m also getting a similar issue-
ok, you are guys right. I’m sorry. This happened with the new Music Assistant core integration.
I’ve just pushed January blueprint update that was already cookin so refresh or reimport the blueprint and let me know how’s that working.
Works perfectly now, thanks for the quick support. My family’s gonna love the flexibility since it’s super hard to hookup a CD player to my sonos kit.
Hi Luka, great work you did on this project i really like it. I made some changes and added a small display to show the status and song title/artist/album info.
I updated the esphome config and created a separate blueprint for sending the currently playing media info to the tagtuner esphome. Can you add this to the project and merge the blueprint with the current one ?
Here is how it looks like:
Let me know if you want to merge it then i will provide you the esphome config / blueprint and updated STL cover for the display.
/Cheers
looking gooood 
Please feel free to open a PR on github - this way I can keep track of it and you will be automatically credited for your work.
Hi,
I couldn’t figure out how to add it to Home Assistant…
I did the whole process, I have downloaded the Yaml file from your GitHub, transferred it to the esp32 through ESP web tool, but I couldn’t get to connecting the device to my wireless network. So I don’t recognize the device in Home Assistant.
Thank You
