Home Assistant Community Add-on: Visual Studio Code

frenck · April 14, 2019, 11:01am

Port 8443 is used internally and not usable from the outside. A black screen indicates a browser cache issue. Try Incognito, if that works, make sure you clear your browser cache.

bramschats · April 14, 2019, 11:21am

Looks like it is browser related! Works in chrome not in Safari! Is this a known problem?

frenck · April 14, 2019, 11:24am

Yes, Safari is not working at the moment. This is an upstream issue.

frenck · April 14, 2019, 9:46pm

Release v0.3.0

Full Changelog

This release adds Hass.io Ingress support to the add-on

Also on this release, a major upgrade on the code-server and vscode running inside this add-on.
Memory usage and general performance have been improved significantly!

Furthermore, ack has been added for easy and quick command line search through your configuration files, e.g., ack light.livingroom.

Changed

Removes password option from documentation
Removes now obsolete i_like_to_be_pwned option
Upgrades hassio-cli to v2.2.0
Updates installation steps in README (#14) (@riemers)
Adds ack
Update README.md (#19) (@riemers)
Upgrades base image to v3.1.0
Upgrades wget to 1.19.4-1ubuntu2.2
Upgrades code-server to 1.792-vsc1.33.1
Improves S6 finish scripts
Adds Hassio Ingress support + General refactor
Fixes some typos in the documentation (#20) (@tjorim)
Fixes Markdownlint warnings

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

Silicon_Avatar · April 14, 2019, 10:09pm

Amazing work, thank you!

frenck · April 14, 2019, 10:15pm

Fixed in v0.3.0 of the add-on.

DavidFW1960 · April 15, 2019, 7:11am

I can no longer connect via my reverse proxy subdomain. I can’t connect using localipaddress:1337
log

[15/Apr/2019:16:54:14 +1000] 403 -(10.90.11.5) GET / HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
2019/04/15 16:54:14 [error] 449#449: *50 access forbidden by rule, client: 10.90.11.5, server: a0d7b954-vscode, request: "GET /favicon.ico HTTP/1.1", host: "10.90.11.100:1337", referrer: "http://10.90.11.100:1337/"
[15/Apr/2019:16:54:14 +1000] 403 -(10.90.11.5) GET /favicon.ico HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)

I do have ingress working and the side panel though.

milakov · April 15, 2019, 7:14am

Hi, what should be the URL for iframe with this new ingress mode in v0.3.0? This is what I have now and it is not working because the VS Code is no longer available at old port.

panel_iframe:
  vscode:
    title: VS Code
    icon: mdi:visual-studio-code
    url: https://myhomeassistant:port

DavidFW1960 · April 15, 2019, 7:21am

panel_custom:
  - name: hassio-main
    sidebar_title: Visual Studio Code
    sidebar_icon: mdi:visual-studio-code
    js_url: /api/hassio/app/entrypoint.js
    url_path: vscode
    embed_iframe: true
    require_admin: true
    config:
      ingress: a0d7b954_vscode

frenck · April 15, 2019, 7:24am

Ingress support has been added, which means the add-on works via the cloud connection as well, simply by clicking the “OPEN WEB UI” button on the add-on page.

You can still enable the “old” direct access method, by setting a port in the network section of the add-on configuration panel.

DavidFW1960 · April 15, 2019, 7:25am

Yes - that’s the part that doesn’t work.
Ingress is working

DavidFW1960 · April 15, 2019, 7:26am

http://ip-address:1337 gives the NGINX error 403 as per above log

teachingbirds · April 15, 2019, 7:39am

Memory usage and general performance have been improved significantly!

Awesome work on this, it was so slow before that I almost gave it up, now it’s useable for me! I have quite the old nuc…

milakov · April 15, 2019, 7:40am

Thanks! Do you think this “a0d7b954_vscode” is going to stay the same?

frenck · April 15, 2019, 7:40am

Yes, that is the add-on slug and is not changeable.

DavidFW1960 · April 15, 2019, 7:41am

I guess so… don’t see why it wouldn’t

kolossboss · April 15, 2019, 7:56am

I have also issues to start the vscode and web SSH und via my Duck DNS/Lets Encrypt ngnix configuration. I get only a dark grey screen, but the app is not loading. With the “configurator” Addon + ingress its working fine. The path looks also a little different.

SSH path: https://xxxxx.duckdns.org:1234/hassio/ingress/a0d7b954_ssh not working
Configurator path: https://xxxxx.duckdns.org:1234/hassio/ingress/core_configurator working

Local its working. ( http://192.168.2.25:8123/hassio/ingress/a0d7b954_ssh )
Via nabu casa cloud its working, too. ( https://xxxxxxxxxxxxxxxxxxxxx.ui.nabu.casa/hassio/ingress/a0d7b954_vscode)

Whats the problem??

DavidFW1960 · April 15, 2019, 7:58am

Are you showing a dummp port number? can’t both be 1234

kolossboss · April 15, 2019, 8:04am

Its only a placeholder but the port is nevertheless the same. I thought that is manged via ingress?! Its my HA port for the proxy

DavidFW1960 · April 15, 2019, 8:07am

I don’t specify a port at all for my proxy. Caddy sees the subdomain and then forwards to ipaddress:port… I never specify a port in the proxt url
So I can go to

 https://xxxxx.yyyyy.duckdns.org/hassio/ingress/a0d7b954_ssh