If your house is like mine you have some rooms that run a little hotter than others (especially if you have servers running). Because of this the need to monitor temperature readings in rooms became a little more important, now there’s a multitude of different ways to tackle this problem but this is by far the cheapest (although more time consuming on the front end) and doesn’t require any cloud services to keep it running. I’d be unfair if I didn’t mention some other good alternatives that use Zigbee/ZWave if you don’t want to go through all this (these are not affiliate links, im not that important).
HomeAssistant
So for some reason in v2021.7.0 HomeAssistant introduced a bug that breaks a lot of systems that rely on its NGINX reverse proxy add-on to provide ssl capabilities. Thankfully the fix itself is pretty simple.
To begin, try to navigate to the site to produce the error, then in the HAS web GUI navigate to the Supervisor Logs (Settings>System>Logs)
Grab the IP that shows up in the error that reads
So for some reason in v2021.7.0 HomeAssistant introduced a bug that breaks a lot of systems that rely on its NGINX reverse proxy add-on to provide ssl capabilities. Thankfully the fix itself is pretty simple.
To begin, try to navigate to the site to produce the error, then in the HAS web GUI navigate to the Supervisor Logs (Settings>System>Logs)
Grab the IP that shows up in the error that reads
So for some reason that Home Assistant OS virtual machine doesn’t really like being on certain versions of Vmware ESXI (typically older versions as I assume they do their testing as close to the newer releases as possible). I believe the issue stems from needing to change your virtual disk to IDE instead of SCSI which causes some underlying hard drive integrity issues that they didn’t plan for. Nonetheless, the fix is pretty easy and just takes a couple of minutes on your time and a Linux terminal (or any terminal that can SSH I guess).
After upgrading my Ubuntu Version and subsequently my kernel I tried running VMware Workstation Pro so I could access my VMs and kept running into the following error code when trying to open the application. Unfortunately, there was no way around it as rebooting, uninstalling/reinstalling, and anything else in my usual low-hanging fruit bag of tricks didn’t work so I had to really figure out what was really going on. Lets start with the actual error.