Until, I use the IFTTT integration to send commands from HA to my Bosch Indego.
@onkelfarmor: Do you have a link to the IFTTT? Is the integration Open Source? Maybe I can reverse engineer something from it?
New release today! This is fun! See release notes for description.
Bad news about the NextPredictiveCutting. I cannot get the API to answer my questions about this. I have searched for resources about this API, but no one has done a reverse engineering recently. I suspect that all reverse engineering has been performed before this summer when Bosch released a new app. I suspect that the protocol documentation I have found is for the old app.
Let me hear from you if you find any bugs or want any improvements!
/J
1 Like
This looks really good, One comments would be to format the instructions in github to give an actual example of YAML code that can just be copied/pasted.
Also, in terms of the directory structure, shoudl it not be config/custom_components/indego as opposed to config/custom_components ?
Looking forward to giving it a go!
Thanks!
I have updated with yaml and gui examples on how to send commands to the mower.
I have also tried to simplify the file and folder structure, and I hope that the instructions is more easy to understand and follow now.
1 Like
tried to get this working. got error:
2019-07-30 17:55:56 ERROR (SyncWorker_8) [homeassistant.loader] Error parsing manifest.json file at /config/custom_components/indego/manifest.json: Expecting value: line 6 column 18 (char 143)
pls advise.
hassio 0.96.5
conf as pointed in github
update. very strange… i added debug lines to conf and restarted hassio. surprise-suprise - its working!
1 Like
I tried to remove the debug flag also, and got the same error as you in the log. But the sensor entities are still working.
Will you add this as an issue in my github project?
This is really great! Have not tried the commands as my stupid bot has lost it’s map… some weird error with the mower itself (I can’t even control it from the phone)
But what you have done here is really great! Thanks very much for all your hard work…
I am going to try and write a lovelace card for this, otherwise, at the moment, this is my layout:
1 Like
Nice card!
I plan to implement all data from the API i have written. I also plan ro make the mower sensors configurable so you can implement the sensors tou want and hide the non-wanted.
I am also rhinking about the posibility to limit the number of states for the mower. As it is implemented now, there are a lot of states registered when themower mowes for a day, eg waking up, reading map, mowing, border cut, return to dock, charging, locating… This makes it hard to for example calculate mowing time for a day or week. Maybe add some configuratio, or add another sensor with only mowing and docked as states?
/J
I have fixed this issue. It turned out that I had missed some “” inside line 6 in the manifest.json. Strange that the error didnt show up when debgging was enabled. Change is checked in in the Master branch.
/J
You’ve got a typo, the documentation says “indego.mower_command” but the actual service (and the screenshot in the documentation) is “indego.mover_command”
I need to get my mower sorted first before I can comment on the states.
I have had so many issues with this mower, it is actually my second one as the first one stopped working, now this one worked for a while and then I got a message in the app saying “not mapped” although it does mow by itself on the smart schedule.
Also, it keeps getting stuck in 3 specific places in the lawn, so I am trying to see if I can get some wheels with more traction… Otherwise, it is the onel mower I know of that does the striped which I love…
Anyway… Thanks again for all your hard work on this…
Found this on another web page where somebody had problems with the API and next mowing time.
Battery: [https://api.indego.iot.bosch-si.com/api/v1/alms/{{alm_sn}}/operatingData]
Next mowing time: [https://api.indego.iot.bosch-si.com/api/v1/alms/{{alm_sn}}/predictive/nextcutting?withReason=true]
Maybe you can use this for something …
Great!
New release is comming tomorrow. A couple of new sensors, more properties on the old ones. Some bug fixes and code refactoring.
After the 0.3 release I will look into the API commands you wrote here. Do you have a link? Maybe there are more information for the component there?
Here is the link to the lastest post with a link to a Windows app using the Api. Some posts later the two Api links are mentioned.
It’s in German 
so is my mower 
1 Like
Both the commands worked. The first command can be used to get battery status, as the people on the german forum says that Bosch is preparing for a new app with battery status visible in the app.
The second command only gives the latest mow command that was sent to the mower. I will try to read the whole forum thread to get a better grip on what they are up to. Maybe they have more information about the API than I have.
I will implement the battery indicator as soon as I have done some refactoring of the API calls. I also need to understand the numbers in the answer from my mower:
{'runtime': {
'total': {'operate': 84358, 'charge': 25409},
'session': {'operate': 132, 'charge': 0}},
'battery': {'voltage': 34.0, 'cycles': 1, 'discharge': 0.0, 'ambient_temp': 30, 'battery_temp': 30, 'percent': 340},
'garden': {'id': 7, 'name': 1, 'signal_id': 1, 'size': 625, 'inner_bounds': 3, 'cuts': 24, 'runtime': 80222, 'charge': 24424, 'bumps': 4633, 'stops': 24, 'last_mow': 4},
'hmiKeys': 1344}