+Screenshot of the button card with script service.
+
+Screenshot of a vertical stack card with 4 buttons and an entity selector.
-
+
+With this new setting, LLM-based conversation agents can tap into our
+{% term intent %} system, which powers Assist. They also get access to every
+{% term entity %} exposed to Assist. That way, you control what your agents
+have access to.
+
+Tapping into our intent system is great because it works out of the box.
+LLM-based conversation agents can do everything that Assist can do.
+The added benefit is that they are capable of reasoning beyond words,
+which Assist was incapable of doing.
+
+For example, if you have a light called _"Webcam light"_ exposed in your
+_"office"_ area, you can give direct commands such as:
+
+> Turn on the office webcam light.
+
+That was also working with Assist previously, but you can also give more
+complex commands, such as:
+
+> I'm going to a meeting, can you please make sure people see my face?
+
+The agent will figure out the intention behind the words
+and call the correct intent on the matching exposed entities.
+
+{% details "What about custom intents?" %}
+
+Our intent system has been built from the start to be extensible.
+Custom integrations and even users can register their own intents.
+This allows you to guide the agent beyond what's capable out of the box.
+
+Here is an example of a custom intent that explains to the agent what
+to do when I leave my home.
+
+```yaml
+conversation:
+ intents:
+ LeaveHome:
+ - "Leave home"
+
+intent_script:
+ LeaveHome:
+ description: "Launch the leave home script. To be used when I am about to leave my home."
+ action:
+ - service: script.leave_home
+ data: {}
+ speech:
+ text: "Done"
+```
+
+With this YAML snippet added to my {% term "`configuration.yaml`" %}, if the
+agent understands that I am leaving home, it will not turn off what it thinks
+I want, it will run my `leave_home` script, which is precisely what
+I want it to do.
+
+{% enddetails %}
+
+This release makes it available for our [OpenAI] and [Google AI]
+{% term integrations %}. To make it easier to get started with LLMs,
+we have updated them with recommended model settings that strike the right
+balance between accuracy, speed, and cost. If you had them set up previously,
+we recommend enabling the recommended settings and emptying the instructions.
+
+Our recommended model settings perform equally well for voice assistant tasks.
+Google is 14x cheaper than OpenAI, but OpenAI is better at answering non-smart
+home questions. We are preparing a blog post with a deep dive into the research
+that went into this feature, coming soon™!
+
+Local LLMs have been supported via [the Ollama integration](/integrations/ollama/) since Home Assistant 2024.4. Ollama and the major open source LLM models are not tuned for tool calling, so this has to be built from scratch and was not done in time for this release. We're collaborating with NVIDIA to get this working – [they showed a prototype last week.](https://youtu.be/aq7QS9AtwE8?si=yZilHo4uDUCAQiqN)
+
+Thanks to everyone who contributed to this feature! [@shulyaka], [@tronikos],
+[@allenporter], [@synesthesiam], [@jlpouffier], and [@balloob]!
+
+[@allenporter]: https://github.com/allenporter
+[@balloob]: https://github.com/balloob
+[@jlpouffier]: https://github.com/jlpouffier
+[@shulyaka]: https://github.com/shulyaka
+[@synesthesiam]: https://github.com/synesthesiam
+[@tronikos]: https://github.com/tronikos
+[Google AI]: /components/google_generative_ai_conversation/
+[OpenAI]: /components/openai_conversation/
+
+### Improved media player commands
+
+We have introduced new media player {% term intents %} that allow you to do
+more while saying less. You can say the following voice commands to control
+media players in the same area as your Assist device:
+
+- _"Pause"_
+- _"Resume"_
+- _"Next"_
+- _"Set the volume to 50%"_
+
+Up until now, we have only proposed sentences targeting a specific entity by
+its name. Due to this limitation, these intents were not the most user-friendly,
+as the sentences were too long to say: _“Skip to the next song on the TV”_.
+
+We added two features to get to the smallest sentences possible. Context
+awareness makes our voice assistant aware of the devices in the same area as
+the satellite. We have also created a smart matching strategy that finds the
+right media player to target.
+
+For example, if you say “pause”, the voice assistant will automatically
+target the media player that is playing.
+
+
+
+It uses the [same conditions as condition cards](/dashboards/conditional/#conditions-options),
+meaning you have a lot of flexibility in what you can do.
+
+[sections dashboard]: /dashboards/sections/
+
+### Control visibility of cards
+
+Wait, we didn't stop there! This same visibility feature is now also available
+for cards! Oh yes! 🚀
+
+
+
+You can now hide or show a card based on certain conditions. This allows you to
+create more dynamic dashboards that adapt to your needs. The big difference is
+that you don’t need a condition card to use this feature. It is available
+directly in the card configuration in the **Visibility** tab.
+
+### Setting a dashboard background
+
+[@Nezz] contributed a great new feature to our dashboarding UI: the ability to
+set a background image for your [dashboard](/dashboards)!
+
+Previously, this was only possible by editing YAML, but now you can do it
+directly from the UI. Even better, you can upload an image directly from your
+computer or provide a URL to one!
+
+
+
+_Photo: [Body of Water Between Green Leaf Trees] by [Ian Turnell](https://www.pexels.com/@samandgos/)._
+
+The same ability (to upload images directly from your computer) was added to
+the picture card, too! Thanks, [@karwosts], for that one!
+
+[@karwosts]: https://github.com/karwosts
+[@Nezz]: https://github.com/Nezz
+[Body of Water Between Green Leaf Trees]: https://www.pexels.com/photo/body-of-water-between-green-leaf-trees-709552/
+[Ian Turnell]: https://www.pexels.com/@samandgos/
+
+## Data tables improvements
+
+Like the [last release](/blog/2024/05/01/release-20245/#more-features-for-our-data-tables),
+this release keeps improving our data tables.
+
+When we [introduced data groupings](/blog/2024/04/03/release-20244/#item-grouping)
+in the tables, you asked for a way to collapse and expand those groupings,
+so we did in the last release! But then we quickly realized that it was not
+enough, and you wanted to be able to collapse and expand all groups at once.
+So, we did that for this release!
+
+
+
+We've also expanded the voice assistant expose data table to allow grouping
+by area and domain.
+
+Additionally, filters you've set in the data tables are now saved in your
+browser session. Meaning, if you navigate away from the page and come back, your
+filters will still be there. But! Each browser tab or window has its own session,
+meaning you can have different filters in different tabs or windows that are
+remembered for that specific tab or window.
+
+## Integrations
+
+Thanks to our community for keeping pace with the new {% term integrations %}
+and improvements to existing ones! You’re all awesome 🥰
+
+### New integrations
+
+We welcome the following new integrations in this release:
+
+- **[Airgradient]**, added by [@joostlek]
+
+You can find these token in your profile settings, under the **Security** tab.
+
+{% my profile badge %}
+
+### Tag entities!
+
+Home Assistant has had support for tags for a long time. The tags feature
+allowed NFC tags or QR codes to be used with Home Assistant, for example, to
+trigger {% term automations %}.
+
+However, tags were not real entities and, thus, not always as logical to use.
+With this release, [@gjohansson-ST] changed this!
+
+Tags are now normal {% term entities %} and can be used in {% term automations %},
+{% term scripts %}, {% term templates %}, and even be added to your
+your [dashboards](/dashboards)!
+
+[@gjohansson-ST]: https://github.com/gjohansson-ST
+
+### Collapsible sections for blueprints!
+
+[@karwosts] makes an appearance again this release with another one of his QoL
+(Quality of Live) improvements. He added the ability to add collapsible sections
+to {% term blueprints %}. This allows blueprint creators to group configuration
+options together or hide advanced or less common options by default.
+
+
+ Each section can be collapsed or uncollapsed by clicking on the section header.
+
+
+Back in the day, the saying was _computers don't lie_. They were deterministic, zeros and ones executing the rules we gave them. With AI, this is the opposite. AI models hallucinate and their output cannot be completely trusted -- yet the current hype is to infuse AI into every product imaginable. Home Assistant doesn't jump on the latest hype, instead we focus on building a lasting and sustainable smart home. We do have thoughts on the subject, so let's talk about AI in the smart home.
+
+Home Assistant is uniquely positioned to be the smart home platform for AI. As part of [our Open Home values](https://www.openhomefoundation.org/), we believe users own their own data (a novel concept, we know) and that they can choose what happens with it. That's why Home Assistant stores all user data locally, including rich history, and it offers powerful APIs for anyone to build anything on top -- no constraints. Empowering our users with real control of their homes [is part of our DNA](/blog/2016/01/19/perfect-home-automation/#limit-the-impact-of-false-positives-and-negatives), and helps reduce the impact of false positives caused by hallucinations. All this makes Home Assistant the perfect foundation for anyone looking to build powerful AI-powered solutions for the smart home - something that is not possible with any of the other big platforms.
+
+As we have researched AI ([more about that below](#the-foundation-for-ai-experimentation-in-the-smart-home)), we concluded that there are currently no AI-powered solutions _yet_ that are worth it. Would you want a summary of your home at the top of your dashboard if it could be wrong, cost you money, or even [harm the planet](https://www.theguardian.com/commentisfree/article/2024/may/30/ugly-truth-ai-chatgpt-guzzling-resources-environment)?
+
+Instead, we are focussing our efforts on allowing anyone to play with AI in Home Assistant by making it easier to integrate it into existing workflows and run the models locally. To experiment with AI today, the latest release of Home Assistant allows you to connect and control devices with OpenAI or Google AI. For the local AI solutions of the future, we are working with NVIDIA, who have made amazing progress already. This will unleash the power of our community, our collective intelligence, to come up with creative use cases.
+
+Read more about our approach, how you can use AI today, and what the future holds. Or jump straight in and add [Google AI](/integrations/google_generative_ai_conversation/), [OpenAI](/integrations/openai_conversation/) to your Home Assistant installation (or [Ollama](/integrations/ollama) for local AI without the ability to control HA yet).
+
+_Huge thanks for contributing: [@shulyaka](https://github.com/Shulyaka), [@tronikos](https://github.com/tronikos), [@allenporter](https://github.com/allenporter), [@synesthesiam](https://github.com/synesthesiam), [@jlpouffier](https://github.com/jlpouffier) and [@balloob](https://github.com/balloob)._
+
+
+
+## The foundation for AI experimentation in the smart home
+
+We want it to be easy to use LLMs together with Home Assistant. Until now, Home Assistant has allowed you to configure [AI agents](#ai-agents) powered by LLMs that you could talk with, but the LLM could not control Home Assistant. That changed this week with the release of [Home Assistant 2024.6](/blog/2024/06/05/release-20246/), which empowered AI agents from Google Gemini and OpenAI ChatGPT to interact with your home. You can use this in Assist ([our voice assistant](/voice_control/)) or interact with agents in scripts and automations to make decisions or annotate data.
+
+Using agents in Assist allows you to tell Home Assistant what to do, without having to worry if that exact command sentence is understood. Even combining commands and referencing previous commands will work!
+
+And because this is _just_ Assist, it works on [Android](/blog/2023/07/20/year-of-the-voice-chapter-3/), [iOS](/blog/2024/05/22/companion-app-for-ios-20245-assist/#assist-on-ios), [classic landline phones](/voice_control/worlds-most-private-voice-assistant/), and [$13 voice satellites](/voice_control/thirteen-usd-voice-remote/) 😁
+
+
LLMs allow Assist to understand a wider variety of commands.
The options screen for an AI agent allows you to pick the Home Assistant API that it has access to.
High level overview of the described agent framework.
Results comparing a set of difficult sentences to control Home Assistant between Home Assistant's sentence matching, Google Gemini 1.5 Flash and OpenAI GPT-4o.
+
+Home Assistant already has different ways for you to define your own intents, allowing you to extend the Assist API to which LLMs have access. The first one is the [intent script integration](/integrations/intent_script/). Using YAML, users can define a script to run when the intent is invoked and use a template to define the response.
+
+{% raw %}
+```python
+intent_script:
+ EventCountToday:
+ action:
+ - service: calendar.get_events
+ target:
+ entity_id: calendar.my_calendar
+ data_template:
+ start_date_time: "{{ today_at('00:00') }}"
+ duration: { "hours": 24 }
+ response_variable: result
+ - stop: ""
+ response_variable: result
+ speech:
+ text: "{{ action_response['calendar.my_calendar'].events | length }} events"
+```
+{% endraw %}
+
+We haven't forgotten about custom components either. They can [register their own intents](https://developers.home-assistant.io/docs/intent_handling) or, even better, define their own API.
+
+### Custom integrations providing their own LLM APIs
+
+The built-in LLM API is focused on simplicity and being good at the things that it does. The larger the API surface, the easier AI models, especially the smaller ones, can get confused and invoke them incorrectly.
+
+Instead of one large API, we are aiming for many focused APIs. To ensure a higher success rate, an AI agent will only have access to one API at a time. Figuring out the best API for creating automations, querying the history, and maybe even creating dashboards will require experimentation. When all those APIs are in place, we can start playing with a selector agent that routes incoming requests to the right agent and API.
+
+To find out what APIs work best is a task we need to do as a community. That's why we have designed our API system in a way that [any custom component can provide them](https://developers.home-assistant.io/docs/core/llm/). When configuring an LLM that supports control of Home Assistant, users can pick any of the available APIs.
+
+Custom LLM APIs are written in Python. When a user talks to an LLM, the API is asked to give a collection of tools for the LLM to access, and a partial prompt that will be appended to the user prompt. The partial prompt can provide extra instructions for the LLM on when and how to use the tools.
+
+## Future research
+
+One thing we can do to improve AI in Home Assistant is wait. LLMs, both local and remotely accessible ones, are improving rapidly and new ones are released regularly (fun fact, I started writing this post before GPT4o and Gemini 1.5 were announced). Wait a couple of months and the new Llama, Gemini, or GPT release might unlock many new possibilities.
+
+We'll continue to collaborate with NVIDIA to enable more local AI functionalities. High on our list is making local LLM with function calling easily accessible to all Home Assistant users.
+
+There is also room for us to improve the local models we use. We want to explore fine-tuning a model for specific tasks like voice commands or area summarization. This would allow us to get away with much smaller models with better performance and reliability. And the best thing about our community? [People are already working on this](https://github.com/acon96/home-llm).
+
+We also want to see if we can use RAG to allow users to teach LLMs about personal items or people that they care about. Wouldn't it be great if Home Assistant could help you find your glasses?
+
+## Join us
+
+We hope that you're going to give our new AI tools a try and join us on [the forums](https://community.home-assistant.io/c/configuration/voice-assistant/49) and in the #voice-assistants channel on [our Discord server](/join-chat/). If you find something cool, share it with the community and let's find that killer use case!
diff --git a/source/_posts/2024-06-12-roadmap-2024h1.markdown b/source/_posts/2024-06-12-roadmap-2024h1.markdown
new file mode 100644
index 00000000000..8b0bf2abd78
--- /dev/null
+++ b/source/_posts/2024-06-12-roadmap-2024h1.markdown
@@ -0,0 +1,160 @@
+---
+layout: post
+title: "Roadmap 2024 Midyear Update: A home-approved smart home, peace of mind, and more!"
+description: "Our first detailed roadmap outlining the direction of the continued development of the Home Assistant project"
+date: 2024-06-12 00:00:01
+date_formatted: "June 12, 2024"
+author: Madelena Mak
+comments: true
+categories: Announcements Roadmap
+og_image: /images/blog/2024-06-roadmap-2024h1/banner.png
+---
+
+
Art by Clelia Rella
Home Assistant Connect ZBT-1 packaging 🤤.
- 
+ 
+
- 
+ 
+
- 
+ 
+
@@ -132,7 +138,7 @@ frontpage_image: /images/skyconnect/skyconnect-cover.png
Model No.
- HASKYCNCT
+ NC-ZBT-9710
Radio Chipset
Silicon Labs Multiprotocol EFR32MG21
@@ -175,13 +181,16 @@ frontpage_image: /images/skyconnect/skyconnect-cover.png
FAQs
- {% details "Why include a USB extension cable?" %} USB 3.0 ports (the ones with blue on the inside) are known to cause significant noise and radio interference to any 2.4Ghz wireless devices. This includes Zigbee and Thread. If you do not use the extension cable, it may not work at all, and if it does, it could be flaky at best with intermittent problems (issues with pairing, device dropouts, unreachable devices, timeout errors, etc).
+ {% details "What is the difference between Home Assistant SkyConnect and Connect ZBT-1?" %} Home Assistant Connect ZBT-1 is the new name for Home Assistant SkyConnect. Though it's a new name and look, they have the exact same hardware, capability, and support. We made this change to help make room for a new line of Connect products, specifically an upcoming Z-Wave Connect product. Going forward, whenever we mention updates or features for Home Assistant Connect ZBT-1, this will also apply to SkyConnect-branded devices. Retailers will continue to sell SkyConnect-branded devices while supplies last, and we would encourage you to purchase whatever is available as they are functionally identical.
+ {% enddetails %}
+
+ {% details "Why include a USB extension cable?" %} USB 3.0 ports (the ones with blue on the inside) are known to cause significant noise and radio interference to any 2.4 GHz wireless devices. This includes Zigbee and Thread. If you do not use the extension cable, it may not work at all, and if it does, it could be flaky at best with intermittent problems (issues with pairing, device dropouts, unreachable devices, timeout errors, etc).
See demo on YouTube. {% enddetails %} - {% details "Which use case do you recommend for Home Assistant SkyConnect?" %} - Our current recommendation for Home Assistant SkyConnect is to use the Zigbee firmware to power your Zigbee network. This solution offers a great experience out-of-the-box.
+ {% details "Which use case do you recommend for Home Assistant Connect ZBT-1?" %} + Our current recommendation for Home Assistant Connect ZBT-1 is to use the Zigbee firmware to power your Zigbee network. This solution offers a great experience out-of-the-box.
As part of our efforts to bring Matter to Home Assistant, we're now focused on ensuring that the Thread experience will catch up and become a first-class citizen, making it easy to connect to your Thread-based Matter devices in Home Assistant without a third-party Thread border router. The Thread firmware is already fully functional under the hood, but we still have some work to do to make the experience of using Thread-based devices in Home Assistant feel good. Once the experience has improved, we will recommend using this Thread firmware to power your Thread network as an alternative to using third-party Thread border routers from Apple or Google. {% enddetails %} @@ -189,10 +198,10 @@ frontpage_image: /images/skyconnect/skyconnect-cover.png
Multiprotocol will remain an experimental feature and is not recommended for use.
- When we launched Home Assistant SkyConnect, we announced our intent to release firmware supporting multiprotocol, which allows the device's Silicon Labs chip to connect to both Zigbee and Thread networks with one radio.
- This experimental firmware has been available since December 2022. Through extensive testing, we have found that although it works in some circumstances, it has technical limitations that lead to a worse user experience. We now do not recommend using this firmware, and it will be experimental for the foreseeable future. Instead, we will focus on making sure the dedicated Zigbee and Thread firmwares for Home Assistant SkyConnect deliver the best experience to users.
+ When we launched this device, we announced our intent to release firmware supporting multiprotocol, which allows the device's Silicon Labs chip to connect to both Zigbee and Thread networks with one radio.
+ This experimental firmware has been available since December 2022. Through extensive testing, we have found that although it works in some circumstances, it has technical limitations that lead to a worse user experience. We now do not recommend using this firmware, and it will be experimental for the foreseeable future. Instead, we will focus on making sure the dedicated Zigbee and Thread firmwares for Home Assistant Connect ZBT-1 deliver the best experience to users.
- If you currently have the multiprotocol firmware installed but don't actively use it to connect to Thread devices, we recommend that you disable multiprotocol.
+ If you currently have the multiprotocol firmware installed but don't actively use it to connect to Thread devices, we recommend that you disable multiprotocol.
Nothing changes for current users of the multiprotocol firmware who are happy with their experience. The experimental multiprotocol firmware will remain available, but we will not recommend it to new users.{% enddetails %}
@@ -200,7 +209,7 @@ frontpage_image: /images/skyconnect/skyconnect-cover.png
1: Relies on the experimental EmberZNet support in Zigbee2MQTT.
See demo on YouTube. {% enddetails %} - {% details "Which use case do you recommend for Home Assistant SkyConnect?" %} - Our current recommendation for Home Assistant SkyConnect is to use the Zigbee firmware to power your Zigbee network. This solution offers a great experience out-of-the-box.
+ {% details "Which use case do you recommend for Home Assistant Connect ZBT-1?" %} + Our current recommendation for Home Assistant Connect ZBT-1 is to use the Zigbee firmware to power your Zigbee network. This solution offers a great experience out-of-the-box.
As part of our efforts to bring Matter to Home Assistant, we're now focused on ensuring that the Thread experience will catch up and become a first-class citizen, making it easy to connect to your Thread-based Matter devices in Home Assistant without a third-party Thread border router. The Thread firmware is already fully functional under the hood, but we still have some work to do to make the experience of using Thread-based devices in Home Assistant feel good. Once the experience has improved, we will recommend using this Thread firmware to power your Thread network as an alternative to using third-party Thread border routers from Apple or Google. {% enddetails %} @@ -189,10 +198,10 @@ frontpage_image: /images/skyconnect/skyconnect-cover.png
Multiprotocol will remain an experimental feature and is not recommended for use.
- When we launched Home Assistant SkyConnect, we announced our intent to release firmware supporting multiprotocol, which allows the device's Silicon Labs chip to connect to both Zigbee and Thread networks with one radio.
- This experimental firmware has been available since December 2022. Through extensive testing, we have found that although it works in some circumstances, it has technical limitations that lead to a worse user experience. We now do not recommend using this firmware, and it will be experimental for the foreseeable future. Instead, we will focus on making sure the dedicated Zigbee and Thread firmwares for Home Assistant SkyConnect deliver the best experience to users.
+ When we launched this device, we announced our intent to release firmware supporting multiprotocol, which allows the device's Silicon Labs chip to connect to both Zigbee and Thread networks with one radio.
+ This experimental firmware has been available since December 2022. Through extensive testing, we have found that although it works in some circumstances, it has technical limitations that lead to a worse user experience. We now do not recommend using this firmware, and it will be experimental for the foreseeable future. Instead, we will focus on making sure the dedicated Zigbee and Thread firmwares for Home Assistant Connect ZBT-1 deliver the best experience to users.
- If you currently have the multiprotocol firmware installed but don't actively use it to connect to Thread devices, we recommend that you disable multiprotocol.
+ If you currently have the multiprotocol firmware installed but don't actively use it to connect to Thread devices, we recommend that you disable multiprotocol.
Nothing changes for current users of the multiprotocol firmware who are happy with their experience. The experimental multiprotocol firmware will remain available, but we will not recommend it to new users.{% enddetails %}
-
![]()
![]()
![]()
@@ -2419,6 +2419,23 @@ frontpage_image: /images/frontpage/green-frontpage.png
+
+
-{% include common-tasks/enable_i2c.md %}
\ No newline at end of file
+{% include common-tasks/enable_i2c.md %}
diff --git a/source/integrations/index.html b/source/integrations/index.html
index 8ca31308fc1..1adb594483d 100644
--- a/source/integrations/index.html
+++ b/source/integrations/index.html
@@ -33,7 +33,7 @@ regenerate: false
Featured
Partner brands
-
@@ -223,7 +232,7 @@ frontpage_image: /images/skyconnect/skyconnect-cover.png
The other big difference is that Yellow comes with support for Zigbee 3.0 and Matter-over-Thread. But Green can also use - these protocols by adding a SkyConnect. + these protocols by adding a Connect ZBT-1.
- Home Assistant SkyConnect
+ Home Assistant Connect ZBT-1
@@ -2174,14 +2174,14 @@ frontpage_image: /images/frontpage/green-frontpage.png
through more complex installation steps.The other big difference is that Yellow comes with support for Zigbee 3.0 and Matter-over-Thread. But Green can also use - these protocols by adding a SkyConnect. + these protocols by adding a Connect ZBT-1.
- Do I need a Home Assistant SkyConnect? + Do I need a Home Assistant Connect ZBT-1?
- If you want to connect Home Assistant Green to the hub of your existing smart home system that uses Zigbee or Thread to communicate, you can do so out-of-the-box for most popular brands. This will be the easiest way to connect your existing Zigbee or Matter devices and does not require a Home Assistant SkyConnect. + It is not strictly required, as most smart home devices and hubs work with Home Assistant Green out-of-the-box, but you should confirm compatibility. For the best experience, pair Home Assistant Connect ZBT-1 with Home Assistant Green, making a single hub solution for your Zigbee or Thread powered smart home.
-You need a Home Assistant SkyConnect if you want to connect Zigbee or Thread* devices directly to Home Assistant Green.
+Home Assistant Connect ZBT-1 allows Zigbee or Thread* devices to connect directly to Home Assistant Green.
* Thread support is currently under development.
- Will Nabu Casa keep supporting the Home Assistant Green? + Will Nabu Casa keep supporting Home Assistant Green?
- Will Nabu Casa keep supporting the Home Assistant Yellow? + Will Nabu Casa keep supporting Home Assistant Yellow?
- Absolutely! We believe in the Home Assistant Yellow! Depending on - who you are and what your smart home looks like, the Home + Absolutely! We believe in Home Assistant Yellow! Depending on + who you are and what your smart home looks like, Home Assistant Yellow might be the better choice for you.
+
+
+
+
+
+ 🇦🇺
+ SmartHome
+ Shipping from Australia
+
diff --git a/source/images/assist/assistant-expose-10.png b/source/images/assist/assistant-expose-10.png
new file mode 100644
index 00000000000..ec0c8cecc56
Binary files /dev/null and b/source/images/assist/assistant-expose-10.png differ
diff --git a/source/images/assist/assistant-openai-mario-02.png b/source/images/assist/assistant-openai-mario-02.png
deleted file mode 100644
index f445841b556..00000000000
Binary files a/source/images/assist/assistant-openai-mario-02.png and /dev/null differ
diff --git a/source/images/assist/assistant-openai-mario-09.png b/source/images/assist/assistant-openai-mario-09.png
new file mode 100644
index 00000000000..79c1abe0335
Binary files /dev/null and b/source/images/assist/assistant-openai-mario-09.png differ
diff --git a/source/images/assist/mario_rename.png b/source/images/assist/mario_rename.png
new file mode 100644
index 00000000000..b600e43f88c
Binary files /dev/null and b/source/images/assist/mario_rename.png differ
diff --git a/source/images/assist/wake_word_engine_location.png b/source/images/assist/wake_word_engine_location.png
index 8b62f0eb696..20b8a4a0ecc 100644
Binary files a/source/images/assist/wake_word_engine_location.png and b/source/images/assist/wake_word_engine_location.png differ
diff --git a/source/images/blog/2024-06-ZBT1/art.jpg b/source/images/blog/2024-06-ZBT1/art.jpg
new file mode 100644
index 00000000000..b8e1a6a414f
Binary files /dev/null and b/source/images/blog/2024-06-ZBT1/art.jpg differ
diff --git a/source/images/blog/2024-06-ZBT1/zbt1-packaging.jpg b/source/images/blog/2024-06-ZBT1/zbt1-packaging.jpg
new file mode 100644
index 00000000000..dcd639050ca
Binary files /dev/null and b/source/images/blog/2024-06-ZBT1/zbt1-packaging.jpg differ
diff --git a/source/images/blog/2024-06-ai-agents-for-the-smart-home/01-assist.png b/source/images/blog/2024-06-ai-agents-for-the-smart-home/01-assist.png
new file mode 100644
index 00000000000..7602e811ca3
Binary files /dev/null and b/source/images/blog/2024-06-ai-agents-for-the-smart-home/01-assist.png differ
diff --git a/source/images/blog/2024-06-ai-agents-for-the-smart-home/02-options.png b/source/images/blog/2024-06-ai-agents-for-the-smart-home/02-options.png
new file mode 100644
index 00000000000..db91ec41e34
Binary files /dev/null and b/source/images/blog/2024-06-ai-agents-for-the-smart-home/02-options.png differ
diff --git a/source/images/blog/2024-06-ai-agents-for-the-smart-home/03-agents.png b/source/images/blog/2024-06-ai-agents-for-the-smart-home/03-agents.png
new file mode 100644
index 00000000000..c0c508f5d06
Binary files /dev/null and b/source/images/blog/2024-06-ai-agents-for-the-smart-home/03-agents.png differ
diff --git a/source/images/blog/2024-06-ai-agents-for-the-smart-home/04-setup.png b/source/images/blog/2024-06-ai-agents-for-the-smart-home/04-setup.png
new file mode 100644
index 00000000000..7d07d6b01db
Binary files /dev/null and b/source/images/blog/2024-06-ai-agents-for-the-smart-home/04-setup.png differ
diff --git a/source/images/blog/2024-06-ai-agents-for-the-smart-home/05-testing.png b/source/images/blog/2024-06-ai-agents-for-the-smart-home/05-testing.png
new file mode 100644
index 00000000000..b9badad484d
Binary files /dev/null and b/source/images/blog/2024-06-ai-agents-for-the-smart-home/05-testing.png differ
diff --git a/source/images/blog/2024-06-ai-agents-for-the-smart-home/06-expose.png b/source/images/blog/2024-06-ai-agents-for-the-smart-home/06-expose.png
new file mode 100644
index 00000000000..e0dcdc4ec47
Binary files /dev/null and b/source/images/blog/2024-06-ai-agents-for-the-smart-home/06-expose.png differ
diff --git a/source/images/blog/2024-06-ai-agents-for-the-smart-home/art.jpg b/source/images/blog/2024-06-ai-agents-for-the-smart-home/art.jpg
new file mode 100644
index 00000000000..3499fe73b6e
Binary files /dev/null and b/source/images/blog/2024-06-ai-agents-for-the-smart-home/art.jpg differ
diff --git a/source/images/blog/2024-06-roadmap-2024h1/banner.png b/source/images/blog/2024-06-roadmap-2024h1/banner.png
new file mode 100644
index 00000000000..c206ab49fad
Binary files /dev/null and b/source/images/blog/2024-06-roadmap-2024h1/banner.png differ
diff --git a/source/images/blog/2024-06-roadmap-2024h1/ha-roadmap-2024h1.png b/source/images/blog/2024-06-roadmap-2024h1/ha-roadmap-2024h1.png
new file mode 100644
index 00000000000..b2e36e75acf
Binary files /dev/null and b/source/images/blog/2024-06-roadmap-2024h1/ha-roadmap-2024h1.png differ
diff --git a/source/images/blog/2024-06-roadmap-introduction/art.jpg b/source/images/blog/2024-06-roadmap-introduction/art.jpg
new file mode 100644
index 00000000000..8dafd437d2b
Binary files /dev/null and b/source/images/blog/2024-06-roadmap-introduction/art.jpg differ
diff --git a/source/images/blog/2024-06/blueprint-input-sections.gif b/source/images/blog/2024-06/blueprint-input-sections.gif
new file mode 100644
index 00000000000..949ce415a53
Binary files /dev/null and b/source/images/blog/2024-06/blueprint-input-sections.gif differ
diff --git a/source/images/blog/2024-06/dashboard-card-visibility.png b/source/images/blog/2024-06/dashboard-card-visibility.png
new file mode 100644
index 00000000000..f80e1638297
Binary files /dev/null and b/source/images/blog/2024-06/dashboard-card-visibility.png differ
diff --git a/source/images/blog/2024-06/dashboard-section-visibility.png b/source/images/blog/2024-06/dashboard-section-visibility.png
new file mode 100644
index 00000000000..6e97dc18b46
Binary files /dev/null and b/source/images/blog/2024-06/dashboard-section-visibility.png differ
diff --git a/source/images/blog/2024-06/dashboards-change-background.png b/source/images/blog/2024-06/dashboards-change-background.png
new file mode 100644
index 00000000000..b5e8f931a75
Binary files /dev/null and b/source/images/blog/2024-06/dashboards-change-background.png differ
diff --git a/source/images/blog/2024-06/data-tables-collapse-expand-all.png b/source/images/blog/2024-06/data-tables-collapse-expand-all.png
new file mode 100644
index 00000000000..948786d1c02
Binary files /dev/null and b/source/images/blog/2024-06/data-tables-collapse-expand-all.png differ
diff --git a/source/images/blog/2024-06/disabling-expiration-login-tokens.png b/source/images/blog/2024-06/disabling-expiration-login-tokens.png
new file mode 100644
index 00000000000..98284bf8c9e
Binary files /dev/null and b/source/images/blog/2024-06/disabling-expiration-login-tokens.png differ
diff --git a/source/images/blog/2024-06/llm-based-conversation-agent-config-flow.png b/source/images/blog/2024-06/llm-based-conversation-agent-config-flow.png
new file mode 100644
index 00000000000..113742ae9fd
Binary files /dev/null and b/source/images/blog/2024-06/llm-based-conversation-agent-config-flow.png differ
diff --git a/source/images/blog/2024-06/social.png b/source/images/blog/2024-06/social.png
new file mode 100644
index 00000000000..05d64255ebd
Binary files /dev/null and b/source/images/blog/2024-06/social.png differ
diff --git a/source/images/connectzbt1/connectzbt1-cover.jpg b/source/images/connectzbt1/connectzbt1-cover.jpg
new file mode 100644
index 00000000000..19a29303333
Binary files /dev/null and b/source/images/connectzbt1/connectzbt1-cover.jpg differ
diff --git a/source/images/connectzbt1/connectzbt1_horizontal.png b/source/images/connectzbt1/connectzbt1_horizontal.png
new file mode 100644
index 00000000000..797884e0091
Binary files /dev/null and b/source/images/connectzbt1/connectzbt1_horizontal.png differ
diff --git a/source/images/connectzbt1/connectzbt1_isometric.png b/source/images/connectzbt1/connectzbt1_isometric.png
new file mode 100644
index 00000000000..2bf0756c956
Binary files /dev/null and b/source/images/connectzbt1/connectzbt1_isometric.png differ
diff --git a/source/images/connectzbt1/connectzbt1_square.jpg b/source/images/connectzbt1/connectzbt1_square.jpg
new file mode 100644
index 00000000000..5c0f032fb32
Binary files /dev/null and b/source/images/connectzbt1/connectzbt1_square.jpg differ
diff --git a/source/images/dashboards/buttons_on_vertical_stack_card.png b/source/images/dashboards/buttons_on_vertical_stack_card.png
new file mode 100644
index 00000000000..3b659e4ae8a
Binary files /dev/null and b/source/images/dashboards/buttons_on_vertical_stack_card.png differ
diff --git a/source/images/docs/configuration/customizing-entity-dialog.png b/source/images/docs/configuration/customizing-entity-dialog.png
index 5dda10ee232..d6076b446a9 100644
Binary files a/source/images/docs/configuration/customizing-entity-dialog.png and b/source/images/docs/configuration/customizing-entity-dialog.png differ
diff --git a/source/images/docs/configuration/customizing-entity.png b/source/images/docs/configuration/customizing-entity.png
index e1ccaa269cc..63e8760af07 100644
Binary files a/source/images/docs/configuration/customizing-entity.png and b/source/images/docs/configuration/customizing-entity.png differ
diff --git a/source/images/docs/configuration/edit_entity-id_in_automation.png b/source/images/docs/configuration/edit_entity-id_in_automation.png
deleted file mode 100644
index 1b20b856cf9..00000000000
Binary files a/source/images/docs/configuration/edit_entity-id_in_automation.png and /dev/null differ
diff --git a/source/images/green/ha-connect-zbt-1-p-1080.jpg b/source/images/green/ha-connect-zbt-1-p-1080.jpg
new file mode 100644
index 00000000000..b237e8385b2
Binary files /dev/null and b/source/images/green/ha-connect-zbt-1-p-1080.jpg differ
diff --git a/source/images/green/ha-connect-zbt-1-p-1600.jpg b/source/images/green/ha-connect-zbt-1-p-1600.jpg
new file mode 100644
index 00000000000..6006a1c60ac
Binary files /dev/null and b/source/images/green/ha-connect-zbt-1-p-1600.jpg differ
diff --git a/source/images/green/ha-connect-zbt-1-p-500.jpg b/source/images/green/ha-connect-zbt-1-p-500.jpg
new file mode 100644
index 00000000000..e2520c6a9bd
Binary files /dev/null and b/source/images/green/ha-connect-zbt-1-p-500.jpg differ
diff --git a/source/images/green/ha-connect-zbt-1-p-800.jpg b/source/images/green/ha-connect-zbt-1-p-800.jpg
new file mode 100644
index 00000000000..0cf68dd9cbc
Binary files /dev/null and b/source/images/green/ha-connect-zbt-1-p-800.jpg differ
diff --git a/source/images/green/ha-connect-zbt-1.jpg b/source/images/green/ha-connect-zbt-1.jpg
new file mode 100644
index 00000000000..f0490a462e9
Binary files /dev/null and b/source/images/green/ha-connect-zbt-1.jpg differ
diff --git a/source/images/green/ha-skyconnect-p-1080.jpg b/source/images/green/ha-skyconnect-p-1080.jpg
deleted file mode 100644
index ce9a7b7b943..00000000000
Binary files a/source/images/green/ha-skyconnect-p-1080.jpg and /dev/null differ
diff --git a/source/images/green/ha-skyconnect-p-1600.jpg b/source/images/green/ha-skyconnect-p-1600.jpg
deleted file mode 100644
index 4bc52dc2f5f..00000000000
Binary files a/source/images/green/ha-skyconnect-p-1600.jpg and /dev/null differ
diff --git a/source/images/green/ha-skyconnect-p-500.jpg b/source/images/green/ha-skyconnect-p-500.jpg
deleted file mode 100644
index 57d240d0e57..00000000000
Binary files a/source/images/green/ha-skyconnect-p-500.jpg and /dev/null differ
diff --git a/source/images/green/ha-skyconnect-p-800.jpg b/source/images/green/ha-skyconnect-p-800.jpg
deleted file mode 100644
index 3e31c6cc429..00000000000
Binary files a/source/images/green/ha-skyconnect-p-800.jpg and /dev/null differ
diff --git a/source/images/green/ha-skyconnect.jpg b/source/images/green/ha-skyconnect.jpg
deleted file mode 100644
index ae601a92f74..00000000000
Binary files a/source/images/green/ha-skyconnect.jpg and /dev/null differ
diff --git a/source/images/skyconnect/skyconnect-cover.png b/source/images/skyconnect/skyconnect-cover.png
deleted file mode 100644
index 37414f55172..00000000000
Binary files a/source/images/skyconnect/skyconnect-cover.png and /dev/null differ
diff --git a/source/images/skyconnect/skyconnect_horizontal.png b/source/images/skyconnect/skyconnect_horizontal.png
deleted file mode 100644
index 7e60655ea0d..00000000000
Binary files a/source/images/skyconnect/skyconnect_horizontal.png and /dev/null differ
diff --git a/source/images/skyconnect/skyconnect_isometric.png b/source/images/skyconnect/skyconnect_isometric.png
deleted file mode 100644
index 93ed17974e1..00000000000
Binary files a/source/images/skyconnect/skyconnect_isometric.png and /dev/null differ
diff --git a/source/images/skyconnect/skyconnect_square.jpg b/source/images/skyconnect/skyconnect_square.jpg
deleted file mode 100644
index 18c328132cb..00000000000
Binary files a/source/images/skyconnect/skyconnect_square.jpg and /dev/null differ
diff --git a/source/installation/raspberrypi.markdown b/source/installation/raspberrypi.markdown
index a6be8339bfb..e469ff8d22e 100644
--- a/source/installation/raspberrypi.markdown
+++ b/source/installation/raspberrypi.markdown
@@ -99,7 +99,7 @@ Use this procedure if Raspberry Pi Imager is not supported by your platform.
2. Download and start Balena Etcher. You may need to run it with administrator privileges on Windows.
3. Download the image to your computer.
- - Copy the correct URL for the Raspberry Pi 3 or 4 (Note: there are 2 different links below!):
+ - Copy the correct URL for the Raspberry Pi 3, 4 or 5 (Note: there are 3 different links below!):
{% tabbed_block %}
{% for variant in site.installation.types[page.installation_type].variants %}
@@ -136,4 +136,4 @@ _Select and copy the URL or use the "copy" button that appear when you hover it.
We get commissions for purchases made through links in this post.
Added in:
-
-
-
-{% raw %}
-
-{% endraw %}
-