-
Notifications
You must be signed in to change notification settings - Fork 303
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
multiple last_called devices with one account #97
Comments
I want to add that it still gets the right values when I restart home assistant |
Can you please try the latest version in #100 and provide debugging logs for
I only need the logs covering these three steps. |
Ok so I added this to my configuration.yaml
This is what I got:
|
You may need to turn off the other components if they're showing up. logger:
default: info
logs:
custom_components.alexa_media: debug When you use the service you should get something like this:
You'll want to find the first time you see |
I updated my post above with the log. |
Thanks. Echo Dot 3 is the only one reporting that it's the last called one. Is last_called true for the other dots? |
No currently not, because I restartet when I added logger. Should I trigger another alexa to get more than one true and post again? |
Yes, as soon as you see the problem, please do the logging steps. |
Ok so now I have two last_called true again, logs:
It also takes some seconds until the second one gets true. After some minutes the wrong one got false again. The logs seem to only report one alexa last called. So is this an ha issue? And here you can see that both are true and just to be sure I show you the binarysensor config that reads that state also:
|
I think I might have found the cause. Looks like we have to separately force HA to update. I'm close to releasing a new release, so I didn't push it to the one you're testing yet. I'll let you know when we release it so you can confirm. |
Ok, I'd like to mention that I tried this in a script in the meantime. But that also did not help
|
That's not the correct service if you're calling the last_called service. - service: alexa_media.update_last_called If you're referring to manually triggering the HA update, you'd have to do it to the media_players which are the source of you're binary_sensor (guessing at syntax for multiple entities). - service: homeassistant.update_entity
data:
entity_id: media_player.echo_dot_1, media_player.echo_dot_2, media_player.echo_dot_3 |
I tried this additionally to the alexa_media.update_last_called service. But yes you are right, if I do this I have to update the meiaplayers. |
New version is out. It should resolve all the issues you referred to. After I confirm it's working in my production I'll make a post on the thread. |
Ok, I'd like to confirm that it works now, the last_called update instantly. Thanks! I have another question about using delays, but I will ask that in the thread, because it will interessant more people. Great work! |
Coming from here
I only have one account, but as noticed in another issue I have echo buttons in my network.
For me it looked like they stay true (last_called) until I restart home assistant.
I don't get an error.
To make it better readable I also extracted the last_called attributes to binary sensor and added them to my UI. This way I was better able to see if when the one gets TRUE if the other ons gets FALSE. But that did not happen. Both stayed TRUE.
In the thread above one other user seems to have the same issue, so I might not be the only one.
See: https://community.home-assistant.io/t/echo-devices-alexa-as-media-player-testers-needed/58639/2000?u=h4nc
The text was updated successfully, but these errors were encountered: