Restart your Google Nest Wifi, Nest Wifi Pro or Google Wifi network from Homey, and plan it the way you want: every night, when the house is empty, or only when nobody is streaming.
Many Nest Wifi users see speeds drop after a few days, and a restart brings them back. The Google Home app has no scheduled restart, so this app adds one to Homey.
Unofficial app, use a separate Google account. Google has no public API for Nest Wifi. The app signs in the same way the Google Home app does, and Google may lock an account used like this. Create a new Gmail account, invite it as Admin to your home in the Google Home app, and sign in with that account. The app includes a step-by-step guide.
What it does
Restart the whole network from a Flow, the device or the configuration page. This is the same as Restart network in the Google Home app.
The app confirms that the network actually went down and came back, and tells your Flows whether the restart was confirmed or failed.
Only one command is sent per restart, and a minimum time between restarts protects against Flows that fire twice.
Restart a single mesh point while the rest of the network stays online.
Run a speed test, pause internet for a device, and prioritize a device.
Presence (optional, off by default): triggers when a chosen device connects or disconnects, and when a new device joins the network.
Device: internet status, connected devices, mesh points online and the latest speed test, with Insights.
Configuration page:
all mesh points with IP address, model, firmware, backhaul and mesh speed
every device with IP, mesh point, band and live traffic
internet and LAN details, including your public IP
port forwarding and speed test history
a log of restarts and outages
Flow cards
When
restart started / confirmed / failed · mesh point restarted · speed test finished · internet down / back · device connected / disconnected · new device
And
internet online · restart in progress · restart allowed now · traffic below X Mbit/s · device connected · device paused · speed test running
Then
restart the whole network · restart a mesh point · run speed test · pause / resume a device · prioritize a device / stop prioritizing
Example: every day at 04:00, if nobody is home and traffic is below 1 Mbit/s, restart the whole network.
Setup
Install the app and open its configuration page.
Follow the guide to create a separate Google account, then sign in once:
Open Google’s sign-in page in a desktop browser and sign in.
Copy a one-time cookie (oauth_token) and paste it in.
Your password is never seen, and the sign-in token stays on your Homey.
Add a device: Devices → + → Google Nest Wifi Controls → Wifi network, then pick your network.
Being gentle on your Google account
Network status is read only every 10 minutes by default.
Connected devices are read every 10 minutes (adjustable).
Presence is opt-in.
The app stops all calls to Google as soon as the sign-in is rejected.
Requirements
Homey Pro. The app runs locally.
Tested with Nest Wifi Pro and Google Wifi. Nest Wifi (2019) uses the same Google cloud service; reports are welcome.
Credits
The restart method was found by nest-rebooter by Joep Prijsman. The sign-in is ported from gpsoauth by Simon Weber. Both are MIT licensed. Thank you!
v0.3.7: Connected devices and mesh links are now read every 10 minutes by default (was 30), so the device and Insights follow the network more closely.
v0.3.6: Removed Download now and Upload now from the device: they were only a 30-minute snapshot. The configuration page and the traffic Flow condition still use live traffic.
v0.3.5: Renamed to Google Nest Wifi Controls, to make clear that it adds control to Nest Wifi, Nest Wifi Pro and Google Wifi.
v0.3.4: Connected devices, mesh links and traffic now show on the device and in Insights again: they are read every 30 minutes (adjustable in the device settings) and whenever the configuration page or a Flow fetches them.
v0.3.3: Tested and confirmed on Google Wifi as well as Nest Wifi Pro.
v0.3.2: Polished English texts. The app is available in English and Norwegian and follows your Homey’s language.
v0.3.1: Step-by-step guide for creating a separate Google account, in pairing and on the configuration page.
v0.3.0: Gentler on your Google account: network status every 10 minutes, live data only when needed, presence is opt-in, longer minimum times between restarts and speed tests, and back-off after errors. Clear advice to use a separate Google account.
v0.2.0: Restart a single mesh point, run speed tests, pause and prioritize devices, presence triggers per device and a trigger for new devices. Shows your public IP. Stops all calls to Google at once if the sign-in is rejected, and updates every 2 minutes by default.
v0.1.4: Configuration page redesigned for narrow windows: lists instead of wide tables, no sideways scrolling.
Earlier the same day (4)
v0.1.3: Cleaner configuration page: compact account line, tabs that fit, combined speed tile. Google tips removed.
v0.1.2: Fixed: adding a network showed a blank screen after signing in.
v0.1.1: New logo in Google colours with a clearer restart arrow.
v0.1.0: First test version: restart the network from Flows with confirmation, live status and a full network overview on the configuration page.
Later updates are posted as replies in this thread, one post per day.
Thanks Abe, and no offence intended. I didn’t mean to step on anyone’s toes!
I usually make apps for the things I’m missing in Homey. Local status of the access points isn’t something I need much in my setup, but being able to control the network was: restarting it at night or when nobody’s home, restarting a single point, running a speed test or pausing a device. So the idea was an app that complements yours, not one that competes with it.
It’s still early days. I haven’t tested it over a longer period yet, so time will show how well it holds up.
About merging: the two work quite differently. Mine signs in to Google with a separate account, yours doesn’t need an account at all, so I think they’re easier to keep apart. And since mine also shows whether the network and the mesh points are online, it might honestly make more sense the other way round than putting mine into yours. To make the difference clearer I’ve renamed mine to Google Nest Wifi Controls. Yours could perhaps be Google Nest Wifi Info?
I totally understand that your app might be a better fit for your specific use case. However, in that case, it might make more sense to keep it for private use. After all, you’re now publishing it to a public App Store where everyone will be able to use it
In general, we try to stick to a single app per brand or device. This makes it easier for users to find the right app for their products, rather than having to choose between multiple apps that essentially support the same devices.
My app already has a few thousand users, so merging things the other way around would be quite difficult, as it could break the integration for a lot of existing users.
That being said, I’m always open to looking at how we can combine the best of both apps. So feel free to reach out if you’re interested in working together on this!
I’m not a developer by trade. I build these apps to scratch my own itch, with a lot of help from AI tools along the way. I’ve installed your app to compare, and as far as I can see it mainly tells me when a point or the internet goes down. Mine is built to actually do something about it, and to show what’s going on in the network: restarting the whole network or a single point with confirmation that it came back, speed tests, pausing or prioritizing devices, connected devices, and Flows to automate it all.
So I see them as two different apps for two different needs rather than duplicates. Yours is for local monitoring without any account, mine is for control. I’d like to keep developing mine and submit it to the App Store once it has proven itself over some time, of course with the same clear warning about using a separate Google account.
Just to be clear on one thing: the projects I built on (nest-rebooter and gpsoauth) are open source, but my app itself isn’t. How it all fits together is my own work, including confirming that a restart actually worked, the safeguards to protect the Google account, the Flow cards and the overview. So if control features ever end up in your app based on what I’ve built, I’d expect that to happen together with me and with credit, not on its own.
I’m still open to working together, and we can talk about how. Thanks again for reaching out!
v0.3.11: Polished texts in pairing, on the configuration page and in Flow card hints.
v0.3.10: The App Store page is now in English only. The app itself is still available in English and Norwegian.
v0.3.9: The Nodes tab on the configuration page now shows the IP address of each mesh point.
v0.3.8: Mesh links is replaced by Mesh points online (for example 6), read from the status the app already fetches. Google’s mesh link count jumps around even when every point is fine.
A small update, and a change of direction. I’m winding this Wifi only app down to build something bigger: a single Controls app that brings the things you normally manage in the Google Home app into Homey and your Flows.
It starts with two. Your Google Nest Wifi (restart, schedule, monitor, all of it) and your Nest cameras. From there the plan is to keep adding the other Google Home devices over time, so one app covers them instead of a separate app per thing.
Thanks to everyone who tried this one and gave feedback, and thanks to Abe for the kind offer to team up. I’ll share the new app once it’s ready. The test version linked above will stop being updated.
Unofficial app, use a separate Google account. Google has no public API for Nest Wifi. The app signs in the same way the Google Home app does, and Google may lock an account used like this. Create a new Gmail account, invite it as Admin to your home in the Google Home app, and sign in with that account. The app includes a step-by-step guide.
