Bosch Indego, How to use Bosch single ID

Got it.
My way was the following:

  • deinstall binding and reboot oh
  • authorize BEFORE adding single key id thing
  • add single key is as thing
  • authorize again

Thank you for your help!


since yesterday (at least that’s when I realized it) the authorization keeps failing with this error:

2023-11-05 09:59:35.974 [INFO ] [internal.handler.BoschAccountHandler] - Attempting to authorize using authorization code
2023-11-05 09:59:36.327 [INFO ] [internal.handler.BoschAccountHandler] - Authorization completed successfully
==> /mnt/usb1/log/openhab/events.log <==
2023-11-05 09:59:36.330 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'boschindego:account:d81d6c15e3' changed from ONLINE to ONLINE: Authorization completed
2023-11-05 09:59:36.332 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'boschindego:indego:d81d6c15e3:560d2b3403' changed from OFFLINE (COMMUNICATION_ERROR): The request failed with error: 403 to UNKNOWN
2023-11-05 09:59:36.332 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'boschindego:indego:d81d6c15e3:a568d7d68e' changed from OFFLINE (COMMUNICATION_ERROR): The request failed with error: 403 to UNKNOWN
2023-11-05 09:59:36.338 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'boschindego:account:d81d6c15e3' changed from ONLINE: Authorization completed to ONLINE
2023-11-05 09:59:36.522 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'boschindego:indego:d81d6c15e3:560d2b3403' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): The request failed with error: 403
2023-11-05 09:59:36.523 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'boschindego:indego:d81d6c15e3:a568d7d68e' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): The request failed with error: 403

It worked for quite some time now, and on commandline I also do not get an error when I authorize the bridge:

openhab> openhab:boschindego authorize eyJraWQiOiJoYURfVWlBTXE3Q2t4WXpGRUp .... many other characters ... w.MVuMZyUSowpyYz9Q5DvJOA

Did Bosch change something in the authorization again?

I also tried to create a new thing - but this also didn’t help.

Yes, Bosch changed something. Home Assistant seems to be facing the same issue.


Well I can’t really make any changes - I have no real idea about how the bindings are done - but I’m willing to do any testing required.


is anyone working on a solution?

Probably not. I already spent a lot of time on this binding, but now it seems like Bosch is actively blocking us:

This is not confirmed, but we are exposing ourselves with “openHAB” as user-agent, so if we are blocked, it’s intentionally. We could change the user-agent, but in the long run we’ll lose this game and probably end up with the same faith as:

I’ll monitor other projects and follow up in case of any news. However, since we are using an undocumented cloud API, trying to circumvent their blocking will probably only make things worse.

Thanks @laursen,

this is very unfortunate.

I’ll try to contact some “resources” at BOSCH directly. Maybe we have a chance to get some proper documentation.

The response from the “official” BOSCH support was not helpful at all:

"Bitte haben Sie Verständnis dafür, dass wir ausschließlich Support nur über die allgemein zur Verfügung gestellten Optionen der App leisten."


"Please understand that we only support the options made publicly available via our app."

Thanks for your time - I really liked this binding - and it was one reason why I initally bought the Indego.

I’m not very hopeful, but the ideal outcome would be:

  • Documentation is made available and official. As part of the rules, it could be stated how many “cheap” and “expensive” calls we are permitted to make per day, and for example if we are allowed to make additional calls while mowing to better track progress. Expensive calls are the ones contacting the mower through the cellular network, whereas cheap calls are just fetching status information already collected by their service. For sure we’ll need to call more often than the average app usage, but at least we would have some ground rules, and they could throw 429 in case of misbehavior.
  • Being allowed and able to set up a client id in the SingleKey account. This would also make it easier to authenticate as we could use the standard OAuth2 flow.

One of my reasons for deciding on the Indego was also the integration possibility. Tomorrow I’ll get it back from repair the third time on the guarantee, so if anything similar happens again, I should be able to return it and get my money back. We’ll see who offers an API at that time. :wink:

I can fully agree to the conclusion in this blog post (which is about MyQ), we’ll see if the situation will be the same for Bosch Indego:

1 Like

Hi there :wave: ,

I recently posted an idea for a workaround on GitHub but as I got no response there, I’ll try my luck here :slight_smile:

I am not too deep into the issue, but would it be a “solution” / workaround to use a random user agent?

  • a UUID
  • a word list for the product (HomeAssistant, OpenHab, ioBroker, …) and a random version number

I assume that the WAF would also block requests, if the user agent changes on every request, but potentially we could perform an automatic retry of requests with a new user agent every time we get a 403.

I also thought about using the same user agent than the official app uses. But yesterday I had the feeling, that the official app also suffers from the 403 problem: I had a large amount of notifications in the app and started to delete them. After deleting 20 notifications or so, the app showed a popup with an error message 15_403 (unsure about the 15 but I definitely saw the 403 and directly remembered this problem here).

Referring to the last paragraph, I am not sure if Bosch is actively blocking third party integrations. Instead it may be some general configuration in the WAF that fits for “normal app usage” but slightly not when used with integrations like OH or HA.

I’m not too keen on that solution as explained here:

we are exposing ourselves with “openHAB” as user-agent, so if we are blocked, it’s intentionally. We could change the user-agent, but in the long run we’ll lose this game

However, lawn season is about to start here in Denmark, so I’ll use that opportunity to at least try a different user-agent to verify if we are indeed blocked, or if the issue is caused by something else.

Another thing we could do is try to get in touch with Bosch and ask for “permission” to use the API. The risk is of course that they explicitly deny us access, but at this point I’m not sure we have much to lose since the integration is broken anyway.

Did anyone track Home Assistant status recently?

1 Like

Thanks for your effort @laursen , really appreciate your work :heart:

From the comments in the HomeAssistant issue, I assume that changing the user agent works to some extend and the possibility for the users to manually adjust the user agent to work around the 403 also seem to work. At least that’s what I think as no one posted anything there since start of december …

As I can see from the latest posts in the HA issues, they added the user agent as a parameter.

Do you also want to introduce something like this or how can I manually change the user agent?

I just tried “Test/1.0” as user-agent and still got 403.

See here: Connection error bosch indego APi · Issue #204 · jm-73/Indego · GitHub

I’m afraid this prediction might have come true:

and might even have even been accelerated by integrations such as Home Assistant’s trying to get around the blocking by manipulating the user-agent.

Out of curiosity I just downloaded the apk of the bosch app and decompiled it using jadx. They are obfuscating the code (which was kinda to be expected). Yet, a bit of searching around in the code shows that they are using “Indego-Connect_.<BuildNumber?>” (currently “Indego-Connect_4.0.3.12955”) as User Agent.
Not really the nicest solution (and not the really the friendly way), but if the binding would provide the option to configure the User-Agent it would be possible to adapt the User Agent to the latest App Version. Thus giving the WAF the impression that the request is coming from the app and making it hard to block.

1 Like

I can confirm that indeed using this user agent bypasses the WAF, and got the binding back online. Thanks for having a look at the APK.

In the meantime I also reached out to Bosch, but have not yet received a reply.

I’m a bit divided in what to do now. Currently the binding is not working. If we fake the user agent pretending to be the app, the binding will probably work for some time, but eventually it might be blocked in some other way. Since the end result is pretty much the same, I suppose we could give it a try.

The only thing worrying me slightly is the risk of wider blacklisting. Bosch could detect our non-app usage pattern, and block the device or user account entirely, so that it would no longer be possible to use the app either.

I guess faking the user agent would give use a few months before they can do anything about it. They would first have to roll out a new version of the app and make sure it’s widely distributed before they can block the user agent - otherwise they would block legit users of the app.

Yet, if the really mean to block third party clients, they could easily detect the pattern (the app will only do requests while actually running and not all the time) and simply block the user accounts. But that would be a quite harsh step.

Thank you very much for your superb work @laursen!

Would it be possible to provide a jar-file to test the updated binding with the current openHAB version?

Of course: org.openhab.binding.boschindego-4.1.3-SNAPSHOT.jar (it will also be included in next patch release).


You rock, thank you very much for this!!

1 Like