Nest integration problems

ok, you confused me. Did you mean to say the Google issue tracker instead of github? other than what you posted, i would not know what to post there.

I can see where you posted in there but there is no response yet. In my setup, I only have 1 user(me) and 1 home. When I go into the “partner connections manager” i can see my devises there and grant the permissions.

I tried moving a device to a different room, no luck there.

If I create a new home, it requires a separate / new subscription. i cannot migrate to a new account either.

Yes sorry Google issue tracker. You should make your own post like I mentioned above, inviting them to engage with you about details of your account. They probably won’t respond to my post.

I created a ticket lets see if it gets any attention.

here is mine Google Issue Tracker

there is another 500 error one related to HA as well here, different issue-> Google Issue Tracker

I just received today an email from Google (they must be really hungry for money!)

We’re writing to inform you about a change to Cloud Pub/Sub message retention pricing, effective June 30, 2024. Starting on that date, we’ll begin charging for storing unacknowledged messages in subscriptions beyond the first 24 hours. Currently, there’s no charge for this within the default seven-day message retention period.

You won’t incur any new charges if:

  • Messages are processed within 24 hours.
  • Unacknowledged messages older than 24 hours are already retained through Topic Retention.

Please note that storage costs of $0.27 per GB-month will be charged after the first 24 hours (similar to other Pub/Sub storage offerings).

What do you need to know?

Starting June 30, 2024, customers will begin to incur charges for retaining unacknowledged messages with subscriptions for more than 24 hours. If you are able to process the messages within this time, you will not see any new storage charges.

What do you need to do?

Unacknowledged messages can result from idle subscriptions, backup needs, or slow processing. Avoid new charges by managing these scenarios as follows:

  1. Idle subscriptions - Delete idle subscriptions to avoid incurring subscription message retention charges.
  2. Backup storage - If you are using subscription retention as backup storage, you can enable an official storage option such Topic Retention or Retained Acknowledged Messages. For instance, Topic Retention will store messages just once at the topic level and they will remain available for all the subscriptions to consume when needed.
  3. Processing delays - Add more subscribers (if possible) to process the messages within a day.

Please note, the default message retention period remains seven days. You will only incur charges for unacknowledged messages that are stored with the subscription beyond 24 hours of publication.

@allenporter, I want to ask if the messages in the Nest integration are acknowledged according Google requires it? And how this can be confirmed?

1 Like

[Edited to simplify]

I saw this email as well and was worried everyone using nest with home assistant will get an email like this. No need to worry.

The default retention period for subscriptions created by nest is 15 minutes (code)

Have a look near the bottom of Google Nest - Home Assistant which has a link to the cloud console for pubsub subscriptions so you can verify yourself.

Some users may have manually created the subscription with different settings and so that’s up to them to figure out what they want to do about it.

2 Likes

So I gave this one more shot. I had to create a new account, remove all of my devices from the old account, now I’m adding them back to my new account. There must be some issue with my original migrated account. I was able to add a thermostat and camera to HA. Once this integration is setup, how do I add another device to it?

Next question. I have to instances of HA in two different homes. do I need to setup two different credentials?

All homes and devices on the same Google account? No you don’t need credentials. During the oauth process you can select the other home though the UI is weird/confusing. You can select devices from multiple homes and turn off what you don’t want added.

Edit: this matches my expectations that the account is setup weird. Unfortunate support couldn’t get it fixed for you.

All homes and devices on the same Google account?

yes ,all devices are configured in 1 home, in 1 account. physically, they are not in the same home.

I guess my main question was can I use the same credentials twice.

I wasted a lot of time with Google and got nowhere to fix my account they kept saying it was fine.

so I have broken my integration. I added a camera to my account now it fails.

I tried to delete it set it up again with no success. I don’t see anything in the logs.

when I hover over the “setup failed” it says internal server error 500

Logger: google.cloud.pubsub_v1.subscriber._protocol.streaming_pull_manager
Source: /usr/local/lib/python3.12/site-packages/google/cloud/pubsub_v1/subscriber/_protocol/streaming_pull_manager.py:131
First occurred: 5:12:17 PM (4 occurrences)
Last logged: 5:12:18 PM

Top-level exception occurred in callback while processing a message
Traceback (most recent call last):
File “/usr/local/lib/python3.12/site-packages/google/cloud/pubsub_v1/subscriber/_protocol/streaming_pull_manager.py”, line 126, in _wrap_callback_errors
callback(message)
File “/usr/local/lib/python3.12/site-packages/google_nest_sdm/google_nest_subscriber.py”, line 283, in callback_wrapper
future.result()
File “/usr/local/lib/python3.12/concurrent/futures/_base.py”, line 449, in result
return self.__get_result()
^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.12/concurrent/futures/_base.py”, line 401, in __get_result
raise self._exception
File “/usr/local/lib/python3.12/site-packages/google_nest_sdm/google_nest_subscriber.py”, line 533, in _async_message_callback
event = EventMessage(payload, self._auth)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.12/site-packages/google_nest_sdm/event.py”, line 346, in init
super().init(**raw_data, auth=auth)
File “/usr/local/lib/python3.12/site-packages/pydantic/main.py”, line 341, in init
raise validation_error
pydantic.error_wrappers.ValidationError: 1 validation error for EventMessage
relationUpdate → subject
field required (type=value_error.missing)

What version of home assistant? Looks like tis expecting a required field that is missing but also looks like something familiar that may have been fixed awhile back

  • Core 2024.4.3
  • Supervisor 2024.04.0
  • Operating System 12.2
  • Frontend 20240404.2

overnight I got this error.
Translation Error: The intl string context varia…
The Nest integration needs to re-authenticate your account

“The Nest integration needs to re-authenticate your account” means that you need to reauthenticate in the UI. This can happen if your authentication credentials need to be refreshed which is normal, but not a common thing. If this happens often then it implies a misconfiguration where the consent screen is set to Testing and not Production and it only gives you test credentails that expire. See “Reauthentication required often” at Google Nest - Home Assistant

I saw relationUpdate error before in Nest Integration gets stuck initializing and fails due to timeout requesting API token. · Issue #104234 · home-assistant/core · GitHub but the user reported the issue went away so didn’t end up fixing.

I was in Production mode as it ran for 25 days.

I may try to delete my cloud, device console projects and start over?

it sucks it seem to be working fine. wasn’t until I added a camera that it crashed.

What is the correct method to add a device? I had it set to automatically add them. Then just reboot HA correct?

Never heard of anything crashing for new devices. I think you just need to add them as authorized to get access. See the troubleshooting steps somewhere it talks about going to the device access partner manager page or something like that (on mobile)

But also, just reath the account of you see that error. It’s normal to reauth sometimes.

i did the reauth, it was successful but no change

i created new cloud projects etc, linked it all and same issue.

hopefully this helps?

2024-04-17 20:07:28.802 DEBUG (ThreadPoolExecutor-4_0) [google_nest_sdm.google_nest_subscriber] Subscriber 'projects/nest-ha-2-123456/subscriptions/home-assistant-Q7lmCOAEjY' configured on topic 'projects/sdm-prod/topics/enterprise-xxxxxxxxxx'
2024-04-17 20:07:28.808 DEBUG (MainThread) [google_nest_sdm.google_nest_subscriber] Starting background watchdog thread
2024-04-17 20:07:28.808 DEBUG (MainThread) [google_nest_sdm.auth] request[get]=https://smartdevicemanagement.googleapis.com/v1/enterprises/xxxxxxxxxx/structures
2024-04-17 20:07:29.107 DEBUG (MainThread) [google_nest_sdm.auth] response={'structures': [{'name': 'enterprises/xxxxxxxxxx/structures/AVPHwEtzU0VsyxRMinmv7hDj04CqzCMQ26kNIo9LfPj-C_e78f7wOB9WR0XBMuQJ_KcCRl1uYwZHk6m97rTWFTK_D4HiNQ', 'traits': {'sdm.structures.traits.Info': {'customName': 'Home'}}}]}
2024-04-17 20:07:29.108 DEBUG (MainThread) [google_nest_sdm.auth] request[get]=https://smartdevicemanagement.googleapis.com/v1/enterprises/xxxxxxxxxx/devices
2024-04-17 20:07:29.959 DEBUG (MainThread) [google_nest_sdm.event] EventMessage raw_data={'eventId': '77a4db2a-0123-4728-90a6-6972b2d8990f', 'timestamp': '2024-04-18T00:07:06.541Z', 'resourceUpdate': {'name': 'enterprises/xxxxxxxxxx/devices/AVPHwEsfQDqMCUScEnL7l6stuPTixZpb_xBAwo6F4XLV7g0tk9NYimTiY56i0CxCrXAWuLohcHpUxpgqFLym7TnwgCQ_mA', 'events': {'sdm.devices.events.CameraSound.Sound': {'eventSessionId': 'AVPHwEtZ3b1QoyakspDTSZkVipkYr3vFnyCbhwNng2GrtxSIFFE_oEOtL1GqkX0IRSbvFY5Gyg3JpdvbIdRoovSIthiJcQ', 'eventId': 'CiUA2vuxr_HBfocTlnflRvQehEPNO-Fg8H_g1xhJpqOUPE2KcpyxEowBAIHtZ3F9kVUZE16FR8-aYSq5Js2N1W5ggWHAZrhrFIQniR8OHnhUFsYyH38sa2LBQc35WO6a3s2TX1SKkId6zJNarIgMdeIST7scep_QFpcYDjzxJ07oAcBrhcPkyKGB5Z5LBxwic6u3fgsxD1uXRefXfKl5ZtyNM0EQ8yyQGPN0HS5w9PGhr32wGqY'}}}, 'userId': 'AVPHwEsCwGJFs1SvO99NrKziV4enovX08qHhT6XdS6ag', 'resourceGroup': ['enterprises/xxxxxxxxxx/devices/AVPHwEsfQDqMCUScEnL7l6stuPTixZpb_xBAwo6F4XLV7g0tk9NYimTiY56i0CxCrXAWuLohcHpUxpgqFLym7TnwgCQ_mA']}

Looks like it’s working great, but maybe that device call is failing? Seems like a nest API bug.
You may need to try to “unstick” the device by moving it between homes or structures? Or make sure the device is authenticated. Double check device permissions here for the new device https://nestservices.google.com/partnerconnections

  1. How do you move it between homes or structures? I only have one. do you mean in the Google app?

If I get it moved, can I move it back? I’ve already created a new account had to pay the $120 again, google is not refunding me 6 months of the service. I’m still fighting that.

  1. In the connection manager all of my devices are selected, like this.