@Jonathan_Draper I’m still getting familiar with how the store review system works. But I think you might already have version 1.0.2 since you had installed the test version before, and I think reviews only affect the store page. In case you do you can go to the settings disconnect, then select “Enable diagnostic logging” and connect again.
Be aware that this will log all your API requests and responses. I tried my best to filter out any personal information like username, address, authentication tokens etc from getting logged (you can look here at the repo). But only enable it if you are comfortable with the data that might get logged. In case you enable it I would appreciate it if you could then try to change the volume. Let me know afterwards and then you can disable the logging again if you want.
Thanks - yes I did have 1.0.2. Disconnected, enabled logging and reconnected then tried changing the volume 3 times. Twice the flow card finished (but no effect on the Echo) and once the flow card failed. Then have reconnected without logging again. BTW when I reconnected without logging the first time, the authorisation in app settings worked but then flow cards generated 401 not authorised errors until I restarted the app, then re-authorised. Now working again.
I just pushed version 1.0.3 which now uses a alternative method for setting the volume. I hope this should now work with your device too. Let me know when you find the time to test it.
Thank you @staeff - just had a chance to test with 1.0.3 and the volume setting now works like a charm - both absolute and relative changes.
I’ve switched over to this app for day to day control of radio streaming on the various echo devices around the house now so it will get a good test over the coming days and I will feed back anything untoward.
Thanks again for your work on this. A beer is on its way!
I have a bunch of Echoes and was interested in the option to whisper a command response - something the Alexa routines seem incapable of doing.
I added version 1.0.3 of the app and connected to Amazon successfully. When I tried to add a device it asked me for device type (just one “Echo” shown) but then it crashed with “Cannot read properties of undefined (reading ‘length’)”.
Restarting the app didn’t help.
I disconnected from Amazon and reconnected, this time selecting the logging option, and got the same error but I’m hoping that gives you a useful diagnostic - or do I have to send you something?
I just pushed version 1.0.4 which should hopefully address this issue and should bring overall stability improvements. Let me know if you are still having issues.
@Jonathan_Draper also FYI if you can check if the new version still works for you
Yes all still working here. BTW one little thing I’ve noticed (this was the same with the other Amazon homey app so not sure if it’s fixable) is that the “is playing” status of the echo device in Homey works fine when playing music but not when playing radio via an app on echo (in my case the BBC sounds app)
Sadly the BBC and TuneIn don’t get along so the BBC sounds app is the only option. Although I tried streaming another station via TuneIn and also no playing status change. It seems a bit patchy with streaming music also. I’ll see if I can spot a pattern.
Thanks for the very fast response. Yes, that’s fixed my issue I can now see all my physical echo devices. Nice work!
When I tried the other Homey app for Alexas I suffered occasional disconnects so switched to using Voice Monkey as a work-around. I’ve now started using your app instead.
Unfortunately, I couldn’t address the main issue I have with Alexa. I use a Flic button to run a routine to tell Alexa to "Play B B C radio four extra’ on our bedroom echo. I use another button to tell it to stop playing after an hour by which time I’m asleep. I use a low volume so I don’t disturb my wife. However, there’s no way to control the volume of the announcements in response to the commands. If I whisper a voice command, Alexa whispers the notification back - but I can’t force this through the routine. I tried using the Say card to whisper and that works fine. But subsequent notifications come back loud again.
Googling around there are loads of people with this issue. Some say changing the alarm volume changes notification volume - but it doesn’t. In any case, I want my alarm to wake me up!
If you can see a solution in the API you are using, that would be great. But I won’t be surprised to learn there isn’t one.
I will try to see if there is a way to influence if/at what volume alexa responds back to text commands. No promises, but if it is possible I think it’s reasonable to add this.
Can you maybe turn on diagnostic logging as described here and let me know the rough timestamp (UTC) when you tried to add your devices afterwards? Maybe the Echo Shows use a different device family from the Echo speakers.
Are you using the amazon.se page? just noticed that for some locations there is no server alias (e.g. alexa.amazon.fr exists but alexa.amazon.se and alexa.amazon.pl don’t), so I might need to add some mapping or let people chose the server on their own.
EDIT: Actually I don’t see any logs from you at all. The amazon.se issues were from the morning. Did you disconnect in the app settings enable the diagnostic logs and then connect again?
From googling around it seems like there is also “ROOK” as a potential value for Echo devices. As for FireTVs at least for now I don’t want to include support for them, as I want to keep the app focused on Echo devices (and also because I don’t have any around to test )
Will create a new version with the updated filters in the next few minues, let me know once you see 1.0.5 and if everything works
Just though of something. As a workaround, you could create a routine which does what you want and then run the routine via the Homey app. This way you can control if alexa even says something at all.
'Fraid not. There’s no way (I know of) for a routine to either force whispered responses, or control the volume of responses. A ton of people looking for a solution on the internet. My last hope is that there might be something in the API. Unsurprised if not.
)
