#Can you share the errors you re seeing

1 messages · Page 1 of 1 (latest)

frail dragon
#

knucksxtreme — Today at 14:25
Logger: homeassistant.components.http.ban
Source: components/http/ban.py:82
Integration: HTTP (documentation, issues)
First occurred: 2:15:29 PM (6 occurrences)
Last logged: 2:25:01 PM

Login attempt or request with invalid authentication from localhost (127.0.0.1). Requested URL: '/api/states/sensor.current_lights_on'. (None)
[14:25]
Logger: hass_nabucasa.cloud_api
Source: components/cloud/alexa_config.py:173
First occurred: 2:15:30 PM (16 occurrences)
Last logged: 2:15:30 PM

Fetched https://alexa-api.nabucasa.com/access_token (400)
[14:26]
Logger: hass_nabucasa.cloud_api
Source: components/cloud/google_config.py:190
First occurred: 2:15:45 PM (1 occurrences)
Last logged: 2:15:45 PM

Fetched https://remotestate.nabucasa.com/request_sync (404)

outer ridge
#

Does your server allow access using your Nabu Casa URL

frail dragon
#

yes

#

which is weird I can do normal stuff, but getting spammed with these errors

#

it seems to be related to the alexa and google sections

#

Just completely logging out for 5 mins of cloud to see if login attempts and errors stop

#

ok so I logged into temp account and I dont have no errors now, so something with normal account is wrong, its like its not been released and causing a issue

#

although, cant connect to google home yet as phone is not allowing me to change login when adding home assistant in google home.

#

breaking out the android phone to try

#

100% the could server had not released my credentials after I disconnected from old instance and logged in on new one as I have just tried a temp email address and I now have full access with no errors

outer ridge
#

Is old server running or shut down

frail dragon
#

shut down