In troubleshooting this, I found that the thermostat wifi configuration can be manually set using the google home app, but unfortunately since they are on a "different" network, they can't be accessed. Isuspect they are configured in this alternative address space. I've repeatedly "successfully" configured the thermostat wifi, but they remain invisible to the app, nest services, and my network. For all of my other devices affected by this issue, I've gone in to manually set the IPV4 address, DNS server and router addresses, and they were able to connect. My two nest thermostats fall into this category. Unfortunately for some reason, when new devices are added to the wifi, many of them connect to the network but with an out of range IP address based on the previous router, so while they are connected to the radio, they have no internet access nor are they visible on the network in the correct address range. Sounds like everything should be great, right? When I had problems with that router and a second brand, I decided to switch to Google Nest mesh. When I configured the new router, it assigned IP addresses starting with 10.x.x.x rather than 192.168.1.x as is customary. this worked fine for years, but my primary router started to fail so I replaced that with another brand. Many thanks to everyone who contributed and answered my questions! I appreciate that a lot.My original wifi infrastructure had two wireless routers, one configured as an AP connected by ethernet to the primary router.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |