[APP][Pro] Google Nest Wifi - Mesh wifi from Google

Apps
,
1

Google Nest Wifi - Mesh wifi from Google

Central topic for questions/discussing the Google Nest Wifi App. You can use this topic to ask questions and share your experiences with the Google Nest Wifi devices.

This app supports Google OnHub routers (by TP-Link and Asus), as well as Google Wifi, Nest Wifi, and Nest Wifi Pro.

:warning: The app should automatically detect the correct model of your Google Nest Wifi device and adjust the device icon and power usage accordingly. If it doesn’t, please generate and submit a diagnostic report.

2

Just installed it!

What functions are exposed by Google?

Or will this forever be to only if the wifi points themselves are connected?

3

Awesome! Which Google Nest Wifi products are you using? It took a bit of guesswork to figure out the right product names for automatic detection during pairing. Let me know if your devices are recognized automatically and have the right device icons.

The available data is quite limited and only provided over LAN. You can actually view it yourself by opening http://DEVICEIP/api/v1/status in your browser.

4

I currently have 4 Google Nest Wifi Pro’s and the icons are correctly set

5

Hi, thanks for this app!

I have Google Nest WiFi, two routers and two satellite. The satellite works as AP and one of the router is also AP but connected with cabel to the main unit.

I can add all of them in the app but I only get status for the two routers, not the AP.

Are they not supported?

Accesspoint

IMG_1065
IMG_10651170×2532 162 KB

Router

IMG_1066
IMG_10661170×2532 170 KB

6

Hi all,

I’ve pushed two updates today (v0.1.3 to stable and v0.2.0 to test) that address a couple of issues and improvements.

v0.1.3
The second-gen Nest Wifi Router and Nest Wifi Point weren’t being recognized correctly due to a misinterpretation of their internal codenames. This has now been fixed, and both devices should be detected properly with the correct icons in Homey.

v0.2.0
I also revisited the implementation of the alarm_connectivity capability. Previously, this was based on the online status from the Nest Wifi API, but it turns out this reflects the WAN connection rather than the device itself.

To fix this, I’ve introduced a new capability: alarm_wan, which triggers when the WAN port is disconnected.

The alarm_connectivity capability has been updated and will now appear as “Device Offline” in the sensor overview. It will only trigger when the device can’t be reached on the network. If this state persists for 24 hours, the device will be marked as unavailable by Homey.

Happy testing! :smile:

7

Just installed Google Nest wifi at home. Discovered this app and I’m wondering… what do you use it for?

8

Hi!

I still don’t get the Satellite AP to work, they are added but always report to be offline. Tried to re-add but no luck. Any ideas?

9

Hi! You can only have a single router within the Google Mesh network. All the other units will act like access points (satellites), either connected wirelessly or via cable to the main unit.

Could you visit http://<IP address>/api/v1/status in your browser for the units which are running as satellites and let me know what data you get?

10

Alright, so the issue might be that I have two routers and two AP, but one of the router is acting as a AP through cable?

This is what I get from one of the AP.

{
   "dns": {
      "mode": "automatic",
      "servers": [  ]
   },
   "setupState": "GWIFI_OOBE_COMPLETE",
   "software": {
      "blockingUpdate": 1,
      "softwareVersion": "1.56.514310",
      "updateChannel": "stable-channel",
      "updateNewVersion": "0.0.0.0",
      "updateProgress": -1.0,
      "updateRequired": false,
      "updateStatus": "idle"
   },
   "system": {
      "countryCode": "NO",
      "groupRole": "leaf",
      "hardwareId": "vento-b4",
      "lan0Link": false,
      "ledAnimation": "CONNECTED",
      "ledIntensity": 100,
      "modelId": "VENTO",
      "oobeDetailedStatus": "OOBE_PROCESSING_PLATFORM_FINALIZATION_START",
      "uptime": 28514
   },
   "vorlonInfo": {
      "migrationMode": "voobed"
   },
   "wan": {
      "captivePortal": false,
      "ethernetLink": false,
      "invalidCredentials": false,
      "ipAddress": false,
      "online": false,
      "pppoeDetected": false,
      "vlanScanAttemptCount": 0,
      "vlanScanComplete": false
   }
}
11

Hi Doekse,

I think I’ve found an issue with satellite/leaf devices in Google Nest Wifi app v0.2.0 on Homey Pro 2026.

All my Nest Wifi satellite access points are online and working normally, and Homey also reports Device Offline = false.

However, Homey shows their uptime as “Offline”.

For example, “Nest tvättstuga” currently shows:

  • Device Offline = false

  • WAN disconnected = true

  • Uptime = Offline

But its local /api/v1/status response clearly reports:

  • system.groupRole = "leaf"

  • system.ledAnimation = "CONNECTED"

  • system.uptime = 562322

  • wan.online = false

So the device is a connected mesh leaf and has an uptime of about 6 days 12 hours 12 minutes, despite Homey displaying “Offline”.

The main Nest Wifi router does not have this problem. It currently reports its uptime normally in Homey.

It therefore looks like the uptime capability may still be conditional on wan.online. For a leaf/satellite, wan.online = false appears to be normal and should not make its uptime display as Offline.

Full /api/v1/status response:

{
“dns”: {
“mode”: “automatic”,
“servers”: []
},
“setupState”: “GWIFI_OOBE_COMPLETE”,
“software”: {
“blockingUpdate”: 1,
“softwareVersion”: “1.56.514310”,
“updateChannel”: “stable-channel”,
“updateNewVersion”: “0.0.0.0”,
“updateProgress”: -1.0,
“updateRequired”: false,
“updateStatus”: “idle”
},
“system”: {
“countryCode”: “NO”,
“groupRole”: “leaf”,
“hardwareId”: “vento-b4”,
“lan0Link”: false,
“ledAnimation”: “CONNECTED”,
“ledIntensity”: 100,
“modelId”: “VENTO”,
“oobeDetailedStatus”: “OOBE_COMPLETE”,
“uptime”: 562322
},
“vorlonInfo”: {
“migrationMode”: “weave_all”
},
“wan”: {
“captivePortal”: false,
“ethernetLink”: false,
“invalidCredentials”: false,
“ipAddress”: false,
“online”: false,
“pppoeDetected”: false,
“vlanScanAttemptCount”: 0,
“vlanScanComplete”: false
}
}

I have four leaf devices showing the same behavior.

12

Thanks for letting me know! I’ll look into this.