embyforkodi (next-gen) 8.X.X support

[RaptorCentauri 56]

On 11/11/2023 at 11:22 AM, quickmic said:

Probably yes, but if this https://github.com/xbmc/xbmc/pull/14972 ever gonna make it to a Kodi release (PR is from 2018?), it would mean I could remove the multiversion workaround and use the native Kodi implementation. Would be a good thing, but let's wait.

The feature is officially in beta now for Kodi v21. It would be great if emby4kodi could utilize it.

[quickmic 1610]

55 minutes ago, RaptorCentauri said:

The feature is officially in beta now for Kodi v21.

I know, I can see the changes in in Kodi's db. I'll review it an decide how to approach.

Actually a lot of code can be removed in next-gen plugin's code and is something for 10.X

9.x must keep compatibility with Kodi 20 and 21.

[gregeeh 1]

Hello Everyone,

I wonder if someone can help me connect Kodi with my remote Emby Server.

LibreELEC 20.2 NextGen 8.2.14

I'm trying to connect to my remote Emby Server using the Manual Method.  I can connect to my Server in a browser by entering https://myusername.domain.com/emby.  However with the same entered in the manual connect window I get an error cannot connect.  Kodi log shows a 404 Error:

2023-12-29 15:57:38.851 T:1545     info <general>: EMBY.emby.emby: tryConnect url: https://myusername.domain.com/emby:
2023-12-29 15:57:39.183 T:1545    error <general>: EMBY.emby.http: [ Statuscode ] 404

Entering nslookup myusername.domain.com via SSH in Kodi resolves just fine.

There is also nothing in the Emby Server Logs showing any attempts of a connection.

What am I doing wrong?

TIA

BTW - There are no port numbers entered via my browser nor NextGen.

[quickmic 1610]

15 minutes ago, gregeeh said:

 

BTW - There are no port numbers entered via my browser nor NextGen.

What do you mean with no Port? When you connect next-gen the portnumber must be entered. Default is 8096 but probably you should change it to 443.

Your browser uses by default 443 for https.

[gregeeh 1]

5 minutes ago, quickmic said:

What do you mean with no Port? When you connect next-gen the portnumber must be entered. Default is 8096 but probably you should change it to 443.

Your browser uses by default 443 for https.

Have tried 443 and still does not connect.

2023-12-29 16:37:25.848 T:2087     info <general>: EMBY.emby.emby: tryConnect url: http://myusername.domain.com/emby:443
2023-12-29 16:37:26.155 T:2087    error <general>: EMBY.emby.http: [ Statuscode ] 404

Also the Emby Server Logs shows no attempt of anyone trying to connect.

[quickmic 1610]

1 minute ago, gregeeh said:

Have tried 443 and still does not connect.

2023-12-29 16:37:25.848 T:2087     info <general>: EMBY.emby.emby: tryConnect url: http://myusername.domain.com/emby:443
2023-12-29 16:37:26.155 T:2087    error <general>: EMBY.emby.http: [ Statuscode ] 404

Also the Emby Server Logs shows no attempt of anyone trying to connect.

443 is for HTTPS

you entered a HTTP which is port 80 or 8096

[quickmic 1610]

http://myusername.domain.com/emby:80

or

https://myusername.domain.com/emby:443

[gregeeh 1]

Get this in logs:

 

2023-12-29 16:45:47.106 T:2087     info <general>: EMBY.emby.emby: tryConnect url: https://myusername.domain.com/emby:443
2023-12-29 16:45:47.109 T:741      info <general>: CActiveAESink::OpenSink - initialize sink
2023-12-29 16:45:47.109 T:741      info <general>: CAESinkALSA::Initialize - Attempting to open device "@"
2023-12-29 16:45:47.214 T:741      info <general>: CAESinkALSA::Initialize - Opened device "sysdefault"
2023-12-29 16:45:47.215 T:741      info <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2023-12-29 16:45:47.215 T:741      info <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S32NE
2023-12-29 16:45:47.515 T:2222     info <general>: EMBY.emby.emby: Reconnect try again:  / 
2023-12-29 16:45:48.909 T:2087     info <general>: Skipped 1 duplicate messages..
2023-12-29 16:45:48.909 T:2087    error <general>: EMBY.emby.http: [ Statuscode ] 404

 

[quickmic 1610]

1 minute ago, gregeeh said:

Get this in logs:

 

2023-12-29 16:45:47.106 T:2087     info <general>: EMBY.emby.emby: tryConnect url: https://myusername.domain.com/emby:443
2023-12-29 16:45:47.109 T:741      info <general>: CActiveAESink::OpenSink - initialize sink
2023-12-29 16:45:47.109 T:741      info <general>: CAESinkALSA::Initialize - Attempting to open device "@"
2023-12-29 16:45:47.214 T:741      info <general>: CAESinkALSA::Initialize - Opened device "sysdefault"
2023-12-29 16:45:47.215 T:741      info <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2023-12-29 16:45:47.215 T:741      info <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S32NE
2023-12-29 16:45:47.515 T:2222     info <general>: EMBY.emby.emby: Reconnect try again:  / 
2023-12-29 16:45:48.909 T:2087     info <general>: Skipped 1 duplicate messages..
2023-12-29 16:45:48.909 T:2087    error <general>: EMBY.emby.http: [ Statuscode ] 404

 

Is the /emby correct?

If you don't mind, can you please sen me the actual URL via PM. I don't need the login credentials, just the URL for checking...

[gregeeh 1]

PM Sent

[quickmic 1610]

Ok, checked. You must use:

https://myusername.domain.com

port 443

NO "/emby"

[gregeeh 1]

Thank you.

Why the no /emby, I don't understand?

Seems to have worked, Kodi seems locked up at the moment after logging in.  Must be getting all the video info.

 

[quickmic 1610]

3 minutes ago, gregeeh said:

Thank you.

Why the no /emby, I don't understand?

Seems to have worked, Kodi seems locked up at the moment after logging in.  Must be getting all the video info.

 

the "/emby" is added by the plugin (internally, by sourcecode).

Edited December 29, 2023 by quickmic

[gregeeh 1]

2 minutes ago, quickmic said:

the "/emby" is added by the plugin (internally, by sourcecode).

That makes sense.  Thanks again for sorting this for me.

[gregeeh 1]

One more question if I may:

Do you know of a way to get the watched status from Plex into Emby?

[js28194 27]

On 12/29/2023 at 12:18 AM, quickmic said:

the "/emby" is added by the plugin (internally, by sourcecode).

Hmmm.... well this maybe a problem.  I have two servers, one at main house and one at vacation house.  Main house has HDHOMERUN Prime 3 and behind nginx reverse ssl proxy, running on Debian.  It's address is https://mydomain.com/emby, so yes, I can drop emby off for this instance.  (Does not pull in any Live TV stuff) that would be nice.

Second home is problem as it running on windows behind Caddy reverse ssl proxy.  It has HDHOMERUN 4k OTA and Two older HDHOMERUN HDHR3 OTA only (they ain't broke), however this is one is https://emby.mydiffdomain.com.

Why hard code anything and let user control the URL?

Thanks for the good work.

[quickmic 1610]

Well, that's legacy from the 4.X versions. Never thought about changing it. However might be possible, I need to check if this causes issues.

I need to mention, I also run 3 Emby server instances also behind proxies and never had issues.

Edited December 30, 2023 by quickmic

[js28194 27]

My ideal scenario would be pull both my cable EPG into my home with OTA only into a single interface.  That location doesn't have any PVR service running, straight Emby.  I may have to install NextPVR over there.  Multiple Servers into one instance would be cool.

Remote home as only OTA and NextPVR service... I will experiment some more.  I read you can connect to NextPVR over WAN if change pin, but I am not sure about integration into the Kodi Channel Guide for a seamless experience.

[quickmic 1610]

13 minutes ago, js28194 said:

https://mydomain.com/emby,

Using tld extensions "/emby" for redirections is not the best idea. Did you think about using https://emby.mydomain.com

That's what I use and is much more reliable as you don't need rewrite rules.

Edited December 30, 2023 by quickmic

[js28194 27]

4 minutes ago, quickmic said:

Using tld extensions "/emby" for redirections is not the best idea. Did you think about using https://emby.mydomain.com

That what I use and is much more reliable as you don't need rewrite rules.

Well, you know if it ain't broke don't fix mentallity.  It's been running smoothly for 5+ years now and trying to change though not of the question, just another project.  Will look into it at some point.  BTW, I know I can accomplish what I want in my above post, site-site VPN in a TAP configuration will allow me to see all HDHOMERUN Devices across both locations, but again, massive reip one location etc etc.

Oh yeah, I remember why... location A you have to use ISP stupid Fiber Modem that doesn't support bridge mode and they won't budge to upgrade their crap, so essentially be double NAT.  Doable, but just further complicates things.

Edited December 30, 2023 by js28194

[quickmic 1610]

"https://emby.mydiffdomain.com"

This will work as well with /emby queries. The server accepts both, there is no need for redirection on proxy side.

try it

https://emby.mydiffdomain.com/emby/system/info/public

https://emby.mydiffdomain.com/system/info/public

both should work.

[sfatula 196]

Where does the watched status come from with dynamic? For example, an episode of an Emby show that claims in Kodi that I have watched 6 times. And it has a last watched date. I doubt I watched it 6 times, where does the date come from? I can't find it in Emby anywhere.

[quickmic 1610]

Yes, info is from emby server.

Not sure how/if you get the counter value on Emby server directly via WebUI (for comparison).

 

 

 

[LittleWizard 31]

Turned back from 9.x to 8.x do to sync problems and nodes problems.

I was trying to set curtimeout to 2secs in advancedsetting, but embyforkodi 8.x revert it to 30sec anytime I restart kodi.

30s is the lowest value permitted by the plugin.

Can I force 2secs someway?

Maybe if I duplicate the row in advancedsettings, the last value overrides the first?

Thanks!

[quickmic 1610]

1 minute ago, LittleWizard said:

Turned back from 9.x to 8.x do to sync problems and nodes problems.

I was trying to set curtimeout to 2secs in advancedsetting, but embyforkodi 8.x revert it to 30sec anytime I restart kodi.

30s is the lowest value permitted by the plugin.

Can I force 2secs someway?

Maybe if I duplicate the row in advancedsettings, the last value overrides the first?

Thanks!

No, cause 8.x uses the higher timeouts for multiselection.