Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Treatlife SL10 - PSK ID 02
See original GitHub issueFirst off, this is a great project. Thank you so much for all the hard work!
When testing the exploit with my Treatlife SL10 bulbs, I ran into the following error, after which the exploit could not continue; it just tried the connection again:
Using PSK v1 - Received PSK ID version 02
Here’s a full log file of the exploit attempt. The error first occurs on line 138.
I believe my bulbs might be a slightly different model from the device profile that already exists (SL10-OMNI-TP120). The branding on this bulb says “TreatLife SL-10 G1 TP120-9/A19,” and it uses a WB8P chip (BK7231S_1.0.5).
Here’s a firmware dump I took after the failed attempt. Will it work for creating a new profile?
Issue Analytics
- State:
- Created a year ago
- Comments:17 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, using the Smart Life app. Most recently, I had them running with LocalTuya by signing up for a Tuya developer account and getting the local_key and device_id from there.
When running the exploit, I specified my own randomly-generated values for local key and device id.
Just to be sure, you’re using the new SL10-v2 profile rather than the previous one, right?
I’ve tested on two bulbs, and they both get to the line
Device should be successfully onboarded on WiFi AP!I can see them attach to wifi from my router logs, but so far I haven’t gotten them to connect to Home Assistant using the LocalTuya integration.