This project helps to replace the default firmware on the SwitchBot Smart Plug Mini via an OTA update, enabling the use of Tasmota open-source firmware without disassembling the device.
There are two SKUs of the SwitchBot Smart Plug Mini released in the US:
- The original "Smart Plug Mini" with model number W1901400, released in early 2022. As of 2023-12, Amazon sells these in four-packs for about $30, two-packs for $19, or one-packs for $12
- The updated "HomeKit Smart Plug Mini" with model number W1901401, released later in 2022. As of 2023-12, Amazon sells these in four-packs for about $38 or one-packs for $15
Some details about the devices are as follows:
- Both devices use identical circuitry. The only difference is the firmware used. More detail can be found in #19
- They use Type B NEMA 5-15 plugs and sockets
- They are ultrasonically welded shut, requiring destruction of the plastic housing to access the circuits within. There are no screws to allow access to the internals, the way there is with the Sonoff S31
- They use the Shanghai Belling BL0937 energy measurement IC to track power usage
- They use the Espressif ESP32-C3 chip for WiFi, Bluetooth Low Energy (BLE), and circuit control. See here to learn about the different types of ESP32. The MAC addresses for WiFi and BLE follow the ESP32 standard of having an of
8000
fset of two. If the WIFI-MAC is
34:85:18:0F:CC:DC, then the BLE-MAC is34:85:18:0F:CC:DE(DC in hex is 220, DE is 222) - The SwitchbOTA flashing process is confirmed to work on both device models using firmware v1.4 or older (v1.3, v1.2)
Writing to the bootloader over OTA is dangerous and not normally done for good reason. If your device loses power or somehow flashes corrupted data, the device will be bricked and require disassembly to reprogram the device. Only perform this process if you are comfortable disassembling your plug to fix it if it breaks! Of course, do not unplug or otherwise disturb the plug while it is performing the OTA.
This is a proof of concept and provided with no warranty.
- TL;DR: Connect the plug to your WiFi network
- Install the SwitchBot app on your phone https://play.google.com/store/apps/details?id=com.theswitchbot.switchbot
- Sign in or create an account (necessary to allow devices to be added/configured)
- Plug the plug into a wall outlet
- In-app, add a device. It's safe to connect it to your WiFi network.
- Note down the BLE-MAC during this process, as it will be referenced later
- This step uses Bluetooth Low Energy (BLE) to scan for devices and send the WiFi network information
- In-app, check the device firmware by going to its settings. As of 2023-12, there was no firmware update button, and the firmware version was v1.4. If you do see the upgrade button, do not press it and wait for a later part
- DONE! The plug is now ready for the firmware flashing process
- TL;DR: Configure your router & DNS to redirect calls to a local IP. Run a local NodeJS server at that IP
- Note down the LAN/local IP address where the NodeJS server will be run. For this example, it will be
192.168.0.69 - Configure your router and/or DNS to redirect calls to SwitchBot servers to instead hit your NodeJS server
- This means that a DNS override or custom DNS record should be added, redirecting both
www.wohand.comandwohand.comto the IP where the NodeJS server will be run. More detail can be found at #3 (comment) - In pfSense, this can be done in the Services->DNS Resolver or Forwarder by adding a Host Override with Host
wwwand Domainwohand.comand a second override with Hostwohandand Domaincom, both having an IP of 192.168.0.69. Save the override and Apply the settings
- This means that a DNS override or custom DNS record should be added, redirecting both
- In PiHole, this can be done in the Local DNS->DNS Records by setting the Domain to
www.wohand.comandwohand.comand the IP to 192.168.0.69 - If your router does not support custom DNS entries, it will almost certainly support setting a custom DNS server. This may be found in the DHCP settings or the System settings. Set the custom DNS server to 192.168.0.69
- Run a local NodeJS server to act in place of the real firmware update server and instead deliver modified firmware files: firstly the OTA file, and then the Tasmota firmware file
- Install NodeJS on your computer https://nodejs.org/en/learn/getting-started/how-to-install-nodejs
- Using a CLI or Terminal,
cdinto theserver/directory and runnpm i(short fornpm install) to install the dependencies required for this project - Once the previous command completes, run
node index.jsto run the server.- OR, if you could not set up a DNS record in the previous step, run
node index.js 192.168.0.69. This will start the server, in addition to a Man-in-the-middle DNS server that redirects*wohand.comcalls to the IP of the NodeJS server, rather than the public IP of*wohand.com. All other DNS lookups will be unaffected
- OR, if you could not set up a DNS record in the previous step, run
- The CLI or Terminal should show
Server listening on port 80. Keep this window open for the duration of the flashing process
- Test the DNS functionality by opening a new CLI or Terminal and running
ping wohand.comandping www.wohand.comto confirm that the local IP shows up. In this example, look for 192.168.0.69 - Test the Node server functionality by opening the SwitchBot app and then looking at the terminal where Node is running. A new line should have shown up similar to
::ffff:192.168.0.101 - /version/wocaotech/release.json. This indicates the server was accessed instead of the realwohand.comand that it successfully served a JSON file to the app. The IP 192.168.0.101 is the IP of the phone running the app. - DONE! The network is now configured and the server should now be ready to serve firmware files to the plug
- TL;DR: Send BLE commands to the SwitchBot plug to trigger the firmware upgrade process
- If you saw an upgrade button in the SwitchBot app, it is now safe to hit that button. No additional actions should be needed, and the firmware replacement process should complete. If no button is present in the SwitchBot app, proceed
- Install an app such as nRF Connect for Mobile. This will be used to connect to the Bluetooth Low Energy (BLE) radio of the plug to trigger the firmware update process. Bluetility for Mac is also reported to work
- Follow the instructions below, or watch the video, or read the GitHub issues outlining the process #43 #3 (comment)
- Using the BLE app of choice, scan for devices and Connect to the device matching the BLE-MAC noted from the SwitchBot app
- Make sure the app is on the Client tab, then expand "Unknown Service" and look at the options within. The last option, "Unknown Characteristic" should have Properties such as "WRITE" and an upload button on the right side. Hit the Upload button on the right side to bring up the Write screen.
- Select the BYTE_ARRAY type from the dropdown and enter in the hex code
57 0F 0A 01 0C(without spaces). Then it Send to transmit the command to the plug- The last two characters represent the firmware version to be flashed, and must be different from the current firmware version.
0C(as shown above) represents v1.2,0Drepresents v1.3,0Erepresents v1.4.0Cshould be safe to use by default. More detail can be found here
- The last two characters represent the firmware version to be flashed, and must be different from the current firmware version.
- Wait a few seconds and look at the NodeJS log to verify the command worked as it should. You should see something such as
::ffff:192.168.0.131 - /version/wocaotech/firmware/WoPlugUS/WoPlugUS_V12.binwhich indicates the NodeJS server was able to send the first.binfile to the plug - Wait about a minute after seeing the NodeJS server log to give the plug time to get ready for the next step.
- Now send a new BYTE_ARRAY command in the BLE app (nRF Connect) with hex
57 0F 0B. Hit Send to trigger the second and final firmware flash step - Wait a few seconds again and then look at the NodeJS log to verify the command worked as it should. You should see something such as
::ffff:192.168.0.131 - /payload.binwhich indicates the NodeJS server was able to send the Tasmota.binfile to the plug - DONE! The firmware flashing should be complete
-
TL;DR: Connect to the Tasmota WiFI. Configure the actual WiFi. Update the firmware. Apply the SwitchBot Tasmota Template. Configure the device
-
NOTE: The NodeJS server is configured to flash Tasmota
tasmota32c3.factory.binwhich is described to be a "Factory binary to be used for initial flashing using esptool." The distinguishing factor is that a factory binary includes an entire partition table, bootloader, etc. rather than just application partition that is later sent for OTA binaries in the future -
NOTE: The flashed Tasmota version is
v11.1.0 Ostaraand not a later version. This is becausev12.0.0 Paulchanged the partition layout to have a Safeboot partition, making the ESPHome firmware harder to flash onto the plug. This change is described in more detail here -
Connect to the Tasmota WiFi. It should be an unsecured WiFi network with SSID
tasmota-0c3d4f-1234showing a portion of the WiFi MAC address and a random number. Once connected, configure it to connect to the real WiFi network. It will likely reuse the IP address it had earlier during the flashing process, which in this example was 192.168.0.131 -
Reconnect your phone to the real WiFi network and navigate to the Tasmota webpage, in this case http://192.168.0.131. Click "Firmware Upgrade," confirm the OTA URL is http://ota.tasmota.com/tasmota32/release/tasmota32c3.bin or something similar, and click "Start Upgrade." Wait a few minutes as the plug updates its firmware and reconnects to WiFi
- NOTE: The firmware upgrade may only succeed once, due to the first Tasmota firmware being a factory version that is easily overwritten. Subsequent firmware upgrades may fail silently, meaning the device reboots but the firmware doesn't actually upgrade. Check the console for signs of an error such as
{"StatusSTK":{"Exception":7,"Reason":"Store access fault","EPC":"403832ae","EXCVADDR":"00000000","CallChain":["40387caa","4038be68","420adf92","4038d178","403801ee","421161a0","42115638","42096b3e","42096bd6","42013be6"]}}to validate if this is happening. This is due to the mismatch in partition layout - The partition layout can be fixed by using the Tasmota Application "Partition Wizard" which can be downloaded from here. Partition Manager is also available but is not needed for this process. Download the
Partition Wizard.tappfile to your computer - Go to the SwitchBot Tasmota interface, into "Consoles" and then "Manage File System." Select the
Partition Wizard.tappfile and click "Upload." If the page refreshes without showing the newly added file, reboot the Tasmota and try again and it should upload - Reboot the Tasmota once the file is uploaded to get Tasmota to recognize the app. Then go to "Consoles" and then "Partition Wizard" to see the following page. It shows that the current partition layout is
app0andapp1andfswhich is incompatible with larger firmwares, hence the need for an upgrade. There is thankfully a section to fix this with one button, "Start migration." Click it, confirm the multiple reboots warning, and wait a few minutes. Note that it will also update the firmware as part of this process - After a few minutes, click the Main Menu button to return to the Tasmota main menu. Confirm that the new partition layout has taken effect by going back to the "Partition Wizard" page, or just go to "Information." Both are pictured
- The SwitchBot is now prepared to accept future Tasmota firmware updates (though is also now incompatible with the ESPHome partition layout)
- NOTE: The firmware upgrade may only succeed once, due to the first Tasmota firmware being a factory version that is easily overwritten. Subsequent firmware upgrades may fail silently, meaning the device reboots but the firmware doesn't actually upgrade. Check the console for signs of an error such as
-
Once the Tasmota page is accessible again, go to "Configuration" and then "Configure Other." In the Template section, paste the following value and check the "Activate" button. Also feel free to change the Device Name, which shows up on the Tasmota home page. Finally, click "Save" and wait for the Tasmota to restart
{"NAME":"SwitchBot Smart Plug Mini W1901400","GPIO":[0,0,32,0,0,0,224,320,321,0,0,0,0,0,0,0,0,0,2720,2656,2624,0],"FLAG":0,"BASE":1}- The template can also be found on the Tasmota device repository https://templates.blakadder.com/switchbot_plugmini_W1901400.html
- The
GPIOnumbers refer to the different GPIO device IDs, found at https://tasmota.github.io/docs/Components/. TheBASErefers to a base template, which in this case is 1 orESP32C3
-
Perform the Power Calibration following the instructions in https://tasmota.github.io/docs/Power-Monitoring-Calibration/
- NOTE: Power Calibration is technically optional but not doing it can cause the power readings to be off by an order of magnitude. It is highly recommended to perform Power Calibration
- I used a Kill-a-watt and a portable space heater or hair dryer after confirming it was in a mode that had a Power Factor of 0.99 or 1.0
- I then used the Kill-a-watt to note the voltage, wattage, and amperage (in my case, 122.3V, 778W, 6.36A)
- I then used the Backlog command in the Tasmota Console to write all three values at once:
Backlog0 VoltageSet 122.3; PowerSet 778; CurrentSet 6360
-
A helpful pointer is to configure the time zone, and set up Daylight Savings https://tasmota.github.io/docs/Timezone-Table/
-
DONE! The SwitchBot Smart Plug Mini is now fully configured and ready to enter service
The included ESP-IDF code is a lightweight OTA client that directly writes to the embedded flash chip, enabling the install of non-app level code, including modfiying the bootloader and partiton table.
- The update is triggered by the app with a BLE message, such as
57 0F 0A 01 0C - The device fetches
http://www.wohand.com/version/wocaotech/firmware/WoPlugUS/WoPlugUS_VXX.binfor the firmware - The request is intercepted and served by the NodeJS web server, which downloads the Espressif binary
- The factory firmware installs the binary to ota_0 or ota_1, depending on past usage
- The binary runs from its OTA partition. If it's on ota_1, it skips to step 6. Otherwise, it performs another OTA, downloading itself into ota_1 and rebooting.
- Once on OTA_1, the device fetches
http://www.wohand.com/payload.binfor OTA - The request is intercepted and served by the NodeJS web server, delivering our desired payload (Tasmota firmware)
- The Espressif binary wipes the internal flash and flashes the payload. It performs two checksums, one of the downloaded binary and another of the flashed binary. It will continue to retry without restarting until the checksums are valid
The WiFi configuration is read from the device's NVS memory by the Espressif binary. This should be configured in the SwitchBot app prior to the process. If for whatever reason it is lost, the binary will make a fallback connection to SSID switchbota, password switchbota. You may need to create this SSID to recover the device.
To support my work, consider making a purchase from SwitchBot using my affiliate link. Alternatively, please see my sponsor page here.
- The digiblurDIY Youtube channel has a video guide for this process, and the website has additional details, including detail on the alternate firmware ESPHome
- This project is similar to https://github.com/khcnz/Espressif2Arduino
- GitHub Issues/Discussions
- Tasmota
- Documentation https://tasmota.github.io/docs/
- GitHub https://github.com/arendst/Tasmota
- Firmware (ESP32-specific) https://ota.tasmota.com/tasmota32/release/
- Template for SwitchBot https://templates.blakadder.com/switchbot_plugmini_W1901400.html
- SwitchBot App
- nRF Connect App