diff --git a/Gemfile.lock b/Gemfile.lock index c9d4c8fa9d6..7a669e9a5ab 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -159,7 +159,7 @@ GEM rack-protection (= 4.1.1) rack-session (>= 2.0.0, < 3) tilt (~> 2.0) - sorbet-runtime (0.5.12043) + sorbet-runtime (0.5.12046) stringex (2.8.6) terminal-table (3.0.2) unicode-display_width (>= 1.1.1, < 3) diff --git a/source/_integrations/apcupsd.markdown b/source/_integrations/apcupsd.markdown index 624900f3242..1fcd372d2e5 100644 --- a/source/_integrations/apcupsd.markdown +++ b/source/_integrations/apcupsd.markdown @@ -50,13 +50,6 @@ Port: description: "The port of the APC UPS Daemon configured above." {% endconfiguration_basic %} -{% note %} - -If you get `ConnectionRefusedError: Connection refused` errors in the Home Assistant logs, it means that Home Assistant is not able to connect to the daemon. Please check if the `NISIP` is properly configured. - -{% endnote %} - - ## Binary sensor This integration provides a binary sensor for the following information from apcupsd: @@ -141,6 +134,30 @@ Some sensors are disabled by default, since they provide information that is onl - UPS Transfer from Battery (XOFFBATT) - UPS Transfer to Battery (XONBATT) +## Examples + +### Send me a push notification when UPS load is high + +{% raw %} + +```yaml +alias: "APC UPS Load High Notification" +description: "Notify when APC UPS load is too high" +mode: single +triggers: + - trigger: numeric_state + entity_id: + - sensor.gogoups_load + above: 80 +conditions: [] +actions: + - action: notify.notify + data: + message: "APC UPS load is high: {{ states('sensor.apc_ups_load') }}%" +``` + +{% endraw %} + ## Data updates The integration {% term polling polls %} data from your APC UPS Daemon every 60 seconds by default. @@ -149,6 +166,16 @@ The integration {% term polling polls %} data from your APC UPS Daemon every 60 This integration does not allow you to control the UPS. For example, you cannot run a self-test. To run a self-test, use the `aptest` command provided by [apcupsd](http://www.apcupsd.org/). +## Troubleshooting + +### Failed to connect + +If you get a **Failed to connect** error when setting up the integration (and/or `ConnectionRefusedError: Connection refused` errors in the Home Assistant logs), it means that Home Assistant is not able to connect to the APC UPS daemon. Please check if the `NISIP`/`NISPORT` in the apcupsd configuration file is properly configured. Additionally, try running `apcaccess` on the host machine to see if the daemon is working properly. + +### Some entities are no longer provided + +If certain entities are missing after a Home Assistant restart, it's likely because they represent event-based data that only appears after specific UPS events (for example, transfer to battery). These entities are cleared when the APC UPS Daemon restarts and won’t reappear until the corresponding event occurs again. + ## Removing the integration This integration follows standard integration removal. No extra steps are required. diff --git a/source/_integrations/discord.markdown b/source/_integrations/discord.markdown index 027c7dcc1f0..9aaf701d419 100644 --- a/source/_integrations/discord.markdown +++ b/source/_integrations/discord.markdown @@ -105,7 +105,7 @@ To include messages with embedding, use these attributes underneath the `embed` | `description` | yes | Description of the embed. | | `color` | yes | Color code of the embed. This value is an *int*. | | `url` | yes | URL of the embed. | -| `author` | yes | Sets the footer for the embed content. | +| `author` | yes | Sets the author for the embed content. | | `footer` | yes | Sets the footer for the embed content. | | `thumbnail` | yes | Sets the thumbnail for the embed content. | | `image` | yes | Sets the image for the embed content. | diff --git a/source/_integrations/home_connect.markdown b/source/_integrations/home_connect.markdown index 5d6dc3f0e13..5eb91f1d958 100644 --- a/source/_integrations/home_connect.markdown +++ b/source/_integrations/home_connect.markdown @@ -1177,7 +1177,7 @@ To solve the above issue, follow these steps: ### Missing options at the "active program" and "selected program" entities -#### Symptom: "Although I have options, some programs that are available on the app are not in the list of options at the "active program" and "selected program" entities" +#### Symptom: "Although I have options, some programs that are available on the app are not in the list of options at the "active program" and "selected program" entities or the entities don't show up" Some programs that are available to select on the app, on the physical device or in the diagnostics file from the device are missing at the "active program" and "selected program" entities. @@ -1189,9 +1189,9 @@ If you see programs in the app or the physical device that are missing in the in The program key needs to be added to the integration. To help with that, you can open an issue at [aiohomeconnect](https://github.com/MartinHjelmare/aiohomeconnect) about the missing program key. -#### Symptom: "No programs available at the "active program" and "selected program" entities nor in the diagnostics file" +#### Symptom: "the "active program" and "selected program" entities are not provided by the integration" -There are no programs available to select at the "active program" and "selected program" entities, and the downloaded device diagnostics file does not list any programs. +The the "active program" and "selected program" entities are not provided by the integration, and the downloaded device diagnostics file does not list any programs. ##### Description @@ -1202,7 +1202,7 @@ The Home Connect API is not sending any programs to the integration. There's no solution for this issue. The only thing that can be done is reporting the issue to Home Connect through these channels: - [Home Connect service and contact](https://www.home-connect.com/us/en/support/contact-and-service) -- [Home Connect developer Help & Support](https://developer.home-connect.com/support) +- [Home Connect developer Help & Support](https://developer.home-connect.com/support/contact) ### Unavailable entities for a device @@ -1245,7 +1245,7 @@ To try to solve the above issues, follow these steps: - If the line between the appliance and the cloud is green, the appliance is connected to the cloud. 4. If everything is correct and the issue persists, contact Home Connect support. - [Home Connect service and contact](https://www.home-connect.com/us/en/support/contact-and-service) - - [Home Connect developer Help & Support](https://developer.home-connect.com/support) + - [Home Connect developer Help & Support](https://developer.home-connect.com/support/contact) ## Removing the integration diff --git a/source/_integrations/stiebel_eltron.markdown b/source/_integrations/stiebel_eltron.markdown index 0454a8fce0a..df582fccfd4 100644 --- a/source/_integrations/stiebel_eltron.markdown +++ b/source/_integrations/stiebel_eltron.markdown @@ -60,6 +60,8 @@ To enable this integration, add the following lines to your {% term "`configurat # Example configuration.yaml entry stiebel_eltron: name: LWZ504e + host: IP_ADDRESS + port: 502 ``` {% configuration %} @@ -68,26 +70,13 @@ name: required: false default: Unnamed Device type: string -hub: - description: The name of the hub where this slave is located. - required: false - default: default +host: + description: The hostname or IP of the stiebel eltron ISG. + required: true type: string +port: + description: The port of the stiebel eltron ISG. + required: false + default: 502 + type: integer {% endconfiguration %} - -{% important %} -This integration requires the [Modbus](/integrations/modbus/) integration to be set up to work -{% endimportant %} - -Full configuration example including modbus setup shown below: - -```yaml -# Full example configuration.yaml entry -modbus: - type: tcp - host: YOUR_ISGWEB_IP - port: 502 - -stiebel_eltron: - name: LWZ504e -``` diff --git a/source/_posts/2025-04-29-eve-joins-works-with-home-assistant.markdown b/source/_posts/2025-04-29-eve-joins-works-with-home-assistant.markdown new file mode 100644 index 00000000000..46d85d3e105 --- /dev/null +++ b/source/_posts/2025-04-29-eve-joins-works-with-home-assistant.markdown @@ -0,0 +1,63 @@ +--- +layout: post +title: "Eve Joins Works With Home Assistant" +description: "They have had multiple Matter-over-Thread devices certified, including a cool outdoor weather sensor and smart heating devices." +date: 2025-04-29 00:00:01 +date_formatted: "April 29, 2025" +author: Miranda Bishop +comments: true +categories: Works-with-Home-Assistant +og_image: /images/blog/2025-04-eve/art.jpg +--- + +Eve and Home Assistant collaboration banner + +We're thrilled to announce that [Eve](https://www.evehome.com/en) has joined the [Works with Home Assistant](https://works-with.home-assistant.io/) program! Eve is at the forefront of the Matter standard and has some great Matter devices focused on local control and privacy in the home. They're bringing a variety of devices to the program, including a couple of firsts! + +## Eve of a New Day for the Open Home + +Eve, based in Germany and part of ABB, is known for making high-quality smart home devices. They've been an early proponent of Matter, as it really aligns with their philosophy of local and private control. In their own words, *"No Eve cloud, no registration and no tracking so your data won't get exposed. Local intelligence and direct communication between Eve devices and smartphones or hubs without cloud dependency."* + +Eve has had a wide range of devices Works with Home Assistant certified, all of which connect directly to Home Assistant via Matter. If you're not aware, Matter is an open smart home standard that allows for local control by directly connecting devices to Home Assistant, keeping your smart home data in your home. In case you missed it, Home Assistant is now [Matter Certified](/blog/2025/03/10/matter-certification/)! + +

Eve WeatherBuilt for outdoor weather sensing, Matter, and a cool segmented LCD display---sign me up

+ +Matter can connect to devices over Ethernet and Wi-Fi networks, but it can also use [Thread](/integrations/thread/), which every Eve device being certified today uses. Thread devices can be directly connected to Home Assistant using a device like the [Connect ZBT-1](/connectzbt1), or can be connected to Home Assistant via an existing hub (Thread Border Router) you may already have from another [smart home ecosystem](/integrations/thread#google). Thread was designed around efficiency and is excellent for low-powered or battery-powered devices. Also, if your smart home balloons up to a hundred devices (or more 😅), you won't overwhelm your Wi-Fi router, as Thread operates independently. + +Eve isn't just a fan of Matter; they're actively shaping the standard. Their team is deeply involved with the development of Matter and the Connectivity Standards Alliance (CSA), and we were delighted to connect with them at the recent CSA meeting in Chicago. Their commitment runs so deep that Eve licenses its technology to help other manufacturers embrace Matter. In fact, fellow Works with Home Assistant partner [Motionblinds](/blog/2025/03/27/motionblinds-joins-wwha/) uses Eve's technology, proudly displaying "Powered by Eve" on their certified motors. + +
+

"Eve and Home Assistant are the perfect match for a local-first, privacy-centric smart home. With Eve devices featuring Matter, Thread, and absolutely no cloud connection in combination with Home Assistant's extensive, local automation capabilities, now everybody can enjoy the smart home the way it was meant to be: with you in control." -Jerome Gackel, CEO Eve Systems +

+ +## Certified Devices + +In case you didn't know, Works with Home Assistant differs from other certification programs as products are rigorously tested in-house to ensure they work seamlessly out of the box with Home Assistant. Any company joining also commits to providing long-term support and firmware updates while being a positive force in the Home Assistant community. Works with Home Assistant is operated by the [Open Home Foundation](https://www.openhomefoundation.org/), and the support of [Home Assistant Cloud](/cloud/) subscribers funds this work. + +Eve has certified the following Matter-over-Thread enabled devices: + +- [Eve Door & Window](https://www.evehome.com/en/eve-door-window) +- [Eve Energy Outlet](https://www.evehome.com/en/eve-energy-outlet) +- [Eve Energy Outdoor](https://www.evehome.com/en/eve-energy-outdoor) +- [Eve Energy](https://www.evehome.com/en/eve-energy) +- [Eve Light Switch (U.S. & Canada)](https://www.evehome.com/en/eve-light-switch) +- [Eve Dimmer Switch](https://www.evehome.com/en/eve-dimmer-switch) +- [Eve Motion](https://www.evehome.com/en/eve-motion) +- [Eve Custom Smart Blinds](https://www.evehome.com/en-us/eve-blinds-collection) +- [Eve MotionBlinds Upgrade Kit](https://www.evehome.com/eve-motionblinds) +- [Eve Thermo](https://www.evehome.com/en/eve-thermo) +- [Eve Weather](https://www.evehome.com/en/eve-weather) + +## Eve-rything You Need + +It is amazing to have Eve in the Works with Home Assistant program, as we've been fans of their focus on privacy and local control for years. The list of devices they certified today is really comprehensive, and I dare say you could build a pretty well-rounded smart home just with their devices. There are even a couple of firsts for the program, including their smart radiator valve, outdoor weather sensor, outdoor outlet, and water-resistant motion sensor. Eve is continuously working on transitioning their complete smart home portfolio over to Matter, so if you spot a device that is not Matter-compatible yet - stay tuned. + +### FAQ on Works with Home Assistant + +- ***If I have a device that is not listed under 'Works with Home Assistant' does this mean it's not supported?*** No! It just means that it hasn't yet gone through testing with our team, either because the brand has not submitted it for testing, or because the device does not fit the program's requirements (ex. it's not an end-device or requires cloud connectivity). It may not be the same polished experience you would get from certified devices, but if you've been using the device for some time without issue, nothing will change. Our community is quite good at listing the devices they have confirmed to work on the integration page, so this is always worth double-checking if you're unsure. We may test it down the road, but it's up to the brand to choose what they submit for testing, so tell them what you want. + +- ***Ok, so what's the point of the Works with program?*** It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must have full functionality within Home Assistant, operate locally without the need for cloud connectivity, and will continue to do so long-term. If you already own one of these devices, congrats! You're safe in the knowledge that the manufacturers are committed long-term to providing Home Assistant support. + +- ***How were these devices tested?*** All devices in this list were tested using a standard Home Assistant Green, with the Connect ZBT-1 as the radio for the Thread Border Router, and our [certified Matter Integration](/integrations/matter/).  If you have a different hardware configuration that works for you, then great. The above hardware is just what our team uses to ensure consistency across testing. + +- ***Will you be adding more Eve devices to the program?*** We are always interested in adding more devices. We're excited to be working closely with the Eve team and look forward to continuing to bring cool new devices to the program. If there are products you'd like to see certified, feel free to let us know! diff --git a/source/images/blog/2025-04-eve/art.jpg b/source/images/blog/2025-04-eve/art.jpg new file mode 100644 index 00000000000..5ab614af292 Binary files /dev/null and b/source/images/blog/2025-04-eve/art.jpg differ diff --git a/source/images/blog/2025-04-eve/eve-weather.jpg b/source/images/blog/2025-04-eve/eve-weather.jpg new file mode 100644 index 00000000000..d8cf3daf869 Binary files /dev/null and b/source/images/blog/2025-04-eve/eve-weather.jpg differ