[TEST] Mammotion – Adapter für Mammotion Luba / Yuka

stolly82

@Freak Lag wohl an dem Mammotion Server issue, heute sind die Zonen alle da gewesen.

Ich versuche es gerade raus zu bekommen, warum der Luba 2 die Zonen nicht über die normalen Calls raus gibt.

@randyandy

Leider bekomme ich aber keinen Kontakt zu meinen Robotern.

Was bedeutet das genau? Nichts da an Objekte oder wie?

Freak

@stolly82

Ah ok, super. Das mit der RTK Antenne will ja auch nicht klappen, aber dann kann ich mir das sparen.

RandyAndy

@stolly82

genau die Roboter and RTK IDs werden nicht angezeigt.
Sieht bei mir so aus:

Andreas

Jaschkopf

Moin. Hab gerade nochmal versucht die Zonen abzufragen. Hatte den Adapter zwischenzeitlich deaktiviert und momentan stürzt er nach ca. 40sek ab. Hier das Log:

host.iobroker
2026-04-20 19:07:10.312	warn	Do not restart adapter system.adapter.mammotion.0 because restart loop detected

host.iobroker
2026-04-20 19:07:10.312	info	Restart adapter system.adapter.mammotion.0 because enabled

host.iobroker
2026-04-20 19:07:10.312	error	instance system.adapter.mammotion.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

influxdb.0
2026-04-20 19:07:09.946	info	Store 1001 buffered influxDB history points

mammotion.0
2026-04-20 19:07:09.766	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

mammotion.0
2026-04-20 19:07:09.766	info	terminating

mammotion.0
2026-04-20 19:07:09.765	error	connack timeout

mammotion.0
2026-04-20 19:07:09.765	error	Error: connack timeout at Timeout._onTimeout (/opt/iobroker/node_modules/mqtt/build/lib/client.js:363:32) at listOnTimeout (node:internal/timers:588:17) at process.processTimers (node:internal/timers:523:7)

mammotion.0
2026-04-20 19:07:09.764	error	uncaught exception: connack timeout

mammotion.0
2026-04-20 19:07:06.452	debug	Area-Name-Re-Request (missing) failed for Luba-VSY6PEGK: Request failed with status code 429

mammotion.0
2026-04-20 19:07:06.431	warn	Modern command path returned Invalid device for Luba-VSY6PEGK, trying Aliyun fallback.

mammotion.0
2026-04-20 19:07:06.323	debug	JWT MQTT connection closed

mammotion.0
2026-04-20 19:07:06.323	debug	JWT MQTT offline

mammotion.0
2026-04-20 19:07:06.314	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for Luba-VSY6PEGK, receiver=1

mammotion.0
2026-04-20 19:07:06.313	debug	Area-Name-Re-Request (missing) failed for RTKBEU240470930: Request failed with status code 429

mammotion.0
2026-04-20 19:07:06.262	warn	Modern command path returned Invalid device for RTKBEU240470930, trying Aliyun fallback.

mammotion.0
2026-04-20 19:07:06.141	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for RTKBEU240470930, receiver=1

mammotion.0
2026-04-20 19:07:06.139	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/property/post

mammotion.0
2026-04-20 19:07:06.139	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/thing/event/property/post_reply

mammotion.0
2026-04-20 19:07:06.139	debug	[MQTT] Physical device topic reachable: /sys/proto/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post

mammotion.0
2026-04-20 19:07:06.139	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post

mammotion.0
2026-04-20 19:07:06.139	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/property/post

mammotion.0
2026-04-20 19:07:06.139	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/app/down/thing/event/property/post_reply

mammotion.0
2026-04-20 19:07:06.139	debug	[MQTT] Physical device topic reachable: /sys/proto/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post

mammotion.0
2026-04-20 19:07:06.139	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post

mammotion.0
2026-04-20 19:07:06.139	info	MQTT connected.

mammotion.0
2026-04-20 19:07:05.934	debug	Aliyun MQTT connection closed

mammotion.0
2026-04-20 19:07:05.933	debug	Aliyun MQTT offline

mammotion.0
2026-04-20 19:07:01.218	debug	Area-Name-Re-Request (missing) failed for Luba-VSY6PEGK: Request failed with status code 429

mammotion.0
2026-04-20 19:07:01.190	warn	Modern command path returned Invalid device for Luba-VSY6PEGK, trying Aliyun fallback.

mammotion.0
2026-04-20 19:07:01.074	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for Luba-VSY6PEGK, receiver=1

mammotion.0
2026-04-20 19:07:01.073	debug	Area-Name-Re-Request (missing) failed for RTKBEU240470930: Request failed with status code 429

mammotion.0
2026-04-20 19:07:01.056	warn	Modern command path returned Invalid device for RTKBEU240470930, trying Aliyun fallback.

mammotion.0
2026-04-20 19:07:01.046	debug	JWT MQTT connection closed

mammotion.0
2026-04-20 19:07:01.046	debug	JWT MQTT offline

mammotion.0
2026-04-20 19:07:00.931	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for RTKBEU240470930, receiver=1

mammotion.0
2026-04-20 19:07:00.928	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/property/post

mammotion.0
2026-04-20 19:07:00.928	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/thing/event/property/post_reply

mammotion.0
2026-04-20 19:07:00.928	debug	[MQTT] Physical device topic reachable: /sys/proto/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post

mammotion.0
2026-04-20 19:07:00.928	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post

mammotion.0
2026-04-20 19:07:00.928	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/property/post

mammotion.0
2026-04-20 19:07:00.928	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/app/down/thing/event/property/post_reply

mammotion.0
2026-04-20 19:07:00.928	debug	[MQTT] Physical device topic reachable: /sys/proto/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post

mammotion.0
2026-04-20 19:07:00.928	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post

mammotion.0
2026-04-20 19:07:00.928	info	MQTT connected.

mammotion.0
2026-04-20 19:06:55.998	debug	Area-Name-Re-Request (missing) failed for Luba-VSY6PEGK: Request failed with status code 429

mammotion.0
2026-04-20 19:06:55.981	warn	Modern command path returned Invalid device for Luba-VSY6PEGK, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:55.976	debug	[PROPS] Property keys for qTfCnXxDojviovYWZhqH000000: iotState, deviceVersionInfo, extMod, knifeHeight, leftMotorBootVersion, iotMsgHz, rtMrMod, iotMsgTotal, loraRawConfig, loraGeneralConfig, leftMotorVersion, betInfo, coordinate, intMod, bmsVersion, stm32H7Version, rightMotorVersion, rightMotorBootVersion, deviceVersion, rtkVersion, ltMrMod, networkInfo, bmsHardwareVersion, batteryPercentage, deviceState, deviceOtherInfo, mcBootVersion

mammotion.0
2026-04-20 19:06:55.873	debug	Aliyun MQTT ensure ok (jwt-offline).

mammotion.0
2026-04-20 19:06:55.872	debug	[ALIYUN-MQTT] Connecting to a5vlvzwIhhj.iot-as-mqtt.eu-central-1.aliyuncs.com:1883 as 81c8d51ab696a9bcc3c6306890b2f090&a5vlvzwIhhj

mammotion.0
2026-04-20 19:06:55.872	debug	JWT MQTT connection closed

mammotion.0
2026-04-20 19:06:55.872	debug	JWT MQTT offline

mammotion.0
2026-04-20 19:06:55.865	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for Luba-VSY6PEGK, receiver=1

mammotion.0
2026-04-20 19:06:55.822	debug	Area-Name-Re-Request (missing) failed for RTKBEU240470930: Request failed with status code 429

mammotion.0
2026-04-20 19:06:55.805	warn	Modern command path returned Invalid device for RTKBEU240470930, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:55.688	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for RTKBEU240470930, receiver=1

mammotion.0
2026-04-20 19:06:55.686	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/property/post

mammotion.0
2026-04-20 19:06:55.686	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/thing/event/property/post_reply

mammotion.0
2026-04-20 19:06:55.686	debug	[MQTT] Physical device topic reachable: /sys/proto/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post

mammotion.0
2026-04-20 19:06:55.686	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post

mammotion.0
2026-04-20 19:06:55.686	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/property/post

mammotion.0
2026-04-20 19:06:55.686	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/app/down/thing/event/property/post_reply

mammotion.0
2026-04-20 19:06:55.686	debug	[MQTT] Physical device topic reachable: /sys/proto/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post

mammotion.0
2026-04-20 19:06:55.685	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post

mammotion.0
2026-04-20 19:06:55.685	info	MQTT connected.

mammotion.0
2026-04-20 19:06:55.590	debug	[PROPS] Property keys for mNT5fCoPVHU90gjmPygZ000000: coordinate, networkInfo, otaProgress, mcuVersion, loraVersion, deviceVersionInfo, deviceVersion, loraGeneralConfig, deviceOtherInfo, rtkVersion

mammotion.0
2026-04-20 19:06:50.786	debug	Area-Name-Re-Request (missing) failed for Luba-VSY6PEGK: Request failed with status code 429

mammotion.0
2026-04-20 19:06:50.767	warn	Modern command path returned Invalid device for Luba-VSY6PEGK, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:50.651	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for Luba-VSY6PEGK, receiver=1

mammotion.0
2026-04-20 19:06:50.650	debug	Area-Name-Re-Request (missing) failed for RTKBEU240470930: Request failed with status code 429

mammotion.0
2026-04-20 19:06:50.631	warn	Modern command path returned Invalid device for RTKBEU240470930, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:50.629	debug	JWT MQTT connection closed

mammotion.0
2026-04-20 19:06:50.629	debug	JWT MQTT offline

mammotion.0
2026-04-20 19:06:50.517	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for RTKBEU240470930, receiver=1

mammotion.0
2026-04-20 19:06:50.515	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/property/post

mammotion.0
2026-04-20 19:06:50.514	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/thing/event/property/post_reply

mammotion.0
2026-04-20 19:06:50.514	debug	[MQTT] Physical device topic reachable: /sys/proto/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post

mammotion.0
2026-04-20 19:06:50.514	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post

mammotion.0
2026-04-20 19:06:50.514	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/property/post

mammotion.0
2026-04-20 19:06:50.514	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/app/down/thing/event/property/post_reply

mammotion.0
2026-04-20 19:06:50.514	debug	[MQTT] Physical device topic reachable: /sys/proto/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post

mammotion.0
2026-04-20 19:06:50.514	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post

mammotion.0
2026-04-20 19:06:50.514	info	MQTT connected.

mammotion.0
2026-04-20 19:06:49.763	debug	Aliyun MQTT connection closed

mammotion.0
2026-04-20 19:06:49.763	debug	Aliyun MQTT offline

mammotion.0
2026-04-20 19:06:45.710	debug	Area-Name-Re-Request (missing) failed for Luba-VSY6PEGK: Request failed with status code 429

mammotion.0
2026-04-20 19:06:45.692	warn	Modern command path returned Invalid device for Luba-VSY6PEGK, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:45.570	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for Luba-VSY6PEGK, receiver=1

mammotion.0
2026-04-20 19:06:45.567	debug	Area-Name-Re-Request (missing) failed for RTKBEU240470930: Request failed with status code 429

mammotion.0
2026-04-20 19:06:45.495	warn	Modern command path returned Invalid device for RTKBEU240470930, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:45.458	debug	JWT MQTT connection closed

mammotion.0
2026-04-20 19:06:45.458	debug	JWT MQTT offline

mammotion.0
2026-04-20 19:06:45.341	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for RTKBEU240470930, receiver=1

mammotion.0
2026-04-20 19:06:45.338	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/property/post

mammotion.0
2026-04-20 19:06:45.338	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/thing/event/property/post_reply

mammotion.0
2026-04-20 19:06:45.338	debug	[MQTT] Physical device topic reachable: /sys/proto/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post

mammotion.0
2026-04-20 19:06:45.338	debug	[MQTT] Physical device topic reachable: /sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post

mammotion.0
2026-04-20 19:06:45.338	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/property/post

mammotion.0
2026-04-20 19:06:45.338	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/app/down/thing/event/property/post_reply

mammotion.0
2026-04-20 19:06:45.338	debug	[MQTT] Physical device topic reachable: /sys/proto/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post

mammotion.0
2026-04-20 19:06:45.338	debug	[MQTT] Physical device topic reachable: /sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post

mammotion.0
2026-04-20 19:06:45.337	info	MQTT connected.

mammotion.0
2026-04-20 19:06:40.282	warn	MQTT subscribe failed (/sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/property/post): Connection closed

mammotion.0
2026-04-20 19:06:40.282	warn	MQTT subscribe failed (/sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/thing/event/property/post_reply): Connection closed

mammotion.0
2026-04-20 19:06:40.282	warn	MQTT subscribe failed (/sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/_thing/event/notify): Connection closed

mammotion.0
2026-04-20 19:06:40.282	warn	MQTT subscribe failed (/sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/thing/model/down_raw): Connection closed

mammotion.0
2026-04-20 19:06:40.282	warn	MQTT subscribe failed (/sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/thing/events): Connection closed

mammotion.0
2026-04-20 19:06:40.282	warn	MQTT subscribe failed (/sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/thing/properties): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/proto/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/a1LLmy1zc0j/Luba-VSY6PEGK/thing/event/+/post): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/a1LLmy1zc0j/Luba-VSY6PEGK/app/down/thing/status): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/property/post): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/a1Nc68bGZzX/RTKBEU240470930/app/down/thing/event/property/post_reply): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/a1Nc68bGZzX/RTKBEU240470930/app/down/_thing/event/notify): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/a1Nc68bGZzX/RTKBEU240470930/app/down/thing/model/down_raw): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/a1Nc68bGZzX/RTKBEU240470930/app/down/thing/events): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/a1Nc68bGZzX/RTKBEU240470930/app/down/thing/properties): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/proto/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/a1Nc68bGZzX/RTKBEU240470930/thing/event/+/post): Connection closed

mammotion.0
2026-04-20 19:06:40.281	warn	MQTT subscribe failed (/sys/a1Nc68bGZzX/RTKBEU240470930/app/down/thing/status): Connection closed

mammotion.0
2026-04-20 19:06:40.280	debug	JWT MQTT connection closed

mammotion.0
2026-04-20 19:06:40.280	debug	JWT MQTT offline

mammotion.0
2026-04-20 19:06:40.198	debug	[PROPS] Property keys for qTfCnXxDojviovYWZhqH000000: iotState, deviceVersionInfo, extMod, knifeHeight, leftMotorBootVersion, rtMrMod, iotMsgHz, iotMsgTotal, loraRawConfig, loraGeneralConfig, leftMotorVersion, betInfo, intMod, coordinate, bmsVersion, stm32H7Version, rightMotorVersion, rightMotorBootVersion, deviceVersion, rtkVersion, ltMrMod, networkInfo, bmsHardwareVersion, batteryPercentage, deviceState, deviceOtherInfo, mcBootVersion

mammotion.0
2026-04-20 19:06:39.842	info	Initialization successful: 2 device(s), telemetry via MQTT.

mammotion.0
2026-04-20 19:06:39.842	debug	Area-name request failed for Luba-VSY6PEGK: Request failed with status code 429

mammotion.0
2026-04-20 19:06:39.825	warn	Modern command path returned Invalid device for Luba-VSY6PEGK, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:39.710	debug	Aliyun MQTT ensure ok (start-polling).

mammotion.0
2026-04-20 19:06:39.709	debug	[ALIYUN-MQTT] Connecting to a5vlvzwIhhj.iot-as-mqtt.eu-central-1.aliyuncs.com:1883 as 81c8d51ab696a9bcc3c6306890b2f090&a5vlvzwIhhj

mammotion.0
2026-04-20 19:06:39.709	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for Luba-VSY6PEGK, receiver=1

mammotion.0
2026-04-20 19:06:39.708	debug	Area-name request failed for RTKBEU240470930: Request failed with status code 429

mammotion.0
2026-04-20 19:06:39.691	warn	Modern command path returned Invalid device for RTKBEU240470930, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:39.598	debug	Area-Name-Re-Request (missing) failed for Luba-VSY6PEGK: Request failed with status code 429

mammotion.0
2026-04-20 19:06:39.580	warn	Modern command path returned Invalid device for Luba-VSY6PEGK, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:39.575	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for RTKBEU240470930, receiver=1

mammotion.0
2026-04-20 19:06:39.575	debug	IoT sync for Luba-VSY6PEGK failed: Request failed with status code 429

mammotion.0
2026-04-20 19:06:39.557	warn	Modern command path returned Invalid device for Luba-VSY6PEGK, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:39.464	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for Luba-VSY6PEGK, receiver=1

mammotion.0
2026-04-20 19:06:39.462	debug	Area-Name-Re-Request (missing) failed for RTKBEU240470930: Request failed with status code 429

mammotion.0
2026-04-20 19:06:39.444	warn	Modern command path returned Invalid device for RTKBEU240470930, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:39.442	debug	IoT sync for RTKBEU240470930 failed: Request failed with status code 429

mammotion.0
2026-04-20 19:06:39.401	debug	[PROPS] Property keys for mNT5fCoPVHU90gjmPygZ000000: coordinate, networkInfo, otaProgress, mcuVersion, loraVersion, deviceVersionInfo, deviceVersion, loraGeneralConfig, deviceOtherInfo, rtkVersion

mammotion.0
2026-04-20 19:06:39.391	warn	Modern command path returned Invalid device for RTKBEU240470930, trying Aliyun fallback.

mammotion.0
2026-04-20 19:06:39.293	debug	[AREA-REQ] Sending sub_cmd=3 (AppGetAllAreaHashName) for RTKBEU240470930, receiver=1

mammotion.0
2026-04-20 19:06:39.289	info	MQTT connected.

mammotion.0
2026-04-20 19:06:34.582	info	starting. Version 0.0.7 (non-npm: DNAngelX/ioBroker.mammotion#9a5ddba9a906e60e81c8ea93406d8658c533e8bc) in /opt/iobroker/node_modules/iobroker.mammotion, node: v22.18.0, js-controller: 7.0.7

host.iobroker
2026-04-20 19:06:33.694	info	instance system.adapter.mammotion.0 in version "0.0.7" (non-npm: DNAngelX/ioBroker.mammotion#9a5ddba9a906e60e81c8ea93406d8658c533e8bc) started with pid 1304960

host.iobroker
2026-04-20 19:06:33.105	info	"system.adapter.mammotion.0" enabled

Machen die Mammotion Server wieder doof?

stolly82

@jaschkopf
bin dran,... bekomme jetzt auch mit meinem Luba keine einzige Zone mehr.

Jaschkopf

Gibt's schon Neuigkeiten?

stolly82

@jaschkopf

Leider nein!

Die Zonen kommen per MQTT und die scheinen da irgendwas geändert zu haben mit dem letztem
Update.

Ich muss den Netzwerk Verkehr per MQTT loggen, was nicht über die Standard Logger funktioniert, da die in der Regel nur HTTP und HTTPS loggen können.

Ist leider nicht „mal eben“ gemacht.

Jaschkopf

Schade, wenn ich irgendwie unterstützen kann sag bescheid

m1k3f15h

Hy,
Bekomme ständig das im log:

Was kann ich tun?
Mike

stolly82

@m1k3f15h sagte:

Hy,
Bekomme ständig das im log:

Was kann ich tun?
Mike

Was stört dich an dem log genau? Geht der Rest?

Beachtet, der Adapter ist im development und Nix it stable und Zonen scheinen aktuell nickt zu funktionieren.

Community Forum

NEWS

[TEST] Mammotion – Adapter für Mammotion Luba / Yuka

Support us

506

32.9k

83.0k

1.3m