-
Notifications
You must be signed in to change notification settings - Fork 42
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
Tradfri doesn't respond to encrypted messages #13
Comments
can you attach the dump? afair the stuff was pretty picky about keeping the connection open... |
Interesting - there does seem to be a response, but we're never doing anything with it. I'll dig further. |
Oh right the response is just the ack, ignore me. I've also tried adding a Host: header to the request, since that seemed to be the only difference to what an iOS device seems to be sending at this point. |
The get_accessories dump seems odd. This should contain 0x06 for kTLVType_State somewhere? |
It looks like there's an 0x06 TLV at the end of each POST to pair-verify, and one at the end of each response? |
Ah - SecureHttp isn't changing \n to \r\n |
Yes, adding |
so you get progress on the tradfri, any success in switching it on and off? |
I'm using Hue bulbs, and it turns out that the Tradfri will only expose Ikea bulbs over Homekit :( I suspect it'd work fine now, I'm able to read the accessory-info characteristics. |
After monkey patching http.client to avoid #12 I can successfully pair my Tradfri, but any packet sent after switching to SecureHttp never receives a response.
The text was updated successfully, but these errors were encountered: