Hello, I added this based on user feedback since I don’t have a Ratgdo device. I’d appreciate it if you could explain the non-functioning feature from a technical perspective. If there’s any YAML code, I’ll try to include it to the best of my ability.
1 Like
I have released a separate app for the Konnected Alarm Panel and GDO. This app is much more stable and offers broader support. For this reason, I will be removing the Konnected Alarm Panel drivers from the Ephome app. I kindly ask users who wish to use the Konnected Alarm Panel and GDO to please use the Konnected Alarm Panel & GDO app.
Hi,
I have an issue with Zuidwijk ESP home doorbell (https://github.com/zuidwijk/esphome-doorbell), not being able to generate a notification on my phone when the doorbell rings.
I have installed the doorbell and it’s physically working (it powers up, the doorbell push button triggers the bell so the relay is working and the ESP is powered up, wifi is working and accessible and the device is visible to the ESP home controller). However, the triggers are not visible to Homey in the insights view, nor are they being picked up by Flows. I can see the status of the doorbell change in ESPhome, but that status change isn’t being picked up by either flow or insights.
Am I configuring something wrong or is there something else going on? I have attached screenshots of both Homey and the ESP configuration for your convenience.
With kind regards,
Geert
Thank you for the detailed report and screenshots — very helpful.
From what I can see, Homey is receiving the doorbell events (the contact alarmentries in Insights confirm this), so ESPHome connectivity is working correctly.
The most likely issue is that the Flow is listening to the wrong entity (for example Status Doorbell instead of the actual Doorbell button sensor).
Could you please try this exact Flow setup:
-
When →
ESPHome Controller→Binary sensor changed -
Device → your
smart-doorbell -
Sensor →
Doorbell(notStatus Doorbell) -
And →
state = true -
Then → send push notification
Also check:
-
In device settings, leave Entity Key empty (or set it only to the actual Doorbell binary sensor key, not the status sensor key).
-
If the button pulse is very short, add this in ESPHome to make it easier for Homey to catch:
filters:
delayed_off: 500ms
If it still doesn’t notify, please send:
-
A screenshot of the Flow card configuration
-
A new Diagnostic Report ID
I’ll help you fine-tune it quickly.
Hi,
I have tried to set up the logic according to your instructions, but I can’t seem to locate the state = true verification - I have attached a snippet of the available ESPhome Controller actions for “when” and “end”.
The state change is clearly visible in the device when the doorbell is pressed (doorbell = yes when pressed) but Flows isn’t able to pick up the state change, neither through binary sensor change nor through the dedicated flow card in the doorbell.
I have attached the test flow (which I tested with testing just it either just on binary sensor and with the doorbell status on), but neither trigger a notification or a variable change.
ID = 2BFDFE2C
Hope this helps..
Geert
The key point is: for the ESPHome Controller → Binary sensor changed trigger, there is no separate “state = true” dropdown. The state is a tag/token from the trigger event.
Also, in your current test flow, the Is on condition can miss the ring because a doorbell pulse is very short (it may already be off by the time that condition is checked).
Please try this exact test flow (no conditions):
-
When:
Doorbell - Gang→ Het contactalarm gaat aan -
Then: send mobile push message
Do not add
Is aanorStatus Doorbell = jafor this test.
If this works, then the trigger is fine and we can add logic afterwards.
If you want to use the generic ESPHome trigger:
-
When:
ESPHome Controller→Binary sensor changed(sensor = Doorbell) -
Use the trigger tag
state:-
In Advanced Flow, drag the
statetag to a Logic boolean check (is true) -
or include it directly in a test notification message
-
Testing the above logic doesn’t trigger a notification so I assume the trigger length is too short to be picked up. I will check with the doorbell vendor if we can change the trigger delay, although I’m a bit surprised that the ESPhome controller doesn’t pick up on state changes after the bell has rung even though it is clearly visible in the device itself.
I’ve made a fix. Please install the beta version of the app, delete the device you added earlier, add it again, and try it out. I’d appreciate it if you could let me know how it goes.
No change unfortunately - find below a second diagnostics ID including attached ESPhome log for the doorbell.
ID: BDB365F2
I’ve prepared another test version. Please reinstall it, delete the device, and add it again. If that doesn’t work either, the issue might be on the automation side. If you let me know the result, I’ll see what I can do. By the way, the reports you’ve sent aren’t reaching me. ESPHome Controller | Homey
This appears to have done it!
What I did differently: reading your comment in the changelog in this being the door sensor I just added the “doorbell” as a door sensor device. This then gave the new card with “doorbell was pressed” - which I directly connected to the notification card, and this worked.
Two snips for your convenience.
Geert
1 Like
