# Google Nest SDM

**URL:** <https://community.homey.app/t/google-nest-sdm/43087>\
**Category:** Apps\
**Tags:** tools\
**Created:** [February 16, 2021, 10:48am UTC](https://community.homey.app/t/google-nest-sdm/43087 "2021-02-16T10:48:22Z")\
**Posts on this page:** 20\
**Page:** 23

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 13, 2022, 8:51pm UTC](https://community.homey.app/t/google-nest-sdm/43087/467 "2022-04-13T20:51:39Z")

</div>

What new cam and doorbell type are you using? Battery, wired?

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 13, 2022, 9:40pm UTC](https://community.homey.app/t/google-nest-sdm/43087/468 "2022-04-13T21:40:54Z")

</div>

I have the same thing for battery type devices, if there is motion and a person detected it only sends the person event.  
When you disable in the home app the person detection it will send the motion.  
There should not be a connection with 6.1 version of the app.

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 14, 2022, 7:01am UTC](https://community.homey.app/t/google-nest-sdm/43087/469 "2022-04-14T07:01:55Z")

</div>

Hi Erwin, I will change the behaviour for the newest devices a bit, when a person event happens I will start a motion event as well, this way a zone will become active for 10 seconds.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [April 14, 2022, 7:47am UTC](https://community.homey.app/t/google-nest-sdm/43087/470 "2022-04-14T07:47:15Z")

</div>

Can someone with Google Nest protect confirm or share his experience ?

- I got no Manual test Active ever triggered even when performing manual test - smoke alarm does seems working (CO nor Heat didn’t tested yet 😉 )
- battery is reporting 100% even after 2 years ?

Naturally the official app do not provide any details on top - battery state just OK/KO, etc.

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 14, 2022, 8:13am UTC](https://community.homey.app/t/google-nest-sdm/43087/471 "2022-04-14T08:13:40Z")

</div>

Just tested it again, for me manual test works, with both Start and End trigger.  
Battery is a battery alarm, not measure, so indeed should be OK/NOT OK. Just noticed that the battery display gives you also the measure option, that is not good, will look into it.

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 14, 2022, 8:17am UTC](https://community.homey.app/t/google-nest-sdm/43087/472 "2022-04-14T08:17:41Z")

</div>

Have been testing to get a meaningful reading for battery level. Capability is still in the device, will remove it with a next revision

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [April 14, 2022, 10:59am UTC](https://community.homey.app/t/google-nest-sdm/43087/473 "2022-04-14T10:59:21Z")

</div>

> [@Martin\_Verbeek](#):
>
> Just tested it again, for me manual test works, with both Start and End trigger.

Thank you - hm, maybe I’m not testing it right ?

I created test flow with one trigger, no condition :

 ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/7/172c112336cb7e7f6347025bf8b7e3b4948b9b4a.png)

I initiated successfully manual checks :

 ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/5/e5bebdc23f0408bc71ee8ed2f1aee1d57a7a262e.jpeg)

The manual check tags and the flow hasn’t been triggered.

 ![obrazek](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/c/fc22e129ffec03871a8baec87dcd1fea6f085e43.png)

It’s not a big deal just the problem is that with battery on 100% and values not getting updated, I have no idea if the integration actually works or not - or can’t test it, until some real alarm - which already happened, to I know it works but still… 😉

Actually maybe I’m not connected anymore ?

```auto
022-04-14 11:03:44 Unhandled Rejection at: Promise { TypeError: Cannot read properties of undefined (reading 'transport_url') at NestLegacyClient.getNESTAuthenticate (/lib/NestLegacyClient.js:195:35) at processTicksAndRejections (node:internal/process/task_queues:96:5) } reason: TypeError: Cannot read properties of undefined (reading 'transport_url') at NestLegacyClient.getNESTAuthenticate (/lib/NestLegacyClient.js:195:35) at processTicksAndRejections (node:internal/process/task_queues:96:5)

```

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 14, 2022, 11:12am UTC](https://community.homey.app/t/google-nest-sdm/43087/474 "2022-04-14T11:12:57Z")

</div>

Could you pm me a bigger chunk of the log? Is this a wired Protect?

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [April 14, 2022, 11:19am UTC](https://community.homey.app/t/google-nest-sdm/43087/475 "2022-04-14T11:19:41Z")

</div>

So I requested again NEST Protect Code and indeed it become broken - so another test was successful, the trigger has been triggered but the value in the Nest Protect didn’t get updated anyway.

**I wonder why I become broken and how can I check it then ;-(**

Btw the code was all that was there, there were some olders logs but I believe they were too old. Anyway if interested, I can PM it for sure.

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 14, 2022, 11:40am UTC](https://community.homey.app/t/google-nest-sdm/43087/476 "2022-04-14T11:40:10Z")

</div>

Yes interested…how long ago was the code requested…should not be an issue, but then again 😁

Martin Verbeek

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [April 14, 2022, 11:45am UTC](https://community.homey.app/t/google-nest-sdm/43087/477 "2022-04-14T11:45:24Z")

</div>

A ! Manual test updated just now (time stamp)…it took some time, it’s working. 😉

So now I wonder why I lost access if it’s maybe expiring… no idea ;-(

The access has been granted the same day you integrated Legacy Nest , it’s not so long time ago… I will need to think how to ensure if it gets broken, I will know.

---

<div class="post-metadata">

**Author:** ![Alfred\_Nyhus](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alfred_nyhus/32/54183_2.png) [@Alfred\_Nyhus](https://community.homey.app/u/Alfred_Nyhus)\
**Post date:** [April 17, 2022, 9:03pm UTC](https://community.homey.app/t/google-nest-sdm/43087/478 "2022-04-17T21:03:20Z")

</div>

Nest Protect battery not work for me

 ![Screenshot_20220417-205354](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/a/bad0e8aa87537a7a35628b75194ed759fd2980b3.jpeg)

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 17, 2022, 9:15pm UTC](https://community.homey.app/t/google-nest-sdm/43087/479 "2022-04-17T21:15:35Z")

</div>

These are the messages you get when you install the nest protect. What is not working?

Martin Verbeek

---

<div class="post-metadata">

**Author:** ![Alfred\_Nyhus](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alfred_nyhus/32/54183_2.png) [@Alfred\_Nyhus](https://community.homey.app/u/Alfred_Nyhus)\
**Post date:** [April 18, 2022, 9:52am UTC](https://community.homey.app/t/google-nest-sdm/43087/480 "2022-04-18T09:52:38Z")

</div>

when i test the smoke alarm, i do not get push alert, doors do not unlock and nothing from Nest mini

[https://homey.app/no-no/flow/DO6NU0/](https://homey.app/no-no/flow/DO6NU0/)

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 18, 2022, 3:32pm UTC](https://community.homey.app/t/google-nest-sdm/43087/481 "2022-04-18T15:32:44Z")

</div>

That’s not good. Could you retry and send me the log ?

Martin Verbeek

---

<div class="post-metadata">

**Author:** ![Alfred\_Nyhus](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alfred_nyhus/32/54183_2.png) [@Alfred\_Nyhus](https://community.homey.app/u/Alfred_Nyhus)\
**Post date:** [April 18, 2022, 8:28pm UTC](https://community.homey.app/t/google-nest-sdm/43087/482 "2022-04-18T20:28:38Z")

</div>

```auto
<small>2022-04-18 22:26:55 checkOnCloud() Not authenticated</small>
<small>2022-04-18 21:54:04 onOAuth2Init() settings enableDebug true</small>
<small>2022-04-18 21:54:03 onOAuth2Init() settings enableDebug false</small>
<small>2022-04-18 21:53:24 checkOnCloud() Not authenticated</small>
**(node:5406) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 7)**
**(node:5406) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'forEach' of undefined at NestApp.firstDataNestProtect (/app.js:258:24) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async NestApp.getDataNestProtect (/app.js:276:30) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5)**
<small>undefined-Invalid Date-undefined undefined ponse NOT Okay and JSON { error: 'access_denied', error_description: 'permission denied', instance_id: 'ec44fabc-eee7-4349-ab71-311df00155cd' }</small>
**(node:5406) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)**
**(node:5406) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'forEach' of undefined at NestApp.firstDataNestProtect (/app.js:258:24) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async NestApp.getDataNestProtect (/app.js:276:30) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5)**
<small>undefined-Invalid Date-undefined undefined ponse NOT Okay and JSON { error: 'access_denied', error_description: 'permission denied', instance_id: '7686f02a-539c-4997-a7c6-64b0fd83c69b' }</small>
**(node:5406) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5)**
**(node:5406) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'forEach' of undefined at NestApp.firstDataNestProtect (/app.js:258:24) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async NestApp.getDataNestProtect (/app.js:276:30) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5)**
<small>undefined-Invalid Date-undefined undefined ponse NOT Okay and JSON { error: 'access_denied', error_description: 'permission denied', instance_id: '7e885b17-d7b9-4883-ac2d-1b8f0aeff134' }</small>
<small>2022-04-18 12:24:13 checkOnCloud() Not authenticated</small>

```

---

<div class="post-metadata">

**Author:** ![Alfred\_Nyhus](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alfred_nyhus/32/54183_2.png) [@Alfred\_Nyhus](https://community.homey.app/u/Alfred_Nyhus)\
**Post date:** [April 18, 2022, 8:30pm UTC](https://community.homey.app/t/google-nest-sdm/43087/483 "2022-04-18T20:30:45Z")

</div>

```auto
**(node:5406) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)**
**(node:5406) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'forEach' of undefined at NestApp.firstDataNestProtect (/app.js:258:24) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async NestApp.getDataNestProtect (/app.js:276:30) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5)**
<small>undefined-Invalid Date-undefined undefined ponse NOT Okay and JSON { error: 'access_denied', error_description: 'permission denied', instance_id: '6d83d289-4b78-4a27-b4c2-c166d5ed72e3' }</small>
**(node:5406) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)**
**(node:5406) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'forEach' of undefined at NestApp.firstDataNestProtect (/app.js:258:24) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async NestApp.getDataNestProtect (/app.js:276:30) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5)**
<small>undefined-Invalid Date-undefined undefined ponse NOT Okay and JSON { error: 'access_denied', error_description: 'permission denied', instance_id: '99451cf5-f796-40d7-8c84-aefbc73c34b0' }</small>
**(node:5406) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)**
**(node:5406) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'forEach' of undefined at NestApp.firstDataNestProtect (/app.js:258:24) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async NestApp.getDataNestProtect (/app.js:276:30) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5)**
<small>undefined-Invalid Date-undefined undefined ponse NOT Okay and JSON { error: 'access_denied', error_description: 'permission denied', instance_id: '4caccec3-ecef-434e-b4ae-ada0057cec21' }</small>
**(node:5406) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.**
**(node:5406) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)**
**(node:5406) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'forEach' of undefined at NestApp.firstDataNestProtect (/app.js:258:24) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async NestApp.getDataNestProtect (/app.js:276:30) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5)**
<small>undefined-Invalid Date-undefined undefined ponse NOT Okay and JSON { error: 'access_denied', error_description: 'permission denied', instance_id: '80f6992c-c3d4-47f6-b40b-7ff27eba9181' }</small>
<small>2022-04-18 12:18:12 Error: 9999 at NestLegacyClient.getNESTUpdatedData (/lib/NestLegacyClient.js:267:12) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async NestApp.getDataNestProtect (/app.js:284:4) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) at async NestApp.getDataNestProtect (/app.js:295:5) getDataNestProtect() Error during subscribing</small>
<small>undefined-Invalid Date-undefined undefined ot Okay Response { size: 0, timeout: 0, [Symbol(Body internals)]: { body: PassThrough { _readableState: [ReadableState], readable: true, _events: [Object: null prototype], _eventsCount: 2, _maxListeners: undefined, _writableState: [WritableState], writable: false, allowHalfOpen: true, _transformState: [Object], [Symbol(kCapture)]: false }, disturbed: false, error: null }, [Symbol(Response internals)]: { url: 'https://czfe23-front01-iad01.transport.home.nest.com/v6/subscribe', status: 400, statusText: 'Bad Request', headers: Headers { [Symbol(map)]: [Object: null prototype] }, counter: 0 } }</small>
<small>2022-04-18 12:18:11 Invoke updateDevicesNestProtect</small>
<small>undefined-Invalid Date-undefined undefined ponse NOT Okay and JSON { error: 'access_denied', error_description: 'permission denied', instance_id: 'c2303bef-001e-4707-ad14-d39c70117368' }</small>
<small>2022-04-18 12:13:15 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 12:11:51 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 12:09:39 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 12:06:22 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 12:06:12 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 12:02:31 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 12:00:22 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:55:16 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:55:03 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:53:44 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:50:43 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:50:06 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:47:18 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:45:38 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:39:12 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:37:53 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:37:18 Invoke updateDevicesNestProtect</small>
<small>2022-04-18 11:</small>

```

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 19, 2022, 5:26am UTC](https://community.homey.app/t/google-nest-sdm/43087/484 "2022-04-19T05:26:57Z")

</div>

I think I see what is happening, there will be a update version today or tomorrow that should fix this…

Martin Verbeek

---

<div class="post-metadata">

**Author:** ![Alfred\_Nyhus](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alfred_nyhus/32/54183_2.png) [@Alfred\_Nyhus](https://community.homey.app/u/Alfred_Nyhus)\
**Post date:** [April 19, 2022, 6:12am UTC](https://community.homey.app/t/google-nest-sdm/43087/485 "2022-04-19T06:12:48Z")

</div>

Thanks 😃

---

<div class="post-metadata">

**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\
**Post date:** [April 19, 2022, 3:30pm UTC](https://community.homey.app/t/google-nest-sdm/43087/486 "2022-04-19T15:30:03Z")

</div>

6.2.0 is on the store, could you do me a favor and test it as well? Please wait at least 1 hour before testing, that is access token expiration cycle.

“6.1.1”: “Problem in Legacy Nest auth and Update of data, remove battery measure for nest protect, add a clear log button”

“6.2.0”: “Implement workaround for Hub Max missing events, this is now retrieved via Legacy interface. Now showing images and triggering on motion/person etc”

To get the Hub Max to work, you need to get a Nest Legacy code set up. You can do that in the configure App, go to the Legacy Nest tab and “request” (copy) and “save”

[Previous page](https://community.homey.app/t/google-nest-sdm/43087.md?page=22)

[Next page](https://community.homey.app/t/google-nest-sdm/43087.md?page=24)