I have upgraded docker based installation from 2.5.0.M2 to 2.5.0.M6.
Starting from M2 the VSC integration with LSP was broken and finally fixed in M5.
I now have a problem with the file paths referenced in the PROBLEMS tab. They all are referencing the rules files by an absolute path /open/conf/rules.
And clicking on the problem the file cannot be opened:
Any idea of how that can be fixed, I have checked the situation with M5, the issue with the path
I started on a test server docker container 2.4.0, just to be sure that the new version of VSC did not introduce the issue:
on 2.4.0 there is not path to the file containing the error
For some unknown reason the issue disappeared
I’m having the same issue after upgrading from oH 2.4 to 2.5 on Raspi 3B running openhabian.
AND some files are shown with absolute and relative paths:
VScode:
Version: 1.41.0 (system setup)
Commit:xxxxx
Datum: 2019-12-11T18:37:42.077Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
Betriebssystem: Windows_NT x64 10.0.18362
Is have the same using OpenHAB 2.5 Release. Is there any workaround?
I had the same issue while I had not saved a VSCode Workspace yet. Since I have done so, the issue has disappeared. I had to restart VSCode though to get rid of some old problems pointing to the wrong path that would not dissapear even when resolved. After that, all seems fine.
Hi,
i am trying to reuse this old topic because it perfectly fits.
Running OH 2.5.10 on a Pi and VS Code 1.50.1
My Workspace is looking as this while Z is a mapped SMD share of the conf folder:
{
"folders": [
{
"path": "Z:\\"
}
],
"settings": {}
}
When using “go to definiton” or other random stuff I get the message that “\openhab\conf\rules\shitty_stuff.rules” is not available.
If VSC is creating the file it is stored at C:\openhab\conf*
Any advise?