Provides the following:
- A Lawn Mower component for control of your MoeBot.
- Further controls to manage whether the MoeBot continues to mow during rain and how long to mow for.
- Ability to alter the multi-zone configuration of the mower (these entities are disabled by default).
- Sensors to monitor the working state, errors and battery level of the MoeBot
- A Vacuum component is also provided for legacy users, but will be removed in a future update.
Easiest install is via HACS
- Add the repository to your HACS install by clicking the button below:
- Restart HA
For manual installation for advanced users, copy custom_components/moebot
to your custom_components
folder in Home Assistant then continue from step 2 above.
Once you have installed the integration (per above)...
- Open the Home Assistant web interface.
- Navigate to "Configuration" > "Integrations".
- Click on the "+" button in the bottom right corner to add a new integration.
- Search for "MoeBot" and select it from the list.
- Enter the required details; Device ID, IP address and Local Key
- Click on "Submit" to complete the integration setup.
The Lawn Mower component as provided by Home Assistant only provides 3 states:
ERROR
- Device is in error state, needs assistance.PAUSED
- Paused during activity.MOWING
- Device is mowing.DOCKED
- Device is docked.
The MoeBot however provides many more states:
STANDBY
- the MoeBot is not mowing; it is either sitting idle in the mowing area or sitting in the dock fully charged.MOWING
- the MoeBot is mowing.FIXED_MOWING
- the MoeBot is mowing in a spiral pattern.CHARGING
- the MoeBot is in the dock charging.EMERGENCY
- the MoeBot is in some non-normal state, perhaps lifted off the ground.LOCKED
- the MoeBot UI is asking for the PIN to be entered.PAUSED
- the MoeBot is currently mowing but the job has been paused.PARK
- the MoeBot is following the boundary wire to return to the dock.CHARGING_WITH_TASK_SUSPEND
- the MoeBot is in the dock charging but will return to mow.ERROR
- the MoeBot is in some error state, perhaps it is outside of the boundary.
The MoeBot integration maps these states per the following table:
Lawn Mower State | MoeBot States |
---|---|
ERROR | EMERGENCY, ERROR, LOCKED |
PAUSED | PAUSED |
MOWING | MOWING, FIXED_MOWING, PARK |
DOCKED | STANDBY, CHARGING, CHARGING_WITH_TASK_SUSPEND |
Additional documentation is provided in the pymoebot
repository.
Unfortunately, 0.3.0 will probably be my last release of this integration since I have now purchased a new Luba 2 5000 and will be decommissioning my MoeBot.
Feel free to continue to log any issues you have an if possible, I may try and address these - though it will be difficult without a physical device to test against.
The following are a list of features I would like to have added if I continued with the MoeBot:
- Improve the current
ConfigFlow
for adding a MoeBot device; maybe attempt discovery or at least use the abilities oftinytuya
to identify the Local Key. - Provide additional sensors to show Tx/Rx message counts to the mower, including error counters (this would require an accompanying update to the pymoebot library).
- Investigate the benefit of moving to a single coordinator for this integration, per the newer integration development guides.
- Add statistic sensors that show the amount of time spent mowing in 24-hour and 1-week period.