VSCode extension

[rugged sedge]

Small development around the VSCode config helper extension for Home Assistant

Wanted to make a topic. I've been cranking out improvements lately (not shipped yet). But wanted to dump what I've done so it might spark more ideas.

• Auto completion for secrets

• Added a UUID generator in the autocompeletion for id and unique_id fields

• Added detection for the use of unknown entity IDs

• Replaced the connection management, with onboarding and debugging/testing features:

• Added support for detecting unknown areas being referenced

• Refactored reloading:

• Added a connection status bar, the links to the instance when connected; and opens up the authentication/connection setup when it is not connected.

• Migrated tokens and instance URLs to be stored in the secret encrypted storage of VSCode (and not in the plain JSON file)

[rugged sedge]

• Detection of unknown secrets being used

[rugged sedge]

• Goto definition capability for secrets

[formal thicket]

Just noticed this, the extension complains about the sort parameter on the settings for the select selector

[rugged sedge]

Fixed in https://github.com/keesschollaart81/vscode-home-assistant/pull/3556

But keep spitting those things 🙏 There is a lot of support missing across the board still. Love to get those out

I should really start shipping the current state though, as the mount of changes and fixes is quite large.

Nevertheless, I still want to try to get:

• Detection of unknown floor_ids used
• Detection of unknown device_ids used
• Detection of uknown file or folder inclusions
• Goto definition of included files
• Add support for auto complete on inclusions
• Handle inclusions on the YAML parser level, so the extension isn't riddled with support it everywhere.
• Finish a poc that does show the output of a template on hover
• Finish a poc that does show the current state of an entity on hover

There is also some other things I want to look into.
I don't think all the new automation syntax is supported / used by default yet (like service -> action). Maybe I can offer fixes for that automatically as well

[formal thicket]

Ah, great.. Already fixed yesterday.. Looks like something I could have added myself. Will do if I ever see such an error again.

[rugged sedge]

• When hovering over an entity_id, it will bring up live information about the entity

[rugged sedge]

• Limited the documention hovering stuff, to the configuration key (YAML key) only. This to give more meaning to the values. In the screenshot below it is visible by the slight background color on just "action"

• Added support for detecting unknown device_ids

[rugged sedge]

• Add showing service action information on hover

• Detect the use of unknown label_ids.

Very depressing instance of Home Assistant... as it consider Christmas to be non-existing

[rugged sedge]

• Detect he use of unknown floor_ids

[halcyon pendant]

Hey 👋! Is it possible add such hover-info for a specific integration too? In Knx we have addresses (1/2/3) and optionally a json file where those map to human readable names etc.

Would be very handy if users could double check with those names - or maybe if those could even be used for auto-completion (name to address).

[rugged sedge]

Not without building a specific language server for it I guess

I did update the schema for KNX though: https://github.com/keesschollaart81/vscode-home-assistant/pull/3586

[halcyon pendant]

Ah ok. I had hoped for some WS endpoint I can provide from the integration.

[halcyon pendant]

thank you very much 😃

[rugged sedge]

• Detect the use of unknown actions

[frail stag]

do you plan a release in the next days ? Current version doesn't work for me

[rugged sedge]

Yeah, cranking out some bugs reported and adding a few missing schemas still

but it seems pretty releasable otherwise

[rugged sedge]

What doesn't work btw? 😄

[frail stag]

Unfortunately the extension itself, ref. :https://github.com/keesschollaart81/vscode-home-assistant/issues/3284

[rugged sedge]

https://github.com/keesschollaart81/vscode-home-assistant/releases/tag/v2.0.0

[formal thicket]

Ooh, a 2.0 release

[rugged sedge]

Yeah seems justified, as the whole YAML parser underneath it has been replaced

😬

[formal thicket]

I guess the Studio Code Server add-on will get an update as well?

[rugged sedge]

Yup, working on that right now

needs some changes on that end

Hmmz the extension didn't publish somehow

😄

[rugged sedge]

Lol just called Kees (repo owner), token expired 😄

Fixed. Ok now the add-on

[halcyon pendant]

I've added even more 😉 https://github.com/keesschollaart81/vscode-home-assistant/pull/3618

[rugged sedge]

Thanks!!

[waxen oxide]

😮 big thanks @rugged sedge for this massive update !!

[frail stag]

Update to 2.0.0 and now I finally see an error:

[rugged sedge]

Yeah known issue, haven't had the time to fix yet, hopefully after the release

[rugged sedge]

Added support for problem providers (with fixes)

[frail stag]

Frenck, thx for v2.x.0 that fixes the parsing issue and the connection not-working !

Now I can use the extension via SMB 😉

[formal thicket]

That looks way better then the big red LEGACY_SYNTAX message I now often see

[frail stag]

Is there a way to have a full list of all warnings instead of opening yaml file one by one for inspection ?

[rugged sedge]

Nope, vscode only shows it per file in the problem pane

You'd have to build an actual linter in order to do that (outside of vscode)

[frail stag]

Thx a lot for the quick feedback

[frail stag]

BTW, I think I found a issue with YAMLParser for value_template, opened a issue