Closed kFYatek closed 1 year ago
Getting the password from the cloud is now the way to go, so I don't think this is justified.
@NickWaterton Doesn't getting the password from the cloud require creating an account with iRobot and registering the robot with it first? Isn't avoiding to do that one of the points of this project?
Doesn't getting the password from the cloud require creating an account with iRobot and registering the robot with it first? Isn't avoiding to do that one of the points of this project?
No, it was never the point of this project. The point of the project was to be able to integrate your Roombas with home automation.
But feel free to maintain your own fork, if it does what you want.
Doesn't getting the password from the cloud require creating an account with iRobot and registering the robot with it first? Isn't avoiding to do that one of the points of this project?
No, it was never the point of this project. The point of the project was to be able to integrate your Roombas with home automation.
But feel free to maintain your own fork, if it does what you want.
OK, got it. A little disappointing, but fair enough. Thanks for your good work on this integration anyway :)
NOTE: This includes changes from #107. You may want to look there first.
Addresses #74
This adds the
initwifi.py
standalone script that allows doing the initial provisioning without the need for the official iRobot Home app.To use it:
Roomba-XXXX
, with XXXX being the first four characters of the BLID)./initwifi.py
, possibly with arguments to your liking./roomba.py
to configure it as usualTested with my Roomba i3.
Acknowledgement: This heavily draws from @kumy's work from the https://github.com/kumy/Roomba-Wifi-Initial-Provisionning repo. They appear to have a R966 with V2 firmware which, judging from their script, requires plaintext WiFi password. I discovered my i3 with V3 firmware to require it hexlified.