Neues YouTube-Video: Visualisierung im Devices-Adapter

[reloxx13]

Info
Adapter	anthbot-genie
Version	0.1.5
npm latest	0.1.5
npm next	-
Source	npm / GitHub
GitHub	https://github.com/reloxx13/ioBroker.anthbot-genie
npm	https://www.npmjs.com/package/iobroker.anthbot-genie
Package	iobroker.anthbot-genie
js-controller	>= 6.0.11
Admin	>= 7.6.20
Node.js	>= 20
Connection	Cloud
Status	latest
Note	unofficial, not affiliated with Anthbot

Hello everyone,

I would like to make version 0.1.x of my ioBroker adapter for Anthbot Genie robotic lawn mowers available.

The adapter is an unofficial cloud adapter for Anthbot Mowrobots. It logs in to the Anthbot Cloud, discovers the available devices, determines the region and IoT endpoints, and regularly polls status data from the robotic mower. In addition, it provides writable states for settings, mowing commands, docking, maintenance, and zones.

Features

• Anthbot Cloud login
• Device discovery
• Region and IoT endpoint detection
• Polling of mower property shadow and service shadow
• Status, metric, diagnostic, and raw-data states per robotic mower
• Control commands via ioBroker states
• Full-area mowing, manual zone mowing, and automatic zone mowing
• Spot mowing, edge mowing, and mowing near the charging station
• Start, pause, resume, stop, and finish mowing tasks
• Return to charging station, including pausing the return trip
• Maintenance commands such as find robot, grass disposal, and disc maintenance mode
• Consumable states for charging port, cameras, and blades, including reset buttons
• Rain and mowing parameter control
• Password is stored as encrypted native configuration

Requirements

• ioBroker with js-controller >= 6.0.11
• Admin >= 7.6.20
• Node.js >= 20
• Anthbot account with a configured Genie robotic mower

Created States

For each detected robotic mower, the following areas are created, among others:

• info.*
• metrics.*
• diagnostics.*
• location.*
• consumable.*
• controls.*
• commands.*
• zones.*
• raw.*

Important Notes for 0.1.x

• new grouped state structure under metrics, diagnostics, consumable, controls, commands, zones, and raw
• diagnostic values for RTK, firmware, OTA, network, GPS/position, map, and errors
• reset buttons for charging port, camera, and blade lifetime
• new commands: find robot, grass disposal, disc maintenance mode, edge mowing, mowing near the charging station, and spot mowing
• task commands: pause/resume mowing, pause return trip, and finish mowing
• control for mowing near the charging station
• full-area mowing with optional edge cutting
• RTK antenna moved warning and command to reset this warning

Some commands may not be available or may be rejected by the mower depending on the model, firmware, current mower state, and available map/edge data.

Manual Zone Mowing

The known manual zones are stored as a JSON array under the following state:

<instance>.<serial>.zones.manual.list

[reloxx13]

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.