I had thoughts around trying to attempt this myself, but it looks like you've added quite a bit of functionality since I forked your code and it may be a little more than I can chew at this point.

But what I'd be very interested in is being able to leverage what you've already done around entity and service auto-completion and using it in AppDaemon. So, I can think of the following things it would need:

• Support for .py files in the appdaemon directory
• If a .py file is open, provide service auto-completion support. Service call always begins with self.call_service("domain/service_name", so for example self.call_service("light/turn_on"
• Entities are generally referenced with the variables entity or entity_id. So, auto-complete after any of the following are typed would be desired:
  • entity = "
  • entity == "
  • entity_id = "
  • entity_id == "

I'm definitely a novice when it comes to VS Code extensions but I'd be happy to help as much as possible.

Getting this error when installing:
Unable to install because, the extension 'keesschollaart.vscode-home-assistant' compatible with current version '1.31.1' of VS Code is not found.

"Unexpected property condition" error is reported when conditions are used in automation actions.

With the trigger below, I get an unexpected property message in VS Code. The for property seems to be the problem.

  trigger:
  - platform: template
    value_template: "{% if is_state_attr('proximity.home', 'dir_of_travel', 'towards') %}false{% endif %}"
    for: '00:05:00'

Checking the configuration doesn't return a error message. And according to the document this for property is correct however: https://www.home-assistant.io/docs/automation/trigger/#template-trigger

Hint on objects from Home Assistant does not work without "restarting" the extension.
Writes "no suggestion".
It does not try to connect to the Home Assistant.
If I open the properties of an extension, disable it and then enable it again, everything will start working until the next VSCode restart.
OS: Windows 10
VSCode: 1.37.0
Extension: 1.0.2

I was using this extension when I was working with Lovelace YAML files designated as the YAML language in VS Code, but since switching to designate them as Home Assistant files, the MDI extension no longer suggests icons using Intellisense.

Entity "binary_sensor.openclose_9" is being highlighted - "Incorrect Type. Expected "object".

Works OK in HA.

Example:

type: picture-elements
image: /local/images/ground_floor_plan.png
elements:
  - type: conditional
    conditions:
      - entity: binary_sensor.openclose_9
        state: 'on'
    elements:
      - type: image
        image: /local/images/ground_floor_plan_open-patio-doors.png
        style:
          top: 5.7%
          left: 50.17%
          width: 16.15%

Probably a nit in line 3 of https://github.com/keesschollaart81/vscode-home-assistant/blob/master/snippets/homeassistant_script.json:

"prefix": "sctript",

Maybe a typo?

When I copy some configuration to duplicate and edit it, the indentation of the pasted configuration is incorrect. The pasted strings take the indentation of the previous line no matter how many blank lines are in between the copy/paste.

e.g. copying these two lines of customization yaml,..

light.bar_downlights:
  icon: mdi:track-light

... and pasting to a blank line below it produces this:

light.bar_downlights:
  icon: mdi:track-light

  light.bar_downlights:
    icon: mdi:track-light

This makes an absolute mess of copying and pasting Lovelace cards in a stack.

        entities:
          - entity: light.lroom_light
            <<: &ceiling-light
              type: custom:slider-entity-row
              toggle: false
              hide_state: true

<<: &ceiling-light is highlighted: Property << is not allowed.

I'm new to VS Code but I think I've installed your extension OK with the URL and LLAT. However, I can't see any of the HA config files - do I need to setup an SSH connection to HA as well? Thanks!

I'm using packages to group configurations. Only one string is expected although more are possible.

Example:
  packages:
    shelly: !include package/shelly/shelly_package.yaml
    sonoff: !include package/sonoff/sonoff_package.yaml
    glance: !include package/glance/glance_package.yaml

Error message:
Incorrect type. Expected "string"

Is the mdi Explorer part of this extension?
Using "Inset Icon Into Editor" inserts it as:

mdi-alert instead of
mdi:alert

Also on a similar note, any idea when the file icons will be updated?

https://github.com/home-assistant/home-assistant-cli Supports specifying server and its token via environment variables. Would be super nice if this extension would use these when the settings in vscode are blank.

Then from terminal I could just use 'code configuration.yaml' and things would "just work" :)

Unless I am doing something wrong the auto-complete does not seem to support packages.
If I am wrong can you tell me what I might be doing and if I am right can you say if this is ever likely to be a possibility?

This is a great extension even with the (apparently) limited functionality with packages, so thanks for creating it!

Just like it says on the title, I just think it would be great to have full color-coding support for Jinja2 snippets inside the .yaml files.

Dependabot can't resolve your JavaScript dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Error whilst updating @types/node in /package-lock.json:
No matching version found for [email protected]

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

You can mention @dependabot in the comments below to contact the Dependabot team.

I recently introduced a few !secret values into my configuration.yaml file, and I started getting this error from the extension:

I'm not sure if this is the same as another issue I saw about !includes, but my !includes seem to be fine. My configuration.yaml is pretty bare-bones, as most of my components are in packages:

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  
  auth_providers:
    - type: homeassistant
    # uncomment this to enable backwards compatible API password support
    #- type: legacy_api_password

  # Location required to calculate the time the sun rises and sets
  latitude: !secret home_latitude
  longitude: !secret home_longitude
  
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 0
  
  # metric for Metric, imperial for Imperial
  unit_system: metric
  
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: America/Halifax
  
  # Customization file
  customize: !include customize.yaml

  # Packages
  packages: !include_dir_named packages

http:
  # api_password: !secret http_password
  base_url: !secret base_url
  use_x_forwarded_for: true
  trusted_proxies:
    - 127.0.0.1

api:

person:

When for an entity using a non-boolean state in a scene I receive an error message. The state doesn't need to be a boolean per se. I.e. for an alarm you can use the 'armed_away' or 'home' state.

I have found two more small ones.

To be honest it is probably more correct to have continue_on_timeout: false (no quotes) but I seem to have a mix in my config and as it is valid either way I thought you'd like to know.
But if it is definitely more correct without quotes feel free to tell me and leave the extension as it is.

Also
you don't allow for ThomasLoven's custom popup card:

Recently VS show "Unexpected property "auth_mfa_modules" at HomeAssistant section in configuration.yaml.
Using HA 0.92.2 and your package 0.5.3

I'm using in my lovelace file a few YAML node anchors.
Unfortunately it show as an error within Visual Studio

automation:
  - alias: 'test'
    trigger:
      - platform: homeassistant
        event: start
    action:
      - wait_template: "{{ is_state('binary_sensor.entrance', 'on') }}"
        timeout:
          minutes: 5

minutes: 5 is highlighted, although it is a correct syntax.

As discussed here danielwelch/coc-homeassistant#1

Would great if it supported Jinja2 (.j2) template extensions.

Currently any Jinja2 templated yaml files in my configuration wont auto complete.

Ever since the version which added "Go to definition" for include files, the CPU usage has skyrocketed for me.

When i am editing a file and saving it, it maxes out one core on my Intel NUC and it is really slow to perform the schema-check.

I am not getting any errors, just a very slow VSCode. Is there any other information i can provide you with to help troubleshoot?

EDIT: I monitored the CPU using top, and as soon as i start to edit a .yaml file the CPU usage goes through the roof so its not just on saving the file. It seems to be the syntax-check which is causing the problem.

In contrast, if i edit a python program i get at most 40% CPU usage, while this extension showed at most 164% CPU usage

I have a complicatied value template for a sensor in configuration.yaml (Thanks Petro!)

But it breaks the yaml markup of the visual studio code addon.

It's this part:

sensor:
  - platform: rest
    name: "Grocy Meal Plan" 
    resource: https://grocy.org/api/objects/meal_plan
    headers:
      GROCY-API-KEY: !secret GROCY-API-KEY
      accept: application/json
    value_template: >
      {% set today = now().strftime('%Y-%m-%d') %}
      {% set items = value_json | selectattr('day','eq',today) | list | first %}
      {% set attributes = ['day', 'recipe_id', 'servings'] %}
      {{ items.items() | selectattr(0, 'in', attributes) | sort(attribute=0) | map(attribute=1) | join(',') }}      

Everything after it is marked as text, but it isn't. It also passes the configuration test of Home Assistant and works as it should.

See image below:

Thanks for the great extension! I would love if I could check my Home Assistant configuration right from VSCode. Would it be possible to provide something for that?

Hey Kees!

I'm not sure if this is is a quirk in the extension or something in Code itself.

When I install the plugin in Code on mac and select the option to "configure now", I'm not really able to configure the plugin:

Pasting the home assistant url goes fine, no problems there, but as soon as I move the focus from the editor to another window (alt+tab) to copy paste the long lived access token, the configuration "window" (The one input line), pops away and I can't paste my token anymore...

The token is too long to remember, so copy pasting would be highly preferred :)

I think will be able to insert the token somewhere in some file, so I'll find a workaround, but it would be nice if it worked :)

Thanks for the effort of creating this lovely plugin, I haven't used it yet, but I love it already 👍

EDIT: Typo's

Please do not ignore current indentation options (4 spaces) and not always force 2 spaces.

I´ve installed the extension into VSCode on OSx, i've configured the https url and the long live token, i followed method 2, but now don´t see the home assistant config files in the explorer.

Do i need to do something to make this files visible?

Hey! So the first time i ran the extension i accidentally typed in the wrong adress. I updated it in settings.json and restarted visual studio code but i still got an error. Strangley enough in the error message it listed the old url. So i removed every setting in settings.json under the extension and uninstalled the extension. Restarted visual and installed the extension again, but even without filling in any settings it still pops up the same connection error message with the old url?

I have installed the addon and it is working great. However I have two HA servers running and the entity completion only works for a single server. Is it possible to make the settings for the add-on specific to a folder i.e. 'Folder settings' and then I could switch between the servers.

Installed extension, configured with server address (I'm sure that the address is correct cause I've tested on browser) and with long live token, then restarted VScode but I get this error:

Error connecting to your Home Assistant Server at https://192.168.1.65:8123, check your network or update your VS Code Settings. Error: 1

VScode:

Versione: 1.32.3 (user setup)
Commit: a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4
Data: 2019-03-14T23:43:35.476Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17134

The following code snippets produces the wrong error: Missing property "event_data_template".

test:
  sequence:
    - event: flow_test
      event_data:
        state: "on"

I hope this can be fixed easily because it is really annoying :)

If one uses a repo where home-assistant config in a subfolder, the plugin won't activate as it just looks for configuration.yaml and ui-lovelace.yaml in the root folder.

This is an example where this can be experienced: https://github.com/PedroLamas/nanopineo2-docker-config

Ideally, I believe that subfolders should be checked for these files.

I use a config like @frenck using a lot of !include

I have a script.yaml file with

script: !include_dir_named ../../scripts

This way the name of the files in folder script is used as the entity_id of each script. But the home assistant add-on see errors in all files of this folder with the error message in title of the issue.
Home Assistant raises no error with those files and work as expected.
You can see example in my repo.

I think the extension might be highlighting some false problems.

1. input_boolean with nothing else defined e.g.

input_boolean:
  my_boolean1:

  my_boolean2:

2. I find that wait_template often (always?) gets highlighted as a problem
   
   

The support for HASS_TOKEN & HASS_SERVER environment variables (added in #11) no longer work in the latest version.

It seems that these were lost in translation during the migration/refactor towards the language server. This causes a problem for the Home Assistant Visual Studio Code add-on for Hass.io, since it relies on them.

The result is the add-on now spawns continues popups:

Use "goto Definition" to jump the the correct position in the secrets.yaml file. Alternatively if it does not exist, create it and allow it to be filled.

I'm using SSH FS to load my workspace via SSH.
It looks like the extension doesn't work when the active workspace isn't local.

I went to "file -> open folder". Selected my hass folder and nothing pops up.

I think the docs are missing something.

Snippets cannot load, as shown in the logs:

The entity-button Lovelace card supports setting the height of the assigned icon using the icon-height property, but the current scheme (v0.6.0) doesn't allow this property.

Example:

      - type: entity-button
        icon_height: 100px
        tap_action:
          action: toggle
        name: Všetky svetlá v byte
        entity: group.all_lights
        hold_action:
          action: more-info

When using the extension to autofill after a dash (-) an extra space is added. Displayed in the screenshot.

When using the entity filter card is used, errors are raised for some card properties:

Example code:

  - type: entity-filter
    entities:
      - entity: binary_sensor.frontdoor_contact_sensor
      - entity: binary_sensor.master_bedroom_outside_door_sensor
        name: Balkondeur
    state_filter:
      - 'on'
    card:
      type: glance
      title: Open contacten
      show_state: false
    show_empty: false

Latest version gets error with config using !includes. It used to be OK.

This works fine in HA but VSCODE shows red wavy lines under all the lovelace/********.yaml - "Incorrect type. Expected object"

    - type: vertical-stack
      cards:
        - !include lovelace/living_room.yaml
        - !include lovelace/kitchen.yaml
        - !include lovelace/utility.yaml
        - !include lovelace/toilet.yaml
        - !include lovelace/hall.yaml
        - !include lovelace/gardens.yaml
        - !include lovelace/garage.yaml

I think there is an incorrect error being flagged in Lovelace picture-entity.

Hi there, great work ;)
What do you think about autocompletion for platforms (e.g. in triggers) and services?

If you use a empty condition in an automation, the message

Incorrect type. Expected "object"

is raised, although it is a correct syntax.