Nest / WiFi Adventure

I've been merging my IoT and AV class C networks into 1 class B network so the automation can talk to the home entertainment devices easier and bring back order to my IP addresses for better filter of what has access to what. For the most part it has just been tedious updating the info close to 200 devices. While I was reconfiguring the house WiFi APs (Access Points) , I set them to enable roaming (AP swap you off to closest AP automatically) which in the case of Unifi APs assumes WAP2 encryption. Most devices handled this just fine but others had a real problem with it. For instance my wired (AC powered) Nest Protect continued to work fine but the battery powered one and the thermostat, in the house, both switched to the shop network I had not changed yet. So technically they were connected but not with enough signal to actually work. Some devices just reconnected no problem while others required a reboot, reconfig or, as in the case of the Nests, flat out refused to connect. So I've had to forget the roaming / zero hand off setup and use a configuration that support multiple encryption methods.

Note to self, NEVER make changes within an hour of bed time.

Went to move my house Z-NET onto the new network as the last thing before bed. Almost 3 hours later I'm back online. 😞 Part of the problem was according the the user forum all I needed to do to update the IP was restart Homeseer. When I did that it asked to install and update which I decided to do. Unfortunately I moved my instance to a SD awhile back to improve performance (the logging was killing the drive that also was recording security cam footage) and it seems the upgrade was confused and wiped most of my install and put a new instance on the old drive. Fortunately having a paranoid bent I backup my Homeseer instance every time the server is restarted so I was able to get a list of the files still in the folder newer than my back up saved off. Then I copied the files in form the new instance and finally the saved files back in. That sorted. I think at least. But it did not find the new IP for the Z-NET. Not surprising since I'm moving from 192.168.* IPs to 10.* IPs. After a bit of file scanning I found the IP needs changed in \Program Files (x86)\HomeSeer HS3\Config\Z-Wave.ini so after changing that and a restart I'm finally back in biz. Time for bed.