Auto-completion for keywords and parameters not working with VS Code v5.10.0

[vumaddibly]

Problem/Motivation

Prior to Nov 2023 the HA VS Code Add-on used to provide auto-completion for keywords (eg alias, description, trigger, platform and mode), parameters (eg state, numeric_state, single) and entity ids/names. Today the only completion that works is for entity ids/names.

Expected behavior

Auto-completion to work for keywords, parameters and entity ids/names.

Actual behavior

When starting to write a new automation the pop-up list of potential auto-completions does not correspond to the current context (see screenshots).

Steps to reproduce

Start to write a new automation and type a single hypen, as though you were about to type '- alias: '. You will be presented with a list of completions that make no sense. Similar problems are experienced as each new keyword is entered.

Proposed changes

Restore the pre-Nov 2023 functionality. Removing and re-installing the add-on does not affect the behaviour.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[vumaddibly]

Several other people are experiencing the same problem due to the number of 'thumbs up' comments. I have repeatedly re-installed the VS Code Add-on but the problem remains.

[vumaddibly]

@frenck, would have a few minutes to look at this please? Despite removing and re-installing the VS Code Add-on several times the problem remains, ie the only auto-completions that work for me are entity names. Auto-completion for keywords and parameters is broken. I think I may have been the cause of the problem as I remember there being a .vscode-xxxxxx file or folder under /config and it looked to be a left-over temporary file and I deleted it - clearly it wasn't! It's strange that a re-install doesn't resolve the problem.
Thanks.

[nicolaufg]

I think I may have been the cause of the problem as I remember there being a .vscode-xxxxxx file

I also see this problem and I never deleted such file or anything similar.

[vumaddibly]

@nicolaufg, I'm wondering what the common factor might be 🤔 Which browser(s) and OS(es) are you using? I only have Macs and iOS mobile devices to test with.

[nicolaufg]

@nicolaufg, I'm wondering what the common factor might be 🤔 Which browser(s) and OS(es) are you using? I only have Macs and iOS mobile devices to test with.

I'm using Linux Mint 20.2. Hass is running dockerised on a Tinker 2 (Debian 10).

5 min later...
Oh, well, that's fun/sad... I just realised this repo is for the Hass addon to get VSCode inside Hass... my problem, which looks just exactly as yours in the screenshots you provided above, is about a VSCode extension to deal with Hass. I'll dig a bit more there, and maybe also get this addon installed in Hass and see how it goes.

I hate growing old :(

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[vumaddibly]

The problem persists. I uninstalled the Add-on, upgraded HA Core from 2024.4.2 -> 2024.4.3 and then reinstalled the VSCode Add-on - no change

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[vumaddibly]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

This issue is still there with Core 2024.5.3, OS 12.3 and Frontend 20240501.1

[4rianton]

Same.. can't use auto complete

[Bartsz]

Same here, but it doesn't work for neither VS Code Server and regular VS Code connected to HA

HA OS 12.3
HA Core 2024.6.3
Running in VM VirtualBox

[Perchycs]

Same thing here running latest version of supervised HA OS.

[shimscharf]

same here using latest version of supervised HA OS

---

Add-on: Studio Code Server
Fully featured Visual Studio Code (VSCode) experience integrated in the Home Assistant frontend.

Add-on version: 5.15.0
You are running the latest version of this add-on.
System: Home Assistant OS 12.4 (amd64 / qemux86-64)
Home Assistant Core: 2024.6.4
Home Assistant Supervisor: 2024.06.2

Studio Code Server log:

[10:42:07] Extension host agent started.
File not found: /usr/local/lib/code-server/lib/vscode/out/vsda_bg.wasm
File not found: /usr/local/lib/code-server/lib/vscode/out/vsda.js
[10:42:08] [172.30.32.2][7dddef66][ManagementConnection] New connection established.
[10:42:09] [172.30.32.2][96d57f44][ExtensionHostConnection] New connection established.
[10:42:09] [172.30.32.2][96d57f44][ExtensionHostConnection] <12864> Launched Extension Host Process.
File not found: /usr/local/lib/code-server/lib/vscode/extensions/keesschollaart.vscode-home-assistant-1.39.0/jinja-language-configuration.json
[10:42:53] [172.30.32.2][7dddef66][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
[10:42:53] [172.30.32.2][96d57f44][ExtensionHostConnection] <12864> Extension Host Process exited with code: 0, signal: null.
File not found: /usr/local/lib/code-server/lib/vscode/out/vsda.js
File not found: /usr/local/lib/code-server/lib/vscode/out/vsda_bg.wasm

Supervisor Log:

2024-07-11 10:50:57.555 ERROR (MainThread) [supervisor.api.ingress] Stream error with http://172.30.33.2:1337/stable-0b84523121d6302fbe30eda7899ec3b81810748e/static/out/vs/workbench/workbench.web.main.css: Cannot write to closing transport
2024-07-11 10:50:58.735 ERROR (MainThread) [supervisor.api.ingress] Stream error with http://172.30.33.2:1337/stable-0b84523121d6302fbe30eda7899ec3b81810748e/static/out/vs/workbench/services/keybinding/browser/keyboardLayouts/layout.contribution.win.js: Cannot write to closing transport
2024-07-11 10:50:58.830 ERROR (MainThread) [supervisor.api.ingress] Stream error with http://172.30.33.2:1337/stable-0b84523121d6302fbe30eda7899ec3b81810748e/static/out/vs/base/browser/ui/codicons/codicon/codicon.ttf: Cannot write to closing transport

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[vumaddibly]

This issue is not stale. I suffered a HDD failure recently, after which I did a fresh install and backup. I have no updates showing but the problem persists.

[shimscharf]

Issue persists

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[shimscharf]

Still persists

[frenck]

Fix in v5.16.0

[vumaddibly]

@frenck, many thanks for your work fixing this. Editing YAML is now soooo much easier! 👏 👏 👏