Lock custom server address

[Blueskies278 88]

Manually added address reverts to the auto-discovered one every time the app restarts.

Please add an option to pin a manually added address.

Thanks

[ebr 16588]

Hi.  What are you calling the "auto discovered" address?

If your server reports the proper address, then the app will always use that.

[Blueskies278 88]

The Emby server is set to port 8098, but the plugin I created ("Air Date Fixer") listens to port 8096. When I add port 8096 and exit the Android app, it reverts back to 8098. For my plugin to work, I need it to use port 8096

Edited 16 hours ago by Blueskies278

[Luke 42858]

An option could be added to the app's setup process to not switch to server reported addresses.

[Blueskies278 88]

7 minutes ago, Luke said:

An option could be added to the app's setup process to not switch to server reported addresses.

This would be amazing if it could be added 

Thanks

Edited 1 hour ago by Blueskies278

[ebr 16588]

7 minutes ago, Luke said:

An option could be added to the app's setup process to not switch to server reported addresses.

IMO that is going to create more problems than it solves.  This use case is truly < 1%

15 hours ago, Blueskies278 said:

The Emby server is set to port 8098, but the plugin I created ("Air Date Fixer") listens to port 8096. When I add port 8096 and exit the Android app, it reverts back to 8098. For my plugin to work, I need it to use port 8096

Why don't you configure the server so it uses the port you really want to?

[Blueskies278 88]

@ebr

 I'm actually trying to do — the port arrangement is a workaround, not the goal. And you're probably right that the address-switching option is niche; I'd rather not need it at all.

The problem: US and Canadian shows air in the evening Eastern, which is already the next calendar day in the UK. TMDB stores air dates as a bare date with no time or timezone, so those episodes show on the wrong day for anyone in Europe. Trakt returns first_aired as a true UTC instant, so it converts correctly for any timezone — which is why Kodi with Trakt shows the right day without any patching.

For episodes already in the library this is straightforward: my plugin shifts PremiereDate and writes it back via ILibraryManager.UpdateItem, re-applying if a later metadata refresh overwrites it. That part works fine and needs nothing unusual.

The difficulty is /Shows/Upcoming — episodes not yet downloaded. As far as I can find there's no plugin hook that fires for those: a metadata provider never sees them, and they aren't reachable by library query either. I originally corrected TheMovieDb's cached season files, but MovieDb 1.9.2.0 stopped reading them, so that approach is dead.

That left intercepting the /Shows/Upcoming request itself — an HttpListener inside the plugin that answers that one endpoint with corrected dates and forwards everything else to Emby untouched. That's the only reason the listener takes the port clients already use and the server moved to 8098. Configuring Emby back to 8096 puts it in front of the listener again and disables the correction entirely.

So the real question: is there a supported extension point for upcoming/virtual episodes? If a plugin could adjust those directly, the listener, the port swap and the address-switching problem all disappear together.

The strategy: concede the small point, establish you've done the obvious things properly, then ask for the hook that would make the workaround unnecessary. If they say yes, the architecture gets simpler and beta testers need no port setup at all.

Is there's a better way to achieve this? I have been working on this plugin for weeks and always hitting a brick wall.

Thanks

 

 

 

 

 

 

 

 

Edited 1 hour ago by Blueskies278