-
Notifications
You must be signed in to change notification settings - Fork 14
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
Intercom still no events #686
Comments
I have the same issue. Everything is working, but the events folder is empty. |
Same here |
I also use the intercom, and it works great here. Are you sure you're waiting for an event to occur? Most states are written after they happen for the first time, so it's normal for the events folder to be empty right after you install the adapter. Once the first 'ding' event occurs, the folder should populate. If it doesn’t, try logging into your Ring account at ring.com. Remove your Raspberry Pi (or whatever device is running ioBroker) from the list of authenticated devices, log out of Ring, then go back to your ioBroker device and generate a new token following the instructions in the README. |
Which country do you live in? I suspect that Intercom support varies by country. The app on my iPhone works fine: when I ring my doorbell, I instantly get a message on the app, but there's no event on the adapter. Previously, the adapter event worked but stopped around March/April 2024. Another guess is that Ring may no longer prioritize Intercom. For example:
I think Ring either changed the way they publish Intercom events or don't publish them in certain regions due to legal reasons. |
I wanted to use the intercom device which I currently use by direct access to the ring-cli-api where I cannot get the Ding event through this adapter. I stopped my script, generated a new token and started the ring-adapter.
The adapter went green, I could see the intercom device under the adapter but I do not saw any events.
I also do not saw the chime device which I can use by my script
The text was updated successfully, but these errors were encountered: