u/Glittering_Beyond397

I created around 10 sub-agents and one main agent that is supposed to manage them and delegate tasks. The weird thing is that the main agent really prefers to work alone instead of using the sub-agents.

I already added pretty strict rules and instructions telling it to delegate work, but it often forgets and still tries to solve everything by itself. Only if I push it really hard does it actually start using the sub-agents properly. Otherwise it just ignores them and completes the whole task alone.

I’m using the newest version (2026.5.7) and everything else seems stable and working fine.

Does anyone know why it behaves like this? Is this normal agent behavior, token/context optimization, or maybe something with the planner logic?

Hi everyone,

After version 2026.4.23, I had a lot of problems with the newer updates. There were many bugs, gateway issues, and everything became very slow. Because of that, I rolled back to 2026.4.23, and it worked very well again.

I waited until 2026.5.5, and that version also worked very well for me, almost the same as 2026.4.23.

Now I see that 2026.5.6 has been released, but this time I want to be more careful before updating. Has anyone already tried this version?

How is it working for you? Any gateway problems, slow responses, bugs, or improvements?

I would really appreciate it if you could share your experience before I update.

I have a Dreame X50 Ultra/Complete, and I think the carpet detection logic is badly designed.

I’m not asking for the robot to rebuild the whole map live every run. The saved map can stay. But when the robot is actually driving over an area, its sensors should be allowed to override the saved carpet layer.

Example:

• During first mapping, the robot detects a rug and saves it as carpet.
• Later I remove that rug.
• The robot still treats that area as carpet and avoids mopping it.
• If I place a new rug somewhere else, the robot often does not detect it after the map is already saved.

This makes no sense to me. The X50 has LiDAR, camera/AI, carpet sensor and other sensors. So why is the saved carpet map treated as more reliable than the live sensor data?

What I think the logic should be:

• Map says “carpet here” = only a suggestion.
• Live sensor says “no carpet here right now” = mop the area.
• Live sensor says “carpet here right now” = lift/remove mop and vacuum.
• If the same mismatch happens several times, then ask the user: “Carpet may have been moved or removed. Update map?”

This does not require a full live remap. It only requires better runtime decision logic.

My questions:

1. Has anyone found a real fix for this, not just manual carpet zones or remapping?
2. Has anyone tested whether Home Assistant, Valetudo, or any local API can access the live carpet sensor state?
3. Is the X50 rootable or supported by any custom/local firmware project?
4. Do other brands like Roborock or Ecovacs handle this better by using live carpet detection during cleaning?
5. Has any developer tried to patch or modify Dreame’s carpet/map behavior?

To me this looks like a software/firmware limitation, not a hardware limitation. The hardware is already there, but the robot seems to trust the old saved carpet layer too much.

I have a Dreame X50 Ultra/Complete, and I think the carpet detection logic is badly designed.

I’m not asking for the robot to rebuild the whole map live every run. The saved map can stay. But when the robot is actually driving over an area, its sensors should be allowed to override the saved carpet layer.

Example:

• During first mapping, the robot detects a rug and saves it as carpet.
• Later I remove that rug.
• The robot still treats that area as carpet and avoids mopping it.
• If I place a new rug somewhere else, the robot often does not detect it after the map is already saved.

This makes no sense to me. The X50 has LiDAR, camera/AI, carpet sensor and other sensors. So why is the saved carpet map treated as more reliable than the live sensor data?

What I think the logic should be:

• Map says “carpet here” = only a suggestion.
• Live sensor says “no carpet here right now” = mop the area.
• Live sensor says “carpet here right now” = lift/remove mop and vacuum.
• If the same mismatch happens several times, then ask the user: “Carpet may have been moved or removed. Update map?”

This does not require a full live remap. It only requires better runtime decision logic.

My questions:

1. Has anyone found a real fix for this, not just manual carpet zones or remapping?
2. Has anyone tested whether Home Assistant, Valetudo, or any local API can access the live carpet sensor state?
3. Is the X50 rootable or supported by any custom/local firmware project?
4. Do other brands like Roborock or Ecovacs handle this better by using live carpet detection during cleaning?
5. Has any developer tried to patch or modify Dreame’s carpet/map behavior?

To me this looks like a software/firmware limitation, not a hardware limitation. The hardware is already there, but the robot seems to trust the old saved carpet layer too much.

I have a Dreame X50 Ultra/Complete, and I think the carpet detection logic is badly designed.

I’m not asking for the robot to rebuild the whole map live every run. The saved map can stay. But when the robot is actually driving over an area, its sensors should be allowed to override the saved carpet layer.

Example:

• During first mapping, the robot detects a rug and saves it as carpet.
• Later I remove that rug.
• The robot still treats that area as carpet and avoids mopping it.
• If I place a new rug somewhere else, the robot often does not detect it after the map is already saved.

This makes no sense to me. The X50 has LiDAR, camera/AI, carpet sensor and other sensors. So why is the saved carpet map treated as more reliable than the live sensor data?

What I think the logic should be:

• Map says “carpet here” = only a suggestion.
• Live sensor says “no carpet here right now” = mop the area.
• Live sensor says “carpet here right now” = lift/remove mop and vacuum.
• If the same mismatch happens several times, then ask the user: “Carpet may have been moved or removed. Update map?”

This does not require a full live remap. It only requires better runtime decision logic.

My questions:

1. Has anyone found a real fix for this, not just manual carpet zones or remapping?
2. Has anyone tested whether Home Assistant, Valetudo, or any local API can access the live carpet sensor state?
3. Is the X50 rootable or supported by any custom/local firmware project?
4. Do other brands like Roborock or Ecovacs handle this better by using live carpet detection during cleaning?
5. Has any developer tried to patch or modify Dreame’s carpet/map behavior?

To me this looks like a software/firmware limitation, not a hardware limitation. The hardware is already there, but the robot seems to trust the old saved carpet layer too much.