You can’t use https with the VSC extension for the LSP, I have tried. I think the issue is that it composes the address for the LSP like http://{openhab.host}:{openhab.remoteLspPort}. You can’t run it through Nginx because you would need to setup a sub directory and proxy it to 5007, so you would need to have the VSC extension try to access it via https://openhab.local/lsp for your example. However, consider the dangers, if you are connecting locally to your server then you shouldn’t need https because we should be able to assume that your local network is secure.
In order to be able to use the VSC extension through Nginx we would need the extension to allow setting the full address for each service. This would add complexity to the extension and its settings, which the developers might be against since most people are not running their OH behind Nginx.
The port 5007 is not running through Nginx, it is open in my firewall.
The issue is, that the host url ist used for connecting to LSP. Normally there should be only the IP used, so a regex to cut away the https:// part would be enogh
Oh I see, I misunderstood what you were trying to do. You are correct, the extension should take the protocol for http(s) as an additional setting, or as part of the uri and strip it for connecting to the LSP because it is not an http tunneled service.
Hello community,
I am new here and newcomers to OpenHAB.
I’ve already posted in another thread before I discovered this right one.
I put my system on a Raspi 4.
Openhabian installed as an image and currently use the homematic binding. That works perfect!
Now I wanted to set up the VS code. I have mounted the folder openHAB-conf as a network drive
and can see the folders in VS code.
If I want to synchronize the things now, I get the following error: command ‘openhab.command.refreshEntry’ not found
I’ve already tried to uninstall the VS code and reinstalled, but to no avail.
Since I am absolutely new to the field, I hope someone can help me.
Thank you so much!
violine
Second i would add the possible fix to the extension now.
I think the connection error has a different source than the https connection.
So its a smell step forward.