#Apps
1 messages · Page 1 of 1 (latest)
I'm struggling with the addon devcontainer - it worked great for me up till some time in January. Now I am stuck spending time figuring out why my dev environment isn't working rather than working on my addons. I'm having the same problem described in https://discord.com/channels/330944238910963714/1327359598608519188 - but it is two months later. Frustrated.
Have people quietly fixed this on their own environments, or is most addon development stalled?
Or is there some clear documentation on how to resolve the issue I just haven't tracked down yet?
Looks like an issue that was either resolved recently, or my container just takes a really long time to start and be functional (without showing activity in the logs while it is getting it ready).
Has add-on development just stopped except for some elite that are able to work without the devcontainer? Coming back to this now, and yet another problem:
'AddonManager.install' blocked from execution, system is not healthy - setup
Is the devcontainer just always broken?
as I need a usb device for my addon I just do it on my main HA instance...
have a local addon there
connect to it with VSCode
there is no need to have a full blown devcontainer for just an addon
in my situation it would only add complexitiy to get the usb device into the devcontainer...
I guess so, but the documenation starts by saying:
The fastest and recommended way to develop add-ons is using a local Visual Studio Code devcontainer. We maintain a devcontainer for this purpose which is used in all our add-on repositories.
Certainly isn't the fastest way any more in my experience. It's been a mess since the start of the year.
How do you handle using the production version of your add-on alongside the version you are developing?