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. I have three concerns at this point.
CHSesame2
andCHSesameBot
were exactly the same. It would be better to move their common parts toSesameLocker
. The reason I hesitate to do so at this point is that I cannot imagine how the upcoming release of SesameOS2 updated Sesame1 will be implemented.18
is supposed to mean. This will be recorded when the CLICK command is delivered. However, the same number is returned whether the event is triggered via Bluetooth (bleClick
) or via WiFi module (wm2Click
). The history handling related to SESAME bot is implemented in the SDK for iOS but not for Android and unfortunately I am implementingpysesame3
based on the SDK for Android.