Issues with new Luba 3 / Yuka models - Integration fails on restart

[JirkaSkr]

Description:
I am using the new Luba 3 (AWD) model and I am experiencing several critical issues that make the integration unstable. It seems the current library doesn't handle the response format of Luba 3 correctly.

Questions for the community:

Does anyone with Luba 2 experience the integration crashing and entities becoming "Unavailable" (N/A) after every Home Assistant restart?

Are there other Luba 3 users who have managed to get it working?

Specific issues I am facing with Luba 3:

Integration Crash on HA Restart: Every time Home Assistant restarts, the integration fails during the first refresh. It throws a TypeError: 'NoneType' object is not subscriptable in mammotion_mqtt.py at line 214 (trying to read res.data["result"]). This seems to happen because the mower returns null/None when queried for device versions, especially in certain modes (e.g., status 11).

Camera Stream is broken: The camera entity is created, but no stream is available.

Missing Mowing Map: The map doesn't load at all.

Zero Coordinates: The mower's position is stuck at 0,0, so it doesn't appear on the map even if the background loads.

Technical context:
The crash during restart seems to be caused by MammotionDeviceVersionUpdateCoordinator sending commands that Luba 3 doesn't respond to in the expected format. If the mower is in a specific state (like status 11), the whole integration gets blocked by HA because of the uncaught exception in the underlying library.

[mikey0000]

Hi, someone has opened an issue with the stack trace of this error and I'll fix it today

[JirkaSkr]

That's great news! Thank you for the quick response.
​I can confirm that the TypeError at line 214 in mammotion_mqtt.py is the main culprit that crashes the whole integration during Home Assistant startup.
​Let me know when the fix is ready, and I'll be happy to test it on my Luba 3 to see if it also resolves the missing map/coordinates and camera issues, or if those will need further investigation.

[JirkaSkr]

Hi,
​I've just updated to the latest version and performed a clean install (deleted integration, cleared cache, and re-added), but the issues with the Luba 3 (2026 model) persist:
​Entities Disabled: Most entities are created but are "Disabled/Blocked" by default. Even after manual enablement, they often show as "Unavailable".
​Zero Coordinates: GPS coordinates for the mower, dock, and RTK station are still reporting 0.0, so the map is not functioning at all.
​Camera Missing: The camera entity is completely missing or not being created for this model.
​Commands: Commands are still unresponsive.
​It seems the data structure or the communication protocol for the new Luba 3 / 2026 series is significantly different from previous models.
​Could you please look into the coordinator.py and how it handles the data fetch for the 2026 series? Let me know if you need specific logs from a certain period to debug this further.
​Thanks for your effort!

[mikey0000]

Logs help a lot, if it's all disabled it means something has failed during setup. Can you jump on discord so I can help you better? Creating a shared account I can use to debug the issues would also help move this along faster

[JirkaSkr]

"Hi Michael, I have the shared account ready for the Luba 3. To make the debugging and communication faster, could we chat on Telegram or WhatsApp?

My Telegram username is: @JirkaSk

Please add me there, and I will send you the login credentials and the current status of the mower. Looking forward to fixing those entities!"

[JirkaSkr]

`Hi Michael,

After updating to the latest Mammotion and PyMammotion versions (0.4.40 and 0.6.2) and performing a clean integration installation on Home Assistant 2026.3.1 (Container Core), critical issues with the Luba 3 AWD 5000 still persist:

After restarting Home Assistant, the integration activates, but all entities still show “not provided” or Unavailable.

GPS coordinates for the mower, dock, and RTK station remain 0,0, so maps do not display.

The camera entity is missing, and commands to the mower are unresponsive.

For reference, the device_tracker entity currently shows:
source_type: gps
battery_level: 80
latitude: -0.000008874577678295323
longitude: -0.000001908021663469863
gps_accuracy: 0
direction: -13
friendly_name: Luba-VAHFNZ3U

It seems that communication with the Luba 3 / 2026 series differs from older models, and coordinator.py still cannot correctly process the data for this series.

I can provide additional logs or a shared account if that helps debug the entity, map, and camera issues.

Thank you for your time and help!

Best regards,
[Jirka Skr]

[JirkaSkr]

Additional RTK data from the mower indicates that real coordinates do exist in the device response:

rtk.mqtt_rtk_info.latitude: 48.95171822113564
rtk.mqtt_rtk_info.longitude: 14.051648928324756

It seems that communication with the Luba 3 / 2026 series differs from older models, and coordinator.py still cannot correctly process the RTK data for this series.

I can provide additional logs or a shared account if that helps debug the entity, map, and camera issues.

Mammotion device data: {'sys': {'device_product_type_info': {'result': 116, 'main_product_type': 'LUBA 3 AWD 5000', 'sub_product_type': '116'}, 'toapp_dev_fw_info': {'result': 1, 'version': '2.2.1.66', 'mod': [{'type': 7, 'identify': '7-BmsBwCd6S5P', 'version': '5.16'}, {'type': 5, 'identify': '5-LubaGnssUM960', 'version': '19929'}, {'type': 9, 'identify': '9-LB2PLWheelG4BT', 'version': '1.2.0.486 (1603461e)'}, {'type': 3, 'identify': '3-LB2PLWheelG4', 'version': '1.2.0.491 (7c98a065)'}, {'type': 10, 'identify': '10-LB2PLWheelG4BT', 'version': '1.2.0.486 (1603461e)'}, {'type': 4, 'identify': '4-LB2PLWheelG4', 'version': '1.2.0.491 (7c98a065)'}, {'type': 8, 'identify': '8-LB2PLMCuH5BT', 'version': '5.1.2.2431 (d54a5dd32)'}, {'type': 1, 'identify': '1-LB2PLMCuH5', 'version': '5.1.2.2472 (013b34258)'}, {'type': 204, 'identify': '204-LB2PLFCutterG4BT', 'version': '1.2.0.486 (1603461e)'}, {'type': 203, 'identify': '203-LB2PLFCutterG4', 'version': '1.2.0.491 (7c98a065)'}, {'type': 11, 'identify': '11-LB2PLX5Bsp', 'version': '1.0.0.397 (375c5835c)'}, {'type': 12, 'identify': '12-LB2PLX5MidWare', 'version': '5.0.0.4655 (82acb0969)'}, {'type': 14, 'identify': '14-stm32llcc68', 'version': '5.1.2.62 (f370f70)'}, {'type': 16, 'identify': '16-EC200A', 'version': 'EC200AEUV1HAR02A07M16'}, {'type': 17, 'identify': '17-LdMid360', 'version': '35.01.1608'}]}, 'toapp_report_data': {'connect': {'connect_type': 2, 'wifi_rssi': -52, 'link_type': 3, 'mnet_rssi': -67, 'mnet_inet': 1, 'used_net': 'NET_USED_TYPE_WIFI', 'mnet_cfg': {'mnet_enable': True, 'inet_enable': True, 'apn': {'cfg': {'apn': [{'cid': 1, 'apn_name': 'orange.m2m.spec'}]}}}, 'dev_net_speed': {'download': 4216}, 'iot_wifi_report': True, 'iot_con_status': 1, 'wifi_con_status': 1, 'wifi_is_available': 1}, 'dev': {'sys_status': 11, 'charge_state': 1, 'battery_val': 80, 'sensor_status': 1, 'last_status': 10, 'sys_time_stamp': '1773771090', 'vslam_status': 1, 'mnet_info': {'model': 'EC200A', 'revision': 'EC200AEUV1HAR02A07M16', 'imei': '863819074688531', 'sim': 'SIM_OK', 'imsi': '208012407142269', 'link_type': 'MNET_LINK_4G', 'rssi': -67, 'inet': {'connect': True, 'ip': 181877984, 'mask': 4278190080, 'gateway': 181877791}, 'iccid': '89330125377810526920', 'operator': '23003'}, 'vio_survival_info': {}, 'collector_status': {}, 'self_check_status': 10, 'fpv_info': {'wifi_available': -1}}, 'rtk': {'status': 4, 'gps_stars': 28, 'dis_status': '216172791159260160', 'co_view_stars': 5654, 'lora_info': {'pair_code_scan': 868, 'pair_code_channel': 3, 'pair_code_locid': 388, 'pair_code_netid': 393, 'lora_connection_status': 1}, 'mqtt_rtk_info': {'rtk_switch': 'RTK_USED_NRTK', 'rtk_channel': 1, 'latitude': 48.95171822113564, 'longitude': 14.051648928324756, 'nrtk_map_convert_status': 1, 'nrtk_net_mode': 1, 'new_rtk_mode': 1}}, 'locations': [{'real_pos_x': -2124, 'real_pos_y': -9813, 'real_toward': -138422, 'pos_type': 4, 'bol_hash': '3121429447574796790'}], 'work': {'path_hash': '1', 'real_path_num': '1', 'ub_zone_hash': '7482302840242147780', 'init_cfg_hash': '8698591852198060591', 'ub_ecode_hash': '3924873099890303549', 'knife_height': 70, 'nav_heading_state': {}, 'cutter_width': -1.0}, 'vio_to_app_info': {}, 'vision_statistic_info': {}, 'basestation_info': {'connect_status_since_poweron': 2}}, 'bidire_comm_cmd': {'rw': 1, 'id': 5, 'context': 3}, 'system_update_buf': {'update_buf_data': ['3', '0', '0']}}, 'net': {'toapp_networkinfo_rsp': {'req_ids': 1, 'wifi_ssid': 'LUBA_3', 'wifi_mac': '94:ba:06:4d:b8:7e', 'wifi_rssi': -52, 'ip': 3232235891, 'mask': 4294967040, 'gateway': 3232235777}, 'toapp_devinfo_resp': {'resp_ids': [{'id': 1, 'type': 6, 'res': 'DRV_RESULT_SUC', 'info': '2.2.1.66'}, {'id': 1, 'type': 3, 'res': 'DRV_RESULT_SUC', 'info': '5.1.2.2472 (013b34258)'}, {'id': 2, 'type': 3}, {'id': 3, 'type': 3, 'res': 'DRV_RESULT_SUC', 'info': '1.2.0.491 (7c98a065)'}, {'id': 4, 'type': 3, 'res': 'DRV_RESULT_SUC', 'info': '1.2.0.491 (7c98a065)'}, {'id': 5, 'type': 3, 'res': 'DRV_RESULT_SUC', 'info': '19929'}, {'id': 6, 'type': 3}, {'id': 7, 'type': 3, 'res': 'DRV_RESULT_SUC', 'info': '5.16'}]}}}

[mikey0000]

I can't add you on telegram with that username

[JirkaSkr]

@JirkaSk

[JirkaSkr]

right Jirkask

[mikey0000]

I can't add you using that username

[JirkaSkr]

GitHub automatically changed the capitalization of my Telegram username. My correct username is all lowercase: @JirkaSk. Please use this to contact me directly.

[mikey0000]

Finally found you, added

[Widgee9]

any update? Luba3 now supported?

[mikey0000]

0.5.0-beta27