Support / Controlling the robot / Home Assistant

Home Assistant: watching Yarbo from your own dashboard

Yardstick adds your robot to Home Assistant with its own integration, which Home Assistant finds on your network by itself. It is six read-only sensors: battery, online, charging, activity, RTK signal and fault code. Nothing here can move the robot.

Read-only, and that is deliberate Yardstick publishes six sensors to Home Assistant and nothing else. There are no switches, no buttons and no number controls: you can watch your robot from Home Assistant, but you cannot drive it from there. Driving is done from Yardstick's own controller, behind its own password.

What you get

One device per robot, with six entities. Every one is read-only.

If you are looking for switches Earlier versions of this page listed entities for blades, lights, the camera, blower speed, blade height and more. Those were never published. The page described an integration that was not built, and it has been corrected. The six above are the whole of it.

How it connects

Home Assistant talks to Yardstick, and Yardstick talks to your robot. The first hop is on your own network. The second goes through your Yarbo account, the same way the Yarbo app reaches the robot, so the sensors are as current as Yardstick's own page and need the same internet connection Yardstick does.

Turning it on

The Home Assistant section of Settings: an Add to Home Assistant button, three setup steps for HACS, this computer's address, and a note that the integration is read only.
Settings → Home Assistant. The button adds Yardstick to HACS; the address below it is the manual fallback.
Safety, and who is in charge Nothing here can start, stop or move the robot. If you want automations that act, they have to act through Yarbo's own app or Yardstick's controller, and Yarbo's safety systems always take priority over anything either of us does.

Getting notifications on your phone

This is the main reason people wire Yardstick into Home Assistant. Yardstick has its own alerts, and they can push to a phone through ntfy or land in your email. But once the robot is in Home Assistant as ordinary sensors, you can send the notification with Home Assistant instead, and it goes anywhere Home Assistant already reaches.

That matters most on Android, where the Home Assistant companion app is very likely already on your phone, so this is one fewer app than setting up ntfy. It works exactly the same on an iPhone. And because you are writing the automation yourself, the alert can do more than appear on a screen: announce itself on a speaker, turn a lamp red, go to everybody in the house, or only bother you between certain hours.

You need the companion app installed and signed in, which gives you a notify service named after the device, something like notify.mobile_app_pixel_9. Home Assistant lists yours under Developer tools → Actions.

A fault code appears

The one worth setting up first. sensor.<robot>_fault_code is empty when all is well, so anything landing in it is the robot telling you it has a problem.

automation:
  - alias: "Yarbo reported a fault"
    trigger:
      - platform: state
        entity_id: sensor.<robot>_fault_code
    condition:
      - condition: template
        value_template: "{{ trigger.to_state.state not in ['', 'unknown', 'unavailable', 'none'] }}"
    action:
      - action: notify.mobile_app_<your_phone>
        data:
          title: "Yarbo has stopped"
          message: "Fault code {{ trigger.to_state.state }}."

The robot has gone quiet

binary_sensor.<robot>_online goes off when Yardstick stops hearing from the robot. Give it a few minutes before it tells you, so a brief blip in the yard does not wake your phone.

automation:
  - alias: "Yarbo went offline"
    trigger:
      - platform: state
        entity_id: binary_sensor.<robot>_online
        to: "off"
        for: "00:10:00"
    action:
      - action: notify.mobile_app_<your_phone>
        data:
          message: "No word from Yarbo for ten minutes."

It finished, or the battery is low

sensor.<robot>_activity and sensor.<robot>_battery cover the everyday ones. Battery is a normal percentage, so a numeric trigger works the way you would expect.

automation:
  - alias: "Yarbo battery is low"
    trigger:
      - platform: numeric_state
        entity_id: sensor.<robot>_battery
        below: 20
    action:
      - action: notify.mobile_app_<your_phone>
        data:
          message: "Yarbo is down to {{ states('sensor.<robot>_battery') }} percent."
Finding your real entity names <robot> is the name you gave the robot, in lower case with underscores, so a robot called Front Yard gives sensor.front_yard_battery. Or skip the guesswork: in Home Assistant go to Settings → Devices & services → Yardstick, open the device, and every entity is listed with its exact name. Copy them from there.
Two alerting systems, not one If you build these, consider turning Yardstick’s own ntfy or email alerts off for the same conditions, or you will get told twice about the same thing. Yardstick’s alerts and your Home Assistant automations do not know about each other. They also fail differently, which is occasionally useful: Yardstick’s alerts keep working when Home Assistant is down, and these keep working if Yardstick’s email account stops accepting logins.
This still cannot move the robot Everything on this page is read only, notifications included. An automation can tell you the robot is stuck; it cannot go and fetch it.

If something is not right

⚠

Error codes

What the fault code sensor is reporting.
🔔

Alerts

Being told about problems without building automations.
FeaturesPricingSupportForumDownloadChangelogReviewsTermsPrivacy

Yardstick is an independent tool for Yarbo robots. Not affiliated with or endorsed by Yarbo Inc. · © 2026 Yardstick Technologies LLC.