As of 7/25/2020 continued development of iRobot Scheduler has ceased. If another developer would like to continue these efforts then please fork the GitHub and also follow the licensing constraints and ownership of the code and intellectual property within the license.
I've been building on this recently for my own purposes - integrated the cleanRooms capability for i7/s9 roombas, currently this uses a single "default" regions JSON specified in the App preferences/inputs. iRobot/Roomba at master · dkilgore90/iRobot · GitHub
I'm happy to provide some community support moving forward - not sure if the repo target change will cause issues with those using the 3rd-party Hubitat Package Manager (I don't use it myself)?
@aaron if you don't mind double-checking that I've properly followed your licensing constraints / appended to ownership
This is great news! I had been hoping this would come along soon. Glad test it out when it is ready. I have several robots that are multi-room capable and would love to free myself from the iRobot app scheduling dependencies and let it all be handled with the Hubitat.
For convenience, if the roomba in question only has 1 map saved, it will use that pmap_id and user_pmapv_id, without needing to specify them in the default rooms JSON -- otherwise these are mandatory to correlate to the proper map.
@pmusselman for now you have to change the preferences input if you want to change which rooms are to be cleaned -- but it should be a small leap to allow the command to be called with a JSON arg each time - which would allow different rooms to be cleaned via RM triggers, etc. The next step would be different sets of rooms per-schedule. On my to-do list, but not yet coded...
Seems a recent irobot update may have broken this convenience feature - it seems to overwrite the creation date of the map with the date it was last used - this was embedded in the user_pmapv_id. Simple workaround to include these IDs in the default regions JSON.
I'm new to the community, so this might be obvious to others. But when I see deprecated in the title, I'm more hesitant on using it. Is there a better approach to connecting Roomba to Hubitat, or is this all we have at the moment?
It works fine just isn't currently supported by the author anymore. Been using it for about a year. If it stops working sometime down the road then you can find an alternative. I myself would likely just fix whatever broke and keep using it. I usually post fixes or enhancements on the thread when issues come up.
I second @lewis.heidrick. The App/driver works great. Until you setup vlans and now it cannot talk to my rest server Once I get all the firewalls rules done, I'm sure it'll keep "rolling on". And I have no clue how to fix it if it breaks, so I'll be right back here hounding lewis with ya! lol
So far, my focus has been on integrating the "rooms" capabilities of roomba i7/s9 models -- but LMK if you run into other issues, I'll do my best to address them.
I don't think I've done anything differently from a previous version, but it seems adding and configuring the app does not add the Roomba device automatically. It doesn't seem like I am able to add this as a virtual device either after the fact.