Internal Server Error on /hello/<USER_KEY>

[bdaneshgar]

I am thinking out loud. I get a server error when testing /hello/<USER_KEY>

My calendar is probably set up incorrectly:

• I have only filled oath_client/google_calendardocument with the client_id and client_secret
• I have not filled out the /users/<USER_KEY>/google_calendar_credentials
• Is /users/<USER_KEY>/google_calendar_credentials to be set up in the /hello/<USER_KEY> page.

Any insight into helping me get into thepage is much appreciated!

/hello/ for the settings UI to edit user-specific data.

Internal Server Error

/next?key= for the time in milliseconds until the next schedule entry.

This works

/epd?key= for the currently scheduled client image used by the e-paper display.

This downloads serial gibberish

/gif?key= for a GIF version of the currently scheduled image for testing.

this triggers the settings_response function in response.py

/artwork?key= to bypass the schedule and get the artwork image directly.

This works

/city?key= to bypass the schedule and get the city image directly.

This works

/commute?key= to bypass the schedule and get the commute image directly.

This works

/calendar?key= to bypass the schedule and get the calendar image directly.

Internal Server Error

/everyone?key= to bypass the schedule and get the everyone image directly.

I am everyone

/wittgenstein?key= to bypass the schedule and get the wittgenstein image directly.

This works.

[bdaneshgar]

I did notice that my browser autocorrected to oath_clients. I noticed in the README.md, there is a reference to both oauth_client and oauth_clients and I see that only oauth_clients is valid.

I am still having trouble with my /calendar?key=<USER_KEY> and /hello/<USER_KEY>

[bdaneshgar]

I took out extraneous URIs from my OAuth Client and it now works!

[maxbbraun]

Thanks for catching the typo!