# \[APP\]\[Pro\] Homey ESPresense room presense system

**URL:** <https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742>\
**Category:** Apps\
**Created:** [November 15, 2023, 6:52pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742 "2023-11-15T18:52:10Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![John\_Clegg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_clegg/32/79366_2.png) [@John\_Clegg](https://community.homey.app/u/John_Clegg)\
**Post date:** [December 23, 2024, 10:25pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/62 "2024-12-23T22:25:07Z")

</div>

Hi

I am getting “This app is not supported anymore!” for the ESPresense app

And the Developer has been suspended. [Profile - Menno\_van\_Hout - Homey Community Forum](https://community.homey.app/u/Menno_van_Hout/summary)

☹

---

<div class="post-metadata">

**Author:** ![Pkoerner81929](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pkoerner81929/32/114822_2.png) [@Pkoerner81929](https://community.homey.app/u/Pkoerner81929)\
**Post date:** [January 7, 2025, 4:07pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/64 "2025-01-07T16:07:58Z")

</div>

Same here. It worked well for me. Is there a way to still keep the app (or any other unsupported app) running in unsupported mode with the last working version?

If not, are there alternatives using espresence devices?

Thanks, Peter

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [January 7, 2025, 5:54pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/65 "2025-01-07T17:54:19Z")

</div>

> [@Pkoerner81929](#):
>
> Is there a way to still keep the app

reinstall the App from the store.

---

<div class="post-metadata">

**Author:** ![Rett\_Pop](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rett_pop/32/69805_2.png) [@Rett\_Pop](https://community.homey.app/u/Rett_Pop)\
**Post date:** [January 8, 2025, 6:19am UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/66 "2025-01-08T06:19:43Z")

</div>

> [@Pkoerner81929](#):
>
> If not, are there alternatives using espresence devices?

From the ESPresense app I switched to a combination of MQTTHub and MQTTClient on Homey. Configured ESPresense boards to publish to MQTTBroker. Created MQTTHub devices with the distance value from each tracker’s I need topic. For a tracker, I do not need to know distance but just the fact of the presense, I’m using MQTTClient When card with a subscription to a corresponding topic and registering its last update time.  
Now the app is seemed in the store again, but this combination gave me more flexibility with more verbosity, though. In particular, it gave me to distinguish which exactly ESP board published update for certain tracker. With ESPresense Homey app I did not manage to achieve that.

---

<div class="post-metadata">

**Author:** ![YouSeeStefan](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/youseestefan/32/88115_2.png) [@YouSeeStefan](https://community.homey.app/u/YouSeeStefan)\
**Post date:** [June 23, 2025, 1:45pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/67 "2025-06-23T13:45:40Z")

</div>

Do you use the Homey apps:

> **[MQTT Broker](https://homey.app/en-us/app/nl.scanno.mqttbroker/MQTT-Broker/)**
>
> A MQTT Broker for Homey

> **[MQTT Client](https://homey.app/en-us/app/nl.scanno.mqtt/MQTT-Client/)**
>
> Subscripe to MQTT topics

or different ones?

---

<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 23, 2025, 4:10pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/68 "2025-06-23T16:10:19Z")

</div>

Correct.  
When you follow the link to the manual in post 1, you’ll see:

 ![Screenshot_20250623_180602_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/7/77df8bc73a4c086a338e4b710b5647fcd1ef2704.jpeg)

MQTT Client isn’t used by the way.

---

<div class="post-metadata">

**Author:** ![Michel\_Hoek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michel_hoek/32/79184_2.png) [@Michel\_Hoek](https://community.homey.app/u/Michel_Hoek)\
**Post date:** [November 25, 2025, 10:25am UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/69 "2025-11-25T10:25:55Z")

</div>

Hi All,

We have made updates to the ESPresense App. You can now add beacons (phones, watches) as Homey devices, these devices can then be used in flows. You can now identify devices that are out of range or coming back into range and what their nearest node (room) is. You can add all the devices that have registered with the MQTT broker. If you have a lot of BLE devices, consider adding filters on your ESPresense nodes.

Creating mappings is no longer required, adding a beacon to Homey automatically creates a mapping for you. For compatibility reasons, the mappings setting still exists and is still used to rename/add your device. We might however remove this setting in the future.

For the ESPresense app to work you need at least:

- ESPresense Nodes (ESP devices with Wifi/BLE and ESPresense firmware installed)
- MQTT Broker (you can use the homey MQTT Broker app)
- Beacons (BLE devices like phones and watches)

For Apple devices, in my experience, it’s best to enroll them on a ESPresense node and then use the irk (Identity Resolving Key, like irk:180000000000000000000000000000f8) instead of the custom id (like iphone:micheliphone) that you can specify during the enrollment process. If your MQTT broker and all your nodes are down (during a power outage), you’ll lose this link, while the irk will always continue to work. For more information about ESPresense, please go to the [espresense.com](http://espresense.com) website.

We did refactor the core workings of the app, check if all your flows are still working correctly.

Let us know if you have any issues. Have fun!

Some example screenshots:

Devices example (3 nodes, 1 beacon):

 ![Devices](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/2/b2e61a3f49e48c94dc3cd5a4d53c668ba24d5943.png)

Add beacon device:

 ![AddDevice](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/1/81f113a8ea79ea535175ede501376e683581d822.png)

Beacon capabilities:

 ![Beacon](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/9/695fbe778a7970baa866f0f6c19d4e83952a155d.png)

Flows:

 ![Flow](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/4/a4d549d53744208969eb2d8e1d95d71aa2cb0f95.png)

---

<div class="post-metadata">

**Author:** ![Menno\_van\_Hout](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/menno_van_hout/32/77843_2.png) [@Menno\_van\_Hout](https://community.homey.app/u/Menno_van_Hout)\
**Post date:** [November 25, 2025, 10:41am UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/70 "2025-11-25T10:41:46Z")

</div>

Awesome Michel thanks a lot for your huge contributions.

---

<div class="post-metadata">

**Author:** ![Anders\_Werner-Erichs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_werner-erichs/32/120885_2.png) [@Anders\_Werner-Erichs](https://community.homey.app/u/Anders_Werner-Erichs)\
**Post date:** [November 26, 2025, 7:07pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/71 "2025-11-26T19:07:53Z")

</div>

Thank you for nice work. My system has been working flawless in over a year.  
But after the update Im getting this error in my flows? What am I doing wrong?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/9/0914ee40908426d4224a4d434493b06b1de69ec3.png)

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [November 26, 2025, 7:31pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/72 "2025-11-26T19:31:11Z")

</div>

Do you perhaps have an app installed that is no longer supported? There was a similar case in this topic:

> [@Cannot read properties of null (reading 'toLowerCase')](https://community.homey.app/t/cannot-read-properties-of-null-reading-tolowercase/112309):
>
> Hi, When I try to add a flowcard “Then \> Apps \> Activate app …”" and try to select app it gives me the error “Cannot read properties of null (reading ‘toLowerCase’)”. I just upgraded from Homey Pro 2019 to 2023 with backup. I also can’t search for any apps available in list. All is working fine after back-up. I have checked my app list and couldn’t find anything strange. Is this a bug in Homey or am I missing something? [image]

---

<div class="post-metadata">

**Author:** ![Rett\_Pop](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rett_pop/32/69805_2.png) [@Rett\_Pop](https://community.homey.app/u/Rett_Pop)\
**Post date:** [November 26, 2025, 10:05pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/73 "2025-11-26T22:05:50Z")

</div>

Fantastic! Thanks for this!

---

<div class="post-metadata">

**Author:** ![Michel\_Hoek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michel_hoek/32/79184_2.png) [@Michel\_Hoek](https://community.homey.app/u/Michel_Hoek)\
**Post date:** [November 27, 2025, 6:48am UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/74 "2025-11-27T06:48:28Z")

</div>

I will look into the issue, maybe I will contact you directly for more information.

---

<div class="post-metadata">

**Author:** ![Michel\_Hoek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michel_hoek/32/79184_2.png) [@Michel\_Hoek](https://community.homey.app/u/Michel_Hoek)\
**Post date:** [November 27, 2025, 2:59pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/75 "2025-11-27T14:59:46Z")

</div>

The auto-complete issue in the flows has been resolved, we will roll out a new version.

Thank you for sending the screenshot. It helped a lot and I was able to reproduce the error. It all had to do with beacons without names populating the auto-complete. It is strange we did not encounter the error during our testing, but it has been resolved.

---

<div class="post-metadata">

**Author:** ![Menno\_van\_Hout](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/menno_van_hout/32/77843_2.png) [@Menno\_van\_Hout](https://community.homey.app/u/Menno_van_Hout)\
**Post date:** [November 29, 2025, 1:22am UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/76 "2025-11-29T01:22:13Z")

</div>

You can install the test version or await Homeys approval.

---

<div class="post-metadata">

**Author:** ![Anders\_Werner-Erichs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_werner-erichs/32/120885_2.png) [@Anders\_Werner-Erichs](https://community.homey.app/u/Anders_Werner-Erichs)\
**Post date:** [December 1, 2025, 2:25pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/77 "2025-12-01T14:25:42Z")

</div>

Sorry for the late reply, I’ve now updated to 1.1.1. It works as intended!!! Awesome job!

---

<div class="post-metadata">

**Author:** ![Chris\_nl](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chris_nl/32/27194_2.png) [@Chris\_nl](https://community.homey.app/u/Chris_nl)\
**Post date:** [May 17, 2026, 10:48am UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/78 "2026-05-17T10:48:56Z")

</div>

Just tried running the new version 1.1.1, but when creating flows the cards refresh every second or multiple times a second, probably on every mqtt update. So it’s hard to set any values to the placeholders. Happens in standard and advanced flows.

Couldn’t upload a video here, so I hope it’s clear whats happening, and that you can maybe look into it. Thanks

---

<div class="post-metadata">

**Author:** ![Rett\_Pop](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rett_pop/32/69805_2.png) [@Rett\_Pop](https://community.homey.app/u/Rett_Pop)\
**Post date:** [May 17, 2026, 11:02am UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/79 "2026-05-17T11:02:16Z")

</div>

I have the same problem. Didn’t report it. Not sure if it can be resolved on the app level.

---

<div class="post-metadata">

**Author:** ![Chris\_nl](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chris_nl/32/27194_2.png) [@Chris\_nl](https://community.homey.app/u/Chris_nl)\
**Post date:** [May 17, 2026, 12:56pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/80 "2026-05-17T12:56:14Z")

</div>

No clue if it’s from the app or the MQTT update on Homey, might have a look into that later. Did just make an update so the app is more useful (to me at least)

@Michel_Hoek @Menno_van_Hout

> <https://github.com/mennovanhout/homey-espresense/pull/8/commits/d45b835896fd95e480a78b5296f71d8b69e933a7>

In this version you will have a new When card (When beacon X changes room and a new AND card Closest node is X. This might make it easier to create flows not based on distance but the room that was already shown on the beacons device tab.

 ![New flowcards](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/e/ce2fade3faab0a0c6ab963032e384daa94851d08.png)

Hope the app can be updated, and everyone using the app will enjoy it 👍

---

<div class="post-metadata">

**Author:** ![Menno\_van\_Hout](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/menno_van_hout/32/77843_2.png) [@Menno\_van\_Hout](https://community.homey.app/u/Menno_van_Hout)\
**Post date:** [May 17, 2026, 5:03pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/81 "2026-05-17T17:03:43Z")

</div>

Merged it and will make it ready for homey to approve.

---

<div class="post-metadata">

**Author:** ![Menno\_van\_Hout](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/menno_van_hout/32/77843_2.png) [@Menno\_van\_Hout](https://community.homey.app/u/Menno_van_Hout)\
**Post date:** [May 17, 2026, 5:07pm UTC](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742/82 "2026-05-17T17:07:05Z")

</div>

Test version v1.2.0:

> **[ESPresense | Homey](https://homey.app/en-nl/app/nl.mennovanhout.espresense/ESPresense/test/)**
>
> Make personalised flows with ESPresense

[Previous page](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742.md?page=3)

[Next page](https://community.homey.app/t/app-pro-homey-espresense-room-presense-system/94742.md?page=5)
