From a8c7a3ffe95653c0b806aadbcaa68dad62586bfb Mon Sep 17 00:00:00 2001 From: Sander Peterse Date: Fri, 7 Jun 2024 12:37:07 +0200 Subject: [PATCH 1/3] Update README.md Added more details regarding known issues. --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2b366a9..f970819 100644 --- a/README.md +++ b/README.md @@ -148,7 +148,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 after you just an impossible commands 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. From d4b2f60a34236daa1cdab897403765d56a4da997 Mon Sep 17 00:00:00 2001 From: Sander Peterse Date: Fri, 7 Jun 2024 12:39:31 +0200 Subject: [PATCH 2/3] Update ISSUE_TEMPLATE.md Improved template --- .github/ISSUE_TEMPLATE.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md index 00e110c..e87d3e3 100644 --- a/.github/ISSUE_TEMPLATE.md +++ b/.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 From c55588a2c06db164cbe00350c5cc2e3fa07dbbfe Mon Sep 17 00:00:00 2001 From: Sander Peterse Date: Fri, 7 Jun 2024 12:42:32 +0200 Subject: [PATCH 3/3] Update README.md Typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f970819..e7f512c 100644 --- a/README.md +++ b/README.md @@ -150,7 +150,7 @@ If you experience any readings from your mower that the sensor does not read out * 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 (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 after you just an impossible commands to the mower. Like docking the mower while it's already docked. +* 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.