Closed SonomaGTS closed 4 years ago
So after a little more poking around I finally found this timeout which seems to resolve part of the issue however I am not sure what the negative impact is reducing that timeout will have for the litter robot api. The default state polling in HA is every 30 seconds so i reduced that 5 min Throttle down to 30 seconds and so far not ran into a snag. Seemed to have updated the status of the little robot relatively quick for initializing a clean cycle but took a little long to reset back to ready but I think that's the slowness of the api getting the update from the litter robot.
I have noticed initializing a cycle through this component changes the waste gauge count starting from 110% went down to 24% with one cycle back to 26% next cycle. Not sure what causes that.
I agree, I set mine to 30 seconds as well, and it seems better. Especially when using a dashboard app to display status.
Cool is 30 sec the norm for these polling sensors? I can adjust that.
For the cycle reset I'll have to see if mine does the same thing
well it's been over a month and not ran into any snags. it's still not perfect but it catches the state changes even if delayed sometimes. Downside of having to fetch the status of the LR remotely from the api after it's updated remotely to the LR. Too bad there is no local api to bypass the cloud entirely.
Does this component update every 30 seconds like the default for HA? Or is it something else? I noticed when I trigger the cycle command it's almost instant but the status and the waste status and even night light are severely delayed. Is there a way to increase the polling?