jpgorganizer / ioBroker.smartgarden

GARDENA smart system adapter for ioBroker
Other
21 stars 8 forks source link

"Bad Request" on Mower command #68

Closed pellenbeck closed 11 months ago

pellenbeck commented 1 year ago

@jpgorganizer I would like to re open issue #66 .

I have contacted the Husqvarna Developer Portal with the problem. After exchanging the information about the RateLimitCounter and some log files, I received the following answer from Husqvarna:

Wir können den Fehler reproduzieren, indem Sie «activity_control_i» nur START_SECONDS_TO_OVERRIDE schicken. Sobald Sie diesen Parameter mit einer Zahl konfigurieren (oder Zahl unmittelbar vom command gefolgt), tritt der Fehler nicht mehr auf. Damit können Sie diesen Umstand (der offenbar «nur» diesen Command betrifft) überbrücken, bis ioBroker ggf. zu einem späteren Zeitpunkt das Verhalten für diesen Command korrigiert.

The answer looks to me like a wrong implementation in the adapter or something that can be adjusted in the adapter. Is there a manual workaround via the adapter?

The problem is that the error "Error: request returned 400 Bad Request" leads to a constant repetition of the requests and thus the RateLimit is exceeded very quickly - which then ends in the error image "Error: request returned 403 Forbidden".

Regards Philipp

jpgorganizer commented 1 year ago

what value do you set in «activity_control_i»? Please post that line of log.

llendi commented 12 months ago

This might be related to my open PR: https://github.com/jpgorganizer/ioBroker.smartgarden/pull/67

pellenbeck commented 11 months ago

Cannot provide any further logs. I just use the adapter and got those error responses. Did not set any values by myself.

jpgorganizer commented 11 months ago

then I don't understand the issue. If you do not set any values, what's the problem. I'm closing the issue

This might be related to my open PR: #67

no

jpgorganizer commented 11 months ago

see before

pellenbeck commented 11 months ago

I use the adapter "out of the box" and received the documented errors.

Gardena Support reports back what the problem is from their point of view.

Your only thin-lipped answer is then that you do not see the problem in the adapter? That's not really understandable.

In fact, the problem doesn't really occur with me anymore; if Gardena has fixed something, I can't say.