From aae6498359d99bd7050f1d04d5178cac7b80fd2b Mon Sep 17 00:00:00 2001
From: mueller-ma <mueller-ma@users.noreply.github.com>
Date: Wed, 29 May 2019 17:37:53 +0200
Subject: [PATCH] Add notification troubleshooting section to docs (#1335)

Signed-off-by: mueller-ma <mueller-ma@users.noreply.github.com>
---
 docs/USAGE.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/USAGE.md b/docs/USAGE.md
index 209a2911..058b8cc4 100644
--- a/docs/USAGE.md
+++ b/docs/USAGE.md
@@ -94,6 +94,17 @@ end
 
 Please refer to the [openhab-android project on GitHub](https://github.com/openhab/openhab-android) for more details.
 
+### I don't receive any notifications
+
+Please have a look at the "Push notification status" on the About screen in the app.
+If it claims that your device is successfully registered at FCM, please open an issue on [openhab-android project on GitHub](https://github.com/openhab/openhab-android) or create a thread in the forum.
+
+### My notifications are delayed
+
+All notifications are sent as "high priority" messages, which means that the device and the openHAB app are waken up and display the notification.
+However vendors/third parties can implement custom "cleanup", "optimization" and "battery saver" apps, which might lead to delayed notifications.
+Please have a look at [dontkillmyapp.com](https://dontkillmyapp.com/) how to make an exception for openHAB in these apps.
+
 ## Trademark Disclaimer
 
 Google Play and the Google Play logo are trademarks of Google Inc.
-- 
GitLab