Have the v.3.7.101 been removed again? because I can only install the v3.5.101
I just purchased echo dot 4âth gen and the 4âth gen was added in the v3.7.101, so it would be nice to have that version
Have a great day
Have the v.3.7.101 been removed again? because I can only install the v3.5.101
I just purchased echo dot 4âth gen and the 4âth gen was added in the v3.7.101, so it would be nice to have that version
Have a great day
Full disclosure - the âreconnectâ button is as it sounds - it assumes that there was some sort of disconnection it couldnât recover from but your credentials are still valid.
If it doesnât work, then itâs a â real disconnectâ where Amazon has said your now logged out - please log back in.
I was just testing with the reconnect - Phil do you mean to say that the reconnect button fails ⊠but then simply restarting homey or the app and your automatically reconnected?
Same Problem here
App show me: connected
Flows doesnât work
After only restart App, everything is ok and flows runs fine
Yep, that fixed it for me too, just restart app, then connect again. I have the idea it takes longer then before before it disconnects (actually it never disconnected, but stopped working), since the last update
Yes. Only clicking âreconnectâ didnât fixed the no TTS. But When i deacticated the app and Then just reactivated it the TTS began to work.
Strange. Now the App runs after this behaviour for 2 days without a Problem.
I have to investigate further. But a massive step forward to the version before!
So you are on the Right way. I left you know if i find out More. I promise
Just see @DaWa74 and @Chris_nl comments abbiegen. Same here.
Today i did get disconnected again, not sure if it is the same âissueâ since I also had to approve the login attempt through a text-message, so maybe Amazon changed something and that was the reason for the disconnect. Will keep testing, but still feel it takes longer before it disconnects
UPDATE: 24 hours online and still working, 0 disconnects
I have thankfully not been disconnected for several days now, I think it only happened once with this new test app, so everything seems to work fine on my end. Iâm on us server here. Thank you so much Jamie!!
TTS worked fine a few days. Then I recognized that it stops working. The app/homey was still shown as connected so I couldnât reconnect via the new button. A restart of the app didnât help, but deactivating + reactivating the app solved the problem for me too. Iâm still connected since days.
Thankâs a lot @Jamie for the update of the app and @PhilS for the tip!!
TTS stopped again after 2 days. But now we know how to get it back:
App deactivating + reactivating
This works manually but also with a flow. So I decide to reactivate the app every time I want Alexa something to say:
First I tried to implement the Alexa speak card in the then part of the first flow. But it didnât work because if you deactivate an app which card you use inside the same deactivation flow the flowcard becomes invalid at runtime and will not continue after reactivation of the app. But it works if you start another flow with a delay. In the delay time the second flow will become valid again.
PS: Sorry, cards are in German. But I hope itâs clear how it works.
Same for me, disconnected just short of 48 hours, itâs way better then the disconnects before
As i mentioned
Great if this workaround works
hello everyone who ever managed to call homey alexa to
to perform a flow or an action with the voice of homey alexa
Groet Jonathan
Hi , I read the FAQ but I canât get the routines to show up. I have a lot of routines and mosto of them have names, I even tried creating a new one for testing but it wonât appear in the flow card. I tried restarting the app and still no success. Any help?
Iâm in EU and I have a lot of Alexa devices ( fire TV cube, show2nd gen, show5, echo plus dot flex and input)and if need be i can help with testing.
No matter what I do, the connected devices become unresponsive after a while (usually few hours). Regularly.
I even deactivated 2fa temporarily and it didnât change anything.
In itâs current state this app is sadly not usable.
PS: Deactivating and reactivating the app does not do anything for me. The devices remain unavailable and I need to reconnect the app.
Just a hint and maybe you tried it before:
You have to type the first characters of your routine names in the selection box of the trigger card of the flow. Only then the routine names appear as a list.
Which version are you using at the moment?
Meanwhile it seems to work stable for 3 days.
I run the proposed test version 3.7.101.
After nearly three weeks now I was disconnected today (red triangle) .
The Reconnect button worked and all Alexa devices were connected again (no triangle).
But didnât respond.
App deactivating + reactivating worked
(Didnât try App restart)
Question @Jamie:
Is it possible to trigger a disconnection and force a reconnection via code/homeyscript?
Yeah I tried that still no luck to this day
@Jamie
Bonjour, merci pour le développement de cette application.
Jâai un petit problĂšme depuis la rĂ©cente mise Ă jour. Je nâarrive plus Ă accĂ©der aux routines faites sur amazon alexa.
Jâai changĂ© de serveur et toujours le mĂȘme problĂšme.
Jâai tout rĂ©installer et toujours rien.
Jâai aussi nommĂ© mes routines mais toujours rien.
Avez vous une solution sâils vous plaĂźt ?
Quelquâun a t il le mĂȘme problĂšme que moi ?
Merci dâavance