This sounds like a pretty amazing way of controlling things without needing to create a full automation. Something like a air freshener that you may only want on for 10 minutes once triggered, regardless of the trigger condition. I have a couple that could benefit from this type of control instead of a full automation.
That's good case for it. In documentation they also mention lock. Didn't look into detail about that but probably also a easy way to automate for specific tasks (if none home or day vs night etc).
Interesting option, but it's annoying that you have to restart Home Assistant to test changes. Isn't it possible to just reload the templates without restarting HA completely? Cause this is a nogo for a smart home
This seems like a lot of work to go around just using automation templates or services. There isn't a single thing here that can't be done with pretty simple automations. Checking "triggered by" and checking values, setting variables (for night mode for example,) are all your friend. Yaml-only in a plugin written by a third party seems like two things I'd rather not make effort to expose myself to honestly. I don't see an automation mentioned here that couldn't be thrown together pretty quickly and used as a template for others.
Thanks for the comment . you probably missed part where it was said "for some cases" it's much better and easier, for others you may end using automation. Or go wild and use Node red - that's great thing with HA that you always have options - and there is NEVER best way, just way you prefer of doing things!
@@BeardedTinker I didn’t miss that part, I’m just a bit confused about the perceived benefit of using an external tool to do something this simple especially with the recent improvements to the automation interface
Again, it all comes down to preferences. You should be aware that some people never use UI to create automation, ome don't even use visual editor in UI for configuring lovelace in HA. As I've said, there are options and this is one of them. Everyone can go whatever route feels he/she is more comfortable with.
This is very interesting. Alternatively I have found some lights control blueprints in the HA community forum which are so complex, that can, I think, achieve the same result when tweaked correctly. I think they are called "sensor light" and "motion activated light". I will not be pasting links here, but you get the idea.
Sadly, it's not enough. I first used easy automations, then entity controller, then came back to automations... Entity controller lacks a lot of functions 😢
Amazing!!! I have been wanting this since the beginning. Make more videos with various examples and/or tutorials specific to the Entity Controller. I LOVED this video 🙏🏼
Thanks for a very interesting video. I never knew about this HACS integration. I can think of a couple of use cases for this especially on my outside lights
Thanks for this. I've got a lamp at the top of my stairs triggered by an automation and on occasion I would like it on at all times but obviously impossible via a normal automation. This will allow me to configure it to have both work so the light doesn't always turn off when there is no motion.
If you use node red, that's great. But a lot of people don't have need to use it. I removed NR around 3 years back as it didn't bring anything extra to my setup. @notenoughtech uses it really a lot, but we don't take it against him 😉
Agreed. Node-Red is my choice too. Much better when setting up and adjusting to simply 'Deploy' with Ctrl+D, rather than a whole HA Restart every time.
@@BeardedTinker HACS Reolink by fwestenberg brought integration of surveillance cameras in HA to a new level and was by far better than anything else in the core. Of course I used it because nothing else was available. The Reolink core integration which came recently (I think it is not a fork from HACS) lacked on functions at the beginning but soon got even better.
Reolink integration that's now part of HA was made with help of fwestenberg until few days before first release of internal HA integration. They did part ways at that time due to some bugs/ideas how to fix them. But it's good that now internal HA integration has all (or very close to all) what original HACS one had.
@@BeardedTinker watched it all now and already jotting down some notes on what I want to try when work day is done! Frankly I’d like to see this one built in to HA. Looking forward to the next gem you find in HACS :)
Thanks for a very good video. But I fail to see what can be done with this integration that cannot be done with HA as-is ? Perhaps if one goes to extremely complicated event sequences there may be advantages that I haven't seen yet. My fear when using such custom integrations, is that one day they brake because the HA dev team did something, and the amount of work needed to clean up when that happens and you have moved a ton of automations into using this integration.
yeah the big benefit also escapes me, maybe the example was not good enough in comparison. Maybe it's for someone who likes doing things more in code and the code side more simpler?
As I've mentioned in the video - everything that this integration does, can also be done in automation. Question is just complexity. For example - for even on/off automation, you generate more code that same thing in yaml via Entity controller. Add trigger ID to make difference if light is already on, time window with different brightness and you get a VERY long automation, instead od 6-8 lines with two word in yaml. It's just question of preferences of course. Hey, some would even go for blueprints and do it that way - there are options for everyone!
Just gave this a try and can not get it to work. This is what I have in Yaml lfie: entity_controller: front_door_light: sensor: binary_sensor.front_door_open entity: switch.porch_light delay: 5 I can not see what I have wrong/ thx D
I don't see anything wrong with the code. Did you restart HA after adding it to configuration.yaml file? And BTW - you can create virtual light out of switch in HA. That way, light will not be shown as switch, but will be visible as light.porch_light.
Did you solve this? Having exactly the same issue. The trigger goes but doesn't turn on the light and the entity controller never leaves the state of idle. Feel like I missed a step
Brilliant, exactly what i need for my patio lights which are set up exactly like your example. This been bugging me for ages. Cheers
Great! Hope it works out as planned!!!
Amazing! Thank you for telling me about it.
Glad you liked it!!!
Thanks. Downloaded, yet to do anything with it.
Hope you'll find it useful!!
This sounds like a pretty amazing way of controlling things without needing to create a full automation. Something like a air freshener that you may only want on for 10 minutes once triggered, regardless of the trigger condition. I have a couple that could benefit from this type of control instead of a full automation.
That's good case for it. In documentation they also mention lock. Didn't look into detail about that but probably also a easy way to automate for specific tasks (if none home or day vs night etc).
Interesting option, but it's annoying that you have to restart Home Assistant to test changes. Isn't it possible to just reload the templates without restarting HA completely? Cause this is a nogo for a smart home
If author decides to do configuration via UI, you wouldn't need to restart. Try asking on GitHub author.
very good advice thanks i will start use this hacs
Enjoy - hope you find it useful!!!
very cool ill have to pick some door and maybe some motion sensors.
Those add a lot of potential automation possibilities
This seems like a lot of work to go around just using automation templates or services. There isn't a single thing here that can't be done with pretty simple automations. Checking "triggered by" and checking values, setting variables (for night mode for example,) are all your friend. Yaml-only in a plugin written by a third party seems like two things I'd rather not make effort to expose myself to honestly. I don't see an automation mentioned here that couldn't be thrown together pretty quickly and used as a template for others.
Thanks for the comment . you probably missed part where it was said "for some cases" it's much better and easier, for others you may end using automation. Or go wild and use Node red - that's great thing with HA that you always have options - and there is NEVER best way, just way you prefer of doing things!
@@BeardedTinker I didn’t miss that part, I’m just a bit confused about the perceived benefit of using an external tool to do something this simple especially with the recent improvements to the automation interface
Again, it all comes down to preferences. You should be aware that some people never use UI to create automation, ome don't even use visual editor in UI for configuring lovelace in HA. As I've said, there are options and this is one of them. Everyone can go whatever route feels he/she is more comfortable with.
This is very interesting. Alternatively I have found some lights control blueprints in the HA community forum which are so complex, that can, I think, achieve the same result when tweaked correctly. I think they are called "sensor light" and "motion activated light". I will not be pasting links here, but you get the idea.
Sadly, it's not enough. I first used easy automations, then entity controller, then came back to automations...
Entity controller lacks a lot of functions 😢
It's not a replacement, but for some simple tasks it can be easier than automation.
Please make video on how we can use self signed certificate for homeassistant and then use TTS because tts is not working with self signed certificate
Very interesting find. Thank you BT! I'm installing it for my main door right now.
Enjoy! This is really interesting integration!!!
Amazing!!! I have been wanting this since the beginning. Make more videos with various examples and/or tutorials specific to the Entity Controller.
I LOVED this video 🙏🏼
More to come!
Thanks for a very interesting video. I never knew about this HACS integration. I can think of a couple of use cases for this especially on my outside lights
Glad it was helpful and thanks for the comment!!!
Excellent, thanks for sharing, that will be a lot easier for motion controlled lights than bespoke automations
Glad it was helpful! Thank you!!!
Thanks for this. I've got a lamp at the top of my stairs triggered by an automation and on occasion I would like it on at all times but obviously impossible via a normal automation. This will allow me to configure it to have both work so the light doesn't always turn off when there is no motion.
This should fir nicely for that scenarion!
sorry but i really can't find the use of this thing. i can do all of that just through node-red. why not use that?
If you use node red, that's great. But a lot of people don't have need to use it.
I removed NR around 3 years back as it didn't bring anything extra to my setup. @notenoughtech uses it really a lot, but we don't take it against him 😉
Agreed. Node-Red is my choice too. Much better when setting up and adjusting to simply 'Deploy' with Ctrl+D, rather than a whole HA Restart every time.
@@3ATIVE but comparing Node Red to Automation (which it is in a way) - you don't need to restart HA when you create/edit automation.
Many HACS integrations are cool and add missing functionallities, but I would never rely on it for core functions like automations.
Why not? There are more than few that started as HACS integrations and ended up in core HA after some time. (Reolink is excellent example).
@@BeardedTinker HACS Reolink by fwestenberg brought integration of surveillance cameras in HA to a new level and was by far better than anything else in the core. Of course I used it because nothing else was available. The Reolink core integration which came recently (I think it is not a fork from HACS) lacked on functions at the beginning but soon got even better.
Reolink integration that's now part of HA was made with help of fwestenberg until few days before first release of internal HA integration. They did part ways at that time due to some bugs/ideas how to fix them. But it's good that now internal HA integration has all (or very close to all) what original HACS one had.
Now this one sounds interesting and I’m only at the start. Seems like you’ve found another gem in hacs 👍
I think so too! Really interesting concept - something we would normally do with automation... Thanks for the comment Iain!!!
@@BeardedTinker watched it all now and already jotting down some notes on what I want to try when work day is done! Frankly I’d like to see this one built in to HA. Looking forward to the next gem you find in HACS :)
@@iainhay2823 it would be great to have this much power in internal integration.
Thanks for a very good video. But I fail to see what can be done with this integration that cannot be done with HA as-is ? Perhaps if one goes to extremely complicated event sequences there may be advantages that I haven't seen yet. My fear when using such custom integrations, is that one day they brake because the HA dev team did something, and the amount of work needed to clean up when that happens and you have moved a ton of automations into using this integration.
yeah the big benefit also escapes me, maybe the example was not good enough in comparison. Maybe it's for someone who likes doing things more in code and the code side more simpler?
As I've mentioned in the video - everything that this integration does, can also be done in automation. Question is just complexity. For example - for even on/off automation, you generate more code that same thing in yaml via Entity controller.
Add trigger ID to make difference if light is already on, time window with different brightness and you get a VERY long automation, instead od 6-8 lines with two word in yaml.
It's just question of preferences of course.
Hey, some would even go for blueprints and do it that way - there are options for everyone!
Wowser! what a find!
Thanks! Glad you liked it.
Thanks, that sounds good.
It really does! Thanks Adi for the comment!!!
Does it work on Nodered ?
What did you have in mind? You can potentially use entities from this controller in Node Red if that's the question.
Thanks B.T.
Welcome Ron! Thanks for the comment!!!
Just gave this a try and can not get it to work. This is what I have in Yaml lfie:
entity_controller:
front_door_light:
sensor: binary_sensor.front_door_open
entity: switch.porch_light
delay: 5
I can not see what I have wrong/
thx
D
I don't see anything wrong with the code. Did you restart HA after adding it to configuration.yaml file? And BTW - you can create virtual light out of switch in HA. That way, light will not be shown as switch, but will be visible as light.porch_light.
Got it working, just need to wait a few seconds longer, lol. Is there a way to have it stay on?@@BeardedTinker
Light? You can use stay mode: danobot.github.io/ec-docs/config-basic/stay-mode/
Did you solve this? Having exactly the same issue. The trigger goes but doesn't turn on the light and the entity controller never leaves the state of idle. Feel like I missed a step
Good usefull info, but HA, is too much of a headache atm for me to set up yet.
HA will always be a headache LOL I guess that is part of its attraction ....you never stop tinkering
@@emms-place sure, I get it. But my tinkering time is divided by so many other tinkers to do. 😆
There is never enough time to tinker with everything we want
@@BeardedTinker To Tink, or Not To Tink, that is the question... I Tink, therefore, I am! 🤣
@@turboturd7954 HA haha