Thank you for the feedback! Could you confirm if this BLE bootloop issue is specific to this Shelly model? If it’s unique to this device, I’ll definitely add the warning. However, if it affects multiple ESP devices, I’d prefer to keep the guide focused on the core flashing process, while users can refer to ESPHome’s documentation or the forums for BLE-specific issues or configurations.
I flashed multiple Shelly Plus Plug S with @angelnu 's PR and mixed up my yaml files. In step 3. of this tutorial I uploaded a yaml with an ota password instead of unprotected_writes: True. When I try the upload-factory-ota I get the following error:
ERROR Transfering partition table is not supported by remote device - upgrade the firmware first!
If I try to upload a different yaml I get this error:
ERROR Error binary size: Error: device aborted flash that would have overriden running partition. Check your device log for more information.
The log on the esp shows:
11:08:01 [D] [ota:148]
Starting OTA Update from 192.168.0.20...
11:08:02 [W] [ota:383]
Remote closed connection
11:08:02 [W] [ota:239]
Auth: Reading cnonce failed!
11:08:02 [W] [ota:411]
Failed to write 1 bytes of data, errno: 104
11:09:43 [D] [ota:148]
Starting OTA Update from 192.168.0.20...
11:09:43 [I] [ota:464]
OTA type is 1 and size is 830704 bytes
11:09:43 [E] [ota:110]
Aborting to avoid overriding running partition
11:09:43 [E] [ota:111]
New partition - addr: 0x0e0000; size: 0x0cb000
11:09:43 [E] [ota:113]
Running partition - addr: 0x0e0000; size: 0x2a0000
11:09:43 [I] [ota:282]
PARTITION TABLE
11:09:43 [I] [ota:283]
===============
11:09:43 [I] [ota:287]
type: 0x01; subtype: 0x02; addr: 0x009000; size: 0x004000; label:
11:09:43 [I] [ota:287]
type: 0x01; subtype: 0x00; addr: 0x00d000; size: 0x002000; label: ota
11:09:43 [I] [ota:287]
type: 0x00; subtype: 0x00; addr: 0x010000; size: 0x0d0000; label: safe
11:09:43 [I] [ota:287]
type: 0x00; subtype: 0x10; addr: 0x0e0000; size: 0x2a0000; label:
11:09:43 [I] [ota:287]
type: 0x01; subtype: 0x82; addr: 0x380000; size: 0x080000; label:
11:09:43 [W] [component:214]
Component ota took a long time for an operation (0.08 s).
11:09:43 [W] [component:215]
Components should block for at most 20-30ms.
Is there any way to fix this or did I brick my device?
Hello dear all, I have Shelly Plug S v2. I have bricked it by flashing tasmota firmware. I could reach the tasmota setup screen, but after I’ve tried configuring WiFi it rebooted itself and never came back. In order to unbrick it I’ve tried several recovery options but nothing worked (Device Recovery - Tasmota).
Following current thread I was hoping to flash it directly.
Now, as previously mentioned by @bkbartk, there is no visible phillips (+) screw at the bottom as compared to the v1 of the device.
Moreover, picture shared on by @bkbartk points to yellow-copper looking metallic head, assuming that it is an internal screw (which is incorrect), it’s not a screw, but in fact top-end of the structural rod, don’t try to unscrew it, it will be unsuccessful.
In order to remove the transparent cap, I’ve used sharp and sturdy but relatively thin knife to insert it between the 2 plastic pieces (transparent cap that covers the pcb and non-transparent housing (black/white) depending on the color of the housing). Going all the way around the edge and gently tilting the knife up allowed me to insert the small flat-head (-) screwdriver into the holes next to the metal plates. Applying significant force, I was able to rip the transparent cap out and access the top layer of the pcb. Top pcb plate does NOT have any visible programmable connectors (VCC, GND, RX, TX GPIO 0) exposed.
I proceeded by disconnecting wifi antenna which was taped to the inner wall of the housing. I couldn’t figure out what to do next. Knowing that I will not use the device, I decided to apply force in order to get the pcb out, I couldn’t, so I resorted to cutting the piece of the housing, in order to check what’s up. With enough force and dedication I successfully broken the pcb in 2 halves. Hopefully my experience would be helpful to someone.
Lessons learned: Do NOT disassemble the V2 device, as it’s clearly not meant for that. Please let me know, if you need more info/photos.
