Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fehlermeldung: Failed to execute get_status on robot xxx ... #549

Open
Norb1204 opened this issue May 19, 2024 · 18 comments
Open

Fehlermeldung: Failed to execute get_status on robot xxx ... #549

Norb1204 opened this issue May 19, 2024 · 18 comments
Labels
stale Issues marked as stale

Comments

@Norb1204
Copy link

Hallo,
nach update PI von Debian 10 nach 12 kommt kurz nach dem Start des Adapters ca. jede Sekunde eine Fehlermeldung.
Adapterversion: Aktuelle DEV (18.05.2024)

Als Anhang das LOG:
log.txt

@copystring
Copy link
Owner

Ja, ich habe dafür einen fix vorbereitet, aber noch nicht hochgeladen.

@copystring
Copy link
Owner

Testest du bitte die neue dev? Da sollte es jetzt wieder laufen.

@Norb1204
Copy link
Author

Fehlermeldungen sind zwar weg aber der DeviceStatus, CleaningInfo wird nicht mehr aktualisiert.

image image

@copystring
Copy link
Owner

Bist du dir sicher, dass das nie aktualisiert wird? Ich kann das bei mir nicht reproduzieren. Vielleicht hast du aber noch nicht die neueste dev installiert?

@Norb1204
Copy link
Author

Habe mal den Adapter gelöscht und neu installiert.
Bei der Standard-Installation funktioniert die Aktualisierung. Dann die DEV installiert, hier funktioniert die Aktualisierung nicht.
Habe z.Z. zwei ioBroker am laufen. Einen mit Debian 10 der andere mit 12. Bei beiden das gleiche Phänomen.

@copystring
Copy link
Owner

Merkwürdig, aber OK. Muss ich mir angucken. Gibt es im Log neue Fehler?

@Norb1204
Copy link
Author

Bei der Standard-Installation kommen halt noch die altbekannten Fehlermeldungen.
Ich werde morgen mir das ganze genauer anschauen und Rückmeldung geben.
Momentan habe ich die Vorgängerversion der DEV am laufen.

@Norb1204
Copy link
Author

Als Anhang ein LOG von mehreren Minuten.
Mit der letzten DEV werden DeviceStatus und CleaningInfo nicht mehr aktualisiert, auch beim Neustart des Adapters nicht.
Erst wenn ich den Adapter lösche und neu installiere funktioniert die Aktualisierung wieder.

log.txt

@nicomania
Copy link

Habe ich auch schon seit Längerem. Kommt jedes Mal, wenn ich eine Reinigung (über die App) starte.

Roborock S8
Adapter v0.6.4
Node.js v18.19.0
NPM 10.5.1

roborock.0 | 2024-05-21 08:21:50.387 | error | Failed to execute get_status on robot 6FkwKSEbh3Tm0119AtENqL TypeError: this.adapter.getMap is not a function at vacuum.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:279:31) at Roborock.updateDataMinimumData (/opt/iobroker/node_modules/iobroker.roborock/main.js:671:4)
-- | -- | -- | --
roborock.0 | 2024-05-21 07:23:57.525 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0 | 2024-05-21 06:32:25.042 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0 | 2024-05-21 06:32:07.604 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0 | 2024-05-21 06:31:34.976 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0 | 2024-05-21 06:29:11.213 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0 | 2024-05-21 06:26:47.228 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0 | 2024-05-21 06:20:47.108 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0 | 2024-05-21 06:17:47.053 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0 | 2024-05-21 06:14:08.623 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0 | 2024-05-21 06:11:47.374 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)
roborock.0 | 2024-05-21 06:08:47.030 | error | Failed to execute get_map_v1 on robot 6FkwKSEbh3Tm0119AtENqL TypeError: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received an instance of Array at new NodeError (node:internal/errors:405:5) at _write (node:internal/streams/writable:315:13) at Gzip.Writable.end (node:internal/streams/writable:612:17) at zlibBuffer (node:zlib:128:10) at Object.asyncBufferWrapper [as gzip] (node:zlib:800:12) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:67:10) at processTicksAndRejections (node:internal/process/task_queues:95:5)

@copystring
Copy link
Owner

Als Anhang ein LOG von mehreren Minuten. Mit der letzten DEV werden DeviceStatus und CleaningInfo nicht mehr aktualisiert, auch beim Neustart des Adapters nicht. Erst wenn ich den Adapter lösche und neu installiere funktioniert die Aktualisierung wieder.

log.txt

Ich glaube, ich konnte den Fehler ganz gut eingrenzen. Magst du es nochmal mit der neuen dev testen? https://github.com/copystring/ioBroker.roborock/tree/dev

@Norb1204
Copy link
Author

Geht noch nicht 100%, teilweise werden die Datenpunkte jede Sekunde aktualisiert. Es gibt auch noch ein paar Fehlermeldungen (siehe LOG).

log.txt

@copystring
Copy link
Owner

Das Aktualisieren jede Sekunde ist ab sofort erstmal so gewollt.
Zum Absturz: war das eine einmalige Sache oder kommt das ständig? Solche Abstürze sind besonders schwer zu finden.

@Norb1204
Copy link
Author

Nach einem Neustart des Adapters kommen noch Fehlermeldungen, danach aber keine mehr.
Die Aktualisierungsfrequenz von 1 sec ist natürlich schon sportlich. Ich hoffe aber dass Du dies irgendwann in den Griff bekommst.

Erst mal vielen Dank von meiner Seite

@copystring
Copy link
Owner

Das macht die Roborock App auch so. In der neuen dev habe ich es jetzt dennoch so angepasst, dass nur dann jede Sekunde aktualisiert wird, wenn das Webinterface verbunden ist. Ansonsten wird wie in der Config des Adapters aktualisiert. Standardmäßig alle 60 Sekunden.

Copy link

stale bot commented Jun 13, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Issues marked as stale label Jun 13, 2024
@nicomania
Copy link

danke auch von mir. @copystring kannst du das bitte ins beta repo schieben? dann teste ich auch mal.

@stale stale bot removed the stale Issues marked as stale label Jun 13, 2024
@copystring
Copy link
Owner

danke auch von mir. @copystring kannst du das bitte ins beta repo schieben? dann teste ich auch mal.

Ja, sobald ich die letzten Fehler in der dev-Version behoben habe, werde ich eine neue beta in latest bereitstellen. Die letzten Monate fehlt mir einiges an Zeit. Deshalb ist es etwas ruhiger geworden.

Copy link

stale bot commented Jun 29, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Issues marked as stale label Jun 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues marked as stale
Projects
None yet
Development

No branches or pull requests

3 participants