It still sounds something specific to your own networking set up. If this was a general problem, i.e. ZC had to be on a “different network” then this forum would be chock-full of people complaining about the same issue.
Could it be something like the network your devices are on is a restricted one where they’re not allowed to see each other? Through a router firmware auto update or somehow something changing things there? Or someone else turned on some restrictions for a guest network? I’m pretty sure that ZC has no knowledge whatsoever of “networks” as such, as simply looks for a Zwift game app device somewhere locally.
I don’t have anything blocking anything on either router. Also, this worked perfectly before the update and as soon as the update happened it stopped working. So sure, there could be something slightly unique going on. But why won’t Zwift talk to the companion on the same wifi network as it has for the last 5 years? It’s only from a LOT of trial an error that I tried using a wifi network that I don’t even use (fully thinking it wouldn’t work for sure as it’s a totally different subnet). But sure enough, it works.
I’m suggesting there’s a bigger problem here, that if Zwift and the Companion app can’t talk to each other on the same WiFi network, there’s something wrong. But, sure, just ignore there’s a problem and wait for thousands of other people to have problems first.
Except that you appear to be the only person having this issue. My Zwift andZC talk to each other perfectly on the same network. This certainly appears to be something specific to your environment, as opposed to an issue on the Zwift side.
I don’t think this is answerable with the information provided. Maybe I could figure it out if I came to your home but I doubt the forum will sort it for you.
Have you already rebooted all of the networking equipment?
Basically you are reporting something that seems to contravene how it works, and you’re the only one I’ve ever heard report it. This does not mean you are wrong of course.
Yes everything is BT enabled. On that occasion I switched to ant+ because the Bluetooth wasn’t showing up on the pairing screen. And the again this morning, everything except the Saris trainer. Please let me have the old pairing option back. At least that worked.
I have seen more than a few reports from people who had to either reinstall or set aside prefs.xml and knowndevices.xml to reset pairing, after which it worked. Not sure if that’s you but I would try it.
I never had a problem before, and soon as the update happens it stops working. I have nothing blocking anything, yet Zwift and the Companion app won’t talk to each other on the same WiFi network. I’d bet others have problems too, they just haven’t surfaced yet.
I’ve got Zwift running on a MacOS connected to the same 5Ghz WiFi as my Android phone running the Companion App. I’ve got nothing blocking connections or any kind of firewall or unique routing. The Companion App can’t talk to Zwift. Both are running the latest version. It was working in the morning, Zwift updated on my MacOS, and then it wouldn’t work anymore. Everything has been shut down and restarted (Mac, Phone, wifi, etc.). I’ve uninstalled Zwift as well as the Companion App. I’ve also disconnected my mesh network so everything is connecting to the same physical router.
To not confuse anything, Zwift MacOS and Companion Android on the same WiFi are not working. But, Zwift on AppleTV (now updated to the new version) works fine with the companion on the same Android phone. It’s only the MacOS to Android where I have a problem. And the problem started as soon as I updated (worked earlier that morning, then didn’t in the afternoon).
My WiFi mesh network is a Netgear Orbi RBR40 (with RBS20 satellites, but same result with satellites turned off) set in router mode (fiber router is in IP Passthrough mode so Orbi does all the DHCP assignment). There’s no security or firewall settings turned on. No settings have been changed on the Orbi for a few years.
