tasmotizer VS OpenBK7231T_App

I tried micropython, liked it, an developed and operated a few home automation devices with it. But changing anything after a few months was a pain - what flashing tool did I use, how did that detail work, etc. Now I run around 15 Tasmota devices in my household and would never look back. The initial flash, depending on the device at hand, can be trivial (e.g. using https://github.com/tasmota/tasmotizer on a device with builtin USB connectivity or with a USB-serial cable) or a bit less so (like the somewhat involved OTA reflashing process https://github.com/yaourdt/mgos-to- for the very handy and inexpensive Shelly devices). In any case, after that it all becomes easy, with web-based configuration, OTA updates, "fleet managament" software like https://github.com/danmed/TasmoBackup, and plug&play integratiom with Home Assistant. If somebody integrated micropython into Tasmota for cases where the countless configuration options and libraries integrated into Tasmota don't suffice, it would be perfect. But meamwhile there is a similar scripting language available within Tasmota for ESP32 devices so I can live with that.

If you use a d1 mini it has usb, just use https://github.com/tasmota/tasmotizer

Oh, that's sad. It seems like such low hanging fruit to support it. There is already a pull request to add the support that OP could use and test.

We start with a couple sensors for temperature, humidity, and particulates. Those connect to an ESP8266 via I2C and some proprietary IKEA protocol. That IKEA protocol wasn't in the default build, so I had to enable a define and rebuild. They've made very cool use of Gitpod so I didn't even have to install anything. I used Tazmotizer.py with a USB programming fixture I got off Amazon to load my custom firmware to the board.

It’s a SonOff Basic and flashed it with Tasmotizer. It didn’t work with the first try but after the third it works pretty well. I was too lazy to solder the pins on it. But if you have many of them, it would be great when you can upload it without a pc.

Incase you don't have a flasher,tasmotizer is an super easy software to flash a single bin file. https://github.com/tasmota/tasmotizer/releases/download/v.1.2/tasmotizer-1.2.exe

Flashing software https://github.com/tasmota/tasmotizer/releases

do i have to do the wiring and run Tasmotizer ?i assume not because the tasmota interface comes up just fine.

Tasmotizer is probably the easiest way to serial flash in Windows (and has cross platform versions for Mac and Linux). That said, it does require a hardwired serial connection.

I've found many of the devices can now be flashed with https://github.com/openshwprojects/OpenBK7231T_App

If you have some Pthyon experience, you should be able to use something like TinyTuya to pull DP data from your Tuya devices. Alternatively, you can use Tuya-Cloudcutter to flash a local-only firmware like ESPHome/LibreTiny or OpenBeken which have much easier integration options (local open API, HTTP, MQTT, etc).

The S40 plugs switched from the ESP8266 MCU in the S31 to a BL602 MCU, so you'll need to flash using OpenBeken or LibreTiny

Since it’s tuya you could install custom firmware (openbeken) for fully local control and use device group feature to sync the light colors without relying on cloud.

Tuya devices, and the Tuya-based Monster, Greeni, etc stuff can be connected to HA using the Tuya Integration, or converted to local-only using Tuya Cloudcutter and connected to HA using Local Tuya, or even flashed with Tasmota, ESPHome/Libre Tiny, or OpenBeken.

A: OpenBeken: What are your opinions of it? I haven't played with it yet, but it being a non native means of getting it into ESPhome has me concerned about stability and project support. Not having to modify the hardware would be nice.

I did this with mine, https://github.com/openshwprojects/OpenBK7231T_App