I succeeded flash tasmota-battery version also set static IP but when the PIR wake there is no message on MQTT.
Its looks that there is no enough time for the esp boot…
Anyone have any idea or experience with this module?
Yes, throw in the trash
And in other words, a horror product. Even though I managed to get him to broadcast his status to me on MQTT most of the time he missed the traffic. In short unreliable …
The images for flash / IO2 are misleasing.
The photo with QR code and labelling IO2 is wrong – the flash pin is the one above IO2!
With my PIR sensor I had to put flash on GND during startup (connecting to power).
There are two empty pins between flash (GPIO0) and GND.
There are two empty pins between RX (GPIO3) and flash (GPIO0).
Here’s what worked for me.
During power up hold GND to the flash pin
after power up the flash pin can be left unconnected
flash with tasmotizer.py
Note the flash pin where I hold the black cable connected to GND during power up.
So, I just got this thing flashed OTA using tuya-convert and tapping the reset button every few seconds to keep it awake. No soldering required. Woohoo!
In order to keep the ESP chip up and connected after flashing, for example while configuring Tasmota or just messing around, one could connect the VCC of the ESP to the V terminal of the empty header in bottom left corner.
When the PIR detects motion the ESP is powered on and it sends out MQTT with POWER ON event. It doesn’t matter if motion continues or not - after about a minute the ESP is powered off for the pre-selected time (there is a switch on the back 2 or 4 minutes). During this time the ESP won’t be powered on again.
If one keeps the ESP up and connected it won’t send out additional MQTT messages (after the first POWER ON event), i.e. it is not usable as continuous motion detector.
I’m using “Tuya MCU” module configuration. Is this the correct one?
i was able to flash the firmware over OTA using tuva-convert. I had used tasmota-battery.bin firmware and used template/comamnds here: https://templates.blakadder.com/DP-WP001.html
Lastly, i had disabled mqtt and just relying on connection status through a PING sensor in home assistant. This is giving me a very fast reaction to movement like 0 to 1 second reaction.
If you ask me how I was able to flash it over OTA, just try hard, first switch to pairing mode and keep pressing (not continuous press, do press and release) so device will stay awake. So far, I had flashed 2 devices.
binary_sensor:
- platform: ping
host: 192.168.178.61
count: 1
scan_interval: 1
name: Night Hall To Entrance Sensor Tasmota
- platform: ping
host: 192.168.178.59
count: 1
scan_interval: 1
name: Entrance To Night Hall Sensor Tasmota
I have an update regarding to successful OTA updates. I had noticed that tuya-flash is waitin for 10 seconds after pushing the intermediate firmware, which is causing issues for battery operated devices and we are failing most of the time because of this timeout. I had changed it to 3 seconds locally and had 2 more OTA flashed motion sensors.
I am not using the tasmota motion sensors anymore, moved to zigbee. I was having issues initial wifi connection. But, last i used it, it was around 1 minutes 40 seconds (approximately)
The problem is that wake up is managed by a different electronic circuit than esp itself and we are not able to manage it. So, there is an external guy who controls when to wake up and sleep