Remote control fails if Emby Theater has been idle

[blue-wizard 2]

Here's the problem I'm having:

 

I have two clients connected to my server.

Client 1 is running Emby Theater. I use this client to play media on my TV.

Client 2 is running the Emby Web App. I use this client as a remote control.

 

Normally, I can see the Emby Theater client under the list of cast devices from the Web App. However, if the server restarts, after both clients have re-connected, the Emby Theater client no longer appears under the list of cast devices. Even if I restart the Web App client, it doesn't display. The only way to get it back is to close Emby Theater and open it again.

 

This error is reproducible. (I've reproduced it just now using the above steps).

Edited January 20, 2018 by blue-wizard

[Luke 38861]

Try going back into it the theater app and navigating. That should bring it back.

[blue-wizard 2]

Tried that. It didn't solve the problem.

 

And even if it did, it wouldn't be a good solution because I want to navigate using the remote and I can't if I can't cast to it...

[blue-wizard 2]

If my Emby Theater (ET) is idle for a period of time, remote control actions do nothing.

 

Here's a scenario that I encounter frequently:

1. I play some media on ET at night before going to sleep.
2. I leave ET running over night.
3. I wake up in the morning and, using a remote control app, try to play some music on ET. Nothing happens.
4. To get it to work, I have to manually interact with the ET machine (move the mouse, tap a key on the keyboard, etc...)

This is not the only scenario or time-scale on which this happens. If ET is idle for a period of time (e.g., 30 minutes or so), this can also happen.

 

The ET machine's power settings are such that it doesn't take any actions when idle (like going to sleep). ET is in the foreground when this happens. I can still connect to ET using my Web App via the cast button. It's just that the remote control functions have no effect on ET.

[blue-wizard 2]

Quick follow-up to note that this has just occurred:

1. I played an album on ET using a remote app
2. The album finished and ET went idle for about 10 minutes
3. Remote app got disconnected from ET
4. I reconnected to ET, tried to play another album and nothing happened
5. I moved the mouse on the ET machine, and suddenly it starts playing

Here are the relevant Power Options configured on the ET machine:

 

 

It's set to never sleep, never turn off the HDD, and wireless adapter power saving is disabled.

[Luke 38861]

@@blue-wizard, i've merged two of your topics that are discussing essentially the same thing. thanks !

[blue-wizard 2]

They are similar, and I don't mind the merger, but this might be a key difference:

1. In one case I cannot see my ET device on the list of devices on the network.
2. In the other case I can see and select my ET device, but when I issue commands nothing happens.

Thanks.

[Guest asrequested]

Check the power options for your NIC. It may be turning off, to save power.

[blue-wizard 2]

Thanks, but that doesn't appear to be the issue either.

 

The NIC is configured not to turn off for power savings.

 

 

[Guest asrequested]

Maybe it's just losing focus. I've been wondering if we need an option to always keep Theater on top. That might help with that.

Edited January 25, 2018 by Doofus

[blue-wizard 2]

The NIC suggestion was a good one. I was fiddling with more settings, and it seems the issue is gone now after I changed these settings:

 

Wake On Magic Packet: Enabled

Wake On Pattern Match: Enabled

 

[Luke 38861]

Well done.