Hello everyone,
Current adapter status:
current version: 0.1.13
installation via npm is available
Node.js requirement is now >= 22
the state structure has been expanded quite a bit and remains stable under the same ioBroker paths for both Genie and M5/M9
it now includes status, diagnostics, location, consumable, zone, control, and command states
M5/M9-specific payloads for status, network, RTK, map status, and total mowing time/area are now also mapped into the existing state structure
on AWS IoT 403 responses, temporary IoT credentials are refreshed once automatically and the failed shadow read or command publish is retried
Over the last few days I also split up and cleaned up the adapter internally and expanded the checks so the internal modules and tests are validated properly. Functionally, this should not have changed any state IDs or command payload behavior.
The submission for the ioBroker latest repository has already been started and is currently waiting for review.
It would be especially helpful to get confirmations from users with an M5 or M9 that the new payload mappings work reliably in day-to-day use.
If anyone tests the current build, these points are especially interesting:
login and device discovery
shadow/status updates over longer runtimes
manual and automatic zone mowing
point mowing
near-charger mowing
behavior after connection issues or 403 errors
As always, feedback is welcome together with adapter version, js-controller version, Node.js version, and relevant log output.
