diff --git a/TroubleShooting.md b/TroubleShooting.md
index 54929be..fed5005 100644
--- a/TroubleShooting.md
+++ b/TroubleShooting.md
@@ -315,7 +315,11 @@ JSON for copy & paste:
 
 ![No JSON](images/NoJson.png)
 
-When the application persists in reporting "No JSON returned from HTTP request." this might be due to a mismatch between the Webhook ID and the device settings on the Home Assistant server. The application options include the ability to clear the Webhook ID in the application forcing a new one to be set up.
+When the application persists in reporting "No JSON returned from HTTP request." this might be due to a mismatch between the Webhook ID and the device settings on the Home Assistant server. We have discovered that the Webhook ID is required for Home Assistant API calls with templates in order to work in a non-privileged account. The application options include the ability to clear the Webhook ID in the application forcing a new one to be set up. This should prevent the above error being shown on startup.
+
+Look for this option in the application settings:
+
+![Nabu Casa Setup](images/delete_webhook_id.png)
 
 # Debug Logs
 
diff --git a/images/GarminHomeAssistantSettings.png b/images/GarminHomeAssistantSettings.png
index 328a3ac..9a70780 100644
Binary files a/images/GarminHomeAssistantSettings.png and b/images/GarminHomeAssistantSettings.png differ
diff --git a/images/delete_webhook_id.png b/images/delete_webhook_id.png
new file mode 100644
index 0000000..68966d1
Binary files /dev/null and b/images/delete_webhook_id.png differ