GitHub Issue / Briefing for markus-lassfolk/home-assistant-yarbo 31.07.2026 13:08 #169

Yarbo Product Talk
1

yarbojs-crypto started this conversation in Show and tell

yarbojs-crypto40 minutes ago

I am running a commercial Yarbo service operation in Switzerland, currently monitoring 5 Yarbo Lawn Mower Pro robots across multiple customer sites. I use Home Assistant as my central monitoring platform and have built a custom WhatsApp alert system (via CallMeBot) on top of your integration to notify myself and service agencies when robots encounter problems.

My setup:

  • Home Assistant (latest stable)
  • Your HACS integration (community_yarbo, latest version / v0.1.0 MVP)
  • 5 × Yarbo Lawn Mower Pro robots across different locations
  • Custom automations triggering WhatsApp notifications

Issue 1: Several error codes are NOT transmitted to Home Assistant

Description

Over the past two days I have observed at least two error types that appear in the Yarbo app but are never reflected in Home Assistant sensors:

Error Code Description (from Yarbo app) binary_sensor._problem sensor._error_code
CM003 Right camera blocked stayed off / OK stayed 0
L001 Linear actuator problem stayed off / OK stayed 0

Evidence: I checked the HA History for both binary_sensor.25070102b2dgd357_problem and sensor.25070102b2dgd357_error_code during the exact time windows when the errors were active in the Yarbo app. Both sensors remained unchanged at off / 0 throughout.

Questions

  1. Are CM003 (camera blocked) and L001 (linear actuator) transmitted in the DeviceMSG MQTT payload at all? Or does Yarbo use a different MQTT topic for these error types?
  2. Is there a known list of error codes that ARE reliably transmitted vs. those that are NOT?
  3. Is there a way to subscribe to additional MQTT topics (e.g. plan_feedback or data_feedback) to catch these errors?

Issue 2: sensor.{sn}_activity only shows standby / working

Description

The sensor.{sn}_activity entity in my installation only has two possible states: standby and working.

I noticed in your v0.1.0 Roadmap that the activity sensor is part of the “Core entities”. However, the error state (which would be a great fallback trigger for errors that don’t update error_code) never appears, even when the robot has an active error in the Yarbo app.

Questions

  1. Is the error state not yet implemented in the current v0.1.0 MVP version, or is this a firmware issue?
  2. When the robot has an active error (e.g. L001), does the activity sensor transition to error in your test environment?

Issue 3: Using community_yarbo_error Event to read error codes

Description

I saw in your Roadmap that v0.1.0 includes the community_yarbo_error event, but does not yet include a dedicated error_code sensor entity.

Currently, when I trigger my automation on binary_sensor._problem, the undocumented sensor._error_code often reads as 0 instead of the actual error code (like RW001).

I am rewriting my automations to trigger on the community_yarbo_error event instead.

Question

  1. Does the community_yarbo_error event payload contain the actual error code (e.g. RW001)? If so, what is the exact JSON structure/key to extract it (e.g. trigger.event.data.error_code or trigger.event.data.code)?

Summary

My WhatsApp alert system works well for errors that correctly update error_code (tested with RW001 simulation). However, real-world errors like CM003 and L001 are completely invisible to Home Assistant, which defeats the purpose of the monitoring system for a commercial operation.

Any guidance on which error codes are reliably transmitted and how to best extract the error code from the community_yarbo_error event would be greatly appreciated. I am happy to provide MQTT packet captures or diagnostics if that helps.

Robot serial: 25070102B2DGD357 (Yarbo Lawn Mower Pro, firmware current as of July 2026)

Thank you for building and maintaining this integration — it is genuinely useful for professional Yarbo deployments.

Posted by a commercial Yarbo operator in Switzerland — 5 robots, multi-site deployment
GitHub Issue _ Briefing for markus-lassfolk_home-assistant-yarbo.pdf
Jörg Schüpbach yarbo.js@gmail.com Switzerland West +41 79 208 13 14

2

Hi there, thank you very much for sharing such detailed feedback and information about your Home Assistant integration setup.

I’ve shared your questions and findings with our team for further review. Since this involves multiple technical aspects, including MQTT data transmission, error code mapping, and event payload structure, we’ll need some time to investigate and gather accurate information.

I’ll keep you updated once I have more details from the team. Thank you again for your patience and for helping us improve the integration experience.

3

Be careful with this integration. This is third-party not the official integration. It hasn’t been maintained recently and has known issues.

This is official integration:

4

This is the yarbo one, but it’s not been updated once since it’s ‘release’. Seeing MIT license forced at the bottom of the page screams vibe coded, combined with one (initial) release makes me feel like Yarbo is going to abandon this one soon.

While yes it’s the official one, it doesn’t really work and they’re not releasing regular updates for it either it seems.

5

There’s been a couple of updates and it works fine for me

6

About a week ago, yarbo entities became unavailable again

Quick view at log shows authentication issue. 2nd time this has happened. I haven’t researched the issue yet

7

I had to delete the integration and add it back and then it worked. Not sure why, but seen others say that was the fix for them too.

8

Yup… did that the first time… didn’t want to have to do it again. I have over 450 devices tracked in HA… I dont mind dialing an integration in. But if it continues to be an issue, it’s not worth it for me to keep it.

9

Yeah they need a way to reset the authentication for the integration. Even changing a password would require a delete and reinstall. I didn’t lose anything by doing so, just a minor inconvenience.