Not sure if this is the best place to post this question.
I use VS code for most of my file edits for yaml, config, ESPHome, etc.
But for my dashboards, I use the UI instead of yaml, with the occasional raw configuration editor.
So all my lovelace dashboards are in the hidden directory which does not show up in VSCode.
My question is, is there a way to force the hidden folders to show up in VSCode?
I really enjoy editing my config since I ādiscoveredā the CS code addon and especially after configuring git properly.
The only thing which really bugs me: Some time after VS code auto saved a file, undo (Ctrl-z) doesnāt work anymore. Accoding to most of what I read about undo history issues, undo should work, even after a file was saved. And if it doesnāt, this is mostly related to a problem with an installed extension.
I have four extensions installed, but deactivating them doesnāt solve the issue:
C/C++
German language Pack
GitLens
Nano Themes
Actually, undo is still working immediately after auto save as long as I stay in the editor. But when I leave the VS code UI, f.e. for checking the config, reloading scripts etc. and returning some moments later, I canāt undo anything anymore.
Is this working for you or do you have the same issue?
Is there any way to turn off the auto-indenting? Itās driving me absolutely bonkers, and Iāve tried turning it to āNoneā in User, Remote, and Workspace, but itās still doing it!
Visual Studio code will constantly crash my home assistant. If Iām coding in Visual Studio Code, at least 3 to 4o time sa day Iāll get trying to reconnect. If I disregard then home assistant freezes and I need to turn it off then back on. If I stop using Visual Studio Code then no crashes all day.
Am I the only one?
Hi Paul - Iāve got the same issue running VS on an older PI3 with an SD card. The moment I try to use VS, it will crash or freeze HASS. Sometimes I can recover by clicking a different page, but while VS is installed, I noticed that even going to Supervisor will some make things freeze up.
The moment I uninstall VS code, everything works fine again. My next test is to run HASS.io on an SSD to see itās maybe an issue with running HASS.io on a crapy SD card. It might be a PI3 thing. Havenāt had this issue on a PI4.
I am currently struggling with configuring Github in Visual Studio Code. Iām able to access my Github repository through the git command on the command line (git push --set-upstream https://[username]:[token]@github.com/[username]/[repository].git master
But how and where do I configure Git Username and Oauth Token in VS Code? When trying to commit through VS Code, the authentication fails and ends in an 404 error.
Update: Solved!
Solution:
Generate an Personal Access Token in Github
In VS Code call āGithub: Set Personal Access Tokenā and set the Token
Is there a trick configuring github for this addon? I set user name and email and add the remote repo for my files. When I am trying to push changes Iāll get a message box to allow access to github. A 2nd tab opens where I am able to grant access to the addon. But then github wants to redirect to the vs code instance and this ends in an error 404. I tried from local ip and using my duckdns domain but with no success.
What am I missing here? I donāt see the āVisual Studio Codeā when searching the addons page? Iāve watched a couple of youtube clips where the VSC is found and installed. Iām running the the ODROID N+ with HA OS.
Fresh install of Home Assistant on a brand new ODROID N2+, first add-on installed is vscode and Iām getting these vertical lines in every file I open! Very annoying to try and code with.
Has anyone experienced these? Theyāre there in both light and dark themes and not present on the Get Started page, just every file I open.
@drcoolzic and another post got me headed in the right direction as I started my HA journey on a RPi4 Ubuntu arm64 node.
Unfortunately was sitting getting errors - for anyone still struggling (Iām doing everything locally, not externally - yet), I had to adjust my Ubuntu firewall
Instead of:
ufw allow from <subnet>/<mask> to any port 8123
Using this cleared it right up:
ufw allow from any to any port 8123
As Iām using a manual supervisor install (thus docker), I believe the chatter was being cut off. I plan to dig a bit deeper to determine what is being called/used so I can lock down a bit tighter but hoping this helps others.
Today i updated Studio Code Server to 4.1.0. Now i get a bunch of errorsā¦ i have a folder āsensorsā where i have yaml files and there my sensors. after update each template sensor shows an errorsā¦
whatās the catch? I mean - what i must change in order to remove those errors? Is it related to VSC or is it just announcement for future HA update uncompatibility?
EDIT: going back to 4.0.0 and all errors are goneā¦
I shoud say that these sensors DO work, even with these errors. So, is it VSCās fault?