Extension doesn't work, and logs don't provide any clue on why

[felipecrs]

The extension simply does not work and there is no clue on why in the logs. Please see the video below:

Code_lRFciLHQIZ.mp4

I would deeply appreciate any help to figure this issue out. Because of it, I was not able to test this PR.

I have this in my .vscode/settings.json:

{
    "files.associations": {
        "*.yaml": "home-assistant",
    },
    "vscode-home-assistant.hostUrl": "https://myhassinstancecorrectaddresswithpropercertificate",
    "vscode-home-assistant.longLivedAccessToken": "absolutelycorrectlonglivedaccesstoken"
}

Extension runs in:

• Advanced SSH & Web Terminal, connected through VS Code Remote SSH on Windows.

I'm running VS Code on:

• Windows
• Mac
• Linux

I'm accessing my files:

• From local disk
• Via remote SSH
• Smb
• Other:

[dziban303]

Hey @felipecrs, yeah it wasn't working for me either. I normally connect to the Home Assistant machine with the SSH FS extension, and like you none of the home assistant features were working.

So I mapped the remote machine as a drive in Explorer (using SSHFS-Win), and now when I open HAss config files from the S: drive or whatever, the extension works as you'd expect.

I don't know why it doesn't work with SSHing from withing VSCode but that does appear to be the issue.

[felipecrs]

Using SSHFS-Win is a great idea. It even helps to offload the Home Assistant server. Thank you for the suggestion.

But I'll keep the issue open, as I think it was supposed to work.

[chemelli74]

Similar situation here, I tried both with UNC path and mapping a network disk.

I can get the entity competition work for a few seconds right after VS code windows reload and then nothing.

I suspect a conflict with some other extensions.