I'm going to have to get some straight 4 connectors for the tag reader board, since I want to do something similar with the ones that I plan to build for my home.
You are most welcome. I'm glad you find my videos to be helpful in your own projects. I try to give enough information to allow someone to either duplicate my build or easily adapt it to their own needs... even if that does mean that they can tend to be a bit lengthy! Thanks for watching. I appreciate the comment... and it is comments like this that motivate me to continue making videos.
Another great Video!! I am trying to fallow along but i dont see your complete yaml file of all the changes. i did see on the blog that there was a link but it dose not work. Did i miss something? I would like to combine your with the vibration sensor and a buzzer so i have a quiet mode.
Thanks. I just checked the blog and the links there did seem to work for me (these are links to a Github Gist file with the complete ESPHome code). But here is the direct link to that Gist again: gist.github.com/Resinchem/f832d8e7305730cc0af8932d51f22335 Let me know if you are still having issues access it.
You are welcome. You certainly deserve all the credit for the development of the ESPHome code. I did also point folks at your pre-built version in case they don't want to build their own. Thanks to you for the idea and the great implementation.
Thank you for your videos. Which lines of the code do I have to remove to eliminate the Vibrating Motor? I am only interested in having luminous information. Thanks again.
Under the switch section, you need to remove the section for the GPIO switch with the ID of vibra, then you also need to remove every instance of "switch.turn_on: vibra". Alternatively, you can leave all the code as it is and just do not install the vibrating motor in your build. The code will still send the signal to turn the motor on/off, but since it doesn't exist, nothing will happen. The code will still work and it won't cause any errors.
I'm using a Roku as my streaming device, which integrates into Home Assistant as a media player. One of the attributes of the entity is 'app_name' (or source), which reports the service or application that is currently running. I show exactly how I make use of this in Home Assistant in my video on the custom button card: th-cam.com/video/mj2CIKqrQlc/w-d-xo.html Let me know if you have any additional questions, but the above video should explain it pretty well.
You didn't miss it... I did! I have the design up on Thingiverse, but simply forgot to include the link in both the video description and the written blog (both of which I've now corrected). To save you the time, here is the link to the enclosure design files: www.thingiverse.com/thing:6115149 Sorry about that! Many times I shoot the video and write the blog in bits and pieces but try to remember to include all the links when I'm finished. Obviously this is one I missed.
@@ResinChemTech Thanks! Any chance you also have the model file for editing (.f3d or similar)? I'd like to modify it a bit to change the LED used. I could probably use it as is but I'd like to try and incorporate a WS2812b as I already have a few of them lying around.
Unfortunately, in the past I've used Tinkercad for all my simple designs. It only creates the .stl files. I'm very slowly trying to learn Fusion 360... but it's a slow process and a bit overwhelming compared to the simplistic Tinkercad. I'd happily share them if I had them... but the .stl and the sliced .gcode are the only things I have. As an alternative, if you look at my other designs on Thingiverse, you'll find enclosures for the standard ElectroCookie boards. The enclosure for the NFC card reader is the same dimensions... just a bit shorter. But the lid is the same. So you could at least snag a copy of the lid from the ElectroCookie versions that doesn't have the LED hole. Maybe it would be easier to add your own LED opening to that as opposed to trying to "fill the hole" from the NFC version? Then again, maybe I have no idea what I am talking about! 3D design is NOT one of my strengths. I really want to learn more about it, but up until this point, most of my designs are simple rectangular boxes for holding components or proto boards.
Actually, I do have complete control over the entertainment system with voice (primarily using an integrated Harmony hub). The missus primarily interacts with Home Assistant and devices via voice. But as I think I've mentioned in a couple of my other videos, I like to have multiple ways or methods for pretty much all my smart devices. In this case, the TV/Roku can be controlled via voice, NFC tags and a Home Assistant kiosk. Oh... and of course by the original remotes. I've found that after a few years of testing that some folks aren't comfortable with certain methods. Visitors or guests that might not have smart speakers (or even those that have Amazon when I have Google) are often hesitant to interact with the house because they 'don't know what to say'. So most of my devices, like the TV, have an alternate way to control it as well. Pretty much everyone (so far) is pretty comfortable with picking up a card and tapping it after I demo it one time. My elderly dad just won't try to talk to Google, but he'll pick up one of those cards and tap it to turn on the TV. It all depends on your needs. But I do try to always provide multiple methods of accomplishing the same task in my own home.
Yea this would have been perfect for my grandmother in the nursing home. She had a hard time changing channels. You might be onto something.. we need to bring accessibility to the elderly.. her nursing home really pissed me off with all no tech to make people life’s more enjoyable..
Well, it can be difficult to help someone that just says "it doesn't work" without providing any details, but mine is still working and I suspect recent changes to ESPHome have broken the code (I rarely update my existing working ESPHome devices to later versions). I suspect it might be the newer requirement to add a platform under the ota: integration. If you edit the YAML in your ESPHome device's configuration, any improper (or missing) syntax will be highlighted (red underlined). If you don't have it, you might need to add the new platform key under the OTA key: ota: platform: esphome password: your-ota-password Mine shows one other necessary change. Under the switch, there are two instances where the line "restore_state: true" needs to be changed to "restore_mode: RESTORE_DEFAULT_OFF". Once I made these changes, the ESPHome code validated without error. Unfortunately, monthly updates to both Home Assistant and ESPHome also nearly always include breaking changes, so you will often run into code or examples that are outdated. And with the number of videos and blog articles I've created, it is simply impossible for me to go back and keep everything current. It just means that you often have to look at the indicated errors or issues and then the documentation to determine the current syntax or use case (exactly what I did to reply to your comment).
What a great video, I am actually trying to do a project for school assistance with NFC cards, this was very helpful, thank you very much.
You are very welcome! I'm glad you found it helpful. Thanks for the comment.
Very nice idea and simple solution. Thanks for this!
You are most welcome. I hope you found it helpful.
Thanks for watching and taking time to comment.
Well done
Thanks! I appreciate it.. and that you took the time to leave a comment.
I'm going to have to get some straight 4 connectors for the tag reader board, since I want to do something similar with the ones that I plan to build for my home.
I enjoy your videos. Very informative and easy to follow. I've built a couple of your projects, with more on the way, including this one.
Thanks!
You are most welcome. I'm glad you find my videos to be helpful in your own projects. I try to give enough information to allow someone to either duplicate my build or easily adapt it to their own needs... even if that does mean that they can tend to be a bit lengthy!
Thanks for watching. I appreciate the comment... and it is comments like this that motivate me to continue making videos.
I usually do modify things a bit, my WAF is different than yours 😎
Absolutely awesome!! thank you so much!!
Thanks! And you are most welcome. Glad you found it at least somewhat helpful.
I greatly appreciate the comment.. and thanks for watching.
Oh, I will be following up with some other questions on Discord later….
Looking forward to it, as always!
I like the project box you printed. Is the STL available?
I can certainly upload it to Thingiverse. Give me a day or so and I'll follow up here in the comments when it is available.
Just wanted to follow up. I've uploaded the enclosure design to Thingiverse and you can now find it here: www.thingiverse.com/thing:6115149
Another great Video!! I am trying to fallow along but i dont see your complete yaml file of all the changes. i did see on the blog that there was a link but it dose not work. Did i miss something? I would like to combine your with the vibration sensor and a buzzer so i have a quiet mode.
Thanks. I just checked the blog and the links there did seem to work for me (these are links to a Github Gist file with the complete ESPHome code). But here is the direct link to that Gist again: gist.github.com/Resinchem/f832d8e7305730cc0af8932d51f22335
Let me know if you are still having issues access it.
Thanks for the shoutout
You are welcome. You certainly deserve all the credit for the development of the ESPHome code. I did also point folks at your pre-built version in case they don't want to build their own. Thanks to you for the idea and the great implementation.
Thank you for your videos.
Which lines of the code do I have to remove to eliminate the Vibrating Motor?
I am only interested in having luminous information.
Thanks again.
Under the switch section, you need to remove the section for the GPIO switch with the ID of vibra, then you also need to remove every instance of "switch.turn_on: vibra".
Alternatively, you can leave all the code as it is and just do not install the vibrating motor in your build. The code will still send the signal to turn the motor on/off, but since it doesn't exist, nothing will happen. The code will still work and it won't cause any errors.
@@ResinChemTech thanks for your answer
What are you using for Home Assistant to know when/what app is active on the tv?
I'm using a Roku as my streaming device, which integrates into Home Assistant as a media player. One of the attributes of the entity is 'app_name' (or source), which reports the service or application that is currently running. I show exactly how I make use of this in Home Assistant in my video on the custom button card: th-cam.com/video/mj2CIKqrQlc/w-d-xo.html
Let me know if you have any additional questions, but the above video should explain it pretty well.
How to Read Encrypted NFC RFID Card all Sectors, & Clone it to Others Card please help me 😢
what are you using for your hapitic - vibration?
amzn.to/3pqcua9 - I show how this is wired and mounted in the video.
Maybe I'm missing it but is there a link to the 3d model of the case for printing?
You didn't miss it... I did! I have the design up on Thingiverse, but simply forgot to include the link in both the video description and the written blog (both of which I've now corrected). To save you the time, here is the link to the enclosure design files: www.thingiverse.com/thing:6115149
Sorry about that! Many times I shoot the video and write the blog in bits and pieces but try to remember to include all the links when I'm finished. Obviously this is one I missed.
@@ResinChemTech Thanks! Any chance you also have the model file for editing (.f3d or similar)? I'd like to modify it a bit to change the LED used. I could probably use it as is but I'd like to try and incorporate a WS2812b as I already have a few of them lying around.
Unfortunately, in the past I've used Tinkercad for all my simple designs. It only creates the .stl files. I'm very slowly trying to learn Fusion 360... but it's a slow process and a bit overwhelming compared to the simplistic Tinkercad. I'd happily share them if I had them... but the .stl and the sliced .gcode are the only things I have.
As an alternative, if you look at my other designs on Thingiverse, you'll find enclosures for the standard ElectroCookie boards. The enclosure for the NFC card reader is the same dimensions... just a bit shorter. But the lid is the same. So you could at least snag a copy of the lid from the ElectroCookie versions that doesn't have the LED hole. Maybe it would be easier to add your own LED opening to that as opposed to trying to "fill the hole" from the NFC version? Then again, maybe I have no idea what I am talking about! 3D design is NOT one of my strengths. I really want to learn more about it, but up until this point, most of my designs are simple rectangular boxes for holding components or proto boards.
I would do a version with voice commands..
Actually, I do have complete control over the entertainment system with voice (primarily using an integrated Harmony hub). The missus primarily interacts with Home Assistant and devices via voice. But as I think I've mentioned in a couple of my other videos, I like to have multiple ways or methods for pretty much all my smart devices. In this case, the TV/Roku can be controlled via voice, NFC tags and a Home Assistant kiosk. Oh... and of course by the original remotes.
I've found that after a few years of testing that some folks aren't comfortable with certain methods. Visitors or guests that might not have smart speakers (or even those that have Amazon when I have Google) are often hesitant to interact with the house because they 'don't know what to say'. So most of my devices, like the TV, have an alternate way to control it as well. Pretty much everyone (so far) is pretty comfortable with picking up a card and tapping it after I demo it one time. My elderly dad just won't try to talk to Google, but he'll pick up one of those cards and tap it to turn on the TV. It all depends on your needs. But I do try to always provide multiple methods of accomplishing the same task in my own home.
Yea this would have been perfect for my grandmother in the nursing home. She had a hard time changing channels. You might be onto something.. we need to bring accessibility to the elderly.. her nursing home really pissed me off with all no tech to make people life’s more enjoyable..
The code is not working anymore
Well, it can be difficult to help someone that just says "it doesn't work" without providing any details, but mine is still working and I suspect recent changes to ESPHome have broken the code (I rarely update my existing working ESPHome devices to later versions).
I suspect it might be the newer requirement to add a platform under the ota: integration. If you edit the YAML in your ESPHome device's configuration, any improper (or missing) syntax will be highlighted (red underlined). If you don't have it, you might need to add the new platform key under the OTA key:
ota:
platform: esphome
password: your-ota-password
Mine shows one other necessary change. Under the switch, there are two instances where the line "restore_state: true" needs to be changed to "restore_mode: RESTORE_DEFAULT_OFF". Once I made these changes, the ESPHome code validated without error.
Unfortunately, monthly updates to both Home Assistant and ESPHome also nearly always include breaking changes, so you will often run into code or examples that are outdated. And with the number of videos and blog articles I've created, it is simply impossible for me to go back and keep everything current. It just means that you often have to look at the indicated errors or issues and then the documentation to determine the current syntax or use case (exactly what I did to reply to your comment).
@ResinChemTech
Thank you for your answer. It took me some time to find all necessary changes in the code, but now mine is working again.