-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
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
Tami4 integration - configuration error #121675
Comments
Hey there @Guy293, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) tami4 documentation |
Hey @tomers, I've sent you an email. |
In: Guy293/Tami4EdgeAPI#10 they reported that changing the app's language fixed it, It still works for me in both English and Hebrew. |
Maybe the problem is related to the number of open profiles in Tami4? I have 4 profiles with 4 phones registered. |
I have a few profiles registered as well, I don't think that's it. |
I think it's something related to the previous integration. |
I can confirm that @Yehazkel 's soultion is working for me. |
@Guy293 |
I haven't implement it in the the intergration yet, shouldn't be too hard I just don't have the time. |
The problem
I tried to configure the Tami4 integration, but failed after the SMS verification stage:
@Guy293, I would like to help you with debugging this issue. Please feel free to contact me personally (my details should be in my Github profile).
What version of Home Assistant Core has the issue?
core-2024.7.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Tami4
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tami4
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
and:
and:
Additional information
Note that
Tami4EdgeAPI==3.0
library works as expected:The text was updated successfully, but these errors were encountered: