-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playbulb Garden #4
Comments
You can use |
I looked online to find examples on how to use the $ gatttool -b D2:57:4B:FF:FF:FF -I
[ ][D2:57:4B:FF:FF:FF][LE]> connect
Connecting... connect error: Connection refused (111)
[ ][D2:57:4B:FF:FF:FF][LE]> Then I tried to read directly via command: $ gatttool -b D2:57:4B:FF:FF:FF --char-read -a 0x0016
Connection refused (111) Any ideas on how to proceed? |
Hi, I used the bluetooth snooping capabilities of my android phone to sniff the playbulb garden protocol:
|
It seems that this https://github.com/Phhere/Playbulb/blob/master/protocols/color.md represents the protocol but the code is offset by 3: 0x0016 -> 0x0019 etc. |
It is possible that each product has their own protocol codes. |
Hi, Just for gathering other models : Blue Label (the cheap color only) and new Sphere are using the same like Garden |
For the record, I'm trying to use these new handles with the Sphere and it doesn't seem to be working. See my comment: #12 (comment) |
Hi,
I tried to test some command listed here with my Playbulb garden but it seems that they changed the command structure?
But the PlayBulb Garden stays white...
Is there any way to sniff the communication between the app and the device to see what data is actually send?
The text was updated successfully, but these errors were encountered: