VSC v5.5.7 or HA 2023.4.6 problem with VSC

Hi All,

I updated today my VSC and HA on same moment. Now when I open a YAML file in VSC (Addon in HA) I see this line on every file:

Unable to load schema from 'http://schemas.home-assistant.io/integration-automation': No content.

I don’t know if this is a issue in VSC or in HA update.

In HA log see those lines. Don’t know if this was happen because of the restart of VSC:

23-04-22 09:57:03 ERROR (MainThread) [supervisor.api.ingress] Stream error with http://172.30.33.1:1337/stable-5e805b79fcb6ba4c2d23712967df89a089da575b/static/out/vs/code/browser/workbench/workbench.js: Cannot write to closing transport
23-04-22 09:57:03 ERROR (MainThread) [supervisor.api.ingress] Stream error with http://172.30.33.1:1337/stable-5e805b79fcb6ba4c2d23712967df89a089da575b/static/node_modules/vscode-textmate/release/main.js: Cannot write to closing transport
23-04-22 09:57:04 ERROR (MainThread) [supervisor.api.ingress] Stream error with http://172.30.33.1:1337/stable-5e805b79fcb6ba4c2d23712967df89a089da575b/static/out/vs/workbench/api/worker/extensionHostWorker.nls.js: Cannot write to closing transport
23-04-22 09:57:54 INFO (SyncWorker_4) [supervisor.docker.interface] Stopping addon_a0d7b954_vscode application
23-04-22 09:57:55 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.1:1337 ssl:default [Connect call failed ('172.30.33.1', 1337)]
23-04-22 09:57:55 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.1:1337 ssl:default [Connect call failed ('172.30.33.1', 1337)]
23-04-22 09:58:00 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_a0d7b954_vscode application
23-04-22 09:58:01 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/vscode/aarch64 with version 5.5.7

Restart VSC and this is the log file:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: Studio Code Server
 Fully featured Visual Studio Code (VSCode) experience integrated in the Home Assistant frontend.
-----------------------------------------------------------
 Add-on version: 5.5.7
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.0  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2023.4.6
 Home Assistant Supervisor: 2023.04.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[09:58:04] INFO: Configuring timezone (Europe/Amsterdam)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-user: starting
s6-rc: info: service init-mysql: starting
s6-rc: info: service init-mosquitto: starting
s6-rc: info: service init-code-server: starting
s6-rc: info: service init-code-server successfully started
s6-rc: info: service init-mosquitto successfully started
s6-rc: info: service init-user successfully started
s6-rc: info: service code-server: starting
s6-rc: info: service init-mysql successfully started
s6-rc: info: service code-server successfully started
s6-rc: info: service legacy-services: starting
[09:58:06] INFO: Starting code-server...
s6-rc: info: service legacy-services successfully started
[2023-04-22T07:58:08.346Z] info  Wrote default config file to ~/.config/code-server/config.yaml
[2023-04-22T07:58:09.896Z] info  code-server 4.11.0 85e083580dec27ef19827ff42d3c9257d56ea7e3
[2023-04-22T07:58:09.900Z] info  Using user-data-dir /data/vscode
[2023-04-22T07:58:09.989Z] info  Using config file ~/.config/code-server/config.yaml
[2023-04-22T07:58:09.990Z] info  HTTP server listening on http://0.0.0.0:1337/
[2023-04-22T07:58:09.990Z] info    - Authentication is disabled
[2023-04-22T07:58:09.990Z] info    - Not serving HTTPS
[09:58:11] 
[09:58:11] 
[09:58:11] Extension host agent started.
[09:58:11] Extension host agent started.
[09:58:11] [172.30.32.2][8a3f6500][ManagementConnection] Unknown reconnection token (never seen).
[09:58:11] [172.30.32.2][2460325f][ExtensionHostConnection] Unknown reconnection token (never seen).
[09:59:57] [172.30.32.2][2b0740f8][ManagementConnection] New connection established.
[09:59:58] [172.30.32.2][8457f7ba][ExtensionHostConnection] New connection established.
[09:59:58] [172.30.32.2][8457f7ba][ExtensionHostConnection] <401> Launched Extension Host Process.
[10:00:34] [172.30.32.2][2b0740f8][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.
[10:00:34] [172.30.32.2][8457f7ba][ExtensionHostConnection] <401> Extension Host Process exited with code: 0, signal: null.
1 Like

same problem here … following

1 Like

Same even on 2023.4.5. I don’t think this is related to any HA updates.

Studio code server issue as its showing on 2023.4.3 as well now

No real solution up to now… Unable to load schema from 'http://schemas.home-assistant.io/configuration' · Issue #615 · hassio-addons/addon-vscode · GitHub

It say its not an issue of Add-On but something with extensions. I don’t have any extension installed…

Same issues here:
“Unable to load schema from ‘http://schemas.home-assistant.io/configuration’: No content.YAML(768)”

The VSC add-on within HA automatically includes the HA extension if I remember correctly.

I ignore the line for now. Wait for update. You can still use the app :sunglasses:

Same Issue

Same here…

Same here…

Same. Watching.

We have to wait. You van use VSC and just ignore the line. That is what I do now.

Maybe an issue with the sub domain? Getting a DNS error when browsing the URL.

Same here… This also seems to be the problem with the binary sensors. At the moment none of mine pings works anymore…


Other ping like platforms still seems to work fine

Other ping like platforms still seems to work fine
image

This looks like the same issue I just described in another thread.

Note the error occurs at the first line of the file because the parser can’t resolve the schema and then doesn’t check the rest of the file (doesn’t matter what the first line is).