ShortN0te

No but PoE and AP helps.

The point is, the anecdotal evidence that you mentioned has nothing to say about other points you are making.

Just because product X runs better in a use case with software Y, does not mean product X is bad.

I do not want to come across like a ubiquity fan boy, since i only use it very targeted privately but the stuff is good, it’s supported and a plug and play solution without the cloud. Exactly what fits the bill for what it’s asked for here.

It is run in operation by thousands of businesses. Does it have problems, sure, like every other brand.

Have run openWRT myself on one of the latest lite APs, was good. Have not noticed a significant difference in the usage between both.

First, I personally have not used it (but a security cam). But i have done some research.

Reolink Integration has Platinum Status on Home Assistant.

If you can set up Frigate then there seems to be 2 Way Voice Communication possible via the Home Assistant App.

There are a couple of Videos that show the process.

Reolink has at least one PoE Doorbell.

m.reolink.com/…/reolink-video-doorbell-poe/

Switches, Security gear, nvr, central local management etc. not really something others can or do offer.

Ia it the best probably not but its still good well functioning equipment, for what it offers.

Just because something else works better, does not mean that it works not good.

Yes its expensive but also good gear mostly (never used the door bell myself).

PoE switch is not necessary, PoE injectors can be had for couple of bucks used.

I would go full IP. Solutions like Reolink or unifi exist that do not need the cloud.

Only challenge would be getting ethernet to the door.

But there are 2 wire to ethernet even with poe from unifi. eu.store.ui.com/eu/en/…/uacc-retrofit-poe-2wire

Not sure if they work well, never uses them but i would try that.

EDIT: Typo

It actually does both. Not really tested the multimonitor features but its there and it works, not sure if to the same degree as in rdp.

No, you have not understood anything. Assuming Jellyfin would go closed source, (ignoring the GPL license and so on) you would not notice anything. Your server and service would be unchanged by this.

Emby is the best example, the community will fork it and you server lives on. Even if not, then the server and software is still yours.

If it becomes an issue, then you’re in the exact same position you’d be in today if you decided to move away from Plex now.

I disagree. Right now you got time to do the research, plan the move and test it out with a demo setup. You do not know if you got the time if Plex decides to screw their lifetime users.

Yes this is hypothetical.

… and may also break compatibility with previous 10.Y releases if required for later cleanup work.

If you read through the whole paragraph, it is clear that they mean the compatibility of previous jellyfin versions.

Also, again:

Note however that the 10.Y.Z release chain represents the “cleanup” of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility,

That means that the code is not cleaned up with that release.

If you would release 11 before the code is considered cleaned up, you would basically break your own defined versioning convention. That is best decided by the active maintainers.

Consider the 10.y.z simply to be 0.y.z and everything works out.

Jellyfin inherited a lot of shitty code and architecture from emby. They simply cannot guarantee anything across patches until it is sorted out.

imho much better then releasing major version after major version because the break stuff regularly.

Also for internal use. The original emby source used not within the code base standardized database access.

Basically changes to the database were not possible since finding references across the code base which part uses which values was impossible.

Note however that the 10.Y.Z release chain represents the “cleanup” of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility,

Its right there at the link you posted.