Leandro Toledo leandrotoledo

pyvenv-3.3 (Ubuntu 13.10, also Debian)

Symptoms

pyvenv-3.3 venvdir
venvdir/bin/python -c 'import sys; print(sys.path)'
# This should print the venvdir in sys.path.

But in buggy Ubuntu/Debian, it doesn't.

It is easy to get service accounts working with App Engine's app_devserver.py - once you know how.

On the way there, you might have pulled out all your hair following one documentation dead end after another, trying to piece together the right information.

Here are the steps you need to take, in exact order, to get this working. Once you follow these steps, you'll be able to use service accounts in local development, so that you can interact with Google APIs (e.g.: Spreadsheet, Calendar) in a way that is consistent with the deployment environment on App Engine.

In order to follow the instructions, you'll be better off using the latest UI for Google Cloud projects. Older interfaces (such as the dedicated App Engine dashboard) have things in different places, under different names, etc. It is a world of pain there.

Also note that I've tested this on several 1.9.x releases of App Engine; I can't confirm the behaviour of earlier releases.

	##
	## See https://github.com/kevin-david/home-assistant-shared/blob/main/esphome/esp32-wave-radon-proxy.yml for future updates
	##

	substitutions:
	name: "<YOUR_DEVICE_NAME_HERE>"
	wave_serial: "<YOUR_SERIAL_OR_UNIQUE_ID_HERE>"
	# See https://esphome.io/components/sensor/airthings_ble.html for how to find this
	# Note: If you have your ESP32 connected to your Wave device, it might cause problems syncing with your phone
	# Suggest powering down the ESP device before running firmware updates or attempting to sync with AirThings cloud, if you care about that