CK-MQTT VS Tasmota

Now if you implemented your mqtt with an i++, this where you can start to have dataloss, because now that you sent 65k messages you finished you start to need actually free packet id.

And it cause a lot more issues that what I said there, that I hope I covered every case in my implementation: https://github.com/signature-opensource/CK-MQTT/blob/develop...

Then, this is just the PacketID Logic.

All of my office devices are connected to Sonoff S31 smart plugs, flashed with Tasmota on their own locked-down VLAN, and can be controlled via voice, Alexa, Tasker automation on my Android, NFC tags at my office door and various scripts triggered via my StreamDeck (on Linux). This all works fantastic, and I can turn on or off my devices, including my printer, when I start or end my day at work.

The best alternative firmware example for true IOT devices is Tasmota [1]. Erase manufacturer firmware for every ESP devices the day after purchase to avoid those careless manufacturer firmwares.

[1] https://tasmota.github.io/docs/

The ESP8266 based Sonoff S31 and ESP32 based Switchbot plugs, both flashed with either Tasmota or ESPHome, are my go-to options for US WiFi smart plugs with power monitoring.

And if you want to turn your ESP8266 into a standalone appliance, with a web interface and directly editable config that doesn't need a build step, Tasmota is another great option.

https://tasmota.github.io/docs/