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.
Many similarities and overlap, main difference is that for Ajax systems you either require an enterprise acces account/api or acces to a public proxy (with the downsides from that).
My app connects the same way as the Ajax app itself (you’ll see a homey device showing up under devices). You can still use the other modes of connecting (except public proxy, I made this app cause I don’t want my data going through a proxy)as well.
Any update on the issue?
Yes, it still isn’t working. 
It also doesn’t work when the alarm is enabled.
I noticed you’ve made some updates to allow viewing the camera, but that isn’t working either.
hmm could you send another diagnostic report, it really looked like an Ajax acces issue, apologies.
Would be this version: Ajax Beveiligingssysteem | Homey Ive also added onvif support, it should auto fill in the needed information for the doorbell/cameras. It might be that that’s the road we need to follow.
Hello MikeTango
Thank you for your feedback, I will be happy to try your app. I prefer this workings.
Is there a rough guide (reference) how to proceed? I saw one in this thread, but it’s older date and I’m not sure if it’s for your app or for the other.
Thank you for your support.
Depends on your usage case, the app should explain the different scenarios and if not feel free to ask here.
Another question, which login are you using? Enterprise API, mobile or local Sia only? I noticed the API login wasn’t linked yet for onvif, should be now
