Not sure how you're not making much use of template sensors. They are essential for me. I have literally hundreds of them and use them for so many different things, including fixing stuff that's not been written correctly, usually third parry integrations, but also creating binary sensors for whether an appliance is on/off based on power monitoring. They are totally invaluable for me.
Actually upon reflection of your comment, what I said wasn't really accurate. I use Node-RED for some more complex automations which probably covers off some situations where I might use one. But also I do have 20 or 30 hidden in yaml which I don't think about because they were created before you could create them in the UI. I have managed to trim them down though as Home Assistant has improved, which is probably the point I was getting at. I do think it's great that you can create template sensors in the UI now. For other things, I cover them off in the automation triggers themselves instead. I do really like your idea of having binary sensors based on power monitoring. Thanks for your comment!
Sorry for the delay in reply! I've added the Home Assistant script to GitHub for you: gist.github.com/letsautomatenet/9c84d96eef95592cca87090eb7b0c734 This will pull your current device's location as reported by Home Assistant. If you create a card on your dashboard then it will open a window where you can enter the name of the zone, select the radius and run the script. (It will fail if you don't enter a radius) Make sure you are on a fairly recent version of Home Assistant as the functionality to pass arguments to scripts from a dashboard (entity "more info") card was only recently added.
![[DOKKAN BATTLE] Worldwide Campaign Announcement Video](http://i.ytimg.com/vi/zxfEiMksZQs/mqdefault.jpg)
thanks for this integration its a great clean up of my system...👍
Not sure how you're not making much use of template sensors. They are essential for me. I have literally hundreds of them and use them for so many different things, including fixing stuff that's not been written correctly, usually third parry integrations, but also creating binary sensors for whether an appliance is on/off based on power monitoring. They are totally invaluable for me.
Actually upon reflection of your comment, what I said wasn't really accurate. I use Node-RED for some more complex automations which probably covers off some situations where I might use one.
But also I do have 20 or 30 hidden in yaml which I don't think about because they were created before you could create them in the UI.
I have managed to trim them down though as Home Assistant has improved, which is probably the point I was getting at. I do think it's great that you can create template sensors in the UI now.
For other things, I cover them off in the automation triggers themselves instead.
I do really like your idea of having binary sensors based on power monitoring.
Thanks for your comment!
well made videos, keep it up
how did you make that zone dashboard on 12:04 i really want one for mine. When me and my wife go to important store to easily add.
Sorry for the delay in reply! I've added the Home Assistant script to GitHub for you: gist.github.com/letsautomatenet/9c84d96eef95592cca87090eb7b0c734
This will pull your current device's location as reported by Home Assistant. If you create a card on your dashboard then it will open a window where you can enter the name of the zone, select the radius and run the script. (It will fail if you don't enter a radius) Make sure you are on a fairly recent version of Home Assistant as the functionality to pass arguments to scripts from a dashboard (entity "more info") card was only recently added.