-
Notifications
You must be signed in to change notification settings - Fork 302
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
Platform alexa_media does not generate unique Ids #260
Comments
|
Try out 1.4.0 and see if this error persists please. |
Hi, (Each HA startup puts about 200 lines into the log, but I think I read you are still working other issues with .97.) If there's anything I can add to this, please advise. |
I'll see if additional checks are needed for this. |
I was wondering if there was something I could provide you to help with this. Am I the only one still getting all these?
Truth be told, I'm not sure if posting the log here discloses acct-specific info.
|
@genem2 Are you still on 1.4.x? We actually did some changes when we went to 2.x that should stop this from happening. The logs you posted don't have anything private but we probably need to understand what happened before this snippet Was there any other errors like a reconnect or disconnect? (edit for grammar). |
No, no. I check on this after each HACS update.
No, just the expected:
One of these for each of my two accounts. |
Oh wait. Do the two accounts share echo devices? We may not have a check for that. |
They do not.
…On Sun, Sep 1, 2019, 1:57 PM Alan Tse ***@***.***> wrote:
Oh wait. Do the two accounts share echo devices? We may not have a check
for that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#260>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALAW6XJOQRDPBVYCD72ADSLQHQUDRANCNFSM4IIRLURQ>
.
|
@genem2 can you try the fix I just staged? You'll need to replace 4 files. No worries if you can't, I'll just stage it in the next release so hopefully I'll finally resolve this old bug. |
So, in .homeassistant\custom_components\alexa_media
And added:
Also removed the earlier pycache (not sure if that would trip us up.) |
Your debug logging setting is wrong. Please see here. Specifically,
Can you please fix the line and reattach? |
So sorry. Corrected; new log attached. |
@genem2 another version for you to try. I think the issue is coming from the fact you have multiple accounts. Some wires are getting crossed so I need to add additional checks. |
So, updated: __init__.py Here are some logs: |
fix: add catch for HomeAssistantError when adding entities
feat: allow exclusions for alarm_control_panel and switches
Awesome. Many thanks, @alandtse and @niemyjski for spending time on this work. Resolved! |
System details
const.py
or HA startup): latest via hacsThe text was updated successfully, but these errors were encountered: