Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auerswald TFS-Universal Doorbell to HA #107

Open
ballchemist opened this issue Mar 13, 2024 · 8 comments
Open

Auerswald TFS-Universal Doorbell to HA #107

ballchemist opened this issue Mar 13, 2024 · 8 comments

Comments

@ballchemist
Copy link

Hi, impressive setup you have made so far.

I am seeking for a moor detailed explanation on the setup for AUERSWALD TFS-Universal Doorbell into the integration to HA.

I have a RASPI5 with HA and a Fritz.Box 7490 - hooked direktly to line 1 the doorbell Auerswald.

I would love to trigger EVENTS when someone is pushing the doorbell...

Any more details on your setup, and how to mirror this one would be deeply appreciatet... THanks!

@swa72
Copy link
Owner

swa72 commented Mar 13, 2024

That's a bit tricky as it involves the Fritzbox, a cheap USB modem connected to HA (and the phone line of the Fritzbox) and the TFS doorbell connected to a phone line of the Fritzbox

  • someone presses the doorbell. TFS calls "**702"
  • "**702" is defined as a group-call inside the Fritzbox, i.e. internally in turn calls "**615#614#610#620#621#2"
  • **615, **614, etc. are my DECT phones
  • 2 is the modem line (last number in the above group call is the modem)

You can pick any DECT phone and talk to the person at the door and press #9 or 9# (I can't remember which) to buzz the opener.

Now to the modem: the modem notices a ring. That's it. But it is an event nonetheless ;-) So we can trigger automations (on sensor.phone_modem, like sending a picture from the camera facing the front door to all local iPhones.

Pretty weird combo but works pretty reliably in my case.

@swa72
Copy link
Owner

swa72 commented Mar 13, 2024

Actually I have to add that I've defined a binary sensor that depends on sensor.phone_modem

    doorbell_pressed:
      friendly_name: "Doorbell was pressed, call initiated"
      value_template: "{{ states('sensor.phone_modem') == 'ring' }}"

@ballchemist
Copy link
Author

Thanks for the pretty detailed answer. I have the similar setting as you already - except the modem for hey Raspberry5… which one did you use?

@ballchemist
Copy link
Author

Similar to something like this?: https://amzn.eu/d/4phTUq3

@swa72
Copy link
Owner

swa72 commented Mar 14, 2024

Yep, according to https://www.home-assistant.io/integrations/modem_callerid/ look for something with a CX93001. I bought mine for cheap off of kleinanzeigen.de (similar to craigslist).

@ballchemist
Copy link
Author

Thanks for the detailed answer. I now managed to set everything up, but somehow got the problem that the modem stays continuously in the state "RING" - it´s detecting a permanent ring even though it´s not called... so if you might have any idea ... happy to include this as well

@swa72
Copy link
Owner

swa72 commented Apr 15, 2024

No breakthru idea other than try to call another number from the TFS-Universal doorbell (a regular phone) to see if the call initiation works?

@ballchemist
Copy link
Author

ballchemist commented Apr 15, 2024

Thanks, seems that there is somewhat a clinche after a ring got accepted, the Modem is not returning into idle... I am currently trying to set idle per default after each ring - but still tricky ...

I am now trying to include a "fallback" - 5 sec after every "call", or at least reagularly I´d like to Deactivate and reactivate the Modem Entity - to ensure it´ll is set to idle... anyone an idea on the yaml code to do so?
Bildschirmfoto 2024-04-15 um 21 18 10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants