The beacon device isn’t finished yet (doesn’t do anything).
I accidentally already put it in the code.
I took it out for the release at it isn’t functional at the moment.
It is still in de code just dragged the folder outside the driver folder. If you drag it back in there its back. But it was mainly only the start.
My idea is:
On pairing you get the list of devices that are in the mapping table.
When added this “beacon” als device has a room sensor.
The closed sensor you have been will be the room sensor value.
Having installed and configured all the components all seems working well. The Lolin ESP-board reports the beacon distance to the MQTT broker, and beacon’s can be enrolled and are available in advanced flows. e.g. Apple Watch 9 en iPhone 14. MQTT Explorer shows beacon updates in the broker.
Except the flow I have doesn’t trigger the 'When a device is closer than…".
Does anyone have an idea why the flow isn’t triggered?
Who can help me? I’m probably missing something. I’ve installed the ESP32 along with the ESPresense and Broker apps. Everything is set up. I created and linked a device, and I also made a flow: if the phone comes within 1 meter, a notification should be sent as a test. However, nothing happens. Additionally, I’ve noticed that I don’t see the phone in the Presence device on Homey, see:
Hello everyone, I have another question. Everything is working fine, but it seems that the device occasionally stops working. This causes the flows to show the status “Broken,” and a second later, they start working again. My timeline is filling up because of this.
Has anyone experienced this issue or have any idea how to fix it?
You can ask dev Martijn at the flow checker app topic. Maybe he can add a “blind time” to the check, like, a flow has to be broken for, say, 10s before a flow is actually considered broken.
Yes I know this topic is about Menno’s app, Geurt.
I do mean Martijn: I responded about the Flow Checker app marking flows too quick as broken,
like shown on the timeline screenshot shown by Sander Jacobson.
Some devices really go briefly offline, resulting in a broken flow notification, which could be ignored with a certain delay.