Litter Robot Integration Dropping Robot

Jinsin456 commented 2 years ago

The problem

For the past week or so my litter robot hasn't been registering any changes and seems to be disconnecting.

The litter robot app is working perfectly and if I reload the integration it works for anything from a few mins to an hour then seems to stop working

What version of Home Assistant Core has the issue?

Core

What was the last working version of Home Assistant Core?

core-2021.12.10

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Litter Robot

Link to integration documentation on our website

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

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: pylitterbot.account
Source: /usr/local/lib/python3.9/site-packages/pylitterbot/account.py:99
First occurred: 08:32:53 (90 occurrences)
Last logged: 20:56:13

Unable to retrieve your robots

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

litterrobot documentation litterrobot source _{^{(message by IssueLinks)}}

probot-home-assistant[bot] commented 2 years ago

Hey there @natekspencer, mind taking a look at this issue as it has been labeled with an integration (litterrobot) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

tctimmeh commented 2 years ago

I am also experiencing this. My logs say

ERROR (MainThread) [homeassistant.components.litterrobot.hub] Invalid credentials

but if I disable/enable the integration then it connects ok. I am running Home Assistant v2022.2.6 on HASSOS on a RPI 4.

cdv-tbh commented 2 years ago

I have had connection issues as well. Now though I am completely unable to connect. Message in the integrations page is:

Retrying setup: Cannot reopen a client instance, once it has been closed.

I'm willing to do anything I can do to help resolve this issue.

Version	core-2022.3.5
Installation Type	Home Assistant OS
Development	false
Supervisor	true
Docker	true
User	root
Virtual Environment	false
Python Version	3.9.9
Operating System Family	Linux
Operating System Version	5.10.103
CPU Architecture	x86_64

tpagden commented 2 years ago

Same situation -

"Retrying setup: Cannot reopen a client instance, once it has been closed."

I believe I have never installed via HACS, so I don't think it's that. Not much in the log from what I can see, but I would very much like to get this rolling.

cdv-tbh commented 2 years ago

i was able to get mine working in the latest release -2022.6.1 I had to remove the repo from hacs as well as uninstall tne addon. _

tpagden commented 2 years ago

i was able to get mine working in the latest release -2022.6.1 I had to remove the repo from hacs as well as uninstall tne addon. _

This was the key for me as well - in order to get rid of the error message above, I had to remove the repo from HACS (didn't know that was a thing), uninstall the add-on, then restart the server. Works for the first time, thank you @cdv-tbh

cdv-tbh commented 2 years ago

@tpagden

I had no idea that was a thing either... I spent way too many hours beating my head against the wall till I found that out. I'm glad it worked for you and hope this is helpful for others in the same boat!

ChrisBaker97 commented 2 years ago

By "uninstall the add-on," do you mean "delete and then re-add the Litter Robot integration," or is there something else that needs to be done? (I had previously removed the repo from HACS after official support was added in 2021.3, and everything's been working fine since using the official integration.)

Yesterday, after upgrading Home Assistant from 2022.5.5 to 2022.6.2, I began seeing disconnects from all of my litter robots, on precisely a 30-minute cycle. I've deleted the Litter Robot integration, rebooted Home Assistant (Docker in my case), and re-installed the integration (including renaming all of the entities again), but I'm still seeing these disconnects from the vacuum.* entities:

However, all of the other entities at least appear to remain active:

In the past, it was not unusual for my Home Assistant logs to show occasional errors like this, but it never resulted in extended periods where I couldn't access the vacuum.* entities:

2022-06-06 07:21:07 ERROR (MainThread) [pylitterbot.account] Unable to retrieve your robots
2022-06-06 08:52:51 ERROR (MainThread) [pylitterbot.account] Unable to retrieve your robots

Happy to assist the devs with any logs or other experiments. Just let me know what you need.

natekspencer commented 2 years ago

@ChrisBaker97 have you tried controlling your LRs from the app when they become unavailable in HA or have you tried pinging the IP of them? In my testing (and the reason for this change), when the LR drops its connection it sometimes takes a while for it to reconnect and report back status as well as being able to be manually controlled. So the unavailability of the vacuum entity plus the last seen date reported can be utilized to help inform that you may need to take action to get the LR back online.

ChrisBaker97 commented 2 years ago

@natekspencer There actually doesn't seem to be anything wrong with the litter robots' connection, just that the vacuum entity is reporting unavailable. They remain connected and controllable from the LR apps and also continue to report sensor data through Home Assistant.

natekspencer commented 2 years ago

@natekspencer There actually doesn't seem to be anything wrong with the litter robots' connection, just that the vacuum entity is reporting unavailable. They remain connected and controllable from the LR apps and also continue to report sensor data through Home Assistant.

Can you share your "last seen" sensor history as well from the same time period as above?

ChrisBaker97 commented 2 years ago

Since that seems to be a limited timeframe, here's the last 24 hours side by side:

The vacuum.* entities are on a 30-minute cycle between docked and unavailable, and last seen seems to be on a 1-hour cycle.

natekspencer commented 2 years ago

That is an interesting reporting cycle. How many robots do you have on your account? I only have one, and it appears to report back every minute when idle when connected.

ChrisBaker97 commented 2 years ago

I have three, and they all show the same pattern.

natekspencer commented 2 years ago

@ChrisBaker97 I've removed the logic that marks the vacuum entity as unavailable in https://github.com/home-assistant/core/pull/73234

ChrisBaker97 commented 2 years ago

@natekspencer thanks. Any idea why the big difference between yours and mine?

natekspencer commented 2 years ago

@natekspencer thanks. Any idea why the big difference between yours and mine?

It could be due to the number of robots you have associated with your account (3 vs 1) or, more likely, different firmware on the robots that limits reporting. Without an official API though, it's hard to say.

home-assistant / core