Test Adapter anthbot-genie v0.1.x

reloxx13

License

Info
Adapter	`anthbot-genie`
Version	`0.1.13`
npm latest	`0.1.13`
Source	npm
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	`>= 22`
Connection	Cloud
Status	latest
Note	unofficial, not affiliated with Anthbot

Hello everyone,

Version 0.1.13 of my ioBroker adapter for Anthbot Genie robotic mowers is now available in the ioBroker latest repository.

The adapter is an unofficial cloud adapter for Anthbot Genie. It logs in to the Anthbot Cloud, discovers the available devices, resolves the region and IoT endpoints, and regularly polls mower status data. It also provides writable states for settings, mowing commands, docking, maintenance, and zones. The state structure stays stable under the same ioBroker paths for Genie 600/1000/3000/5000 as well as M5/M9 models.

Features

Anthbot Cloud login
device discovery
region and IoT endpoint resolution
polling of mower property shadow and service shadow
automatic refresh of temporary IoT credentials after AWS IoT 403
status, metrics, diagnostics, and raw data states per mower
location states for GPS and local position data
M5/M9 mappings for status, battery, errors, network, RTK, map, and total mowing time/area
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 terminate mowing tasks
return to the charging station including pause while returning
maintenance commands such as find robot, grass discharge, and disc maintenance mode
consumable states for charging port, cameras, and blades including reset buttons
rain, obstacle, voice volume, and mowing parameter controls
raw data for property shadow, service shadow, Anthbot event code translations, and area definitions
password is stored as encrypted native configuration

Requirements

ioBroker with js-controller >= 6.0.11
ioBroker Admin >= 7.6.20
Node.js >= 22
Anthbot account with at least one connected Anthbot mower

Created States

For each detected mower, the adapter creates the following sections among others:

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

Current Highlights in 0.1.13

available through the ioBroker latest repository
grouped state structure under metrics, diagnostics, consumable, controls, commands, zones, and raw
M5/M9 payloads for status, battery, errors, network, RTK, map, and total mowing time/area are mapped into the existing state structure
temporary IoT credentials are refreshed automatically once after AWS IoT 403, and the failed shadow read or command publish is retried
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 discharge, disc maintenance mode, edge mowing, mowing near the charging station, and spot mowing
task commands: pause/resume mowing, pause return trip, and terminate mowing
control for mowing near the charging station
full-area mowing with optional edge cutting
RTK antenna moved warning and command to clear that warning

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

Manual Zone Mowing

Known manual zones are stored as a JSON array under this state:

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

To start one or more zones, write to this state:

<instance>.<serial>.commands.mowing.startZone

Accepted values:

single zone by ID: 3
single zone by name: Front yard
multiple zones, comma-separated: 3,5,Back yard
multiple zones as JSON array: [3,5,"Back yard"]

Automatic zones are available under <instance>.<serial>.zones.autoList and are started with <instance>.<serial>.commands.mowing.startAutoZone.

Spot Mowing

Spot mowing is started through this state:

<instance>.<serial>.commands.mowing.startPoint

Accepted values:

coordinates as text: 123,456
coordinates as JSON object: {"x":123,"y":456}

After successful execution, the state is cleared again.

What Feedback Is Helpful

login with Anthbot account
detection of one or more mowers
updates of status, metrics, diagnostic values, and connection state
M5/M9 mappings for status, network, RTK, map status, and total mowing values
start, pause, resume, stop, and terminate mowing tasks
return to the charging station and pausing the return trip
manual and automatic zone mowing, if zones exist in the Anthbot app
spot mowing, edge mowing, and mowing near the charging station, if supported by the device
resetting consumable values only when the corresponding lifetime value is at or below 5 percent
behavior with wrong credentials, cloud connection issues, or AWS IoT 403

Please include adapter version, ioBroker/js-controller version, Node.js version, and relevant log excerpts when posting feedback. Please do not publish credentials, tokens, serial numbers, or other personal data.

Note: The adapter is unofficial and is not affiliated with or supported by Anthbot.

Transparency Note

AI was used as a supporting tool while creating this adapter, especially for code drafting, structuring, documentation, and review. Technical responsibility, testing, and publishing remain with the developer.

Installation

Via ioBroker Admin

Open the adapter view.
If the latest repository is not active yet, select or enable latest in ioBroker Admin under Settings -> Repositories and refresh the adapter list.
Search for anthbot-genie in the latest repository and install the adapter.
Create an adapter instance after installation.
Enter Anthbot username, password, and country code in the adapter configuration.
Start the instance and check the log and states.

Via CLI

Install the current version via npm:

iobroker repo set latest
iobroker update
iobroker add anthbot-genie

Or install the exact version:

iobroker add anthbot-genie@0.1.13

If the instance was not created automatically after installation:

iobroker add anthbot-genie --enabled

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 adapter is now included in the ioBroker latest repository and can be installed directly from the ioBroker adapter view.

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.

reloxx13

Adapter got added to latest repo!

Community Forum

NEWS