Alexa or Google assistant: sorry, emby home isn't responding right now

[JFJFJF 1]

I used to run Emby on a local server but that made it hard to reach from mobile apps and impossible to connect to Google Assistant or Alexa.  So I recently migrated everything to a Digital Ocean droplet, got myself a Lets Encrypt cert and set that up. So now I am able to access my Emby library via https://emby.<mydomain>.com.  This works great for the Emby mobile apps but I can't get Alexa or Google Assistant to work.  I have paid for an Emby Premiere subscription.

I created a user account on my server and associated my Emby Premiere email to that. I got an email to "Confirm Emby Account Link" and clicked it and successfully added my server to my Emby Connect. Then I am able to link the accounts via Alexa or Google Assistant, each of which takes me to an emby.media page where I enter my Emby Connect username and password and then I select my server name from the dropdown.  Both systems say my account is successfully linked, but when I try to actually use them via the digital assistant, it tells me there's an error connecting.

What am I missing?

[Abobader 3464]

Hello JFJFJF,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[JFJFJF 1]

I was able to get Alexa partially working.  Alexa discovered that if I ask "MB Home" to play a specific song, Alexa says "I'm having trouble yadda yadda yadda"  but if I ask it to play "songs by <artist>", it will actually work!

However Emby on Google Assistant is still FUBAR.

[visproduction 315]

There are software security limitations per domain.  Usually, any problem goes away if your domain has SSL status.  If not, some browsers just stop audio control completely.  I think this also happens with various Google audio apps.  If you are not on a SSL domain, try looking for the audio security exception controls for Alexa.  If you are using a browser and you are connecting to either an IP address or a domain without SSL, the chrome exception control is here: chrome://flags/#unsafely-treat-insecure-origin-as-secure

If you make the exception to your domain or IP address, audio should start working when you restart your browser.

Hope that helps.

[Luke 42079]

@JFJFJF regarding google home, can you please join in and try this out?

Stay tuned for a similar one for Alexa. Thanks !

[JFJFJF 1]

I messaged Harry to see if I can join the Alpha.  I'll report back once I get access and can test it.