I have the same and push the confirm button anyway. Then you can try it again. I have to try it two to four times sometimes until the picture will be displayed and then it could be that you have to enter the code several times until the capture will be accepted.
In a nutshell: try it several times
The error means your cookie has expired so you’re no longer logged in. That’s why you need to redo the captcha. Focusing on the overall login issues, but once we move to config_flow you should be able to relogin without restarting.
thanks.
how about the captcha? I dont get that in my notifications ?
ok, thanks
No automations working anymore since 2.1
The workaround advertised does not stop the messages being added to the frontend event viewer.
Just figuring I’d try asking here because I’m sure a few people use Alexa Guard… I was trying to using Alexa Guard as part of a DIY alarm system… (the spinning white light indicating the system is armed) … but what I noticed is that with Away lighting enabled (Which is nice when we are actually away) Alexa ends up turning most of (nearly all) lights listed on shortly after enabling Guard and just leaves them on all night. Sometimes a random light will go off but 3 times now it has just left all of my living room lights and kitchen lights on all night. My assumption was that since it asks for zip code it would know what time zone and not have every light in the house on at 3:00 am…
Has anyone else noticed the timing for Away Lighting seems to be a little off? The description says: “Alexa uses machine learning to determine the right lighting activity for your home based on lighting usage across customers.” I was just wondering if it was just me or other people have noticed this.
Hi, I have problem’s with captcha. And the problems is related to url in configuration. If I use as url amazon.it, I do not have captcha but receive an error ‘Failed call to service configurator/configure. get’. But if I use as url amazon.com, I get captcha and I’m able to log in, but all my Alexa device are unavailable. There is some problems with Italian site ?
Yeah, I have not been too impressed with Alexa Guard lighting. I have seen the light mostly stays on throughout the night.
2.1.2* is out.
Bug fixes mainly. Fallback is 1.4.1 to login issues you don’t want to debug. For those using amazon.it there may be a bug if you have 2FA and end up in a configurator loop. It’s hard for me to debug since Amazon tries to redirect my account to the US domain if there are issues so I may only be seeing it because of the attempt to redirect me.
For those of you using include_devices please note all your switches/Alexa Guard devices will not appear until you include them.
For those on hassio, you may have to restart 2-3 times before HA will load the dependencies.
Please note, we’ve swapped repositories to custom-components. If you haven’t done so, please reinstall from HACS so it tracks from the new repo.
*Yes, we skipped 2.1.1, there was a bug if you had an older cookie. We left that in beta only.
Fix
- update alexapy to 1.1.1 (33f3247) (fixes #346; fixes #344)
- add enable retry for media_player and alarm_control_panel setup (2f2f7a0)
- add retry_async wrapper to automatically retry after failures (2ce12f4)
- clean discovery_info of unneeded values prior to passing (b5e1894) (fixes #336)
As always, please use the the Wiki and FAQ if you need instructions or have questions. Also, please help in documenting features in the wiki since this thread is basically unsearchable now. We also use GitHub for bug reports/feature requests .
2.1.2 may have fixed it but if not, you may have to disable 2FA.
Update.
Fixed bug (Amazon’s webpage changed). Update.
Alan if you have a vpn with an Italian server, you can debug the .it situation.
The announce feature in the Alexa apps works fantastic with multiple speakers (it’s cool you can chose either typed or spken text), can we replicate this exact functionality via the component?
I have tried using a multi room group (created in the app) and using the ‘announce’ type, but it doesn’t seem to replicate the native function and audio sync can be sketchy (it’s flawless via the app!).
Just an FYI…
Today updated Home-Assistant to 0.98.4.
A couple of days ago updated Alexa from master branch (then days old).
The Alexa app continued to work fine. (HA 0.98.2?)
Todays HA update appears to have broken my Alexa devices.
That said had a back up Alexa Ap configuration and using that one works.
Just noticed looking at the master branch it is a day or so old …V2.1.2
Should I give the newer Alexa app (V2.1.2) a try?
I don’t think it’s a geolocation issue. I think it’s because my accounts are marked as US accounts.
File an issue and get us some logs; last I checked our command is the same as the native app but who knows if that’s still true. We based it off the Routine you can program in the Alexa app.
You should always take the latest patch version. I’d suggest using HACS or using releases instead of taking from master. We make no guarantee that master is consistent with a tested release.
I am using hassio 098.4 and just installed 2.1.2. I get the configure screen where it asks for the captcha but I can’t get past it. I’m rebuilding my HA system after an SD card failure and I remember from my last 0.84 system that after submitting a bad captcha, the next time it came up had the captcha right there. What is different now?
How do I enter the captcha if I can’t see it?
Also, I went looking for 1.4.1 but can’t seem to find it on the github site. Can someone point me to it if I need to get it?
Thanks.
OK Got it!
I had to delete the pickle file in the config directory and reboot.
I also found releases at:
Anyone had any luck with the Amazon Auto? Overall I’ve been able to use it as an echo device to control HA devices, etc. It shows up as a media Device, but it does not seem to be available as a media device. My main goal was to hopefully be able to get audio alerts, etc
It shows as this in HA
is_volume_muted: false
media_content_type: standby
media_position_updated_at: 2019-09-10T22:52:25.803756+00:00
source: Local Speaker
source_list: Local Speaker
available: true
last_called: false
friendly_name: car_echo
supported_features: 56253
For some reason, I can’t update my HA past 96.5 without getting the following error. I have updated Alexa media player to 2.1.2 through HACS but keep getting the error. I saw that this was fixed back in 1.4.1 in early August. Any ideas?
Unable to prepare setup for platform alexa_media.media_player: Platform not found (cannot import name ‘MEDIA_PLAYER_SCHEMA’ from ‘homeassistant.components.media_player’ (/Users/xxx/homeassistant/homeassistant/lib/python3.7/site-packages/homeassistant/components/media_player/init.py)).
IS the Alexa Guard working properly via this component? I’m trying to arm it via automation like this
automation:
- alias: "Arm"
initial_state: 'on'
trigger:
platform: state
entity_id: group.family
to: 'off'
action:
- service: alarm_control_panel.alarm_arm_away
entity_id: media_player.my_echo
And it seems like the automation is calling the service OK but nothing happens in Alexa. Trying from “Services” to call also but nothing just happens. In Alexa App the Guard works fine.
Any luck doing what you want in the app or webapp? If it’s the webapp, it’s fairly easy to debug the network calls so we can imitate it.
You are on an old version still. Make sure you delete any old version and then try reinstalling from HACS. On startup it should identify the version you’re running.
2019-09-10 23:54:55 INFO (MainThread) [custom_components.alexa_media]
-------------------------------------------------------------------
alexa_media
Version: 2.1.2
This is a custom component
If you have any issues with this you need to open an issue here:
https://github.com/custom-components/alexa_media_player/issues
-------------------------------------------------------------------
2019-09-10 23:54:55 INFO (MainThread) [custom_components.alexa_media] Loaded alexapy==1.0.2
Yes. However, you need to use the proper alarm_control_panel entity though if you want to use alarm_control_panel commands. You can’t target a media_player. It should look like alarm_control_panel.alexa_guard_XXXXX. If it’s not being discovered as an entity, then we may need logging from HA startup to help you. Check the Wiki for info.
1 Like