You do not need to master YAML to create automation. The UI is already there to work you through. Not sure why you say that.
Do you use a screen reader?
Hey Lakini! Product person from the OHF here, nice to meet you and happy to connect for ideas ^^ you can find me on discord under the same handle in the HA server.
I’m not a dev either so we will handle perfectly 
Database & Knowing a fridge is a fridge are complementary solutions from the same main problem - we need to start considering Devices a first class citizen inside HA and that will allow us to understand internally that “whats the average temperature” should exclude the fridge sensor becasue, well, its a fridge. Having a database is going to help us extend this information and allow us all collectively to say “hey this is also a device that requires wall-mounting” or “hey this requires a long setup” and more information that again is tied to the device and not the individual entity.
But again this is roadmap, we aim to share a direction that we might fullfill different ways, some solutions we still don’t have specific details on how.
3 Likes
Definitely looking forward to the privacy changes. Hopefully it’s an RBAC type implementation.
I know this has probably been mentioned elsewhere, but I would really like to see a focus on cameras and video doorbells in regards to dashboards and the companion app. At the moment there is all sorts of cards etc that you can use, but I would really like HA to build the “best card” or setup to these devices. Especially video doorbells.
Otherwise well done team!
Hope that the marketing team at Nabu Casa get checked here on the choice of naming convention before the final product is manufactured and announced.
Suggest take some inspiration from Ubiquiti on this point as they just renamed a feature from “AP Analyzer” to “Radio Manager” as part of improved user experience for their latest UniFi OS release, (and they also renamed “RF Scanning” to “AirTime Scan” and moved it under Radios → Environment in their UI).
A good naming convention should be choose for improved user experience, or rather be choosen to help promote better user understanding and knowledge, so it is a balance between user friendliness and correctness, but there is also not an absolute need to totally dumb down the names for this purpose to completly ignore the correct technical terminologi and nomenclatures.
So again, I think that “Z-Wave Radio Adapter”, “Zigbee Radio Adapter”, “Thread Radio Adapter”, “EnOcean Radio Adapter”, “Bluetooth Radio Adapter”, and “Wi-Fi Radio Adapter” would probably make for the best naming convention here, as then you have a futureproof naming convention schema that can also be used for future radio adapters like example “LoRa Radio Adapter”, etc…
Regardless, an antenna is not the radio part, and a digital radio adapter whhuch MCU runs an IoT protocol is not only an antenna.
3 Likes
Absolutely like the guest mode! RBAC type of acces would be top notch!
I have a huge amount of solar, battery storage, an EV, an electric hot water heater, and a thermostat which can all be controlled by Home Assistant. I would love for it to be easier to do things like when I’m exporting excess power to increase the hot water heater temperature to store the energy there, start charging my car, and turn down the AC.
what we really need to improve interaction is full screed tablet mode in ha app with swipe (option to disable top bar ect without other addons) and ability to have the camera pop up from front on any switch trigger we want in full screen…
yes i do this via browser mod, but you have to keep re regging the browser evey so often.
I currently use motionEye and set up web hooks. The webhooks wasn’t easy initially (had to inspect the HTTP with netcat) but once I figured out how to integrate motion notifications it was nice. It reads the camera via rtsp and does all of the processing on HA. Not the best but it works for what I need it for in the moment.
I totally agree. I feel that this topic was super important and then the ball was dropped and we have barely seen any new feature since the release. I would like to see more development in this areas as well. Better breakdown, trends, cost per device/entity etc.
I wouldn’t go as far as saying the ball was dropped. So many awesome stuff has been added. It’s a matter of choosing what benefits most users and what the volunteers choose to work on.
Let’s try to send our positive energy towards this topic in the hope it gets some traction.
3 Likes
These were the Top 3 Votes from the Month of what the Heck 2024:
- access control (867 Votes)
- notifications (518 Votes)
- comments in YAML (389 Votes)
I can see no.1 is addressed.
But what about the others?
1 Like
As worded in the description, number 3 probably won’t be seen, as it requires understanding the nature of the issue. Now, if someone were to ask for the developers to make it possible to add and preserve comments when going between the UI and a YAML file, perhaps something could be done to address it, because that’s really what people want.
I do notifications via automations. I can share an example
This was counter intuitive at first because if you want continuous notifications and monitoring you need to set a periodic timer as the trigger and a condition to check.
1 Like
You could most likely reduce these automations into a single one.
Not easily if you wanted detailed notifications I think. The logic would get messy pretty quick as the number of triggers and conditional blocks grows. It would likely reach a point where it would be a challenge to relate between triggers and notifications.
One automation per notification type keeps it all grouped and organized. Automations do not appear to create additional load as they are just listeners on an even loop from what I can tell (I have not reviewed the automation source so this is an assumption).
Automations can be grouped and I added the “Alerts” label for aesthetic purposes. It makes it really obvious that its only purpose is to notify.
2 Likes
Thanks for your example. I am doing notifications, as well. Actually I think most peoble do. The topic is about the complexity of the notifications across different platforms.
Here you can see the “month of what the hack” topics ordered by votes:
It seems not much of it has made it into the roadmap.