# \[APP\]\[Pro\] Home Assistant - Community App

**URL:** <https://community.homey.app/t/app-pro-home-assistant-community-app/71477>\
**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:** 22

<div class="post-metadata">

**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:** [March 29, 2023, 2:09pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/427 "2023-03-29T14:09:16Z")

</div>

Hi @SossieNL , @Peter_Kawa  
The zone settings are Homey default. It’s not defined in the app.  
Let me check the SDK later if it perhaps depends on a special capability.

@SossieNL Just to check in my side…  
You added the sensor as sensor device?  
Can you please go to device/maintenance/repair dialog and go to device detail. Please post the details (or send as PM)  
I think the sensor is not defined as motion sensor in HA but as simple binary\_sensor. Perhaps the alarm\_motion will raise the zone activity, but a custom capability like alarm\_generic not.

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [March 29, 2023, 2:27pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/428 "2023-03-29T14:27:55Z")

</div>

> [@RonnyW](#):
>
> Let me check the SDK later if it perhaps depends on a special capability.

I can answer this one, it has 2 things that are mandatory to be included as zone activity.  
It needs to be of class `sensor`, and be 1 of 2 capabilities, `alarm_motion` or `alarm_contact`

---

<div class="post-metadata">

**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:** [March 29, 2023, 2:35pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/429 "2023-03-29T14:35:01Z")

</div>

Thanks, @Caseda.

@SossieNL  
So it’s caused by using alarm\_generic instead of alarm\_motion.  
I will take a look at the code how exactly the HA entities are interpreted.

---

<div class="post-metadata">

**Author:** ![SossieNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sossienl/32/11341_2.png) [@SossieNL](https://community.homey.app/u/SossieNL)\
**Post date:** [March 29, 2023, 3:52pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/430 "2023-03-29T15:52:16Z")

</div>

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/7/f7c75fcc345bc851161edbaefa742e2c2e4d0339.jpeg)

Hmm. That’s very empty. Yes added it as a sensor

---

<div class="post-metadata">

**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:** [March 29, 2023, 3:55pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/431 "2023-03-29T15:55:49Z")

</div>

Hm, the app should read the current entity details.  
Can you please check if your sensor entity has an attribute device\_class? If yes, is it set as “motion”?

…and thanks for your donation 🍻 😀

---

<div class="post-metadata">

**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:** [March 29, 2023, 4:12pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/432 "2023-03-29T16:12:49Z")

</div>

My sensor shows device\_class motion, that seems right  
@SossieNL In HA, go to :

 ![Screenshot from 2023-03-29 20-42-28](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/9/497eb034fd97bb7ad6d887a5565cd29fb4467ac4.png)

When I re-add it to Homey,  
 ![Screenshot from 2023-03-29 18-24-16](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/2/5285568d99d9611367ebb1d621a0365d0f8ea523.png)

it shows up as alarm\_motion sensor and activates the zone  
 ![Screenshot from 2023-03-29 18-25-06](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/9/594a450ca94c0e5fa982e3ef370fd197e7127a07.png)

> [@SossieNL](#):
>
> That’s very empty.

I also have an empty device details screen now, but it did work a while ago, I checked several HA devices. @RonnyW

The application log screen still shows info though:

```auto
[log] 2023-03-29 18:24:53 [Driver:sensor] [
  {
    "name": "presence-toilet-occupancy",
    "data": {
      "id": "binary_sensor.presence_toilet_occupancy"
    },
    "capabilities": [
      "alarm_motion"
    ],
    "icon": "../../../assets/icons/capabilities/alarm_motion.svg",

```

---

<div class="post-metadata">

**Author:** ![schmucke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/schmucke/32/79913_2.png) [@schmucke](https://community.homey.app/u/schmucke)\
**Post date:** [March 30, 2023, 8:14am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/433 "2023-03-30T08:14:43Z")

</div>

Good morning @RonnyW,

when i try a “or” with a “Lux” card, i just become this error:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/e/3e2524e702aab290fbb5720e3ac0997f6406a42a.png)

the sensor himself change the values right:  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/1/314551173e17035127309f051901d27cdd12a5a2.png)

thx

---

<div class="post-metadata">

**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:** [March 30, 2023, 2:00pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/434 "2023-03-30T14:00:56Z")

</div>

Hi @schmucke  
The existing conditions (Value “text”/“numeric”) are used for the generic capabilities measure\_numeric and measure\_generic. These capabilities are used if there is no defautl capability found for the entity based on its device class.  
And measure\_luminance doesn’t have default condition cards.

So far the technical reason. Now to your flow:

- You can’t use the card you tries. Beside there is a bug (error message) you found 👍 it’s not checking the luminance capability
- measure\_luminace doesn’t provide a condition card
- **So only and recommended solution is to use a logic card and the global tag**

![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/a/9a43114c041091d5040539c57492aeb6d3a8a3ec.png)

Perhaops it also would be better to remove these cards because it’s irritating.  
capability dependent cards are not so nice to use for dynamic devices that can have dynamic capabilities.

---

<div class="post-metadata">

**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:** [March 30, 2023, 2:15pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/435 "2023-03-30T14:15:50Z")

</div>

@schmucke  
I took your question as suggestion to read the first numeric capability from the device if measure\_numeric is not found so it will be possible to use this card also for devices without measure\_numeric, but with another numeric capability.  
So it’s working a bit mor generic 🙂

This will be added to the next version.

---

<div class="post-metadata">

**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:** [March 30, 2023, 7:17pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/436 "2023-03-30T19:17:56Z")

</div>

New **test version 1.3.0**

> **[Home Assistant Community](https://homey.app/en-us/app/io.home-assistant.community/Home-Assistant-Community/)**
>
> Connect to Home Assistant

**Changes:**

- Fix for switch device state not updating if a second entity is added.

- Fix for generic flow conditions “Numeric value greater” and “Textvalue equal”.  
These condition cars are checking the capabilities measure\_numeric or measure\_generic. In these capabilities are not found, the first numeric or text cability is used. This way these cards can also be used for sensor devices with other capabilities like temperature or luminance.

- Now the most importand addon:  
**Added possibility to individually add, change and remove entities.**

- And in addition there is a new device type to create a device from scratch and add your entities. You can see it as an easy “build your own device” alternative to compound devices.  
No need to add the HA integration, no HA restarts. Just add the device and add your entities.  

* * *

**Some details about the entity functionality:**

**Add entity:**  
Go to device maintenance/repair dialog to start…

 ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/d/5d023c98cc4ce5d42550db184b2205edf34a7e09.png) ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/2/6248ea600f3b40f0b540ea7c39d0167f4df999cc.png)  
Now you can select an entity start writing some text to filter the list.  
 ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/8/181bcc3d199abd8c341fead16372e0adac9a4b0b.png)  
Select the entry you want to add to your device. Some fields are preassigned with entity dependent content like name and unit. You can adjust name and unit to your needs.  
In addition the capability is also shown that will be used to add th entity. It’s discovered by the entities device class or unit.  
 ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/0/30e836b7e008292ffbdb66a0be11a4aeb1f8b52f.png)  
You can change the capability using the dropdown list. You can also change the subcapability name.  
If you want to add the capability as main capability (without subcapability like “onoff” to get quick actions), you can easily check the checkbox or delete the subcapability name in the capability field.  
If you need to convert the HA entity value you can add a JavaScript function. The “i” button gives some hints how to use it.  
 ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/1/918ffacb3330b1d37d7559f78dd69edbd6aac983.png)  
The Button “Add Entity” adds instantly your entity as new capability.

**Change entities:**  
All this way added entities can be changed afterwards. Adjust name, unit or converter function.  
Select one entity that was added to your device.

 ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/f/2f773dfba57a13b6ee9074c0c9254e3f2a1f5220.png)  
Then change the details.  
 ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/8/f806c57b2c408354bcc9428cb5a997e3507c1b43.png)

**Remove entities:**  
You can remove the entities just as easily:

 ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/2/8270c728a60fecab30fdae946aaf5ff96cbf7f10.png)

* * *

**Some technical details:**

- This functionality is based on the previously added functionality of adding device sensors in device settings. Entities added this way can be changed or removed in the same way.
- Main entities added on device pairing (like light or thermostat capabilities) can’t be adjusted.
- Only entities of type sensor, binary sensor, button or switch can be added. These entities can be used in a generic way. In contrast, special entities that need a special capability handling or special HA services to interact with HA, will still only be useable using the corresponding Homey device.
- But using this new feature, you can easily add some single sensors to your existing device.

* * *

Now have fun building your devices in Homey 🪄

Please report issues providing some details like changed device type, added entity type (domain, perhaps screenshot of entity details from HA developer tools).

---

<div class="post-metadata">

**Author:** ![Davide\_Zamo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/davide_zamo/32/32590_2.png) [@Davide\_Zamo](https://community.homey.app/u/Davide_Zamo)\
**Post date:** [April 1, 2023, 6:54am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/437 "2023-04-01T06:54:19Z")

</div>

i used this new functionality to add my dryer…

---

<div class="post-metadata">

**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:** [April 1, 2023, 8:19am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/438 "2023-04-01T08:19:13Z")

</div>

Hi Edwin, the switch update should be fixed in new test version.

---

<div class="post-metadata">

**Author:** ![SossieNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sossienl/32/11341_2.png) [@SossieNL](https://community.homey.app/u/SossieNL)\
**Post date:** [April 1, 2023, 8:55am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/439 "2023-04-01T08:55:44Z")

</div>

Worked like a charm!! Thanks!!

---

<div class="post-metadata">

**Author:** ![SossieNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sossienl/32/11341_2.png) [@SossieNL](https://community.homey.app/u/SossieNL)\
**Post date:** [April 1, 2023, 9:29am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/440 "2023-04-01T09:29:01Z")

</div>

Another one. Anyone any luck with the 4 & 6 button Aqara Opple switch/buttons?

I don’t see them under “Button” or “Switch”. But I do see them under “Sensor”. The value of “action” changes rapidly to a text describing the action I did. For instance; “button\_1\_single”.

I assume we need to do something in HA again? Any advice?

---

<div class="post-metadata">

**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:** [April 1, 2023, 11:42am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/441 "2023-04-01T11:42:58Z")

</div>

If it’s sensor, then you can react with a flow on state change. Just us the ‘value changed’ flow card and check the value using the flow card tag in a logic card.  
Here is a similar example (this and following posts):

> [@\[APP\]\[Pro\] Home Assistant - Community App](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/411):
>
> A sensor can have a state dependent on the HA implementation as string, number or boolean value. I think it’s a string/text value. The first flow card is used for additiona generic sensors (added in device settings). So use the “Value (text) has changed”. This shoudl trigger on the value change. Perhaps you have to add a logic card to check the value if it changes twice. You can log the value using the card tag into the timeline to see what content is sent.

---

<div class="post-metadata">

**Author:** ![SossieNL](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sossienl/32/11341_2.png) [@SossieNL](https://community.homey.app/u/SossieNL)\
**Post date:** [April 1, 2023, 2:46pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/442 "2023-04-01T14:46:30Z")

</div>

Yeah that’s how I implemented it. So it does work! However, it’s a bit less efficient, better to see a button-pressed scene? where you can also have single or double presses. That’s now al IF / THEN in my flows.

---

<div class="post-metadata">

**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:** [April 1, 2023, 3:08pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/443 "2023-04-01T15:08:29Z")

</div>

🤷‍♂️ That’s how HA works. Every integration has it’s own logic and implementation. No general logic to rely on.

And a button entity has only a timestamp that would trigger a flow like your “value has changed” trigger. You would need a single button entity in HA for every physical button on your wall device.

But hey, you can just use existing trigger for your sensor device.  
Much better than using a device independent event trigger in case of buttons that don’t have any entity in HA but sending only events like Hue’s.

---

<div class="post-metadata">

**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:** [April 1, 2023, 5:53pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/444 "2023-04-01T17:53:38Z")

</div>

New **test version 1.3.1** :

- Adjustes “non physical” devices like scenes to handle the new “add entities” functionality.
- Some optical adjustments in repair view

---

<div class="post-metadata">

**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:** [April 2, 2023, 8:12pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/445 "2023-04-02T20:12:12Z")

</div>

About **app crashes caused by invalid JSON content** …

Sometimes I get crash reports because inside the used HA websocket module an exception is thrown while parsing the JSON string sent from HA. This error occours bacause the JSON string is invalid (double quotes, invalid characters, invalid syntax).  
The HA app can’t react on this error because it processed asynchronous inside the module.

I got information from the module developer about a fix in HAs `orjson` module that will hopefully fix this issue.  
If your HA app crashed with an error like `SyntaxError: Unexpected token : in JSON at position 3272`, you will need to **update your HA installation to 2023.3 or newer.**

To track this error, please report such errors/crashes including information about your HA version. Thanks.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [April 6, 2023, 9:58am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/446 "2023-04-06T09:58:08Z")

</div>

Hi @RonnyW , fantastic app, thank you for developing it, it allows me to add boiler, which is HA connected via ESP32 and Bluetooth 😉

I was recommending now somewhere else to use HA for connecting some LGThinq appliances but when there is ton of sensors, switches etc., there are no real appliances… may I ask you, do you plan to add more devices, eg. washer and dryer ? 🫣

**update** just discovered you included custom devices in the TEST, looking on it right now 😉

[Previous page](https://community.homey.app/t/app-pro-home-assistant-community-app/71477.md?page=21)

[Next page](https://community.homey.app/t/app-pro-home-assistant-community-app/71477.md?page=23)