# \[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:** 56

<div class="post-metadata">

**Author:** ![Marco\_Rombout](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marco_rombout/32/47933_2.png) [@Marco\_Rombout](https://community.homey.app/u/Marco_Rombout)\
**Post date:** [June 19, 2024, 8:00pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1114 "2024-06-19T20:00:54Z")

</div>

Hi @RonnyW , I experience the same as described here.  
Debug log: a01d24bb-e93d-40d7-894a-4c5cadce5940  
I tried the latest version of Home assistant community as well as the beta.

Any tips, tricks? I’ve removed, restarted, reinstalled the lot to no avail unfortunately.  
I guess it’s on the HA side they’ve changed something (but what…?)

 ![err1](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/6/4656ada32c5d78580d4eb2fd5e773b80e1b3a3b5.png)  
 ![err2](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/7/27f1b71fc5a6717e93813cf13b829f3fb4929439.png)  
 ![HA](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/9/2973d77c306444c051a3007238410b18093741bf.png)

---

<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:** [June 19, 2024, 8:55pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1115 "2024-06-19T20:55:23Z")

</div>

I can only see the error code “1” (ERR\_CANNOT\_CONNECT).  
That means that the app can’t connect to HA via WebSocket connection.

Is it a new app install oder did it work before with an older HA version?

---

<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:** [June 19, 2024, 9:07pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1116 "2024-06-19T21:07:48Z")

</div>

I guess you’d use HTTP instead of HTTPS

---

<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:** [June 19, 2024, 9:29pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1117 "2024-06-19T21:29:01Z")

</div>

I think @Peter_Kawa is right.  
You are using dyndns. But locally, your HA is running on http as default. So you also have to use http for dyndns/port forwarding.

---

<div class="post-metadata">

**Author:** ![Marco\_Rombout](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marco_rombout/32/47933_2.png) [@Marco\_Rombout](https://community.homey.app/u/Marco_Rombout)\
**Post date:** [June 20, 2024, 6:56am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1118 "2024-06-20T06:56:15Z")

</div>

Yes, it worked before with an older HA version.  
Because of repairs I needed to be done to a propriatary bridge it has been disabled for approx 2 months.  
When I re-instated the connection nothing happened so I started troubleshooting.

---

<div class="post-metadata">

**Author:** ![Marco\_Rombout](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marco_rombout/32/47933_2.png) [@Marco\_Rombout](https://community.homey.app/u/Marco_Rombout)\
**Post date:** [June 20, 2024, 6:58am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1119 "2024-06-20T06:58:15Z")

</div>

I tried a local http connection as well.  
[http://172.x.x.x:8123](http://172.x.x.x:8123)

Same result unfortunately

---

<div class="post-metadata">

**Author:** ![Marco\_Rombout](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marco_rombout/32/47933_2.png) [@Marco\_Rombout](https://community.homey.app/u/Marco_Rombout)\
**Post date:** [June 20, 2024, 7:06am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1120 "2024-06-20T07:06:01Z")

</div>

I think it can be certificate related when using DDNS.  
Error: request to [https://xxxxxxxxxx.dyndns.org:3689/](https://xxxxxxxxxx.dyndns.org:3689/) failed, reason: unable to verify the first certificate  
HA shows this with network setting;

 ![HA](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/5/759a0de2ed105aafd4b90d669efda00f59eba178.png)

However, bypassing certificate verification by just plain and simple HTTP results in error as well.  
Perhaps you can check again? f86e6dec-3a73-4fc1-a7f0-44263fde8949

---

<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:** [June 20, 2024, 7:15am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1121 "2024-06-20T07:15:59Z")

</div>

If https is set in HA settings, you can only use https, not both parallel because the same port is used.

I’m not sure if selfsigned certificates are accepted. I use https only via reverse proxy and a real letsencrypt cert.

---

<div class="post-metadata">

**Author:** ![Ronni](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronni/32/34633_2.png) [@Ronni](https://community.homey.app/u/Ronni)\
**Post date:** [June 23, 2024, 1:09pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1122 "2024-06-23T13:09:51Z")

</div>

After installation of my new Aqara T1M Zigbee ceiling light in HA, I was adding it to Homey as 2 separate devices (lights), as expected because it also have a RGB ring that can be controlled separately. I can control both lights in Homey - HOWEVER, when I turn on the main light from within Homey, it does not fade in, as it does in HA when I turn it on from there. Is it because that the HA Community App in Homey first sends the brightness, and afterwards the turn on command? Because it have the behavior if I just change the brightness while the light is off, and on the RGB Ring it fades in if I change the brightness while off. (Strange that they are acting differently on this).  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/6/064fe6300609f79e7f9e92e900f1f15e104fcba4.png)

---

<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:** [June 23, 2024, 1:26pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1123 "2024-06-23T13:26:28Z")

</div>

If I remeber right, the app sends the “on” command and (last known) color/brightness in one API call.  
You can try a flow action with duration. Perhaps that’s what you want. If yes, the HA integration perhaps uses duration as default.

---

<div class="post-metadata">

**Author:** ![Ronni](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronni/32/34633_2.png) [@Ronni](https://community.homey.app/u/Ronni)\
**Post date:** [June 23, 2024, 1:33pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1124 "2024-06-23T13:33:27Z")

</div>

Aaarh, the duration works. I’ve never used this option before…! 😆  
Thank you very much Ronny! 🙏

The only issue is that it can’t be turned on with duration using the “mood” action. But that’s ok!

---

<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:** [June 23, 2024, 1:44pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1125 "2024-06-23T13:44:05Z")

</div>

I can imagine a device setting for default duration. This can be used as default if no other value is set in a flow card.  
So all actione like Mood, manual on/off would use a duration.

---

<div class="post-metadata">

**Author:** ![Ronni](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronni/32/34633_2.png) [@Ronni](https://community.homey.app/u/Ronni)\
**Post date:** [June 23, 2024, 2:00pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1126 "2024-06-23T14:00:43Z")

</div>

If you find this default duration setting somewhere, please let me know. 😉

---

<div class="post-metadata">

**Author:** ![Grzegorz\_Zalewski](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/grzegorz_zalewski/32/58310_2.png) [@Grzegorz\_Zalewski](https://community.homey.app/u/Grzegorz_Zalewski)\
**Post date:** [June 26, 2024, 10:42pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1127 "2024-06-26T22:42:29Z")

</div>

Hi the integration stop worked for me around 5 days ago.  
I regenerate the new token and now I cant connect.

 ![Arc_2024-06-27_00.38_C7pBKSif](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/d/eddc054fdaf710d11efdd5fd48007925a86e0949.png)  
Any ideas

---

<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:** [June 26, 2024, 11:49pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1128 "2024-06-26T23:49:32Z")

</div>

(m)DNS issues?  
You could try using the HA IP address instead,  
I.e.:  
`http://192.168.10.20:8123/`

---

<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:** [June 30, 2024, 11:32am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1129 "2024-06-30T11:32:23Z")

</div>

New **live version 1.5.24** :

- Added token for previous state to app trigger ‘entity state changed’.

With this trigger you get now the new and previous entity state. If you want to react on a special state chage (from x to y), you can now use the tokens without needing other variables.

![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/6/56e8c41968d5ee4cf934e045e91db4cc2954524a.png)

---

<div class="post-metadata">

**Author:** ![basvanderploeg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/basvanderploeg/32/83556_2.png) [@basvanderploeg](https://community.homey.app/u/basvanderploeg)\
**Post date:** [July 3, 2024, 12:49pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1130 "2024-07-03T12:49:38Z")

</div>

@RonnyW Is there a way to prevent devices without a battery from showing up in the _More \> Batteries_ section of the Homey app?

I’ve added some sensor devices without a battery capability, but they still show up in the list with Battery devices.

 ![IMG_1457](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/1/81640818e3454efe0e1d081fc20382bd6d84fb43.png)

---

<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:** [July 3, 2024, 1:10pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1131 "2024-07-03T13:10:50Z")

</div>

I thought, only devices with measure\_battery are listed.  
The driver has a battery setting “others” to be able to add battery data.

Perhaps that’s a but in mobile app. I have to ask Athom…

---

<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:** [July 16, 2024, 5:56pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1132 "2024-07-16T17:56:55Z")

</div>

New **test version 1.6.0** :

- “only” a technical **performance optimization** to reduce CPU usage significantly

Check your app CPU insights the next hours/days. It should look like this now 😀

 ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/d/0d0d5864a64bc6ef9b539824925cb20f1514627e.png)

---

<div class="post-metadata">

**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:** [July 17, 2024, 10:03am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1133 "2024-07-17T10:03:21Z")

</div>

Hi.  
After update to v1.6.0 most of my Homey HA devices does not update anymore. The entities do not update in Homey when they change in HA.

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

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