sander1988 / Indego

Home Assistant Custom Component for Bosch Indego Lawn Mower
Apache License 2.0
95 stars 29 forks source link

Instalation error API #236

Closed n4rs closed 4 months ago

n4rs commented 4 months ago

I know API error is a knows issue when updating for what I saw here, problem is I'm doing a fresh install, never had it before, and I can't even get passed the menu where it asks me to define as a mower or a vacuum. As soon as it passes that menu it gives API error, so I can't change the user_agent that's in the know issue, since I can't access the configs for it.

kimzeuner commented 4 months ago

For another user it helped to delete the indego folder in custom components and then re-install it.

See issue #236

n4rs commented 4 months ago

Already did it. The error stayed the same after reinstalling. The thing probably is that the other user was making an update. I am doing a new install. Is there another workaround?

kimzeuner commented 4 months ago

Did you restart ha between deleting the folder and re-installing ? Unfortunately i dont know another workaround. Maybe you can try to install version 5.5 or 5.6 first and then make the update ? Do you have any error logs so the developer can have a deeper look ?

brononius commented 4 months ago

I'm following. Getting the same behavior.

Removed it, (couldn't delete the folder, wasn't there) rebooted and reinstalled 5.7.

Same with version 5.6 and 5.5...

brononius commented 4 months ago

Today, I was able to connect with 5.6.1 (and also 5.5). But when I update towards 5.7, it starts failing.

boschindego.log

When I now remove the config folder (5.6.1), and update throught HCAS (5.7), it seems to work? I'm just not sure about the version. Looks like the integration is still on 5.5? This after a restart.

Schermafdruk van 2024-06-30 10-02-18 Schermafdruk van 2024-06-30 10-02-55

`

kimzeuner commented 4 months ago

And did you already change the user-agent under "configure" in your integration ? If not, change it to anything without "HomeAssistant". The 403 error looks like it is not changed.

brononius commented 4 months ago

I´m not seeing a possiblity to change the user field.

KR

Ben

On 30 jun 2024 at 10:36, kizeu @.***> wrote:

And did you already change the user-agent under "configure" in your integration ? If not, change it to anything without "HomeAssistant". The 403 error looks like it is not changed.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

kimzeuner commented 4 months ago

Ok, just checked your screenshots again at compared it with my setup. It really seems as your integration is still on 5.5 so you will not be able to change the user agent as it was released with 5.7 Can you re-download version 5.7 by clicking on the three dots in the upper right corner (in hacs) and go to download again and select 5.7 ?

brononius commented 4 months ago

Had to remove it completely, reboot 2 times, and installed 5.7. But resulting in the same error again...

Then remove 5.7, install 5.6.1, everything goes fine. Upgrading to 5.7, restart HA, and getting back into troubles. As you can see in the printscreen, no way to select another User-Agent. Only in 5.7.2, I've got another user-agent. But I can't select.

Schermafdruk van 2024-07-01 08-04-10

Schermafdruk van 2024-07-01 08-17-05

Log file: home-assistant_indego_2024-07-01T06-19-24.535Z.log

kimzeuner commented 4 months ago

You can not select the text field and type in any other text ? That's strange and to be honest i have no idea why this happens. Is the integration working with version 5.7.2 ? As the default user-agent was changed it should work.

brononius commented 4 months ago

Ahhh, so the trick is to simply use another name for the User-Agent? I thought you had to select (dropdown or so) something else...

Just typ in something you want, I entered for example Toby (name of my mower), and it works...

image

kimzeuner commented 4 months ago

Yes, correct. Sorry if it was not clear in my explanations. Glad to hear that it works now.

donalddaisy commented 4 months ago

For me it worked to use a common user agent. In my case I picked Mozilla/5.0