Alexa TTS troubleshooting

[CatmanV2]

Evening (at least here)
Alexa TTS has suddenly stopped here (mid afternoon)
Normally I'd replace the cookie.
When I went to the domain, I was forced to change my password. Did that and exported the cookie. But still no voice.
I can't see anything at all in the logs:

2021-02-12 18:05:02.869   luup_log:0: ALTUI: runLua(local GardenTemp = math.floor(0.5+luup.variable_get("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", 20415))
luup.call_action("urn:dlna-org:serviceId:DLNAMediaController1", "Say", {Text="The temperature outside is" ..GardenTemp.. "degrees.",Volume=40,GroupZones="Everywhere"}, 22))
2021-02-12 18:05:02.870   luup.call_action:: 22.urn:dlna-org:serviceId:DLNAMediaController1.Say 
2021-02-12 18:05:02.870   luup_log:22: VeraAlexa: addToQueue: added to queue for 22
2021-02-12 18:05:04.035   luup_log:0: ALTUI: Evaluation of lua code returned: nil

But I'm sure I need to look somewhere else and damned if I can recall where. Someone give me a pointer?

TIA

C

[therealdb]

Give the oath tool a try. It’s very easy to setup and once done no password are needed.

[CatmanV2]

@therealdb said in Alexa TTS troubleshooting:

Give the oath tool a try. It’s very easy to setup and once done no password are needed.

Thanks. Having a nightmare troubleshooting at the moment. Brain seems everywhere :(. First thing I remembered was the cookie this morning! So back up and running.

Where's the oath tool, chap?

Cheers

C

[therealdb]

From the original read me on https://github.com/thorsten-gehrig/alexa-remote-control

In order to use MFA, one needs to obtain the MFA_SECRET from Amazon account:

• You should have MFA using an App already working before proceeding
• Add a new app
• When presented with the QR-code select "can't scan code"
• You will be presented with the MFA shared secret, something like 1234 5678 9ABC DEFG HIJK LMNO PQRS TUVW XYZ0 1234 5678 9ABC DEFG
• Now you have to generate a valid response code via oathtool -b --totp "<MFA shared secret from above>" and enter that in the web form

Going from here the MFA shared secret becomes the MFA_SECRET for the alexa_remote_control script Treat that MFA_SCECRET just like your password - DO NOT share it anywhere!!!
It is assumed that MFA secured accounts are less likely to get a captcha response during login - that's why MFA might yield better results if the plain username/password didn't work for you.

[CatmanV2]

Right gotcha!

May well give it a try, thanks, as ever

C

[LibraSun]

I'm back to testing Vera Alexa (now rev. 0.97) and thus far no improvement. 99% silence despite being correctly configured.
Here's a data point to mull over:

luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command='-e weather -d "Living Room"'}, 366)

yields this LatestResponse on Vera:

sending cmd:weather to dev:Living Room type:A15ERDAKK5HQQG serial:eb48978706f5459f890ef0ec5aa9fce9 customerid:A3SL3Z0HELH3YG

and this in Vera's LuaUPnP Log (among other lines):

Device_Variable::m_szValue_set device: 366 service: urn:bochicchio-com:serviceId:VeraAlexa1 variable: LatestResponse was: ERROR: unknown option weather /storage/alexa/alexa_remote_control.sh [-d <device>|ALL] .......