Been using the Venstar colourtouch T7900 for a while now and was very happy with it. But ever since configuring HomeAssistant with my local Certs/Authority (I run it all local only and access remotely via Wireguard), it won’t communicate with HA anymore. I updated the firmware and rebooted it and it came back for about a week but has since become unavailable again in HomeAssistant and rebooting fails to fix it anymore.

anyone else have this issue. or am I missing something here?

side note/context: I have both the thermostat and HomeAssistant configured with static IP addresses, if that matters at all.

  • @[email protected]English
    9•10 months ago

    I’m not sure what caused your problem, but I can tell you that I am using the Venstar integration with https, and it works fine for me. With that in mind, have you tried removing the thermostat from home assistant entirely, and then adding it back fresh?

    • @[email protected]OPEnglish
      2•10 months ago

      I tried that; it re-paired but then disappeared after about a day or so. Figure there is something going on with my NAT/Avahi setup, but this shouldn’t be an issue considering it worked before I added TLS. Maybe there is a setting in HA that I need to adjust.

      I’m not as familiar with the networking configuration options in HA. I’m assuming I have everything set up correctly since everything else works as intended. I’m running it as a VM in Proxmox and my background is in network development so naturally everything else on my network is installed in regular linux vms/containers behind nginx. Is there a specific config file for https or is it just the usual HA config file?

  • ScrubblesEnglish
    1•10 months ago

    Judy a hunch, but I wonder that if by enabling https it requires all statement calls to be https, and I am guessing the calls to your Ip are standard http.

    • @[email protected]OPEnglish
      2•10 months ago

      that’s a good point, didn’t think of that. I never saw any kind of setting on Venstar’s end to adjust any related settings (not surprised tbh). Maybe I can find something in HA to allow http calls for that device alone? I’m gonna look into that

      • @[email protected]English
        3•10 months ago

        If you’re only accessing HA locally, enabling https with a self-signing certificate will cause annoyance like this. I recommend just disabling https. If you still need https, you can terminate it using another webserver like nginx so you can still access the HA instance directly via http.

        • @[email protected]OPEnglish
          1•10 months ago

          yes, external termination is definitely ideal (I prefer https when possible as my browsers are set to reject http and it gets annoying with local stuff. plus I’ve got a local CA I use so it’s not a lot of extra work to set up).

          Thing is, I find HA a bit frustrating to configure, it’s not like the other linux LXCs/VMs I run on my proxmox so I’m not super familiar with installing stuff outside of the HA OS in that container. is the process any different than running nginx on any other distro?