grumblez

Fortunately all of their lights work over a standard Zigbee connection. No need for a Hue Hub or App at all. I was already transitioning my lights from using the Hue Hub/App to directly connecting via Zigbee/HomeAssistant before this was announced.

Yeah that's covered in the article, but only applies to subdivisions of more than 5 houses. So the builders build larger anyway with ownership hidden in a shell game of LLCs to get around the regulation and build without that 100 year water supply.

The issue there is that G-Suite's OAuth2 implementation doesn't yet support PKCE.

Hi. ZT team member here.

Networks members will continue to be able to communicate with the controller down as long as they were online before the controller went down. Not a full solution, I know.

Otherwise, it's a difficult problem to solve. The only way we could let you run a network controller as a back up right now would be to give you the private key for the controller, which would allow you to change everybody else's network on that controller, too. Not the best of ideas giving that info away!

There was interruption between GCP's monitoring & services on GCP. I also have my own Prometheus/Grafana stack in there and it kept chugging along fine, even though their DB graphs show severe dips in tx/sec in the time period in question.

Actually, looks like it was something between their monitoring system & the DB. Per my prometheus stats, DB kept chugging along the whole time.

Judging by the tx/sec count on a database I have hosted in us-west2, looks like their network backplane went up & down a few times between 5:58pm and 6:21pm tonight

"lesser known" as in protocols such as IPSec, ZeroTier, WireGuard, etc. Of which IPSec has been around forever and many NATs/Firewalls have special handling rules built in, just as @api mentioned in another comment. Yes, ZeroTier uses UDP underneath, but that doesn't mean symmetric NATs don't/won't cause havoc to peer to peer protocols using UDP.

If all sites are behind symmetric NATs, there's not much ZeroTier could do to help aside from telling him to assign direct mappings on the NAT/Firewall to each ZT instance. Symmetric NATs are antithetical to peer to peer communication. Many I've run across in the wild have special rules to handle IPSec which won't exist for other lesser known protocols. It's also possible the user wasn't willing or able to make network configuration changes to make those p2p connections possible. Without seeing what the user tried & support recommended, it's not really fair to throw out such baseless accusations.

Your physical network settings likely didn't allow direct connections between peers. Fix that and it'll work fine.

Breaking News: Advertisers concerned feature is working as advertised.

That's good to know. What confuses me is why they're saying "We continue to experience high levels of network congestion in the eastern USA", when I'm in us-west2 (Los Angeles) and none of my CloudSQL instances, nor is my k8s cluster showing up or contactable...