Jump to content

Emby Server running = slow scenes in Home Automation controller (Vera)


Recommended Posts

Posted

I have absolutely no clue about Vera, but have you tried running a netstat in a cmd session on the whs box?

Posted

OK I managed to properly uninstall the UPnP Event Proxy plug-in and its gone in the top list now. Still slow scenes in Vera after all that. 

 

If I run NETSTAT on the WHS there is a massive list of port numbers listed.

Posted

OK I managed to properly uninstall the UPnP Event Proxy plug-in and its gone in the top list now. Still slow scenes in Vera after all that.

 

If I run NETSTAT on the WHS there is a massive list of port numbers listed.

Yeah! The headaches of Vera plugins! Let me tell you... Their Lua/Luup platform is extremely finicky and unstable!

 

For instance if your version of their UI is running smoothly, then they actually suggest you DO NOT UPDATE from that version, even if a new one is released. Far from what we are use to here at emby, eh!?

 

Lua code is also very flakey, not solid like JavaScript/jquery and not even close to .net (based on the fact that you don't have to actually declare variables as any sort of type!) you can literally change a variable type in the middle of scripting. It reminds me of how lenient vbscript was...

 

Anyway back to the issue at hand!

 

2 minutes is ludacris! We need to figure this out.

Posted

netstat -b shows the process names, here is what I see for Emby, the IP address being that of the WHS 2011 server. 

 

 [MediaBrowser.ServerApplication.exe]
  TCP    192.168.0.x:61671      emby:https             ESTABLISHED
 [MediaBrowser.ServerApplication.exe]
  TCP    192.168.0.x:61672      104.28.23.116:http     ESTABLISHED
 [MediaBrowser.ServerApplication.exe]
  TCP    192.168.0.x:61673      emby:http              ESTABLISHED
 [MediaBrowser.ServerApplication.exe]
  TCP    192.168.0.x:63063      api:https              CLOSE_WAIT
 
I am 99% sure Emby is causing this issue with Vera running slowly and why the heck would the memory usage on the Vera go up by about 30% when Emby is running, thus probably causing the slowness in the Vera web GUI for the scenes. Devices are not affected however and they turn on / off instantly OK all the time.
Posted

Not sure what 104.28.23.116 is? It ping's and is something to do with a website called Cloudflare http://104.28.23.116/

Posted

Cloudflare is part of the Emby web hosting infrastructure.

Posted

I just tried stopping a load of my application services on my WHS 2011 box to try and rule out anything else causing the issue and the only thing that makes Vera quicker is killing Emby. 

 

Running perfmon /res loads the windows Resource monitor, one thing I can see is that Emby is constantly using some kind of multicast IP address of 239.255.255.250

 

I couldn't really see any active connections to the Vera box IP in this resource monitor. 

Posted

 

netstat -b shows the process names, here is what I see for Emby, the IP address being that of the WHS 2011 server.

 

[MediaBrowser.ServerApplication.exe]

TCP 192.168.0.x:61671 emby:https ESTABLISHED

[MediaBrowser.ServerApplication.exe]

TCP 192.168.0.x:61672 104.28.23.116:http ESTABLISHED

[MediaBrowser.ServerApplication.exe]

TCP 192.168.0.x:61673 emby:http ESTABLISHED

[MediaBrowser.ServerApplication.exe]

TCP 192.168.0.x:63063 api:https CLOSE_WAIT

 

I am 99% sure Emby is causing this issue with Vera running slowly and why the heck would the memory usage on the Vera go up by about 30% when Emby is running, thus probably causing the slowness in the Vera web GUI for the scenes. Devices are not affected however and they turn on / off instantly OK all the time.

So, there isn't the delay when you turn each device on/off, it is just when you are running scenes??

 

Also, wondering what "CLOSE_WAIT" is a report of from netstat...?

Posted

Hi

 

Yes only scenes, devices are not affected. 

Posted

Also, wondering what "CLOSE_WAIT" is a report of from netstat...?

 

I'm not sure, maybe @@Luke can give us some insight.

Posted

Looking in the Emby server log this morning, I can see a couple of errors in there, not sure if related to this issue in anyway? They can be seen here on this thread.

 

Also I turned off all the DLNA options in Emby but it still shows this in the log:

 

Info - App: Loading MediaBrowser.Dlna, Version=3.0.5724.3, Culture=neutral, PublicKeyToken=null

AgileHumor
Posted (edited)

@@cw-kid, I never was able to resolve this...but wanted to mention also noticed the UI5 became unusable via the WebGUI. 

 

Remote Apps or http get commands would fire scenes or light control and lights instantly, but pushing a button in the UI5 webgui would take forever.  I also have Emby, and nobody on the Vera forums shared similiar issues when I posted about it.   It started about 6+ months ago.

 

I recently started moving some things from Vera to HomeSeer as PLEG/UI7 was unusable to program (as it also would take minutes to save PLEG settings)...I wonder if my experience could have been related to also having Emby.

 

Not enough data to correlate, but seems related enough to share.

Edited by AgileHumor
Posted

I just can't se to replicate this. I wonder if it has to do with Emby Connect... Maybe??

 

I haven't used Connect so it is potentially the only differences in our setup, besides our client choices.

AgileHumor
Posted

I do use/have EmbyConnect.  Maybe something I'll test as I still need to control UI5 as I switch over many months.

Posted

@@AgileHumor

 

Thanks for also confirming you had similar issues. Certainly sounds the same as its only the Vera web GUI that is slow running scenes, all Vera mobile apps, Aeon minimote handsets, and sending HTTP requests to Vera via Curl command line all work perfectly and the scenes run instantly. just not in the web GUI when Emby is also running.

 

Could you please list the Vera plug-ins you had installed? And also the Emby Server plug-ins you have installed?

 

Emby Connect, I have setup my remote users to use Emby Connect for logging in to various Emby clients etc.

Posted (edited)

Here's my list of installed Plug-ins perhaps so users with this issue can compare. 

 

Vera Plug-ins

 

Count DownTimer

Wake-on-LAN

CurrentCost EnviR Energy Monitor

iTemp Plug-in

VeraAlerts

Squeezebox Control

DLNA Media Controller & UPnP Event Proxy

KodiRemote (XBMCState)

MultiSwitch

 

EMBY Server Plug-ins

 

Auto Box Sets

DVBLink TV

Dropbox

Kodi Sync Queue

 

What I don't understand is when running the TOP command on the VERA box in terminal when Emby is not running the memory usage is about 140% and everything in the Vera Web GUI runs OK. If I then launch Emby server you can see the memory usage of the Vera box climbing and can go as high as 190% or more and then running the scenes in the Vera web GUI is delayed. 

 

Cheers

Edited by cw-kid
AgileHumor
Posted

Sure!  I'm worried the problem is with Vera's network UPNP autodisover then Emby...but it could be.

 

Vera Plugins:

  • Philips Hue
  • Russound
  • Global Cache
  • Foscam
  • Somfy
  • Virtual Switch
  • PLEG
  • Ping Sensor
  • Day Night
  • Wakeup Light
  • Simple Alarm
  • Battery Monitor
  • Multisiwtch
  • SysMon

 

Emby:

  • Auto Box Sets
  • Cover Art
  • Google Drive Sync
  • ServerWMC
  • Kodi Sync Queue (new)
  • PlayOn (new)
Posted

Vera support have just emailed me again:

 

We’ll need to do some more tests to properly identify the issue and see if it’s logged in the LuaUPnP log. At the moment I can tell you the port which was kept busy on the Vera unit, port 49451, as it can be seen from the log output for netstat I ran on the 18th :

 

Proto Recv-Q Send-Q Local Address Foreign Address State

tcp 0 0 192.168.0.100:49451 192.168.0.10:62882 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62874 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62881 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62876 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62873 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62872 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62883 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62875 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62886 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62878 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62885 TIME_WAIT -

tcp 0 0 192.168.0.100:49451 192.168.0.10:62880 TIME_WAIT -

 

.100 is the Vera box .10 the WHS 2011 server running Emby.

  • Like 1
  • 2 months later...
Posted

Hi

 

An update

 

I never got to the bottom of this problem however after recently replacing my VeraLite UI5 box with a new VeraEdge UI7 box this problem has gone. 

 

I no longer have issues with scenes running slowly in the Vera web GUI when Emby server is also up and running on the network. 

  • Like 1
Posted

It is funny you should bring this topic back up because I have been experiencing a huge lag with my veralite.

 

Each light turns off independently instead of the whole scene activity at the same time.

 

Hearing about your experiences makes me wonder if I too should update to the edge.

AgileHumor
Posted

@@cw-kid, have you ever tried HomeSeer?  I switched from Vera and have been much happier.

 

Runs on Windows/Linux, or they have some appliance like devices like the Vera.

 

I've been using Kodi/Emby with a plugin to interface HomeSeer....just like you can do with Vera and Kodi.

Posted

No not really used HomeSeer. I did use mControl with WIndows MCE for a while in the past though before I got my first Vera box. 

 

I guess I could run HomeSeer as my HP Microserver is running as a file server 24/7. 

 

The VeraEdge UI7 has been OK, had some issues with some devices but on the whole its not too bad. 

 

I would probably buy a Fibaro Home Center 2 next time. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...