Now how would we go about and figure out how to control the LED ring? GPIO3 seems to react to a monochromatic light, but only fully on or off, and only at a certain percentage
Im remove PCB from case without damage…
It for sure use ESP32-U4WDH and BL0937.
There is 4 LED’s. Im not sure if they are RGB or each have own color… Maybe they are driven by PWM …
Looks like U0TXD and U0RXD from chip is not exposed to any pins so reflashing my device looks like will not be possible…
I’ve noticed that addressing the RGB leds too soon in the boot cycles causes the device to reboot or become unresponsive. It might be the same as your issue @mebrotus. Fortunately, flashing the device was still possible in those cases. I’ve added a safeguard around this and created a PR in the esphome devices repo. I’ve got two devices running this config as stable as can be. Config for Shelly Plus Plug S by bobkersten · Pull Request #370 · esphome-devices/esphome-devices · GitHub
hi all,
I would like to make my shelly plus plug s work additionally as a ble gateway (for esphome(dot)io/cookbook/ble_itag.html).
my first try failed while flashing with esp32_ble_tracker and ble_client modules - firmware was too big for one of two partitions left from shelly (2x almost 2MB), but was ok to flash something smaller.
then I found a way to re-partition flash to make one big app partition Safeboot Partition Layout - Tasmota and used esphome temporary “proof of concept” firmware with one Itag and … it became permanent. it worked, itag works, relay works, but thats it, I cant flash it any more wirelessly. it says “conneciton reset by peer”. even with the minimum firmware (ota and wifi module).
or serial is my only way? shelly support didn’t provide me pinout (obviously) and I couldn’t find it as well by myself. from 18 pins would not be so easy to find rx tx etc
thank you
Because if I need to do some “advanced” functions Im more familiar with esphome coding(yaml) than Shelly scripts… Also If with Shelly FW I want in plug get some data from other HA sensor I need to use MQTT or some API calls to HA which is more complex than simple calling sensor from esphome code…
For simple on/off switching and reading power usage I think normal fw is ok… Also this is my view and maybe all thing can also be done with Shelly scripts…
@DejanBukovec yes i used sewing needles and they are only pushed on the contacts. It was a quick and dirty construction. I am currently creating a pcb for easy flashing. But this need some time.
I opened a pull request to change the platform to esp-idf.
since we do have the “ESP32 RMT LED Strip” platform with esphome 2023.5, it is possible to address the LEDs when using the esp-idf framework.
With this it is possible to use the plug as a bluetooth proxy too, because of the much smaller footprint.
If you want to get inspiration until the pr is merged, you can take a look at my proposed changes:
Hi,
many thankes for the PinOut Points.
My Shells Plus Plug S ist defekt after 10 Days. There is nothing of reaktion at the device.
No reset ist possible, also is no power betwen GND and 3,3Volt.
Is there any to find out, ore some poit to check?
Hmm… this solution did not work for me.
First I tried to migrate via the software way. Migrated from Shelly Software to tasmota is easy. But I was not able to migrate from tasmota to ESPHome. Tried it the hole day along.
So I decided to open this thing and but the needles on it. I flashed with esptools on a raspberry. (tig's Blog)
The software said that the bin file is copied correct. But the plug is dead. I tried a second one. Also dead.
**daniel@raspberrypi**:**~ $** esptool.py --port /dev/ttyS0 write_flash 0x0000 ~/shelly-plus-plug-s-3.bin
esptool.py v4.6.2
Serial port /dev/ttyS0
Connecting...
Failed to get PID of a device on /dev/ttyS0, using standard reset sequence.
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting...
Failed to get PID of a device on /dev/ttyS0, using standard reset sequence.
Detecting chip type... ESP32
Chip is ESP32-U4WDH (revision v3.1)
Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: b0:b2:1c:0f:9a:80
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Flash will be erased from 0x00000000 to 0x000d9fff...
Compressed 892336 bytes to 589471...
Wrote 892336 bytes (589471 compressed) at 0x00000000 in 53.5 seconds (effective 133.5 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
**daniel@raspberrypi**:**~ $**
No reaction if I put 3,3 Volt and Ground directly on the pins. No reaction if I put in the wall outlet.
Oh no, I killed my two plugs.
Any ideas? Maybe it is better to buy the ATHOM plugs with pre flashed ESPHome?