A while back I ditched Windows for Linux desktop (long time Linux user, just not desktop) because I’ve learned to hate Microsoft.

I have 2 Sengled WiFi bulbs that I thought were useless now that Sengled is dead (although the app seems to be able to login again now, I’ll never trust it). But then I found Sengled Tools which, among other things, documents a very simple way to communicate with Sengled bulbs using JSON over UDP. The sample light custom component is only ~100 lines of Python and adding the UDP and JSON from Sengled Tools would be maybe 50-100 more. I took this as an invitation to improve my Python and rescue the bulbs so I started reading up on Home Assistant development.

I now have this overwhelming VS Code install with devcontainers etc. etc. which seems crazy overkill for the task at hand and I really resent AI being shoved in my face every time I try to do something - especially when the main purpose of the exercise is to learn.

I run Home Assistant in a VM and I worked out I can virsh console hass and then docker exec -it homeassistant sh. I think there’s maybe a sshd addon I could use and there is also the File Editor addon.

I guess I’ve answered my own question, and maybe I just wanted to have a rant about being “forced” back into the Microsoft ecosystem in order to develop for Home Assistant - but I would be interested to learn about other options.

  • Great Blue Heron@lemmy.caOPEnglish
    2·
    10 hours ago

    Yeah, I’m just learning that now. Devcontainers is great because it runs a full instance of Home Assistant for debugging and test. There is DevPod Containers that might do the same thing, but I don’t use DevPod so it’s also a bit overwhelming (using that word a lot today…) to get going and I’m not sure if it’s compatible with the devcontaiers configuration in the Home Assistant dev tree.