No more webhook notification for incoming_call

stefan

Hi, since about 3 weeks i am no longer receiving the webhook with the event "incoming_call". I only get one with the event "missed_call". But the problem is that the missed_call comes delayed because the doorbell seems to wait for an answer. Why is the incoming_call event no longer sent?

2

Comments

15 comments

Date Votes
  • Comment author
    joel

    I'm experiencing the same issue with the "incoming_call" event not being sent. I was using the push type "NDB-incoming_call" to get snapshots from the doorbell.
    I've tried a new approach, using the "NDB-rtc" push type to trigger a request to "/getevents" and fetch the "incoming_call" subevent. However, the most recent event isn't available immediately in the response.
    Is this approach the right way? What would be the best approach to handle this?

    1
  • Comment author
    Leslie Community moderator

    Hello Stefan & Joel,

    The teams are currently investigating. They would need more information from you : 

    • the email address of your Netatmo end-user account
    • the app_id or the name of the concerned developer app (to be found here : https://dev.netatmo.com/apps/)
    • did you notice if the problem started on the 21 October ? There was a release on this date 

    For your privacy, you can send me these information via the contact form 

    Thanks and have a good day,

    Leslie - Community Manager

    0
  • Comment author
    Permanently deleted user

    Hello

    Same issue here.

    No incoming_call event

    Only "missed_call" or "accepted_call" but after the doorbell ring !

    Do you have news about this bug ?

    0
  • Comment author
    m.koehler.89

    https://community.home-assistant.io/t/netatmo-doorbell/121925/219

    the topic is already being hotly debated.

    0
  • Comment author
    Udo

    @Leslie

    Are you able to say when a solution can be expected?

    0
  • Comment author
    m.koehler.89
    • Edited

    Is there any news on this? It still doesn't work and even worse - I get a blocked VPN address: https://prodvpn-eu-11.netatmo.net/restricted/ ... - I can no longer retrieve images via Webhook.

    Before that, it was still via https://netatmocameraimage.blob.core.windows.net/production/

    0
  • Comment author
    Leslie Community moderator

    Hello, 

    I performed some tests on my side and indeed the snapshot URL leads to a 404

    Also, the push_type event is not "incoming_call" anymore but "NDB-human" when someone is detected

    I forwarded the information to the teams and they are currently taking a look at it

    Have a good day,

    Leslie - Community Manager

    1
  • Comment author
    m.koehler.89
    • Edited

    Thank you Leslie,

    Word is already getting around among colleagues and in the community that there has been no improvement for weeks... Even with Apple's Callkit function, there is no way to switch it off, which is very annoying, as it rings continuously at work and elsewhere!

    Don't get me wrong but no improvement with the bell for 17 days is a bit annoying, at least if there could be a success or correction, would have been nice. 

    Instead, there are now other errors with the camera, which means that the photos can no longer be retrieved via Webhook. 

    0
  • Comment author
    Leslie Community moderator

    Hello all,

    Good news, we just pushed a fix to make "incoming_call" event come back and resolve the snapshot display problem

    It seems OK on my side, can you please test and come back to me if you still detect a problem ?

    Have a good day,

    Leslie - Community Manager

    1
  • Comment author
    m.koehler.89

    ...'type': 'incoming_call',
    ...'snapshot_url': 'https://netatmocameraimage.blob.core.windows.net/... ' 'push_type': 'NDB-incoming_call'...

    Super! Leslie thank you very much for the announcement. I had to make a new webhook connection beforehand. It worked perfectly. Everything works as before. Thank you very much! :-)

    0
  • Comment author
    francesco.sabia.n3tp

    Please give us the possibility to not receive the notification on the Netatmo app. A lot of people using HomeKit… and I read this was already asked.. please listen to us

    0
  • Comment author
    Udo
    • Edited

    I can also confirm that the event incoming_call as well as screenshot is back working.

    Thank you!

    0
  • Comment author
    stefan

    Same here. Works as before. Thank You!

    0
  • Comment author
    m.koehler.89

    So wait a minute... Doorbell works now... but when people are recognised in front of the door, ‘human’ appears and the photos are still recognised with error 404. Please check this for yourselves. I still can't retrieve any pictures when people are recognised.

    {'type': 'human', 'data': {'user_id': 'xxxxxx', 'snapshot_id': 'xxxx3', 'snapshot_key': 'xxxxxx', 'snapshot_url': 'https://prodvpn-eu-5.netatmo.net/restricted/xxxxxx.jpg'....

    0
  • Comment author
    Leslie Community moderator

    Hello,

    The "NDB-human" events are normally the ones for our native app, and are behind our VPN for security. I asked the teams if it's normal that you also receive them, I'm waiting for a feedback

    Meanwhile, you should focus on "incoming_call" event as it's the correct one for 3rd parties

    Have a good day,

    Leslie - Community Manager

     

    0

Please sign in to leave a comment.