After spending quite some time trying to set up a brand new OH3 instance on Ubuntu using Docker or HyperV on a Windows 10 WSL2 instance, I decided to take a different approach. The process was filled with roadblocks, so I opted to upgrade my existing Windows OH box from version 2 to 3 ‘in place’ after a thorough backup. The official documentation made it seem manageable, but I was still on the lookout for any potential pitfalls, especially since most discussions I found were not specific to Windows.
One of my goals was to switch from MySql to PostgreSQL, with PostgreSQL running in a Docker container on separate hardware. While I was open to the idea of starting fresh and losing historical data, I was hopeful that preserving it wouldn’t be too difficult. I assumed this would be best handled after the upgrade. Additionally, I wanted to transition away from using .items and .things files, opting instead to manage everything through OH’s database for a cleaner setup.
Another aspect of the upgrade involved replacing my old HS Z-stick with the new Aeotec Z-stick I purchased for this project. I was aware that this would likely need to be done post-upgrade. Throughout this process, I was curious about any potential issues or warnings others might have encountered, especially regarding the ‘upgrade in place’ method and its impact on adapting to the semantic model.
Overall, while the journey has been challenging, it’s been incredibly rewarding to see how the new features and improvements in OH3 can enhance my home automation setup. I’m particularly excited about the potential for more seamless integration and better organization of my devices and rules. If anyone has tips or experiences to share, especially regarding PostgreSQL migration or optimizing the new database approach, I’d be more than happy to hear them!