Correct, that is all the binding does is create a string channel.
You could create a rule that sets the value when the system starts as the rules trigger. There may be another way via metadata, but never had to do this.
Lastly if you use a RELATIVE url address, then it will work in http and https as it will use the address that your using to access the main UI as the start of the cameras stream.
That is what I also proposed to do.
May I kindly ask why this isn’t the default behavior of the related item ? Wouldn’t that help where people have problems in case of mixed URLs ( http inside of https ) and accessing camera content via myopenhab.org ? I assume that there is a very simple reason behind it.
A) I dont think of everything when I create a binding.
b) the binding used to use a different port for each camera, now its the same port of all cameras.
c) People may not use the string contents only in the way that you are wanting to do it. Consider using the string in a rule or for sending to telegram to attach a picture to a push message.
Relative only works with a browser, when used in other sitations you may need an absolute path.
I still think this is a valid and good idea worth looking at further, perhaps it should be a config for the binding to choose if you want relative or absolute paths.
Alexa is another use case as it requires the HTTPS url and port to display cameras on echo show devices and the like. I suspect it would not make everyone happy
Hi @matt1
thanks for this detailed answer !
Reading your answer I see that
is valid for me as well and I realize that the current configuration most probably is the better compromise.
what about e.g.
I think that Alexa needs the urls with a valid SSL cert and with HTTPS, so I think people are adding them manually and not using the string items, I could not find the Alexa setup steps in the docs to refer to.
I think this is worth looking at, but more keen to make it the default behavior and have people change it if they want the old way. I suspect people in rules and other use cases are hard coding the url and not using the items. I have no way of knowing and this is a guess.
Currently making the urls relative would fix this issue talked about and also another which is what happens if the system has the wrong network card selected, the IP is wrong in those cases. I think it would fix more issues then it causes to make it the default behavior.
Thank a lot! 
That is working.