Does anyone have an idea or experience with using the fire cube in automations. I would e.g. like to be woken up by the cube with a live stream of a TV show or to pause the film playback when I fell asleep…
Good morning , i updated to HA latest version and raspberry swap 3 to 4 … and the only problem is Alexa was asking me the configuration again , but when the popup appears… has not written in it.
Any help to understand how to fix it ?
Thanks
@MorningZ Were you able to get this to work? I have uninstalled, reinstalled, restarted, and even clicked my heels together many times. Nothing works! I keep getting stuck at this stupid screen.
Nope, the integration is still sitting there whining. Authentication doesn’t work, no way to uninstall it.
I’ve since moved my Alexa stuff back into Node-RED and the Alexa2 palette
This is a great integration, but I could only get it to work in nodered using “announce”
{"message":"Back Door Open","data":{"type":"announce"},"target":["media_player.office_dot"]}
Is there a difference between announce vs tts?
Does Alexa2 allow us to use echo as media player? Thanks.
I don’t know if this still works/is updated but this allows you to send “voice” commands without actually speaking I believe…
2 Likes
I am also having the blank authentication page. I have tried different browsers, and machines, with no change.
“Announce” has a chime before the message is ‘spoken’, “tts” does not include the chime.
Thanks and yes - that’s what I thought. Any thoughts on why “tts” doesn’t work, but announce does?
For me ‘tts’ works, an example below
[
{
"id": "d949a7d0.919c38",
"type": "api-call-service",
"z": "888b3510.d1bbd8",
"name": "Alexa - Porch lights disabled",
"server": "8a3231e1.3f0e1",
"version": 1,
"service_domain": "notify",
"service": "alexa_media_juan_carlos",
"entityId": "",
"data": "{\"message\":\"Porch lights have been turned off\",\"data\":{\"type\":\"tts\"}}",
"dataType": "json",
"mergecontext": "",
"output_location": "payload",
"output_location_type": "msg",
"mustacheAltTags": false,
"x": 1381.111083984375,
"y": 232.2222137451172,
"wires": [
[]
]
},
{
"id": "873f242f.5a5288",
"type": "inject",
"z": "888b3510.d1bbd8",
"name": "",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "",
"payloadType": "date",
"x": 1104.4444444444443,
"y": 231.11111111111111,
"wires": [
[
"d949a7d0.919c38"
]
]
},
{
"id": "8a3231e1.3f0e1",
"type": "server",
"z": "",
"name": "Hassio",
"legacy": false,
"rejectUnauthorizedCerts": true,
"ha_boolean": "y|yes|true|on|home|open",
"connectionDelay": false
}
]
Never mind - it just started working. Odd, but great! Thank you!
I am about as amateur a HA user as it gets, so please forgive me for asking what is probably a silly question. An automation that we have come to rely on stopped working today, and I am scrambling to try to figure out how to fix it.
I use an automation to grab caller ID from an Obihai, parse a contacts list and grab the name, then push that name out of 5 Alexa devices. It has worked really well for the past month, but this morning, it started saying “Sorry, I am having trouble accessing your Simon says skill right now.”
From Developer Tools:
Service: notify.alexa_media_dot_bedroom
Service Data:
message: >-
Incoming call from {{ states("sensor.clid_name") }} . Incoming call from {{
states("sensor.clid_name") }} . Incoming call from {{
states("sensor.clid_name") }} .
data:
type: tts
The sensor does have correct information in it. Narrowing it down to:
message: >-
'test {{ states("sensor.clid_name") }}'
data:
type: tts
also returns the same error, but:
message: >-
test
data:
type: tts
does work, so the alexa media player itself IS working, it just isn’t handling my template anymore, for some reason. I have tinkered with a good bit since yesterday, but do not know how to even begin to figure out where anything could have broke.
1 Like
Ah, I had forgotten that node-red-contrib-alexa-remote2 does TTS to the echo. I use it for parsing voice commands.
In my setup, TTS is pretty critical to how the smarthome works.
So, I may have to use that palette as a backup for AMP.
Anyone experience inconsistency with this addon? Works sometimes and sometimes it does not?
Asking this again since my question 20d ago didn’t garner any responses:
With 2FA enabled, I am now being asked to reauthorize every 6-7 days.
- Is anyone else reauthorizing with this frequency?
- Can anything be done to extend the time or is this the new “experience”?
I have another question on the same topic, getting below message while authenticating and have not enabled two factor authentication yet:
Please enter your information. Cookie import may be easiest!
WARNING: Amazon incorrectly reports ‘Enter a valid email or mobile number’ when 2FA Code is required.
There was a problem
Enter a valid e-mail address or mobile number
Is it necessary to enable, two factor authentication? I have 3 installations of HA at my home and one or the other instance keep asking for re-authentication, is there any better way to keep is working?
It is now a requirement of the component, as mentioned here:
I personally do not have to authorize that often, usually a few weeks… sometimes goes longer…
Before and after I enabled 2FA, I have to reauthorize about every 3 or so weeks.