[KEIN BUG] Bips und Schraffur öffnen Fehler/Bips and hatch open error

Fehler nur zu dieser Firmware
Gesperrt
sarakha63
Beiträge: 20
Registriert: Mi 25. Apr 2018, 13:59
Mäher: Husqvarna Automower 315
Firmware des Mähers (MSW): MSW 6.xx.xx
Herstellungsjahr: 2017
Robonect-Modul: Robonect Hx (Rev.5)
Robonect Firmware: 1.0beta7

[KEIN BUG] Bips und Schraffur öffnen Fehler/Bips and hatch open error

Beitrag von sarakha63 » Do 26. Apr 2018, 00:02

Ich bemerkte ein seltsames Verhalten auf meinem 315x. Beim Navigieren auf dem Webserver werden die Mäher zweimal ausgelöst und der Automower meldet einen Öffnungsfehler.

Ich habe versucht, die API und es tut das gleiche mit cmd = Version cmd = Batterie cmd = Motor but not at all for cmd=status

Es scheint, dass das Problem nur während geparkt gesehen wird. Aber es ist nervig, da der Mäher zweimal Automower verbinden sendet eine Push-Benachrichtigung, aber nichts ist auf robonect gesehen.

Ist es etwas an meiner Seite oder ist es ein bekannter Fehler?

-----------------------------------------------------------------------

I noticed a strange behavior on my 315x. When navigating on the web server the mowers bips twice and automower reporte a hatch open error.

I tried the api and it does the same with cmd=version cmd=battery cmd=motor
but not at all for cmd=status
It seems the problem is only seen while parked. But its annoying as the mower bips twice automower connect sends a push notification but nothing is seen on robonect.

Is it something on my side or is it a known bug ?

mow-joe
Beiträge: 118
Registriert: Mi 2. Aug 2017, 12:27
Wohnort: Bayern
Mäher: Husqvarna Automower 315
Firmware des Mähers (MSW): MSW 7.xx.xx
Herstellungsjahr: 2017
Robonect-Modul: Robonect Hx (Rev.4)
Robonect Firmware: V1.1b

Re: Beeps and hatch open error

Beitrag von mow-joe » Do 26. Apr 2018, 14:40

I would suggest to post in English as the google translate results are rather misleading and hard to read.
Most of the folks can communication in English here.

As to your issues - not sure if this is a known issue.
It is completely normal, that the mower will beep when you access the Web-UI as robonect just uses the same physical interface as the mower display does. So from the mower electronics perspective, it just assumes that the display has been used and then beeps.

No idea about the "open hatch" error - where did you see that? can you please post a screenshot or photo?

Malmgren
Beiträge: 32
Registriert: Di 13. Jun 2017, 18:37
Wohnort: Sweden
Mäher: Husqvarna Automower 310
Firmware des Mähers (MSW): MSW 6.xx.xx
Herstellungsjahr: 2016
Robonect-Modul: Robonect Hx (Rev.4)
Robonect Firmware: 1.0 beta 7

Re: Bips und Schraffur öffnen Fehler/Bips and hatch open error

Beitrag von Malmgren » Mo 30. Apr 2018, 13:23

I've got the same problem, every time the api is accessed the AM makes two small beeps. I'm polling the api from my home automation (openhab) so it makes the sound once every minute, which makes kinda big problem. Except for the beeps everything seems to work alright, no error messages to be seen anywhere. Not sure if this only happens while charging, I had to remove the polling to get some sleep tonight ;)

Benutzeravatar
shadowkiller
Beiträge: 1984
Registriert: Do 11. Jan 2018, 08:42
Wohnort: Würzburg
Mäher: Husqvarna Automower 315
Firmware des Mähers (MSW): MSW 10.xx.xx
Herstellungsjahr: 2017 (Modell 2018)
Robonect-Modul: Robonect Hx (Rev.5)
Robonect Firmware: V1.1b

Re: Bips und Schraffur öffnen Fehler/Bips and hatch open error

Beitrag von shadowkiller » Mo 30. Apr 2018, 17:24

If I‘m remembering correctly, there is no possibility for Fabian to make this sounds end or reduce to only wanted once’s. On another discussion he said, only Husqvarna could change this.

The only possibility to make the sound end is switching off the Speaker inside the mower.


shadowkiller
WLAN oder Robonect funktioniert nicht? Erstmal die Tipps lesen!
--
Kompendium für Mähroboter: Download ERFAdoc (ca. 4,3 MB, 232 Seiten-PDF) von Fidatex
--
Es ist schon alles gesagt, nur noch nicht von allen. (Karl Valentin)

Malmgren
Beiträge: 32
Registriert: Di 13. Jun 2017, 18:37
Wohnort: Sweden
Mäher: Husqvarna Automower 310
Firmware des Mähers (MSW): MSW 6.xx.xx
Herstellungsjahr: 2016
Robonect-Modul: Robonect Hx (Rev.4)
Robonect Firmware: 1.0 beta 7

Re: Bips und Schraffur öffnen Fehler/Bips and hatch open error

Beitrag von Malmgren » Mo 30. Apr 2018, 18:31

shadowkiller hat geschrieben:
Mo 30. Apr 2018, 17:24
If I‘m remembering correctly, there is no possibility for Fabian to make this sounds end or reduce to only wanted once’s. On another discussion he said, only Husqvarna could change this.
It didn't do this with Robonect firmware 0.9e or 1.0 preview. The only thing that has changed on my mower is the Robonect firmware, so it must be something there that has changed.

/Daniel

Benutzeravatar
shadowkiller
Beiträge: 1984
Registriert: Do 11. Jan 2018, 08:42
Wohnort: Würzburg
Mäher: Husqvarna Automower 315
Firmware des Mähers (MSW): MSW 10.xx.xx
Herstellungsjahr: 2017 (Modell 2018)
Robonect-Modul: Robonect Hx (Rev.5)
Robonect Firmware: V1.1b

Bips und Schraffur öffnen Fehler/Bips and hatch open error

Beitrag von shadowkiller » Mo 30. Apr 2018, 21:32

So we have to wait, what Fabian will say.
Thanks.


shadowkiller
WLAN oder Robonect funktioniert nicht? Erstmal die Tipps lesen!
--
Kompendium für Mähroboter: Download ERFAdoc (ca. 4,3 MB, 232 Seiten-PDF) von Fidatex
--
Es ist schon alles gesagt, nur noch nicht von allen. (Karl Valentin)

Admin
Administrator
Beiträge: 2519
Registriert: Di 19. Jan 2016, 18:34
Wohnort: Kiel
Mäher: Gardena SILENO City 500
Firmware des Mähers (MSW): MSW 11.xx.xx
Herstellungsjahr: 2017 (Modell 2018)
Robonect-Modul: Robonect Hx (Rev.5)
Robonect Firmware: stets die Allerneuste :-)
Kontaktdaten:

Re: Bips und Schraffur öffnen Fehler/Bips and hatch open error

Beitrag von Admin » Sa 5. Mai 2018, 22:47

The status request is designed to work without waking the mower.
For other requests, as batter, engine... Robonect needs to wake it up. During this wake up process, the mower beep twice.

Why do you need to request other values than the status?
Werbefläche zu vermieten. :lol:

Malmgren
Beiträge: 32
Registriert: Di 13. Jun 2017, 18:37
Wohnort: Sweden
Mäher: Husqvarna Automower 310
Firmware des Mähers (MSW): MSW 6.xx.xx
Herstellungsjahr: 2016
Robonect-Modul: Robonect Hx (Rev.4)
Robonect Firmware: 1.0 beta 7

Re: Bips und Schraffur öffnen Fehler/Bips and hatch open error

Beitrag von Malmgren » So 6. Mai 2018, 10:41

Admin hat geschrieben:
Sa 5. Mai 2018, 22:47
The status request is designed to work without waking the mower.
For other requests, as batter, engine... Robonect needs to wake it up. During this wake up process, the mower beep twice.
Ok... And this hasn't been changed between 1.0 pre and 1.0 beta? Can't really understand what has changed then. I am using the openhab binding, don't think the calling has changed there. I'll throw in @reyem here ;)
Admin hat geschrieben:
Sa 5. Mai 2018, 22:47
Why do you need to request other values than the status?
I think this is also a question that @reyem would answer much better than me. I actually only use the status myself. @reyem, could the binding be designed as only requesting needed info? As it is now, the mower starts with its double-beeping as soon as I configure a Thing pointing to it, even when I don't connect anything to any of the channels.

/Daniel

edit: Seems tagging users doesn't work in this forum. I sent reyem a PM instead, asking him to comment in the thread 8-)

reyem
Beiträge: 22
Registriert: Fr 21. Apr 2017, 14:14
Mäher: Husqvarna Automower 105
Firmware des Mähers (MSW): MSW 6.xx.xx
Herstellungsjahr: 2017
Robonect-Modul: Robonect Hx (Rev.3)
Robonect Firmware: 0.9e

Re: [KEIN BUG] Bips und Schraffur öffnen Fehler/Bips and hatch open error

Beitrag von reyem » So 6. Mai 2018, 21:56

The OH Binding is just calling status in a polling thread. Maybe try manually to call:

http://your-mower-ip/json?cmd=status

in your browser. If it then "beeps" the mower firmware would be the issue. If it does not beep, try to set the binding to DEBUG level. Then any other command would be logged in the form:

send HTTP GET to: {} (where {} would be the url showing the command) Maybe there is some item update propagated all the time!?

Gesperrt

Zurück zu „FW 1.0 Beta 3“