I don’t have a SmartThings Hub. This will be a direct connected device which uses Wifi to connect to my home network and communicate with Smartthings cloud.
I am following this official documentation which shows the setup instructions for esp8266. I have setup the toolchain and everything correctly. But when I run the setup.py of the repository with esp8266 like its mentioned in the documentation, I’m getting an error.
Submodule path 'iot-core': checked out 'ab9fd27d5e3be3edfcb45b2b1547b1c63f5685b6'
HEAD is now at ab9fd27 feat : feat : Release SDK v2.1.1
Fail to find setup script
Usage: python setup.py [BSP_NAME]
--------------------------------------------------
ex) python setup.py bl602
ex) python setup.py esp32
I don’t see the esp8266 module under the apps folder also in the Reference repository
Is this board not supported? Then why is the documentation including the instructions for esp82666?
Am I doing something wrong?
There is not much resources available for this topic.
But I do know this board has the required capability as I am currently using multiple of these boards with Blynk cloud as a direct connected device.
UPDATE: It appears that the official SmartThings C SDK repository has been completely purged. All files and references to ESP8266 support have been removed, with only ESP32 content remaining. The repository’s history has also been wiped clean — no commits, no tags, no traces. It’s as if ESP8266 support never existed.
Here’s a snapshot from the Wayback Machine showing that this SDK did in fact once support ESP8266 devices.
This move feels like a complete slap in the face to developers who invested time and effort into building on this platform. The ESP8266 was and still is fully capable of supporting direct-connected devices, as demonstrated by projects like Blynk Edgent, which continue to support the ESP-01 and other ESP8266 variants reliably.
Erasing history like this is not just irresponsible, it’s deeply disrespectful to the developer community. Basically a big F*U to all the developers out there.
Not my area, but my reading of the repository ‘README’ is that with version 2 of the SDK they moved to only supporting BLE rather than SoftAP. The version 1 code is still available in other branches of the repository.
I’m curious about your motivation for making the devices compatible with SmartThings without owning a hub.
It seems that you will encounter numerous disadvantages with very few benefits.
The reason for this was that softAP has a lot of connection issues, and it wass hard to support new features from Samsung. As ESP8266 doesn’t support BLE, it was removed.
As mentioned in the above link, if you want to use softAP-base SmartThings SDK including ESP8266, you need to use this version:
