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
Connection to device succeeded but no datapoints found ...
Treatlife SL10 - PSK ID 02 tuya-cloudcutter/tuya-cloudcutter#88 ... I'm attaching the debug log (device id obfuscated) from my attempt to ...
Read more >TREATLIFE Smart Light Bulbs 4 Pack, 2.4GHz Music Sync ...
TREATLIFE Smart Light Bulbs 4 Pack, 2.4GHz Music Sync Color Changing Light Bulb, Works with Alexa Google Home, A19 E26 Dimmable LED Light...
Read more >APP Help - Treatlife
Steps to connect the smart light bulb to the Treatlife APP with AP mode? 1. Tap the “+" on the upper right corner...
Read more >TreatLife - Apps on Google Play
Build exclusive intelligent lighting life, provide personalized interactive settings and convenient lighting supporting services.
Read more >TREATLIFE SL10 Wi-Fi Smart Light Bulb User Manual
Quick Start Guide Smart Wi-Fi Light Bulb https://www.tapo.com/app/download-app/ Getting Started Get the Tapo app from the Apple App… TREATLIFE ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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.