When opening a .rules or .items file, the OPENHAB symbol gets temporarily added to the activity bar, as long as one of the .items, .rules or .sitemap files are open in an editor
If I remember the previous version of the OPENHAB VS Code extension correctly, I was able to see Files AND the Items and Things tree together stacked in the EXPLORER side bar.Now they appear to be separated.
So what I’m looking for is that I can stay in the EXPLORER side bar and have files and the trees for Items and Things all visible in one side bar w/o jumping around.
Any help is appreciated to get this fixed.
Openhab version running on Synology DS: 2.2.0.010
VS Code version: 1.27.2 running on PC Win 10, 1809
openhab VS Code extension: 0.4.0
Sorry I didn’t get it. I’m quite a noob to this whole stuff. Is there anything to configure, that the items / things will work properly again? Currently it looks like this in my VS Code Editor
hello,
i am a newbie trying to learn openhab and watching bkhobby instructional videos on youtube. after installing the extension 0.4.1 and connecting to my openhab 2.4.1 running on synology ds118 with vs code Version 1.31.1 running on a macOS 10.14.3, everything seems to work except i don’t get the sidebar icon or the things and items trees. thanks for any help.
update - the sidebar icon started showing up after quitting the program and going back in it just showed up, but now i have the more common problem, which is nothing populating the items and things trees.
the icon on the sidebar shows a clock and there is a blue trace on the top animating like it is thinking, but it never fills the trees. this means that is not connecting to the rest api on my server?
I recently switched to openHAB 3.2 and now my openHAB icon has disappeared in the sidebar.
I read this thread and set everything up accordingly as described here. Unfortunately the icon has not reappeared and I can neither see the items nor the things in my system.
I have stored a token for access in the config.
I also activate Allow Basic Authentication in the API Security settings.
I threw it all down like you said (but not only the extension, complete VSC). I also manually deleted all the remains of the installation in Win10 and reinstalled it.
Now everything is back and VSC is working as it should.