# \[APP\]\[Pro\] Home Assistant - Community App **URL:** \ **Category:** Apps\ **Tags:** app, tools, homey-pro, home-assistant\ **Created:** [October 31, 2022, 8:25pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477 "2022-10-31T20:25:26Z")\ **Posts on this page:** 20\ **Page:** 76
**Author:** ![Sibren\_ter\_Hove](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sibren_ter_hove/32/79870_2.png) [@Sibren\_ter\_Hove](https://community.homey.app/u/Sibren_ter_Hove)\ **Post date:** [July 22, 2026, 2:05pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1517 "2026-07-22T14:05:21Z")
Right now if you add a device that is a home battery for example i need to add it manually and add the entities manually. Is it not possible to expand the device types? With the right entitities and setup so it shows as a home battery and also shows correct in the energy dashboard? Same with ev cars. ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [July 22, 2026, 2:24pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1518 "2026-07-22T14:24:22Z")
Do you have an example HA entity wherr the app could ‘see’ which entity/attribute is the right one? I only know devices with multiple independent entities that are all standalone without any attribute marking them as import/export value - and you can’t use the entity name because every integration it doing it different. ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [July 26, 2026, 3:10pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1519 "2026-07-26T15:10:16Z")
**Lawn mowers** were requested in the past. Now I got some time to add a simple device. It has only the mower\_state capability (mowinf, docked. paused, error) and the services to start/pause/dock after the picker got changed. Anyone here who wants to check if it’s working? I have no device to test, so all is done in theory based on HA entity description. > **[Supported features​ - Lawn mower entity | Home Assistant Developer Docs](https://developers.home-assistant.io/docs/core/entity/lawn-mower/#supported-features)** > > Derive entity platforms from homeassistant.components.lawn\_mower.LawnMowerEntity | Derive entity platforms from homeassistant.components.lawnmower.LawnMowerEntity > Btw. The HA activity “returning” is not provided by the Homey capability, so that’s currently not used. If mowers have additional states, it could make sense to add the entity state also as string capability to use this in flow conditions. But let’s see… ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [July 27, 2026, 7:47pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1520 "2026-07-27T19:47:34Z")
New **test version 1.17.0** : - Added **lawn mower** device > **[Home Assistant Community | Homey](https://homey.app/en-us/app/io.home-assistant.community/Home-Assistant-Community/test/)** > > Connect to Home Assistant Please test is it’s possible to add and control a HA lawn mower 🙂 ---
**Author:** ![deejayreissue](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/deejayreissue/32/81912_2.png) [@deejayreissue](https://community.homey.app/u/deejayreissue)\ **Post date:** [July 28, 2026, 9:17pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1521 "2026-07-28T21:17:15Z")
Can anyone talk me through how to simulate a When card for a Button press using this app please? Athom have not exposed button presses on the official HA app for some ridiculous reason. ---
**Author:** ![SmartHomePrimer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomeprimer/32/150702_2.png) [@SmartHomePrimer](https://community.homey.app/u/SmartHomePrimer)\ **Post date:** [July 28, 2026, 11:33pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1522 "2026-07-28T23:33:04Z")
Look for the “When the state of [entity] has changed” card. Select your entity which will be named input\_button together with the entity name. i.e. “input\_button.[entity name]” ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [July 29, 2026, 5:09am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1523 "2026-07-29T05:09:35Z")
In addition… When adding a button device, ![Screenshot_20260729_070649_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/a/eae58831c162e6fe2a58111e8a8a63c3e3696827.jpeg) then you get a trigger card like this. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/3/13006ea5abc6c3a9c910c317f44f9fc22957c3ab.jpeg) When adding a button to an existing device in repair view, you can use the generic capability changed trigger like described above. ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [August 9, 2026, 5:10pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1524 "2026-08-09T17:10:50Z")
Has anyone had the chance to test lawn mower device? Just asking if it’s working in real live and if the app version is ok for live version 🙂 ---
**Author:** ![Olivier67](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olivier67/32/118108_2.png) [@Olivier67](https://community.homey.app/u/Olivier67)\ **Post date:** [September 1, 2026, 6:54am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1525 "2026-09-01T06:54:27Z")
Hello @RonnyW I have been using your application for some time and thank you again On the other hand, recently I wanted to add all the devices on Alexa, everything goes up in Alexa except the shutters. The shutters seem to have the right capability and class. These components go back well from home assistant through HA Cloud and the home assistant skill. Have you ever had this kind of problem? Thanks ---
**Author:** ![Geronimo206](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/geronimo206/32/29921_2.png) [@Geronimo206](https://community.homey.app/u/Geronimo206)\ **Post date:** [September 2, 2026, 12:22pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1526 "2026-09-02T12:22:40Z")
Hi, @RonnyW Thanks for this amazing app, I use it a lot! I think I may have found a small issue with how `lock` entities are handled when Home Assistant temporarily cannot update them. I have 3 Tedee locks in Home Assistant, imported into Homey through the Home Assistant Community app. Two of those locks are connected to the same Tedee Bridge, while the third one uses another bridge. Last night I suddenly got a huge amount of lock/unlock entries in the Homey Timeline for exactly those two locks on the same bridge, even though neither lock physically moved at any point. The interesting part is that the timestamps in Homey match Tedee errors in my Home Assistant log almost exactly. There are also several `Error fetching tedee data: Error while communicating with the API` messages. The third Tedee lock, connected to another bridge, does not appear to show the same behaviour. My suspicion is that the affected lock entity temporarily becomes `unavailable` or another non-`locked` state whenever communication with that Tedee Bridge fails. Looking at the Home Assistant Community lock driver, I noticed this: `await this.setCapabilityValue("locked", data.state == "locked");` If I understand this correctly, this means that **every state other than literally `locked` is translated to `locked = false` in Homey**. So states such as: `unavailable unknown locking unlocking` would all effectively become **Unlocked** in Homey. Would it perhaps be safer for the app to only change the Homey capability for explicit states? Something along the lines of: `if (data.state === "locked") { await this.setCapabilityValue("locked", true); } else if (data.state === "unlocked") { await this.setCapabilityValue("locked", false); }` …and simply retain the previous Homey state for `unavailable`, `unknown`, `locking`, etc.? I realise the underlying Tedee communication errors are something I need to investigate separately, but ideally a temporary HA/API failure should not result in Homey reporting that a physically locked door has been unlocked? ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 2, 2026, 6:41pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1527 "2026-09-02T18:41:44Z")
Hi, thanks for your hint. You are right, an undefined state should not toggle the Homey state. I fixed this and now only locked/unlocked is used. **New test version 1.17.2:** - Fixed lock state > **[Home Assistant Community | Homey](https://homey.app/en-us/app/io.home-assistant.community/Home-Assistant-Community/test/)** > > Connect to Home Assistant ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 13, 2026, 11:42am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1528 "2026-09-13T11:42:12Z")
New test version 1.18.0: - Added climate support for device entities: When using a climate entity attribute “temperature” with Homey capability target\_temperature, the value is not used directly as a climate capability. Imported values are converted from °F to °C based on HA settings. If this capability is changed in Homey, the climate service is called to adjust the HA target temperature (incl. °C=\>°F conversion). - Added heat\_cool mode support for climate device. If HA climate entity is set to heta\_cool mode, the Homey climate device is showing 3 climate views: 1. Standard target temperature 2. High target temperature 3. Low target temperature Limitations: - Currently it’s not possible to hide not needed capabilities. They are not removed completely to not break your flows if heat mode changes. - The thermostat views have all the same name in the dropdown list on top of thermostat view. It seems to be a bug in WebGUI. It’s already reported. This new functionality is still beta state. Please try if it works and report issues. I can’t really test it without a matching HA device (and generic device doesn’t allow heat\_cool mode). > **[Home Assistant Community | Homey](https://homey.app/en-us/app/io.home-assistant.community/Home-Assistant-Community/test/)** > > Connect to Home Assistant This update is based on this [Github issue](https://github.com/RonnyWinkler/io.home-assistant.community/issues/10). ---
**Author:** ![JOR1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jor1/32/17206_2.png) [@JOR1](https://community.homey.app/u/JOR1)\ **Post date:** [September 15, 2026, 5:50am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1529 "2026-09-15T05:50:21Z")
Hi. After latest update I have issues controling my HA heatpumps from Homey. I get the folloving red error message when trying to change target temp from Homey android app: {“code”“invalid\_format”,“message”:“expected float at ‘taget\_temp\_high’”} Rgds. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [September 15, 2026, 6:00am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1530 "2026-09-15T06:00:48Z")
If you like, while waiting on a fix, you can revert to the stable version 1.16.1 by just installing it per app store (don’t uninstall anything): [https://homey.app/en-nl/app/io.home-assistant.community/Home-Assistant-Community/](https://homey.app/en-nl/app/io.home-assistant.community/Home-Assistant-Community/) ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 15, 2026, 7:11am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1531 "2026-09-15T07:11:44Z")
Thanks for reporting. The new added low/high target temperature caused the issue when using a “normal” climate device. The new **test version 1.18.1** should fix the issue (I hope). > **[Home Assistant Community | Homey](https://homey.app/en-us/app/io.home-assistant.community/Home-Assistant-Community/test/)** > > Connect to Home Assistant ---
**Author:** ![JOR1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jor1/32/17206_2.png) [@JOR1](https://community.homey.app/u/JOR1)\ **Post date:** [September 15, 2026, 7:56am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1532 "2026-09-15T07:56:09Z")
Thanks a lot. I can now set target temp again for whole degrees like 18.0, 19.0, 20.0 as before, but Homey App UI is now in 0.5 degree steps. My devices in HA does not support half degrees. When pushing temp up or down, I get this error when temp is 19.5 or 20.5: ![2026-09-15 09.36.19](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/c/bc0177a1c72e4e32778d91e5518f8ea15b0ce730.jpeg) Otherwise this works fine. Rgds. ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 15, 2026, 9:01am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1533 "2026-09-15T09:01:06Z")
Has your HA climate entity a steps attribute? When adding this entity as thermostat dehice, Homey should use the min/max/steps definition from climate entity. ---
**Author:** ![JOR1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jor1/32/17206_2.png) [@JOR1](https://community.homey.app/u/JOR1)\ **Post date:** [September 15, 2026, 9:56am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1534 "2026-09-15T09:56:43Z")
This is how it looks like in HA: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/9/99ffed4c1f1cce571ff0ef4b104d5006ac361e18.png) ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 15, 2026, 3:06pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1535 "2026-09-15T15:06:01Z")
Look good. The min\_temp, max\_temp and target\_temp\_step is used during pairing. Has this changed in HA after you added the thermostat to Homey? ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [September 15, 2026, 3:33pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1536 "2026-09-15T15:33:04Z")
I added a capability update if min/max/steps has changed. So the current thermostat device should be updated now with the current HA attributes. Please check, if this solves your issue. New **test version 1.18.2** : > **[Home Assistant Community | Homey](https://homey.app/en-us/app/io.home-assistant.community/Home-Assistant-Community/test/)** > > Connect to Home Assistant [Previous page](https://community.homey.app/t/app-pro-home-assistant-community-app/71477.md?page=75) [Next page](https://community.homey.app/t/app-pro-home-assistant-community-app/71477.md?page=77)