New error message: Device 'xxx' does not exist in your Home Assistant instance

[DaveOzzie]

[trianglesis]

Same here:

Similar to: #1054

Revert back to 5.19.3 and everything is fine again.

[Destroyer061090]

same as me.. a lot of this wrong information.

[cnotin]

I have a similar issue but with areas "unknown-area"

[cnotin]

Also reported here: keesschollaart81/vscode-home-assistant#3938 which is the VSCode extension that this addon uses and which seems to provide these warnings

[jmfargas]

I have a similar error with custom:layout-card:

view_layout:
  grid-area: "dispositius"

Shows the error: Area 'dispositius' doesn't exist in your Home Assistant instance
This error strarted after updating vscode-addon from version 6.0.0 to 6.0.1

[merlinpimpim]

Can we have a correction soon, please?

[merlinpimpim]

up

[jmfargas]

Does anybody know weather there is a plan to fix this error? It is quite annoying. And I cannot go back to the previous version because the backup did it with the new version?, it's very strange? Alternatively, does anybody know where to find the previous version? Many thanks!

[merlinpimpim]

Really annoying!
Impossible to debug anything!

Normally I should see 1 error in this file, but with the bug it shows me 613!
Where is the real problem? Impossible to know!

Please fix this bug quickly!

[snikolic-cpt]

Same here, but with "Area"...

in automations.yaml

Developer tools -> automations is not reporting any errors.

Studio Code Server
Current version: 6.0.1

[JelmerD]

I have the same issue and it seems to have to do something with the 'new' target: selector.

  actions:
    - action: script.turn_off_indoor_lights
      metadata: {}
      data: {}
    - action: timer.finish
      metadata: {}
      data: {}
      target:
        floor_id:
          - second_floor
          - first_floor
          - ground_level

If I remove the floor_id and the corresponding floors, or if I change it to:

        floor_id: [second_floor, first_floor, ground_level]

it seems to work just fine.

Also, since it throws the warning as a Floor xxx does not exist it seems to think everything is part of the floor_id list. I think the interpreter/Language Mode needs an update? Also, when I change it to seperate areas (area_id) it will say Area xxx does not exist.

Maybe this helps troubleshooting the problem and fixing it? Since I started to make use of custom blueprints more and more I need to edit my automations in yaml more often :)

edit3:
I think the interpreter just doesn't know area_id, floor_id, etc. as key. Because I now see it triggers right after I do this when using a custom blueprint:

edit1: @keesschollaart81 (https://github.com/keesschollaart81/vscode-home-assistant) could you have a look at this and see if it has to do with your code?

Workaround

edit2: some sort of workaround for anyone running in this issue
Move the error-giving automation to the bottom of the file. At least then you don't have the faulty warnings in 'correct' automations. Not the best solution, but at least it helps me troubleshooting other stuff (new blueprint and the red part you see in the screenshot below). You can also notice it now changed to area warnings instead of floor warnings, kinda sorta confirming my statement made above.

[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!

[Destroyer061090]

Still present