fcsraka.blogg.se

1. Bliss lights update#
2. Bliss lights android#

Here is a list of commands that I sent (alternating between Nebula only and Stars only): Value: c7c5207b64ca9fe414e210c249a8da606a863ef5 Looking through more logs, it’s clear that the app sometimes sends the 01 write request through 1911 prior to sending a command through 1912, but also seems to have the capability to send multiple commands through 1912 after one another. Phone sends command c7c5207b64ca9fe414e210c249a8da606a863ef5 to change lights to stars only through 1912.Phone sends 01 request to projector through 1911.Projector sends back 0da3fe0961edf42718cc2967034afe3748 (again, no pattern I can see between different times).Phone sends a read request through 1914.Projector sends reply (WireShark doesn’t say what it is).

Phone sends write request 0cc4c38bb5649aae797759a5daece26f02 (this changes every time, and there’s zero pattern for each command) through 1914, to pair the device I’m assuming.

Bliss lights android#

I sniffed some bluetooth packets using my Android phone while sending some commands through the app, and the order of notable events essentially was:

Bliss lights update#