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
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
reinstall the App from the store.
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.
1 Like
Do you use the Homey apps:
or different ones?
Correct.
When you follow the link to the manual in post 1, you’ll see:
MQTT Client isn’t used by the way.
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 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):
Add beacon device:
Beacon capabilities:
Flows:
2 Likes
Awesome Michel thanks a lot for your huge contributions.
1 Like
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?
Do you perhaps have an app installed that is no longer supported? There was a similar case in this topic:
Fantastic! Thanks for this!
I will look into the issue, maybe I will contact you directly for more information.
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.
You can install the test version or await Homeys approval.
Sorry for the late reply, I’ve now updated to 1.1.1. It works as intended!!! Awesome job!
1 Like
