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

[yarbojs-crypto]

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

4. Is the error state not yet implemented in the current v0.1.0 MVP version, or is this a firmware issue?
5. 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

6. 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

[yarbojs-crypto]

Jörg Schüpbach Yarbo Support Switzerland West : yarbo.js@gmail.com +41 79 208 13 14

[queensranch]

Update / Live Test Finding — L001 not transmitted via MQTT

Hi Markus,

We just had a perfect live test opportunity and found a reproducible finding regarding L001.

What happened:

1.	Robot “QueensRanch New” had an active L001 (Linear actuator problem) error visible in the Yarbo App
2.	We actively subscribed to `community_yarbo_error` in HA Developer Tools → Events
3.	We acknowledged and cleared the error in the Yarbo App

Result: No community_yarbo_error event was fired in Home Assistant — neither while the error was active, nor when it was cleared. This confirms our earlier finding about CM003 as well.

Question: Is L001 (and CM003) simply not included in the MQTT DeviceMSG payload by Yarbo firmware? Or is there a different MQTT topic we should be listening to for these error types?

This would be very helpful to know — either as a known limitation or as something to investigate on the firmware side.

Thanks for the great work on this integration! 🙏

Jörg Schüpbach Yarbo Support Switzerland West : yarbo.js@gmail.com +41 79 208 13 14