It wouldnāt be the same code. Itād require someone to code support for the feeder.
There are two apis right now, the litter robot api and the autopets api. Autopets is completely different and seems to be firebase based. The litter robots api seems easier, though it is going away some time in 2021. Iāll have to think of a path forward. Litter robots api seems like a 5-10 hour fix. Autopets seems like 40+ and
Iād have to get my workbench setup to sniff all the firebase stuff. Thatāll take some time. Either way, they changed it significantly enough that there is a bunch of work
First thanks for maintaining the litter robot manager integration. It seems this is a common problem with all of these companies in terms of nerfing their own products, not understanding that automation isn't about a bunch of standalone devices, but integration. I don't understand their motivation in this case though as they don't make money on maintenance. It seems this company should benefit from playing friendly with developers. Would it be helpful if us owners started opening tickets and putting pressure on their support to open up their API? The only benefit I have obtained from the wifi connect is the integration with my hub... otherwise it's just a really expensive and virtually unneeded app.
I suppose it wouldnāt hurt. But I donāt know that it helps either. I have spoken to the Autopets COO, Jacob Zuppke, and he at least recognizes the value of an api. He had told me it was originally in their 2020 plans but, as with many businesses, plans changed in 2020 due to COVID-19. So maybe at some point they will but who knows when. The reality is most of these companies arenāt thinking of home automation, theyāre just checking the box of āwe have an appā
Actually I saw the cause of that error and fixed it but that occurred because you got an access denied. Are you sure the email and password is correct? If so Iām wondering if the secret is user specific (usually they are not)
Yes, I am sure my email and password were correct. I will try the whole process again to be sure (I just now restored a backup). Will go through process again:
Delete old app, delete old driver, uninstall with HPM, import new app, import new driver, install app.
Looks like it works! Everything looks good. Restoring rules now to fully test. I believe you can put it into HPM (I used the app from your link above, with the older driver code) so manual install not necessary.
Thanks so much!
Edit: Restored all rules, everything works great!
For those of you struggling with the order in which things have to be updated/restored (I certainly did), this might save you some time:
backup your database. If things go badly, you need this to come back to.
export any RM rules that use the Litter Robot device, because they are going to break. As a warning, if you do this on an iOS (iPad, iPhone) device, iOS will append a .txt suffix to the file, which means that RM will not import it back (wants to see .json). Doesn't matter whether you export a bunch of rules or just one rule, same issue. You will have to go to a computer and delete the .txt suffix in order to import (below).
delete the RM rules that you exported, which used Litter Robot device. If you want, you can check the "In use by" section on the LR device to see that all are gone. All that should be left "In use by" are dashboards, the tiles will break but can be fixed easily (below).
Remove the Litter Robot Manager app.
Remove the Litter Robot device. You will see a complaint that the dashboards are using the device, ignore that.
If you had installed the Litter Robot integration via Hubitat Package Manager, uninstall the Litter Robot integration. This will delete the Apps Code for Litter Robot Manager and the Driver Code for Litter Robot. The driver code for Litter Robot does not change, but, sigh, it gets deleted.
install user app Litter Robot Manager, enter credentials. Your login should be successful. Do the configuration for the app.
import (not restore) the RM rules that you exported above in step 2. An import is needed because this is a different Litter Robot device, and you need to get the chance to choose the newly-installed device.
Go to any Dashboard child apps that showed Litter Robot attributes, check the checkbox for the new Litter Robot device so that it can be used on those dashboards. Go to each dashboard, fix those broken tiles. For some odd reason, after selecting the Litter Robot device, the attribute selection list for Litter Robot device doesn't appear, only HSM attributes. Choose Last Updated, close the tile editor, open the tile editor, and you will now be able to choose from the Litter Robot attributes.
