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

phoneBook not working ?! #16

Closed
pitleh opened this issue Feb 9, 2019 · 5 comments
Closed

phoneBook not working ?! #16

pitleh opened this issue Feb 9, 2019 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@pitleh
Copy link

pitleh commented Feb 9, 2019

Hi SeydX,

It seems that the phonebook data is not stored or not being used.
What is it I am doing wrong?
Please help.

I have correctly activated the "phoneBook": true,
Also the CallMonitor is activated combinded with Telegram, which is working fine.

Incoming call! 012345678 ( No name )
Incoming call - 012345678 ( No name ) - was disconnected!

Thank you,
Pit

@seydx
Copy link
Owner

seydx commented Feb 12, 2019

It depends on how the data (phone number) is stored and how the phone number is showing on the display.

I.e if a phone number is stored with (+49) and the number which is calling shows only (0) it will be not displayed via telegram

For Germany (+49) i added a function to fix this, but not for other countries

@seydx seydx self-assigned this Feb 13, 2019
@seydx seydx added the enhancement New feature or request label Feb 13, 2019
@pitleh
Copy link
Author

pitleh commented Feb 16, 2019

Hi SeydX,

I checked this on my end, in my Fritzbox phonebock the number was stored without the +49.
btw. I live in Germany.
I supect that the phonebock has not been transfered to the Homebridge server.
Since I don't know how to do this.

Any advise would be very welcome.

Thank you,
Pit

@seydx
Copy link
Owner

seydx commented Feb 16, 2019

Hey,

Im currently working on v3 and this should be fixed in v3

I have implemented a new function only to solve this issue ^^

@pitleh
Copy link
Author

pitleh commented Feb 16, 2019

Thank you for the heads up.
Looking forward for the new version.

@seydx
Copy link
Owner

seydx commented Mar 2, 2019

Should be fixed with v3

@seydx seydx closed this as completed Mar 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants