Skip to content
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

new H3S token #23

Closed
Anbercube opened this issue Aug 2, 2023 · 8 comments
Closed

new H3S token #23

Anbercube opened this issue Aug 2, 2023 · 8 comments

Comments

@Anbercube
Copy link

Managed to grab my H3S's BLE token with Bluetooth Smart Scanner App .
token : 35548a967abddcffffff3043524b544d
raw data (only show up when pressing power button of the remote):

{
    kCBAdvDataAppearance = 961;
    kCBAdvDataIsConnectable = 1;
    kCBAdvDataManufacturerData = <46003554 8a967abd dcffffff 3043524b 544d>;
    kCBAdvDataRxPrimaryPHY = 129;
    kCBAdvDataRxSecondaryPHY = 0;
    kCBAdvDataServiceUUIDs =     (
        "Human Interface Device"
    );
    kCBAdvDataTimestamp = "712591390.796815";
}
@helgek
Copy link

helgek commented Aug 18, 2023

@manymuch this one is different from the one which was reported by mayongze before.

@helgek
Copy link

helgek commented Sep 8, 2023

@Anbercube I have added your information to the Stack Overflow post

@manymuch
Copy link
Owner

manymuch commented Sep 9, 2023

I am thinking if the token is actually "device specific" or "model specific"? From designing view, it seems "device specific" is more reasonable. It prevent one remote turning on the all same projectors in the same room. If so, sharing token by model seems useless. Are there anyone success with provided token rather then sniffering?

@helgek
Copy link

helgek commented Sep 11, 2023

@manymuch absolutely. I had also been wondering if they would really store the same manufacturer code in all respective remotes. I had once ordered a second Elfin remote but I can't recall if I sniffed the signal before pairing it with the projector. This would be one way to find out I guess. But otherwise I guess we will have more clarity about this anytime soon when more people have tried the advertising implementation.

@jack-webb
Copy link
Contributor

@manymuch I found some data points that could indicate the codes are device-specific, and not model-specific. I'm not sure this is totally conclusive though, at least without more testing. Wydt?

Reports of 2 different tokens for Horizon Ultra:
#5 (comment)
#30 (comment)

Reports of 2 different tokens for Horizon 1080p:
#24 (mine)
#5 (comment)

I'll test this other token on my Horizon 1080p and report back. It might be a little while before I can do that.

Also looks like we have two different codes for Elfin on the SO answer:
https://stackoverflow.com/questions/69921353/how-can-i-clone-a-non-paired-ble-signal-from-a-remote-to-trigger-a-device/75563140#75563140

@jack-webb
Copy link
Contributor

Created #31 to put this discussion in one place :)

@helgek
Copy link

helgek commented Nov 9, 2023

@jack-webb Thank you :)

@manymuch
Copy link
Owner

Thanks for the sharing. The token is now considered device specific. See issue #31. Closing all token sharing issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants