Emby Home / Google Home

[FrogMaster 27]

On 14/12/2021 at 10:18, cayars said:

I would get rid of NPM and uninstall docker.  Make sure Emby is running on the host itself and not in docker.  The Pi barely has enough muscle to run Emby Server and you don't want it doing other things (at least until you have a working baseline).

I'm really not sure why you would need a reverse proxy on the Pi anyway as hopefully Emby is the only thing running there so you don't have a reason to reroute ports (main reason to use NPM). It's likely you didn't set up NPM for web socket or the stack needs tuning for something like Google Home or Alexa.  But since you don't need this just remove it and docker to get those resources back as well as greatly simplify the setup so Home can talk directly to Emby with no middle man involved.

 

NPM on the Pi was probably due to my suggestions regarding the simplicity of configuring SSL. I'd be inclined to agree that WebSocket support most likely needs to be enabled for the proxy host. With NPM that is as simple as turning it on for the configured host in the settings.  

@timter51If you're only running NPM for SSL. You can export the SSL Certs that NPM has already generated then install them directly to your Emby Server. Though renewing the certificates will need to be done with an alternative method to NPM if it is uninstalled. However, I would try to simply enable the WebSocket support first and see if that resolves your problems.

This is what my personal configuration looks like within NPM:
 

[timter51 6]

@FrogMaster @cayars thank you both for your help, it's much appreciated. I think I'm at the giving up stage at this point, and wait it out for (hopefully) more solid support for Google Home. However if you have any thoughts on anything else I can try.... here is where I currently am:

1. Stripped everything back to just DietPi + Emby, using the certificate that NPM generated

2. Router - 443 open and fowarding to internal Pi Emby server IP / UPnP has mapped external 443 to Emby server 8920

3. Emby - Local ports set as 8096 and 8920 / External ports set as 8096 and 443 / External address as my duckdns address / allow external connections on / secure required for all remote / certificate loaded

I can access my server over https absolutely fine from outside of my network (using my https://mydomain.duckdns.org address), tested on numerous devices. Browsers report it's using the NPM / Let's Encrypt generated cert. Emby Connect has the server loaded and can access it fine when I use it outside my network. But still Google Home is having none of it, always the "not responding" message. I've tried everything I can think of!

[Carlo 4561]

Have you tried eliminating the proxy and port forwarding directly to Emby?
I know this isn't the way you want to run things but it's only to test and do some diagnostics to see where things fail. It's much easier to fix a problem when you can find the layer the problem exists in.

You may be able to run a test without changing your existing software setup at all by installing Emby on a 2nd computer (just for testing) with one library and a couple pieces of media. 
Obviously make sure it's working correctly with Emby Connect then try with Google Home.

The more layers you can remove the easier things get to troubleshoot. If this test works that's a strong indication the problem is in the Reverse Proxy config and you know to focus attention on that piece.

You may also want to check your router to see what type of info it can log and filter.  That could be quite handy as well to see if there is communication back and forth and what it looks like.

This is what I would do if it were me.

[Luke 42078]

@timter51?

[FrogMaster 27]

On 20/12/2021 at 06:52, cayars said:

Have you tried eliminating the proxy and port forwarding directly to Emby?
I know this isn't the way you want to run things but it's only to test and do some diagnostics to see where things fail. It's much easier to fix a problem when you can find the layer the problem exists in.

You may be able to run a test without changing your existing software setup at all by installing Emby on a 2nd computer (just for testing) with one library and a couple pieces of media. 
Obviously make sure it's working correctly with Emby Connect then try with Google Home.

The more layers you can remove the easier things get to troubleshoot. If this test works that's a strong indication the problem is in the Reverse Proxy config and you know to focus attention on that piece.

You may also want to check your router to see what type of info it can log and filter.  That could be quite handy as well to see if there is communication back and forth and what it looks like.

This is what I would do if it were me.

Based off his previous post; He's already removed NPM from his setup.  

He's only using an SSL Certificate that had been generated by NPM. Which he exported and installed directly to his server. 
Which, really is no different then using say certbot to generate a SSL certificate. (This is what NPM actually leverages during the registration of the SSL Certificate.) 

At least, that's my understanding of his last reply. 

[FrogMaster 27]

On 20/12/2021 at 05:28, timter51 said:

@FrogMaster @cayars thank you both for your help, it's much appreciated. I think I'm at the giving up stage at this point, and wait it out for (hopefully) more solid support for Google Home. However if you have any thoughts on anything else I can try.... here is where I currently am:

1. Stripped everything back to just DietPi + Emby, using the certificate that NPM generated

2. Router - 443 open and fowarding to internal Pi Emby server IP / UPnP has mapped external 443 to Emby server 8920

3. Emby - Local ports set as 8096 and 8920 / External ports set as 8096 and 443 / External address as my duckdns address / allow external connections on / secure required for all remote / certificate loaded

I can access my server over https absolutely fine from outside of my network (using my https://mydomain.duckdns.org address), tested on numerous devices. Browsers report it's using the NPM / Let's Encrypt generated cert. Emby Connect has the server loaded and can access it fine when I use it outside my network. But still Google Home is having none of it, always the "not responding" message. I've tried everything I can think of!

The only other thing I could possibly suggest is perhaps resetting the Google Home connection to the Emby app. Perhaps it has something cached from previous attempts before it was functioning properly? 

I can tell you how this is done on Android. I imagine it's similar on iPhone but I can't say as I haven't used one in an extended period. 
1) Open the Home application
2) Click Your Profile / Account Picture  > Assistant Settings
3) Click on the Explore option. (It's about half way down, alternatively you can just search for it.)
4) Search for Emby > Click the Emby Icon on the left hand, not the name. (This should bring up the details page.)
5) Scroll to the very bottom > Click Reset (It's kind of hard to see, it's right next to the "Terms of Service" option.)

Then try reconfiguring it then speaking to Emby Home. Perhaps you may find some luck.
Hope this helps!

Edited December 24, 2021 by FrogMaster

[chaank 0]

Hi there. I stumbled upon this thread because I'm just trying to connect Emby Home to Google Home. My question:

Is it possible that Emby Home is only available in the US and/or some other countries but not in Germany (where I am)? When searching for "Emby" in the Explore-section inside the Google Home app there is no result. Or am I missing anything?

Thanks for helping!

Edited February 2, 2022 by chaank

[chaank 0]

In addition to what I wrote before:

When searching for "Emby" on the assistant website from Google, there's a search result in the english version but not in the german version - see images.

[Luke 42078]

On 2/2/2022 at 6:32 AM, chaank said:

In addition to what I wrote before:

When searching for "Emby" on the assistant website from Google, there's a search result in the english version but not in the german version - see images.

Hi, yes we are working on adding additional language support. Thanks for the feedback.

[timter51 6]

On 22/12/2021 at 16:25, Luke said:

@timter51?

Nearly a year later and I feel like I've plucked up the courage to try and get Google Home working with Emby.... before I start, have there been any recent updates that might have helped fix issues?

[Luke 42078]

@FrogMaster @timter51 @chaank

Can you please join in and try our new Google Home support?

Thanks !