Anleitung Doorbird Integration mit SIP Funktion

[Gerhard]

Danke für deine sehr Detaillierte Beschreibung

[Gerhard]

Das wundert mich nicht, du hast ja überhaupt nichts in der Loxone Config bei Audio Benutzerdaten eingetragen

[Gerhard]

Was genau hast du wo eingetragen? Ich kämpfe noch mit dem externen Audio

[Gerhard]

Was genau hast du denn da in der Loxone config bei audio extern eingetragen. Kannst du das mal posten. Ich habs noch nicht ganz kapiert :/

[Gerhard]

Mit dem Admin Benutzer kann das auch nicht funktionieren. Es muss immer ein zusätzlicher Benutzer mit den entsprechenden Rechten angelegt werden.

[hme0354]

I am using doorbird with lan. so why I have the same problem?

[TomekWaw]

BTW, hme0354 on that restarting issues you've mentioned in CamStream4Lox thread.
I noticed some Doorbird timeouts on my Synology. Once or twice every single day.
But they are short - usually one or few seconds.
I believe its not because of Doorbird restart, as it boots much longer.
But this is still interesting why that happens.
My Hikvision and BCS camers does not suffer this issue.
I might have a weaker Wifi range outside of my front door, but I believe it's not that weak to cause timeouts.

[challo]

for me it's the same. First motion is not transfered to loxone. after i changed schedule as described it's working fine now. Tanks!

[hme0354]

really strange. I deactivated the motion sensor. Every day the cat of my neighbor was detected several times.

[challo]

strange, i'll check it at my installation this evening

[TomekWaw]

Ok, now it's working. Really strange!

I had a setting before:
- Schedule for HTTP Action "doorbell" - never
- Schedule for HTTP Action "motionsensor" - always
and only motion sensor has been passing to Loxone

Then I changed schedule to:
- Schedule for HTTP Action "doorbell" - never
- Schedule for HTTP Action "motionsensor" - never
and still only motion sensor is being passed to Loxone

Finally I changed schedule to:
- Schedule for HTTP Action "doorbell" - always
- Schedule for HTTP Action "motionsensor" - never
and since then - both doorbell and motion sensor signals are passed.

So it seems that action for doorbell HTTP Action is required for it to work.
And action for motion sensor isn't required.

I really don't get that part of the software....

[challo]

i also have 2 https actions dorbell and "legacy api http notification motionsensor" and i don't get motion signal in loxone. i never looked at the schedule. but maybe thats the issue. Does anyone use both signals and it's working?

[hme0354]

have you tried if one of the signals will be blocked by doorbird and not send to loxone if the schedule is set to not ring or so?

in my understanding the schedule is only for the doorbird app. but if you need a schedule you can build on in loxone aswell.

[TomekWaw]

Yes. As I understand HTTP(S) Actions have to be enabled in "Schedule for actions" and only one action may be enabled at a time on this Schedule. I would very like to be mistaken here, but have no any clues how to configure it differently

[challo]

you only get doorbell signal or motion signal in loxone?