Merge branch 'master' of github.com:jm-73/Indego

.github/ISSUE_TEMPLATE.md

@@ -15,7 +15,8 @@ labels: bug
 
 - [ ] I have updated to the latest available of the Indego component version.
 - [ ] I have updated to the latest available Home Assistant version.
-- [ ] I have read the readme and checked for other open or recently closed issues for similar bugs/issues.
+- [ ] I have read the README https://github.com/jm-73/Indego/blob/master/README.md) and especially read the part about the KNOWN ISSUES (https://github.com/jm-73/Indego/blob/master/README.md#known-issues).
+- [ ] I have checked hecked for other open or recently closed issues for similar bugs/issues.
 
 ## The problem
 

README.md

@@ -183,7 +183,9 @@ If you experience any readings from your mower that the sensor does not read out
 
 ## Known issues
 * A special [Chrome plugin](#installing-the-chrome-extension) is required to complete the account linking in HomeAssistant.
-* The Bosch Cloud (running on Azure) might block this integration from time to time. You might see HTTP 4XX errors like 'The connection to the Bosch Indego API failed!'. This might happen during component setup or during state updates. In that case you might be able to workaround the issue by changing the user agent (using the Configuration panel in HomeAssistant of this component).
+* The Bosch Cloud (running on Azure) might block this integration from time to time. You might see HTTP 4XX errors like 'The connection to the Bosch Indego API failed!'. This might happen during component setup or during state updates. In that case you might be able to workaround the issue by changing the user agent (in Settings > Devices & services > Bosch Indego Mower > Configure).
+* You might see HTTP 5XX errors from time to time (most of time once a day). In that case there is a problem on the Bosch Cloud side which is temporary unavailable.
+* HTTP 5XX errors can also occur right after you have sent an impossible command to the mower. Like docking the mower while it's already docked. 
 
 ## New issues
 If you experience issues/bugs with this the best way to report them is to open an issue in **this** repo.