Core: [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found

[DubhAd]

Home Assistant release with the issue:

0.101.3

Last working Home Assistant release (if known):
Unknown

Operating environment (Hass.io/Docker/Windows/etc.):

venv on Debian 9.11

Integration:

cloud

Description of problem:

2019-11-19 16:48:41 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2019-11-19 16:51:12 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2019-11-19 17:40:11 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2019-11-19 18:13:34 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2019-11-19 22:27:41 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2019-11-20 06:36:07 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2019-11-20 08:22:21 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2019-11-20 08:50:44 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2019-11-20 09:06:44 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

cloud:

Traceback (if applicable):

Additional information:

Also reported by others in the HA Discord

[probot-home-assistant[bot]]

Hey there @home-assistant/cloud, mind taking a look at this issue as its been labeled with a integration (cloud) you are listed as a codeowner for? Thanks!

[balloob]

This happens if Home Assistant is trying to report a state while the entity has not been configured on Googles side to have states reported.

Do you have state reporting enabled ?

I wonder if it has something to do with the recent changes to the local Google implementation.

[stepanov1975]

Same issue here. Have 500 errors now

arch | x86_64
-- | --
dev | false
docker | false
hassio | false
os_name | Linux
python_version | 3.7.5
timezone | Asia/Jerusalem
version | 0.101.3
virtualenv | true

[DubhAd]

Do you have state reporting enabled ?

Yes, I do

[stsybizov]

Same error on 102.2

[stsybizov]

resolve. I did new installation and don't added "cloud:" section in configuration.yaml

[balloob]

Wait, I am confused. Did you get this error while you are using a manual set up of Google Assistant ?

[corchat]

I had the same problem. Fixed it by adding service_name to my tts section. It now looks like this.

tts:
  - platform: google_translate
    service_name: google_translate_say

[amblyo]

I got the same problem.

A question have come to my mind.
Is it supported to have config in cloud: and at the same time config the entities in the web ui?

[Mave922]

I have the same problem.

I configured the integration via the web ui. I just checked my config and I do have an entry for cloud:

[balloob]

We're working on getting re-certified that should hopefully fix this problem.

[DKFrederik]

Home Assistant release with the issue:

0.103.5

Operating environment (Hass.io/Docker/Windows/etc.):

venv on Ubuntu 18.04

Integration:

cloud

I get the same thing. I even can't restart home assistant, have to restart the system (ubuntu) to get home assistant to boot up again.

The last error I get is:

ERROR (Thread-7) [pychromecast.socket_client] [PhilipsTv:8009] Failed to connect. No retries.

It's not only the philips tv It's the pychromecast.socket_client in general. It's stalling at any of my chromecast devices ramdomly when I try to restart home assistant.

[arnoldpistorius]

@balloob How long is the recertification process going to take?

[balloob]

Apologies. Realized it was caused by another bug. Releasing fix in 0.103.6. You will need to trigger one more sync from another location, then everything will be working again.

[lellky]

@balloob what does that mean?

[balloob]

Report state works again once you upgrade to 0.103.6 and ask Google Assistant to "Sync my devices"

[lellky]

Awesome! Good news!

[DKFrederik]

I still get some errors on this subject...

2020-01-08 01:14:29 ERROR (MainThread) [hass_nabucasa.google_report_state] Unexpected error
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/hass_nabucasa/iot_base.py", line 108, in connect
await self._handle_connection()
File "/srv/homeassistant/lib/python3.7/site-packages/hass_nabucasa/iot_base.py", line 147, in _handle_connection
await self.cloud.auth.async_check_token()
File "/srv/homeassistant/lib/python3.7/site-packages/hass_nabucasa/auth.py", line 145, in async_check_token
await self.cloud.run_executor(self._check_token)
File "/srv/homeassistant/lib/python3.7/site-packages/hass_nabucasa/__init__.py", line 169, in run_executor
return self.client.loop.run_in_executor(None, callback, *args)
File "/usr/lib/python3.7/asyncio/base_events.py", line 747, in run_in_executor
executor.submit(func, *args), loop=self)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 163, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown

[balloob]

@DKFrederik please open a new issue and also include your versions in use and when it occurs.

[martinlong1978]

@DKFrederik Did you open a new issue? Could you link it here please? I'm also still getting the same error after upgrade to 103.6, and a resync of my devices.

[DKFrederik]

@martinlong1978 No i did not. But I found my root cause. It was the entry mobile_app: in the configuration.yaml file.
I didn't investigate further yet due to lack of time. I just comment it out until I get the time to look into it....
I just started to comment out all of my entries until I didn't get the above error any more

[martinlong1978]

ok. Thanks for responding

Martin

On Thu, 9 Jan 2020 at 23:39, Frederik Kristian Pedersen <
[email protected]> wrote:

@martinlong1978 https://github.com/martinlong1978 No i did not. But I
found my root cause. It was the entry mobile_app: in the configuration.yaml
file.
I didn't investigate further yet due to lack of time. I just comment it
out until I get the time to look into it....
I just started to comment out all of my entries until I didn't get the
above error any more

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/28894?email_source=notifications&email_token=AACJ7G6WXD6NZGPYPNRFOYLQ46YUHA5CNFSM4JPPRLXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEISFQDY#issuecomment-572807183,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACJ7GYT35BGN6G2BZPAWYTQ46YUHANCNFSM4JPPRLXA
.

[DKFrederik]

@martinlong1978
Sorry to disturb you again, but i made some progress that might interest you.

So I got the time to look into this (or rather the problem came back, so I had to look into it!). It seems that, at the time when things went bad with nabu casa vs. google integration, some funky things went on with the auth core component. Can't seem to figure out what exactly, but by the logs, it seems tight couplet.
So what I did was (to be sure I was on the right track) rename the hole hidden folder in the config directory ".storage" (I renamed it to be sure that I could return to the same state). After I renamed the folder, I forced Home Assistant to shut down (killed the service) and then restarted the system (Home Assistant) I then had to reintergrate my intergrations!
I have now been up and running, without any problems what so ever, for the entire day!

Just thought I would share my "findings", it might help you too!

Best regards
Frederik