Це відео не доступне.
Перепрошуємо.
5 Things Home Assistant Needs This Year
Вставка
- Опубліковано 3 сер 2024
- There is no Year Of for Home Assistant this year, but I do have some thoughts on what would make Home Assistant THE smart home platform.
#homeassistant
Who am I?
My Name is Jeff. I am an DIY-er and Automator of boring things. And, of course, a huge Home Assistant fan. Oh, I also live in a house that tweets.
Follow Me:
Github - github.com/thejeffreystone
Twitter - / thejeffreystone / / slackerlabs
On the Web - slacker-labs.com/
Discord - / discord
And if you like this video you could always fuel my automation habit -
Buy a Slacker Labs T-shirt: slackerlabsmerch.square.site/
One Time Donation:
Paypal: www.paypal.com/paypalme/Slack...
Cash App: $slackerlabs
Buy me a coffee: www.buymeacoffee.com/icE6DeBut
.
Or use my Amazon affiliate link which provides a small commission on things you buy without additional cost to you - www.amazon.com/s/ref=as_li_ss...
Affiliate Links:
Music - Epidemic Sound: www.epidemicsound.com/referra...
What is the one feature you think would make Home Assistant the best platform out there?
If they can improve the local voice assistant to do more than just control HA devices (obviously will require internet) would be awesome.
That and making templating easier by not requiring templates... If that makes sense. A way of accomplishing the same thing via basic logic/commands
I would love one simple thing: fix the template editor preview in the developer tools. Right now it does behave differently from how the template entities do, so for complex templates - which are tested and working in the preview - it might fail which is frustrating 😅
One thing I found to help with this is to use variables to pull in the states at the top of the template. That way it is easy to set them to unavailable or xxx or blank and ensure the template does something meaningful rather than throwing an error when something breaks.
@@JaneTaubman that does indeed help to test edge cases and missing values but still there are function calls which are interpreted differently between the UI and code - can’t tell you exactly which ones as I’m out of the office but I have a couple as comments in my yaml code to remind me to not use them 🤣
It's a simple thing, but while they show the last time an automation or script was triggered it would be great to also have a "last edited" column.
That way, when we're working on a new automation or even just updating a recent one, then we can click the column header to sort by edit time to bring it to the top rather than needing to scroll through the list every time just to make a small tweak.
Esp if you can't quite remember the name you gave it a month ago...
The scene "test" button is a must have. It's so annoying...
I only get time to play with Home Assistant when my Daughter is in bed. I still can't check/edit scenes for fear of clicking one with a light in her room...
I would like to see some of the functions from Spook included especially the Repair messages when messing around with Entities and swapping out kit, as it highlights any automations or groups which need changing.
The ability to link entities and attributes together is such an obvious evolution for Home Assistant. I completely agree that having this ability would change the way how we automate things.
Problem is, the devs have a vision of their own and while I do appreciate these types of videos from your and people alike, it seems that only way to make some changes is using the What The Heck month and pray you get enough upvotes.
At least that's what it looks like to me. Great video by the way.
Homeassistant in an Open Source project so build the stuff you want I see and open a pull request. Or going another route and build it as an HACS integration and skip all the ‘official channels’.
Some of the points made in this video are can also be build today - I do use scripts to automate the generation of device and entity groups, use template sensors which abstract the information of individual entities into one ‘logical state’ and are automatically calculated on the values of the entity type in an area (just like Jeff mentioned, all temperature entities in an area are combined into one logical temperature automatically).
Nothing that could not be done today, it’s just a matter of thinking in data layers and decouple actions from entities. But I agree, it would be nice of HA to automatically provide that functionality.
@@PushingPixels_de Non-developers have good ideas too.
another Great Video Jeff. loved all the ideas - especially the room presence /temp one - setting the rooms with the other sensors like the tracker in the person attributes hopefully someone seems this and knows how to code to put this in.
Absolutely hate the Scene feature right now. I work on the automation at night and I don't want to have to roam the entire house to set them or adjust them. That's why there is 0 scenes and I create everything with a script instead.
I use Google Calendar instead of Workday sensor.
I include PERSON NAME [Work] in the google calendar, and create Google Calendar sensors that look for PERSON NAME [Work].
Then have the automation check if PERSON NAME [Work] is on or off to see if that person is working that day or not
Great new set!
Here we go ...
1) Move Automation to it's one sidebar menu,
2) Have some default automations:
a) Notification when new version, HACS, etc.
b) Notification/Monitor devices/entities and set a threshold for how long the device can be offline (Zigbee battery powered devices, etc.)
3) Get smarter with automations - if I light is triggered on, then when to trigger off instead of 2 automations
4) Adding a device of X, suggest automations for it based on the room, etc.
I'm not looking for "clippy" in HA, but there are some things that could come standard to get up and running and stable faster
Oh I like that. Default automations. They could be disabled by default and you just have to enable them if you want to use them.
3) can be done today with TriggerIDs. I have several automations that handle on/off. Motion triggers on and motion clear triggers off
From your mouth to HA’s ears! Great ideas.
Totally agree with all your points!
Additionally I want to test an automation by clicking on a trigger to see if it works based on that trigger.
Scene Test Button - YES!
And the big features needed:
Tags for everything. Basically like areas but on steroids. Especially useful for categorising automations, helpers etc.
Proper support for renaming entities.
A checking system for finding dangling entity references across the configuration.
Moving the energy UI elements into the dashboard so it can be included in other pages. By all means ship with an energy dashboard page ready made, but it should be built out of generic parts not be a special bunch of UI code.
The tracking of users movement over time on the map is a great feature, but the blobs aren’t time stamped.
Ending on a corker: On the iOS app on iPhone the dropdowns are infuriating as they only work if the keyboard is hidden. The is absolutely bonkers as this massive bug has been present at least a year.
Love number 3 - would be amazing to have this smarter person situation sensor!
What a great video! Great suggestions and ideas. I’d personally love to see a few HA supported template automations. There are the top rated community automations, and those are great for me, a tinkerer and programmer, but my 65yr old dad being able to add his own automation for lighting or thermostats using the most common use cases and verified and documented by the HA team would go a long way to making the platform more user friendly for less tech people.
the automation between multiple brands of devices. So not being locked down one suplier/brand. I like the aqara switches to use with sonoff and ikea devices.
Drag and drop will always be the missing big piece of the puzzle
What do you want to drag and where do you want to drop it? Honestly can’t see an area where that would be useful, apart from the dashboard but that needs to get fixed first to not randomly rearrange itself and scale into ugly mode…
We are getting some cool drag and drop in 2023.2 but probably not what you are thinking. I don't really do dashboards and no one in my house really interacts with home assistant directly so im not sure why it would useful.
Love to have a way of designing your own dashboard layouts like you do a website. The current way is just so clunky and confusing.
I’d like to see if I rename an entity it’s also renamed in all automations that use that entity
All great ideas.
I use HA at two locations, I’d love it if when I get a notification and touch it, if it would open the correct one up rather than the one that was used last, doesn’t seem like a big ask.
I didn't even know this was an issue. And I agree. That seems like a proper fix.
I love the sound of number 5!
5
I would love the ability to add custom, changeable attributes to any entity or device and build a new device from different entities (like sensors)
It should also be fine if Home Assistant will become more userfriendly. It should be more easy to add a device and build the automation. When a device is added for example, Home Assistant can ask in which area this device will be used. It knows already what type of device it is. It can ask if I want add an extra suffix for the device name and can create automatically name this device as .___.
And when I go to the device and say "Add Automation" it can give some suggestions, such as time based event, event based on other device etc.. So that I can only answer the questions and building the automation tasks by this way.
Device:Entity … all those devices that you add show up in devices regardless of type (wifi, BT, zigbee), not just the entity.
Like updating Frigate, and the update kills Frigate because it is for the new version of Frigate which I have not installed.
area attributes....YES
I just started with HA, it is hard! It’s like coming in the middle of a movie and trying to figure out whats happening! You better figure on watching hours of UA-cam, there is nothing easy about being a newbie.
I want to more about that perspective. What do you see as the biggest hurdles as a newbie?
@@SlackerLabs First I had to learn the terminology (cards, dashboard, Matter, Zigbee ect). When I watch a UA-cam, they go so fast I must keep replaying the videos. If not for UA-cam the average person would give up in frustration I’m sure 🤣
I think they're working on that last oner with the new beta release, or at least something similar to that.
The entity/device relationship is amazingly muddled and shows the history that devices were added later. Devices are referenced in the data structures by UUID but entities are named. This is probably because originally the configuration was via hand written YAML where entering UUIDs doesn’t work. But the confusing effect of this is that renaming an entity in the UI won’t update its references (eg dashboards and automations); it must be done manually. Eh?!
Some recent changes have really had me shaking my head. Services can now return data? Why? You have entity state and attributes for that. The weather integration users are now needlessly complicated as a result.
The whole data model backing HA is all a bit too fragile IMO. It’s great software, don’t get me wrong, but it drives me nuts at the same time.
Sorry, had to moan.
(Also read your other post)
For as far as I understand what you say, I agree completely.
I just started with HA a few weeks ago, currently only testing on an old RPI. Honestly I wasn't even aware of some of the issues you mentioned in this video. But, I was very surprised and even dissapointed when I found out that HA doesn't have a proper RBAC (Role Based Access Control). Hopefully this is high on their priority list.
I'm not sure it is. It could be. But also not sure the use case.
@@SlackerLabs I'm not comfortable giving someone else access to HA without having the possibility to define what they can access. For example, I don't want other users of my HA to have access to stuff in my bedroom, or a garage door, or some other device only specific users should be able to access. Sure there are some workarounds (e.g. hiding some UI elements, custom dashboards etc.) but AFAIK it currently all comes down to "security through obscurity" - which is not really security. This should be customizable per-user (bonus if there are also user groups with same options). And I do have other potential users in my household whom I'd like to give access to *specific* things but deny some other...
Ahh yea. I think you just get admin and regular users. I think you could set certain things to only be seen by admins.
My smart home is just automated. So I don't have a use for that type of security.
But I think to be good it's going to have to be at the device or entity level. And I think that might get really complex.
Actually entities that were last added to the Database would work I believe.
In regards to the Workday sensor, I have Home Assistant see a shared ICS file of my work Calendar to emulate a similar thing:
If there is no out of office on a weekday, then I'm working.
If there is an entry on a weekend then I'm doing overtime
I do the same, I use a calendar for my schedule as I only work a couple of days now most weeks, but the day can vary. This also lets me compute the alarm time from the work start time and tells me how many days to bill at the end of the month.
What do you use to pull the ICS in ?
@@markloughtonUK iCal from HACS