IP Access control T24 push notification fails


I am using a T24 doorcam with Mobotix Live on Iphone. I can see the video from the camera and get a red box around the image when the doorbell is pressed, however, the doorbell doesn’t ring anymore. I have deleted the IP profile for my phone and created a new one - but no success so far.

In the network configuration testing dialog, I get the following response. Can anyone help me clarify if it contains a useful clue as to why the message failed?

Kind regards,

Niels van Strien

ps: I stripped urls out of the message below due to limitations of this forum

Sending IP message using profile “iPhone 12 Niels for Ring Events” (this may take up to one minute!):
INF: loading notify profile ip9 …
INF: name given by user is iPhone 12 Niels for Ring Events …
INF: using profile preset “push”
INF: set profile send order “parallel”
INF: set profile address “2446E659-6FC3-4BA8-AA16-7ECABC173B41”
INF: set profile data type “msg”
INF: set profile message “$(ID.NAM) rings at $(TMS.HOUR):$(TMS.MIN) on $(TMS.MON)/$(TMS.DAY)”
INF: set profile raw boundary “–next-image–”
INF: force generation of current JPEG …
INF: using push profile ‘iPhone 12 Niels for Ring Events’
INF: authorization key is valid
INF: * Trying…
INF: * Connected to ( port 443 (#0)
INF: * libcurl is now using a weak random seed!
INF: * ALPN, offering http/1.1
INF: * SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256
INF: * ALPN, server accepted to use http/1.1
INF: * Server certificate:
INF: * subject: C=US; ST=California; L=Mountain View; O=Google LLC;
INF: * start date: Apr 13 10:23:09 2021 GMT
INF: * expire date: Jul 6 10:23:08 2021 GMT
INF: * subjectAltName: host matched cert’s
INF: * issuer: C=US; O=Google Trust Services; CN=GTS CA 1O1
INF: * SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
INF: > POST /fcm/send HTTP/1.1
INF: Host:
INF: Accept: /
INF: Content-Type:application/json
INF: Authorization:key=AAAARC7p…1UVCnwpA
INF: Content-Length: 341
INF: * upload completely sent off: 341 out of 341 bytes
INF: < HTTP/1.1 200 OK
INF: < Content-Type: application/json; charset=UTF-8
INF: < Date: Mon, 17 May 2021 12:41:05 GMT
INF: < Expires: Mon, 17 May 2021 12:41:05 GMT
INF: < Cache-Control: private, max-age=0
INF: < X-Content-Type-Options: nosniff
INF: < X-Frame-Options: SAMEORIGIN
INF: < Content-Security-Policy: frame-ancestors ‘self’
INF: < X-XSS-Protection: 1; mode=block
INF: < Server: GSE
INF: < Alt-Svc: h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v=“46,43”
INF: < Accept-Ranges: none
INF: < Vary: Accept-Encoding
INF: < Transfer-Encoding: chunked
INF: <
INF: * Curl_http_done: called premature == 0
INF: * Connection #0 to host fcm.googleapis.com left intact
INF: Notification failed (200)
ERR: push notification failed (rcode=1)

we have already identified the Push Notification issue. The issue seems to lie in the Google Firebase Server.

Our developers are working together with the Google engineers to deliver a solution as soon as possible.

Thank you. I will check the forum regularly for updates.

Should I be able to configure the doorbell ringing (on the Mobotix Live app) from within my own network, without dependencies on an external service? If yes, can you point me to a configuration example?

Kind regards,


when the MobotixLive was created a decision was made to use Firebase in order to save on Smartphones battery life. Because a direct local connection would require the app and the camera to community the whole time. Resulting on emptying the battery quicker.
Since this issue is only shown in iOS devices you could try our old Mobotix App from the AppStore. You should keep in mind that this app is not updated any more so incompatibilities with latest iOS versions might occur.

The old Mobtix app does notify me when the doorbell rings! This is a good temporary workaround. I do hope that the firebase issue will be resolved soon.

Thank you for your help

The problem should be solved by now. We tested it in our devices and the Push Notifications work again.

Test it also in your device and let me know if you still have problems.

I just tested it and it works again. Thank you for the help.