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

[quickmic 1389]

1 hour ago, LittleWizard said:

Sometimes my Kodi on Nvidia Shield (android) hangs on stop or at the end of the file.

Yesterday I found that waiting a lot, Kodi does finally return to main interface.

I attach the log.

Seems like a timeout in accessing the file (dragonball) and after about 4 minutes it timed out and Kodi run again.

I could think about a problem with the NAS, but kodi from a rasberry (libreelec) and embyforkody doesn't seem to have this problem on the same network (both wired lan).

kodi.log 94.52 kB · 0 downloads

Log looks fine, but I see a 2 minutes gap. This should not happen, but it's Kodi based.

As a workaround, you can lower the network timeouts in plugin menu -> advanced settings -> network timeouts.

Default is 2 minutes and that's exactly matching with the 2 minutes gap in your log.

Keep in mind, content-multiselection is also using this timeout value. e.g. lowering to 30 seconds will also lower the time for selecting content (the selection menu).

To sum it up, it's not a plugin issue. It's a Kodi problem and I also run into this issue on my raspi in very very few cases. Maybe 1 out of 100 playbacks.

[LittleWizard 30]

Thanks a lot!

[joshuap94118 1]

Just downloaded and installed 8.2.13, getting popups for websocket offline.

pfa, logs from emby 4.7.13 and kodi (emby for next gen on fire 4k max)

Thanks!

Joshua.

2023-08-18 19:27:38.969 T:9901     info <general>: Emby.hooks.websocket: --->[ websocket connect ]
2023-08-18 19:27:38.970 T:9901     info <general>: Emby.hooks.websocket: Close wesocket connection 851843645d104d17b4bea3db0b4c817c / jp-HP-Z800-Workstation
2023-08-18 19:27:38.970 T:9901    error <general>: Emby.hooks.websocket: [Errno 32] Broken pipe
2023-08-18 19:27:38.970 T:9901    error <general>: Emby.hooks.websocket: [Errno 107] Transport endpoint is not connected
2023-08-18 19:27:38.971 T:9845    error <general>: EmbyCon.resources.lib.websocket_client|ERROR|Error: [Errno 103] Software caused connection abort
2023-08-18 19:27:38.976 T:9901    error <general>: Emby.hooks.websocket: [Errno 101] Network is unreachable
2023-08-18 19:27:38.976 T:9901     info <general>: Emby.hooks.websocket: [ websocket connect failed ]
2023-08-18 19:27:40.110 T:26963   error <general>: Emby.hooks.websocket: [Errno 32] Broken pipe
2023-08-18 19:27:40.111 T:26963    info <general>: Emby.hooks.websocket: [ websocket connect in progress ]
2023-08-18 19:27:41.112 T:26963    info <general>: Emby.hooks.websocket: THREAD: ---<[ ping ]
2023-08-18 19:27:43.988 T:9901     info <general>: Emby.hooks.websocket: --->[ websocket connect ]
2023-08-18 19:27:43.988 T:9901     info <general>: Emby.hooks.websocket: Close wesocket connection 851843645d104d17b4bea3db0b4c817c / jp-HP-Z800-Workstation
2023-08-18 19:27:43.989 T:9901    error <general>: Emby.hooks.websocket: [Errno 32] Broken pipe
2023-08-18 19:27:43.989 T:9901    error <general>: Emby.hooks.websocket: [Errno 107] Transport endpoint is not connected
2023-08-18 19:27:44.005 T:9901     info <general>: Emby.hooks.websocket: ---<[ websocket connect ]
2023-08-18 19:27:44.005 T:27755    info <general>: Emby.hooks.websocket: THREAD: --->[ ping ]

 

2023-08-18 19:27:29.358 Info Server: http/1.1 Response 204 to host1. Time: 2ms. http://192.168.0.40:8096/emby/Sessions/Playing/Progress 2023-08-18 19:27:42.508 Info Server: http/1.1 Response 206 to host1. Time: 199330ms. http://192.168.0.40:8096/emby/videos/177158/stream?static=true&MediaSourceId=93d78d1893c5c09713fce002c568aa61&PlaySessionId=5cf675f011444f3bb5ff4c72fe230037&DeviceId=1b113ec1-b83f-43df-85ea-b3b358c58592 2023-08-18 19:27:43.282 Info Server: http/1.1 GET http://192.168.0.40:8096/emby/videos/177158/stream?static=true&MediaSourceId=93d78d1893c5c09713fce002c568aa61&PlaySessionId=5cf675f011444f3bb5ff4c72fe230037&DeviceId=1b113ec1-b83f-43df-85ea-b3b358c58592. Accept=*/*, Host=192.168.0.40:8096, User-Agent=Kodi/20.2 (Linux; Android 9.0; AFTKA Build/PS7646.3554N) Android TV/9.0.0 Sys_CPU/armv7l App_Bitness/32 Version/20.2-(20.2.0)-Git:20230629-5f418d0b13, Accept-Charset=UTF-8,*;q=0.8, Accept-Encoding=deflate, gzip, Range=bytes=478731243- 2023-08-18 19:27:44.031 Debug App: ScheduledTasksWebSocketListener Begin transmitting over websocket to 192.168.0.193 2023-08-18 19:27:49.405 Info Server: http/1.1 POST http://192.168.0.40:8096/emby/Sessions/Playing/Progress. UserAgent: Emby for Kodi Next Gen/8.2.13 2023-08-18 19:27:49.406 Debug SessionManager: OnPlaybackProgress StateChange 5cf675f011444f3bb5ff4c72fe230037 2023-08-18 19:27:49.407 Info Server: http/1.1 Response 204 to host1. Time: 2ms. http://192.168.0.40:8096/emby/Sessions/Playing/Progress 2023-08-18 19:27:59.110 Info Server: http/1.1 POST http://192.168.0.40:8096/emby/Sessions/Capabilities/Full?format=json. UserAgent: EmbyCon-1.11.20 2023-08-18 19:27:59.135 Debug AuthenticationRepository: UpdateCapabilities id: 34 2023-08-18 19:27:59.136 Info Server: http/1.1 Response 204 to host1. Time: 25ms. http://192.168.0.40:8096/emby/Sessions/Capabilities/Full?format=json 2023-08-18 19:27:59.429 Info Server: http/1.1 POST http://192.168.0.40:8096/emby/Sessions/Playing/Progress. UserAgent: Emby for Kodi Next Gen/8.2.13 2023-08-18 19:27:59.430 Debug SessionManager: OnPlaybackProgress StateChange 5cf675f011444f3bb5ff4c72fe230037

kodi.log embyserver.txt

[quickmic 1389]

1 hour ago, joshuap94118 said:

Just downloaded and installed 8.2.13, getting popups for websocket offline.

pfa, logs from emby 4.7.13 and kodi (emby for next gen on fire 4k max)

Thanks!

Joshua.

2023-08-18 19:27:38.969 T:9901     info <general>: Emby.hooks.websocket: --->[ websocket connect ]
2023-08-18 19:27:38.970 T:9901     info <general>: Emby.hooks.websocket: Close wesocket connection 851843645d104d17b4bea3db0b4c817c / jp-HP-Z800-Workstation
2023-08-18 19:27:38.970 T:9901    error <general>: Emby.hooks.websocket: [Errno 32] Broken pipe
2023-08-18 19:27:38.970 T:9901    error <general>: Emby.hooks.websocket: [Errno 107] Transport endpoint is not connected
2023-08-18 19:27:38.971 T:9845    error <general>: EmbyCon.resources.lib.websocket_client|ERROR|Error: [Errno 103] Software caused connection abort
2023-08-18 19:27:38.976 T:9901    error <general>: Emby.hooks.websocket: [Errno 101] Network is unreachable
2023-08-18 19:27:38.976 T:9901     info <general>: Emby.hooks.websocket: [ websocket connect failed ]
2023-08-18 19:27:40.110 T:26963   error <general>: Emby.hooks.websocket: [Errno 32] Broken pipe
2023-08-18 19:27:40.111 T:26963    info <general>: Emby.hooks.websocket: [ websocket connect in progress ]
2023-08-18 19:27:41.112 T:26963    info <general>: Emby.hooks.websocket: THREAD: ---<[ ping ]
2023-08-18 19:27:43.988 T:9901     info <general>: Emby.hooks.websocket: --->[ websocket connect ]
2023-08-18 19:27:43.988 T:9901     info <general>: Emby.hooks.websocket: Close wesocket connection 851843645d104d17b4bea3db0b4c817c / jp-HP-Z800-Workstation
2023-08-18 19:27:43.989 T:9901    error <general>: Emby.hooks.websocket: [Errno 32] Broken pipe
2023-08-18 19:27:43.989 T:9901    error <general>: Emby.hooks.websocket: [Errno 107] Transport endpoint is not connected
2023-08-18 19:27:44.005 T:9901     info <general>: Emby.hooks.websocket: ---<[ websocket connect ]
2023-08-18 19:27:44.005 T:27755    info <general>: Emby.hooks.websocket: THREAD: --->[ ping ]

 

2023-08-18 19:27:29.358 Info Server: http/1.1 Response 204 to host1. Time: 2ms. http://192.168.0.40:8096/emby/Sessions/Playing/Progress 2023-08-18 19:27:42.508 Info Server: http/1.1 Response 206 to host1. Time: 199330ms. http://192.168.0.40:8096/emby/videos/177158/stream?static=true&MediaSourceId=93d78d1893c5c09713fce002c568aa61&PlaySessionId=5cf675f011444f3bb5ff4c72fe230037&DeviceId=1b113ec1-b83f-43df-85ea-b3b358c58592 2023-08-18 19:27:43.282 Info Server: http/1.1 GET http://192.168.0.40:8096/emby/videos/177158/stream?static=true&MediaSourceId=93d78d1893c5c09713fce002c568aa61&PlaySessionId=5cf675f011444f3bb5ff4c72fe230037&DeviceId=1b113ec1-b83f-43df-85ea-b3b358c58592. Accept=*/*, Host=192.168.0.40:8096, User-Agent=Kodi/20.2 (Linux; Android 9.0; AFTKA Build/PS7646.3554N) Android TV/9.0.0 Sys_CPU/armv7l App_Bitness/32 Version/20.2-(20.2.0)-Git:20230629-5f418d0b13, Accept-Charset=UTF-8,*;q=0.8, Accept-Encoding=deflate, gzip, Range=bytes=478731243- 2023-08-18 19:27:44.031 Debug App: ScheduledTasksWebSocketListener Begin transmitting over websocket to 192.168.0.193 2023-08-18 19:27:49.405 Info Server: http/1.1 POST http://192.168.0.40:8096/emby/Sessions/Playing/Progress. UserAgent: Emby for Kodi Next Gen/8.2.13 2023-08-18 19:27:49.406 Debug SessionManager: OnPlaybackProgress StateChange 5cf675f011444f3bb5ff4c72fe230037 2023-08-18 19:27:49.407 Info Server: http/1.1 Response 204 to host1. Time: 2ms. http://192.168.0.40:8096/emby/Sessions/Playing/Progress 2023-08-18 19:27:59.110 Info Server: http/1.1 POST http://192.168.0.40:8096/emby/Sessions/Capabilities/Full?format=json. UserAgent: EmbyCon-1.11.20 2023-08-18 19:27:59.135 Debug AuthenticationRepository: UpdateCapabilities id: 34 2023-08-18 19:27:59.136 Info Server: http/1.1 Response 204 to host1. Time: 25ms. http://192.168.0.40:8096/emby/Sessions/Capabilities/Full?format=json 2023-08-18 19:27:59.429 Info Server: http/1.1 POST http://192.168.0.40:8096/emby/Sessions/Playing/Progress. UserAgent: Emby for Kodi Next Gen/8.2.13 2023-08-18 19:27:59.430 Debug SessionManager: OnPlaybackProgress StateChange 5cf675f011444f3bb5ff4c72fe230037

kodi.log 125.66 kB · 0 downloads embyserver.txt 2.74 MB · 0 downloads

That's not a plugin issue. Check you network configuration.

 

[joshuap94118 1]

Thanks for the reply Quickmic!

This is all local network, no firewall, nor proxy. 

Is there something else I can trace/test/log to figure out what is going on?

Thanks!

 

[quickmic 1389]

2 hours ago, joshuap94118 said:

Thanks for the reply Quickmic!

This is all local network, no firewall, nor proxy. 

Is there something else I can trace/test/log to figure out what is going on?

Thanks!

 

Run a test with a clean Kodi installation on a PC.

btw, EmbyCon reports the same issue.

EmbyCon.resources.lib.websocket_client|ERROR|Error: [Errno 103] Software caused connection abort

Also it's not good running both plugins simultaneous.

Edited August 20, 2023 by quickmic

[quickmic 1389]

btw, you can also disable the websocket connection in plugin menu. But this NOT recommended at all. You will lose the realtime sync capabilities.

plugin config menu -> "Sync' -> "Enable websocket connection"

[markdj 48]

On 8/17/2023 at 5:13 PM, quickmic said:

@markdj

Any pattern when this started?

I'm still using .39 emby server. With .40 I experienced some websocket/realtime update issues but no playback issues as you reporting.

Can you reproduce the issue on a fresh Kodi installation on a PC. Not on the box, cause lot's of issues are related to specific Kodi versions/hardware.

 

It’s been like this for a while for me. Small microstutter or video speeding/catching up. I’ll try a fresh installation soon, but no promises. Possible it’s a Kodi issue but I’ve literally tried everything already.

[quickmic 1389]

20 minutes ago, markdj said:

It’s been like this for a while for me. Small microstutter or video speeding/catching up. I’ll try a fresh installation soon, but no promises. Possible it’s a Kodi issue but I’ve literally tried everything already.

Please send me Kodi debug log via PM. Maybe I find something.

[quickmic 1389]

Also try disable Upnp in Kodi

https://kodi.wiki/view/Settings/Services/UPnP_DLNA

Edited August 20, 2023 by quickmic

[quickmic 1389]

Also try disable portmapper plugin on emby server

[quickmic 1389]

Finally, disable ALL hardware acceleration in Kodi. Sometimes it's buggy. Kodi menu -> Player -> Videos -> look for hardware acceleration (on multiple spots)

[markdj 48]

1 hour ago, quickmic said:

Finally, disable ALL hardware acceleration in Kodi. Sometimes it's buggy. Kodi menu -> Player -> Videos -> look for hardware acceleration (on multiple spots)

I’ll send a log later today and hope it contains all of the recent information then

As for your suggestions, I’ve tried them all but without success. Disabling hardware acceleration makes it a complete stutters, unplayable mess. UPnP was already unchecked and removing Port Mapper on Emby Server gives an error, but I have disabled assigning a random port somewhere else in the settings there (Network, most likely).

Thank you for helping, though!

[joshuap94118 1]

Hey @quickmicyou were right, it was a network issue. Albeit, not a proxy/firewall one.

Built a vm, win10, same issues. Upgraded to the 4.8.0.42 beta, same issues.

Tore thru everything I could think of, pulled an old ddwrt router, flashed it to clean, same issues.

Finally found it on the unifi network AP logs, must be a freak conflict but the RSSI on the firestick is ~75-80 and it apparently bounces/roams between two different APs and in that brief moment the websocket connection times out.  This probably doesn't happen to many other people and I'll order an hdmi extender to reposition the stick but it would be awesome if there were configuration options to either ignore the error since good buffering apparently means I never notice it or change the timeout/repeat error threshold.

Thanks again.  Awesome product! (not the firestick. Just the emby server and kodi add-on)  

[quickmic 1389]

Great you found the issue. Network problems can be really tricky to debug. You could also try disable roaming on Unifi. There is an option called "Lock to access point" in Unifi config.

However, relocating is surly the better option.

52 minutes ago, joshuap94118 said:

 if there were configuration options to either ignore the error

Would be possible, but frankly, I'm not a big fan of ignoring issues. Such problems should be addressed even if you didn't experience playback issues. There could be other side affects too.

 

 

Edited August 21, 2023 by quickmic

[quickmic 1389]

17 hours ago, markdj said:

I’ll send a log later today and hope it contains all of the recent information then

As for your suggestions, I’ve tried them all but without success. Disabling hardware acceleration makes it a complete stutters, unplayable mess. UPnP was already unchecked and removing Port Mapper on Emby Server gives an error, but I have disabled assigning a random port somewhere else in the settings there (Network, most likely).

Thank you for helping, though!

Thanks for the log.

I see some Kodi issues.

1. disable plugin config menu -> sync -> "use path substitution"

2. if this doesn't help, try enable transcoding

[quickmic 1389]

General info:

If you enable "use path substitution" make sure the following Kodi option is disabled:

"media" -> "Videos" -> "extract video information from files"

but leave this one enabled:

"media" -> "Videos" -> "extract chapter thumbnails"

[LittleWizard 30]

On 8/18/2023 at 6:32 PM, LittleWizard said:

Thanks a lot!

 

On 8/18/2023 at 12:06 PM, quickmic said:

Log looks fine, but I see a 2 minutes gap. This should not happen, but it's Kodi based.

As a workaround, you can lower the network timeouts in plugin menu -> advanced settings -> network timeouts.

Default is 2 minutes and that's exactly matching with the 2 minutes gap in your log.

Keep in mind, content-multiselection is also using this timeout value. e.g. lowering to 30 seconds will also lower the time for selecting content (the selection menu).

To sum it up, it's not a plugin issue. It's a Kodi problem and I also run into this issue on my raspi in very very few cases. Maybe 1 out of 100 playbacks.

I'm sorry, just to investigate deeper since now it hangs till timeout quite always: the connection which takes too long without reply is versus my Nas o something else? Could be emby server which does not respond?

[quickmic 1389]

2 hours ago, LittleWizard said:

 

I'm sorry, just to investigate deeper since now it hangs till timeout quite always: the connection which takes too long without reply is versus my Nas o something else? Could be emby server which does not respond?

Could be everywhere, but the usual suspect is Kodi/box (hardware). Did you test Kodi on a PC?

[SwanStream 59]

Dumb question... I've copied my kodi setting (appdata/roaming) to another pc and all works well, only I want to change user. When I remove server, add server and select the user I want it gives me the welcome message, but even after a restart doesn't show the 'currently watching' for that user, tracking the original... What am I doing wrong or how can I get it to 'swap' user?

 

[SwanStream 59]

Never mind... update library did the deed.

[quickmic 1389]

6 hours ago, SwanStream said:

Dumb question... I've copied my kodi setting (appdata/roaming) to another pc and all works well

 

As it works on a PC, Emby server and plugin has no issues.

ergo, could be Network connection (Wlan maybe) or Kodi is buggy on the box. Could you try different Kodi versions? I know there are 64bit 32bit versions of Kodi for apks etc.

[LittleWizard 30]

22 hours ago, quickmic said:

Could be everywhere, but the usual suspect is Kodi/box (hardware). Did you test Kodi on a PC?

Yes, and also on raspberry libreelec. I have this problem only on Nvidia shield pro. Very strange. On raspberry I have now another problem: embyforkody does not update sync automatically. Llibreelec is always running, when I turn on Tv and make kodi exit from screensaver, the films states are not updated to nvidia. I have to disable and enable embyforkodi and it suddenly sinc everything correctly. This is after latest addon update. Maybe I'll try a full addon reset.

[quickmic 1389]

New BETA version available 8.2.14:

Delta changelog 8.2.13 -> 8.2.14

(realtime) progress progress updates even if Emby server is busy
(another) fix dynamic nodes (genre and tags) for mixed content
fix webdav issue
add recommendations for dynamic nodes
fix library updates when "use path substitution" is enabled (plugin) and "extract video information from files" is enabled (Kodi). Actually "extract video information from files" should always be disabled.
fix remote client selection when Emby server doesn't report a Username

[Seger 110]

On 21.8.2023 at 05:30, joshuap94118 said:

Hey@quickmicSie hatten Recht, es war ein Netzwerkproblem. Allerdings kein Proxy/Firewall.

Habe eine VM erstellt, Win10, die gleichen Probleme. Auf die Betaversion 4.8.0.42 aktualisiert, dieselben Probleme.

Habe alles durchgesehen, was mir einfiel, habe einen alten ddwrt-Router gezogen, ihn geflasht, um ihn zu reinigen, die gleichen Probleme.

Endlich wurde es in den AP-Protokollen des Unifi-Netzwerks gefunden. Es muss sich um einen seltsamen Konflikt handeln, aber der RSSI auf dem Firestick beträgt ~75-80 und er springt/roamt offenbar zwischen zwei verschiedenen APs und in diesem kurzen Moment fällt die WebSocket-Verbindung aus. Das passiert wahrscheinlich nicht vielen anderen Leuten und ich werde einen HDMI-Extender bestellen, um den Stick neu zu positionieren, aber es wäre toll, wenn es Konfigurationsoptionen gäbe, um den Fehler entweder zu ignorieren, da eine gute Pufferung anscheinend bedeutet, dass ich ihn nie bemerke oder das Timeout ändere /repeat-Fehlerschwelle.

Danke noch einmal. Tolles Produkt! (nicht der Firestick. Nur der Emby-Server und das Kodi-Add-on)  

you can also set the stick to a fixed AP at unifi, then it should not jump.