VSCode Extension: 'Setup' fails with macOS 15 - fix included

[twischi]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

I am working on macOS 15 and the VS Code Extension.
Expedition this that 'Setup' runs without failing.

Actual behavior (suspected bug)

I am working on macOS 15 and the VS Code Extension. The Extension permanently fails with 'Setup'.

Terminal shows this root cause error message:
Error: $HOME must be set to run brew.

Some research (googling) show's that this a common error with macOS 15. A problem with the HOME-Variable.

I investigated the main script 'extension.js' and fixed it for macOS 15: HOME is set manually.

See attached the fixed 'extension.js'. With code-compare you can find the minimal changes and might fix it.

Regards Thomas

Fixed file:
extension.js

Error logs or terminal output

Error: $HOME must be set to run brew.

Steps to reproduce the behavior

See actual behavior section

Project release version

normal version

System architecture

ARM 64-bit (Apple M1/M2, Raspberry Pi 4/5)

Operating system

MacOS

Operating system version

macOS 15

Shell

Bash

Additional context

macOS 15.7.3 at MacBook Air, M3

[ChinmayLonkar]

Hello @twischi ,

This looks like a system level problem, can you check if your HOME variable is correctly set using echo $HOME in your VS Code terminal? let me know if this works. I was not able to reproduce this issue on MacOS 15.4 on M1 MacBook Pro

[twischi]

@ChinmayLonkar
Thxs for your replay.
Yes in VS Code Terminal (bash 5.3) and both build in macOS Terminals (bash & zsh) the HOME Variable is set correctly.

Greets Thomas

[ChinmayLonkar]

Hi @twischi ,

It's hard to reproduce this issue, can you run . $LOW_CODE_PATH/install.sh in the terminal and share your output? You might be prompted asking to replace files, you can select the option to replace all files. Please also share any other relevant information that could help debug this issue.

[multicatch]

In my case the Setup takes forever, no progress even after 1h.

I cloned the repo and tried to run the scipt, I got this output:
./install.sh: line 54: realpath_int: command not found

realpath_int is a function found in export.sh of esp-matter. And even though I did source ../esp-matter/export.sh, the installer still cannot find this command.

I fixed it by replacing line 54 with this:

script_dir="$(realpath $(dirname "${self_path}"))"

It ran, but then complained about the lack of venv.

So I ran the install.sh script in the venv created by the VSCode ESP-IDF plugin (by using "Open ESP-IDF terminal").

[twischi]

@multicatch
For me it feels like 'there is no active development' going on at LowCode. Maybe I am wrong but last commit is 6 month old.
What I have done is: to switch to classical 'esp-matter' and there uses the ZAP-Light example.

Why I have done this:

• Now I edit the ZAP File to get es Matter-UI behavior i desire.
• Than I edit app_main.cpp, app_diver.cpp and app_priv.h to steer my hardware.

Hint: This comes with serval new obstacles, that have solved.

• Get the ZAP File in my now Project folder with related 'zap-templates'-Folder
• Get ZAP GUI Tool running to edit and recreate *.matter files after *.zap- edit
• (Optional) I build myself a tool that reports the Cluster and the set Attributes during start of MCU to see what going on. This uses pure CHIP code.

This way again has a significant complexity as I had to lern about the Matter-Data-Model and the ZAP tool, but this is generally Matter knowledge and I am free to chose any supported MCU like esp32h2, esp32c3, esp32s3 and so on.

Greets
Thomas