Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roomba no longer updating "cleaned_area" or "cleaning_time" attributes #50333

Closed
drinfernoo opened this issue May 9, 2021 · 5 comments
Closed

Comments

@drinfernoo
Copy link
Contributor

The problem

I have a Roomba 960, which has been working very well with the core integration for a few months now... But suddenly I'm no longer getting the cleaned_time or cleaned_area attributes updated.

I noticed it first a few days ago in 2021.4.6 (though I'm fairly certain it was working in that same version at some point), but have since updated to 2021.5.1, and am still seeing this behavior. I don't see any unusual behavior in logs, and my robot is connected successfully, because I can definitely control it from HA.

Has anyone else experienced this?

What is version of Home Assistant Core has the issue?

2021.5.1

What was the last working version of Home Assistant Core?

2021.4.6

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Roomba

Link to integration documentation on our website

https://www.home-assistant.io/integrations/roomba/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@quinten94b
Copy link

I've had the same issue for a couple of weeks. I think even from before 2021.4.x
I'm not seeing anything in my logs regarding the Roomba / Irobot integration

What is version of Home Assistant Core has the issue?
2021.5.1

What was the last working version of Home Assistant Core?
Definatly more than a month ago

What type of installation are you running?
Home Assistant OS

@drinfernoo
Copy link
Contributor Author

I think that this happened because of a software update on the Roomba... I am currently on version 2.4.16-216, updated 4/29/2021, and I think that may have been when it broke for me. It doesn't appear that those attributes are even reported in the vacuum's state anymore, but it would be great if this would get looked at.

@drinfernoo drinfernoo changed the title Roomba no longer updating "cleaned_area" or "cleaned_time" attributes Roomba no longer updating "cleaned_area" or "cleaning_time" attributes May 24, 2021
@drinfernoo
Copy link
Contributor Author

Actually, it does seem that way indeed. I've connected to the robot manually via rest980, and found that the mssnM and sqft values are no longer updated during cleaning. I'm not sure if that change did actually coincide with the 2.4.6-216 firmware update, but it seems it won't be possible to get those anymore.

There is a value (mssnStrtTm) that gets updated with the "mission start time", but there would actually need to be some effort there in order to figure out the time elapsed since start. Regarding cleaned area, I don't see anything useful in the response, but this is the full state response for my robot from one instant in his cleaning cycle:

{
  "netinfo": {
    "dhcp": true,
    "addr": 3232235968,
    "mask": 4294967040,
    "gw": 3232235777,
    "dns1": 3232235777,
    "dns2": 0,
    "bssid": "b8:ee:0e:d8:25:62",
    "sec": 4
  },
  "wifistat": {
    "wifi": 1,
    "uap": false,
    "cloud": 1
  },
  "wlcfg": {
    "sec": 7,
    "ssid": "4F6C6C6976616E64657273203247"
  },
  "mac": "d0:c5:d3:cd:4c:75",
  "country": "US",
  "cloudEnv": "prod",
  "svcEndpoints": {
    "svcDeplId": "v011"
  },
  "wifiAnt": 1,
  "mapUploadAllowed": true,
  "localtimeoffset": -420,
  "utctime": 1621813545,
  "pose": {
    "theta": 178,
    "point": {
      "x": 44,
      "y": -35
    }
  },
  "batPct": 100,
  "dock": {
    "known": true
  },
  "bin": {
    "present": true,
    "full": false
  },
  "cleanMissionStatus": {
    "cycle": "quick",
    "phase": "run",
    "expireM": 0,
    "rechrgM": 0,
    "error": 0,
    "notReady": 0,
    "mssnM": 0,
    "mssnStrtTm": 1621813755,
    "expireTm": 0,
    "rechrgTm": 0,
    "sqft": 0,
    "initiator": "localApp",
    "nMssn": 188
  },
  "language": 0,
  "noAutoPasses": false,
  "noPP": false,
  "ecoCharge": false,
  "vacHigh": false,
  "binPause": false,
  "carpetBoost": true,
  "openOnly": false,
  "twoPass": false,
  "schedHold": false,
  "lastCommand": {
    "command": "start",
    "time": 1621813750,
    "initiator": "localApp"
  },
  "langs": [
    {
      "en-US": 0
    },
    {
      "fr-FR": 1
    },
    {
      "es-ES": 2
    },
    {
      "de-DE": 3
    },
    {
      "it-IT": 4
    }
  ],
  "bbnav": {
    "aMtrack": 97,
    "nGoodLmrks": 9,
    "aGain": 8,
    "aExpo": 72
  },
  "bbpanic": {
    "panics": [
      9,
      6,
      14,
      8,
      6
    ]
  },
  "bbpause": {
    "pauses": [
      6,
      17,
      17,
      14,
      17,
      16,
      5,
      2,
      6,
      0
    ]
  },
  "bbmssn": {
    "nMssn": 187,
    "nMssnOk": 60,
    "nMssnC": 105,
    "nMssnF": 22,
    "aMssnM": 36,
    "aCycleM": 33
  },
  "bbrstinfo": {
    "nNavRst": 15,
    "nMobRst": 0,
    "causes": "0000"
  },
  "cap": {
    "pose": 1,
    "ota": 2,
    "multiPass": 2,
    "pp": 1,
    "binFullDetect": 1,
    "langOta": 1,
    "maps": 1,
    "edge": 1,
    "eco": 1,
    "svcConf": 1
  },
  "hardwareRev": 3,
  "sku": "R960020",
  "batteryType": "li26",
  "soundVer": "31",
  "uiSwVer": "4582",
  "navSwVer": "01.12.01#1",
  "wifiSwVer": "21045",
  "mobilityVer": "5938",
  "bootloaderVer": "4042",
  "umiVer": "6",
  "softwareVer": "v2.4.16-126",
  "tz": {
    "events": [
      {
        "dt": 1619870400,
        "off": -420
      },
      {
        "dt": 1636275601,
        "off": -480
      },
      {
        "dt": 1647165601,
        "off": -420
      }
    ],
    "ver": 10
  },
  "timezone": "America/Los_Angeles",
  "name": "Kreacher",
  "cleanSchedule": {
    "cycle": [
      "none",
      "none",
      "none",
      "none",
      "none",
      "none",
      "none"
    ],
    "h": [
      9,
      9,
      9,
      9,
      9,
      9,
      9
    ],
    "m": [
      0,
      0,
      0,
      0,
      0,
      0,
      0
    ]
  },
  "bbchg3": {
    "avgMin": 357,
    "hOnDock": 4308,
    "nAvail": 336,
    "estCap": 7126,
    "nLithChrg": 125,
    "nNimhChrg": 0,
    "nDocks": 120
  },
  "bbchg": {
    "nChgOk": 123,
    "nLithF": 0,
    "aborts": [
      0,
      0,
      0
    ]
  },
  "bbswitch": {
    "nBumper": 25359,
    "nClean": 473,
    "nSpot": 28,
    "nDock": 120,
    "nDrops": 1021
  },
  "bbrun": {
    "hr": 98,
    "min": 38,
    "sqft": 291,
    "nStuck": 86,
    "nScrubs": 222,
    "nPicks": 628,
    "nPanics": 315,
    "nCliffsF": 8514,
    "nCliffsR": 2636,
    "nMBStll": 8,
    "nWStll": 21,
    "nCBump": 0
  },
  "bbsys": {
    "hr": 4470,
    "min": 42
  },
  "signal": {
    "rssi": -32,
    "snr": 56
  }
}

@drinfernoo
Copy link
Contributor Author

drinfernoo commented Jun 7, 2021

#51163 has been merged, which works around the cleaning time by calculating it based off of mssnStrtTm, but I'm afraid it appears that there simply isn't anything useful in the response for calculating cleaner area any longer 😕

After debugging against the dorita980 package, to get the raw JSON response as mentioned above, the only fields that change during the cleaning cycle are related to the position and signal strength... I am still able to get cleaned area from the iRobot app, once a clean map has been generated, but the only thing I can think is that they're calculating this server-side, meaning that would be a cloud-only feature.

Unfortunately, dorita980 doesn't yet (maybe won't ever? There doesn't appear to have been much movement since 2017) support a cloud API for iRobot firmwares from 2.x and onward.

@github-actions
Copy link

github-actions bot commented Sep 5, 2021

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Sep 5, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Oct 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants