My thoughts exactly…
People are unaware of the energy cost (and environmental impact) of these gimmicks.
My thoughts exactly…
People are unaware of the energy cost (and environmental impact) of these gimmicks.
just an idea, but if one of the issues is lack of awareness… it follows that it could be cool to have some kind of “energy used by your AI” estimator, that tries to guess the energy used by generation (and possibly training) of the models you’re using. ![]()
I feel like the biggest waste is the developer resources wasted on these useless AI task. I realize big companies are shoehorning it into every product in a desperate attempt to justify the billions spent but home assistant doesn’t need to do that.
I agree. Surely they could focus on better things like allowing us to place a badge anywhere on the dashboard instead of the header only. (Mushroom chips are a workaround but aren’t the same in many ways).
Starting with this release, Assist will detect if your voice command’s actions all took place within the same area as the satellite device. If so, a short confirmation “beep” will be played instead of the full verbal response. Besides being less verbose, this also serves as a quick reminder that your voice command only affected the current area.
I’m really hoping we get the ability to customize the beep sound soon. I’m doing a Star Trek theme for my Voice Assistants and I’d really like to use the Chirp wav I’ve got.
I love the new history window syncing, I’ve been wishing for that for months. However I notice that when zooming in/out on a history page that includes both numerical (graph) and non-numerical (bar) entities, the two types do their little zoom animations over different durations. The graphs move to the new state faster than the bars.
I interpreted their message as AI being an energy-sapping technology (which it is) — not referring to HA’s energy features.
Thanks for the automation editor updates (3 dots menu, resizable) and for the Repeat as well! Good job ![]()
Agreed, what a useless “feature”.
How to get Hue MotionAware working?
You can already customise responses by silencing the default response with
set_conversation_response: ""
and using
action: assist_satellite.announce
to play whatever response you want.
Logger: homeassistant.components.shelly
Quelle: helpers/update_coordinator.py:424
Integration: Shelly (Dokumentation, Probleme)
Erstmals aufgetreten: 08:57:53 (3 Vorkommnisse)
Zuletzt protokolliert: 09:20:02
Error fetching MQTT-Licht-Bad data: An error occurred while retrieving data from MQTT-Licht-Bad
like the idea of common_controls a lot, having the most used ones automatically emerge.
(Ive had something like that for years in a manual card, but would be cool to have the system auto-create that)
However, after some initial difficulty getting them to show at all (I had excluded event_type call_service from recorder), they now come and go.
as they’re apparently cached per 24 hours, does this mean the instance has to gather data per day too? And start all over after midnight?
That wouldnt really make sense to me. My espresso machine is the favorite here, and it’s really odd it isnt there after a nights sleep, requiring several toggles (while it is stand-by during the day and wont require a toggle for its day to day use, so it ll never make it based on a single day…)
I can force it and a few others, but to me it would make most sense if HA would truly gather data over at least a week or so.
Also to keep the UI more stable, always showing those die-hard entities, not just the ones that popup during (section of) the day.
During beta I’ve been able to adapt to all breaking changes in the theming variables ( move to Web awesome), especially the menubar. Thanks to Dcapslock
Ive uploaded the changes in in my card-mod theming
Kiosk-mode is pending an update and Keep-text-in-tabs was already fixed ! thanks to Elchininet
almost forgot the changes to ha-slider broke slider-entity-row but there is a temporary fix in the issue (thanks to JP during #beta ) so we can at least continue to colorize those sliders ![]()
update
fix for slider-entity-row was just released by Thomas, tyvm!
I finally got a chance to install the update and I’m able to select “no wake word” for my devices. Exactly what I was hoping for! Thanks team!
I was looking for a calendar of the workday!
Now, does anyone have a method to show only the opposites of them in a calendar? So the off-days are shown, but not the on-days?
I am thinking its limited to QSX installs where keypads generate multitap and press+hold commands.
I hope I’m wrong, but if so I am stuck with blueprints and automations for my picos and keypads
I like the updates. Great work. I am migrating from Homeseer and wondering if this will ever be implemented?
Homeseer has a simple check box on every device.
Did the new release change something about how values retrieved using the jinja states() function are represented? i.e. I’m getting odd “7.1 min” out of Waze travel time after the update instead of the usual “7 min”
The automation editor updates are great, much more usable now!