Dockerized Home Assistant to Home Assistant Yellow

This past week, I transitioned from a self-hosted Home Assistant on Docker to a Supervised Home Assistant powered by Home Assistant Yellow. Unfortunately, I did not know the delay the POE (Power over Ethernet) unit would have, but I thought it was worth it because POE is perfect for this appliance.

A little background is that Home Assistant Yellow is a hardware appliance that runs the open-source Home Assistant home automation platform. It is designed to be plug-and-play, support thread, matter and Zigbee. In addition POE (Power over Ethernet) capability eliminates the need for a separate power source, making it even more convenient to install.

The process of transitioning from a self-hosted Home Assistant on Docker to a Supervised Home Assistant powered by Home Assistant Yellow and POE is straightforward. I backed up my current configuration and data. Then, I transferred configuration to the new setup and restarted Home Assistant. I would say it discovered nearly 95% of my devices correctly & did a fantastic job of transitioning automation and configurations over. However, there can be some challenges when it comes to Z-wave devices. Due to the nature of Z-Wave, transitioning platforms is hard because there are entries in Home Assistant, Z-Wave JS, and on the physical Z-Wave controller. Despite my best efforts, I have to exclude and include some devices again. It appears as though Z-Wave 700 Series is significantly more affected, and I have no idea why.

Overall, transitioning from a self-hosted Home Assistant on Docker to a Supervised Home Assistant powered by Home Assistant Yellow and POE was smooth, easy, and seamless process with the exception of Z-wave devices. The Home Assistant Yellow and POE setup offers the convenience of plug-and-play installation and eliminates the need for a separate power source. I’m taking this as an opportunity to ensure that all of my devices have S2 enabled, as well as a perfect time to replace batteries and test automation.

Leave a Reply

Your email address will not be published. Required fields are marked *