Impressive. I just installed 20 Tuya devices and 4 RSTP cameras to use with an ancient Synology DSM and am now planning to use HA. I have not had so much fun since I installed Linux 0.9 from floppy disks back in the day. You folk are doing something really cool.
Great work thank you very much for all you do. About the state of the data table, would be great if in the cogs menu we could save as a preset with a name and so by defaul, the state is in the local browser but then we can choose to select as a preset saved in our user profile and even set it as a default
What you guys are building is fantastic and much needed in this world of corporate greed. The only thing I feel is missing is that we tend to the needs of the tinkerer 100% but have somewhat failed to make the transition into the HS world as pain free as possible. Been in this environment for a bit more than a year now and I just start to come out of the constant frustration phase. One very important obstical for beginners is the gui. It's a very nice feature that you can build it exactly as you want it but I feel it's the wrong default. Sure it builds it self but who starts up their HA journey with a complete setup of devices? No, that's not how it works. When you start you probably will only have a very limited number of devices attached and when you as much as touches the default build, trying to add or change something, the attitude is "we'll, you're on your own, kid". Problem is also the inability to get the default gui to work for real on different screen layout/sizes. So, in the same time as you desperatly trying to get the grip of how the structure of HA works and what does what, you are also supposed to maintain and constantly update a handful of guis every time something is added/replaces/removed. It's an overwhelming task that is far from ideal for other then advanced users. What we should desperately need to do to make the transition easier is a default gui that is more adaptive to different screen variations, built itself and kept doing so even if the user did change or replaced something and then of course, being able to do so without having to master yaml from day one. A default gui that you could live with and looks nice enough, until you have your feet on dry land with the rest of the home automation project. We have to realise that a home can be lived in by other people then the tinkerer and to make HA a success we need to not only have tools for the tinkerer but also make the ha project tolerable for the rest of the family, that suffers the consequences of the project, or the risk of project shutdown is very high. It will be thrown out by an angry mob, consisting of wife and kids. This concept already exists. Take a look at Dwain's dashboard and you see what I mean. Takes away a lot of headakes and keeps the family happy while I can concentrate on getting things to work properly. So the thing already exists. Well than, case closed. Probably not. Thing is you need to reach a level of growth before you will even find those features that you so desperately needed day one.
i'm disappointed that timers can't be managed from assist for devices that are not esp32, such as using assist from browser or tablet (ip cam + stream assist). But I created a script that accepts a duration and a text field and with a bit of attempts I managed to do exactly the same with my system. This means implementing the function in HA should not be that hard
Wondering if I can make android tablets smart displays using home assistant and kiosk browser? Would really love to get rid of my nest hubs at some point. Just annoyed about these at this point.
Yes, I have 6 Kindle Fire devices that have been repurposed and running Fully Kiosk, along with an old Android phone that drives some monitors via a USB-C to HDMI connector.
Impressive. I just installed 20 Tuya devices and 4 RSTP cameras to use with an ancient Synology DSM and am now planning to use HA. I have not had so much fun since I installed Linux 0.9 from floppy disks back in the day. You folk are doing something really cool.
Thanks for all the work you put into the product.
I think we need the homeassistant skyline on the default homeassistant dasboard in the background on the bottom.
Wow! Another cool feature that I always wanted. Reverse engineering Blueprints. 👌 ... and I'm only half way through the video.
sad youtubers selling blueprints until yesterday
Great work thank you very much for all you do.
About the state of the data table, would be great if in the cogs menu we could save as a preset with a name and so by defaul, the state is in the local browser but then we can choose to select as a preset saved in our user profile and even set it as a default
keep it up
What you guys are building is fantastic and much needed in this world of corporate greed.
The only thing I feel is missing is that we tend to the needs of the tinkerer 100% but have somewhat failed to make the transition into the HS world as pain free as possible.
Been in this environment for a bit more than a year now and I just start to come out of the constant frustration phase.
One very important obstical for beginners is the gui. It's a very nice feature that you can build it exactly as you want it but I feel it's the wrong default. Sure it builds it self but who starts up their HA journey with a complete setup of devices? No, that's not how it works. When you start you probably will only have a very limited number of devices attached and when you as much as touches the default build, trying to add or change something, the attitude is "we'll, you're on your own, kid". Problem is also the inability to get the default gui to work for real on different screen layout/sizes.
So, in the same time as you desperatly trying to get the grip of how the structure of HA works and what does what, you are also supposed to maintain and constantly update a handful of guis every time something is added/replaces/removed.
It's an overwhelming task that is far from ideal for other then advanced users.
What we should desperately need to do to make the transition easier is a default gui that is more adaptive to different screen variations, built itself and kept doing so even if the user did change or replaced something and then of course, being able to do so without having to master yaml from day one.
A default gui that you could live with and looks nice enough, until you have your feet on dry land with the rest of the home automation project. We have to realise that a home can be lived in by other people then the tinkerer and to make HA a success we need to not only have tools for the tinkerer but also make the ha project tolerable for the rest of the family, that suffers the consequences of the project, or the risk of project shutdown is very high. It will be thrown out by an angry mob, consisting of wife and kids.
This concept already exists.
Take a look at Dwain's dashboard and you see what I mean. Takes away a lot of headakes and keeps the family happy while I can concentrate on getting things to work properly.
So the thing already exists. Well than, case closed.
Probably not. Thing is you need to reach a level of growth before you will even find those features that you so desperately needed day one.
Thanks for the feedback. Rest assured it's already on the roadmap and we are working towards there steadily!
So when is Home Assistant's default theme going to start getting some of that new font love like the website?
MicroWakeWord firmware example is still missing in the firmware repository. Will be there in the next release.
i'm disappointed that timers can't be managed from assist for devices that are not esp32, such as using assist from browser or tablet (ip cam + stream assist). But I created a script that accepts a duration and a text field and with a bit of attempts I managed to do exactly the same with my system. This means implementing the function in HA should not be that hard
Wondering if I can make android tablets smart displays using home assistant and kiosk browser?
Would really love to get rid of my nest hubs at some point. Just annoyed about these at this point.
Yes, I have 6 Kindle Fire devices that have been repurposed and running Fully Kiosk, along with an old Android phone that drives some monitors via a USB-C to HDMI connector.
why only template helpers can be assigned to a device? 🤔🤔
I agree. Would love to see even more
Joost
Knocki is to much expensive. Maybe we could realise this with Aquara vibration Sensor DJT11LM?