Support SESAME bot #15
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to @Chabiichi-san, I was able to get one SESAME bot. His offer is very much appreciated.
This PR is the initial try to support SESAME bot. This should work anyway but I am still checking the stability.
I have two concerns at this point.
CHSesameBotMechSettings
, the Android SDK implementation does not useCHSesameBotLockSecondsConfiguration
.Although the main reference for me is reverse engineering of the Android SDK, I have implemented some iOS-only classes (e.g.,
CHSesameBotLockSecondsConfiguration
) to organize the data easily for users.CHSesameBotUserPreDir
,CHSesameBotLockSecondsConfiguration
).Unfortunately, in reality, those parameters do not seem to be reflected in the actual operation. For instance, in the factory default settings,
lockSeconds
andunlockSeconds
are set to 10 seconds each, but the arm is actually running for less than 10 seconds. For now, I leave it anyway and wait for the firmware updates!solves #13