Sure, Here is the diagnotics key:
945d950a-fefb-4195-85e0-46be69e8c9f0
Was that log with a doorbell press? I now see the video drivers doing their job at least but I couldn’t spot the press.
Yes this diagnostic is +/- 30-40 sec after doorbell press
And what does step 4 say " In the version 202 or later check app → Configure → Diagnostics → Doorbell events, what does it say there when you press the doorbell."
none recorded yet - press the …
Im gonna publish a new version in a sec, we’ll split the doorbell into it’s own device. Will hopefully make troubleshooting easier.
Could you do two things:
1. Remove old doorbell from devices, and add it again via doorbell driver.
2. Press the doorbell, then within 20-30 seconds create a new diagnostic report and send it
3. check app → Configure → Diagnostics → Doorbell events, what does it say there when you press the doorbell.
add the doorbell as doorbell.
The diagnostics are the same.
Diagnostics key:
4501a8b5-91c2-4b90-bf47-1e737eabb576
cheers, the doorbell shows now, just correct DoorBell stream targets. Try: Ajax Beveiligingssysteem | Homey
The logs are helping with pinpointing seeing as I don’t have the device, again much appreciated.
Diagnostics the same.
Diagnostics key:
b0f08767-8bdd-4f5e-9709-1b67b531f922
So I see a failure from the doorbell now, but need some more info. Could you try this new version: Ajax Beveiligingssysteem | Homey
The failure does seem to look like a permission issue. Could you also do the following:
- Test while armed: arm the system, then press the doorbell. If the ring now shows up in Homey, your doorbell access is set to “only when armed” — change it to Always if you want rings while disarmed.
- Check video access for the Homey account: in the Ajax app, open the doorbell → its video/privacy access settings, and make sure the Homey integration signs in as has live-view (“VIEW_LIVE_STREAM”) access, with the policy set to Always.
