Tasmota VS arduino-esp32

BTW, there is one more way - if your devices are connecting to some kind of central hub, e.g. MQTT broker, they may send a "sticky" (retained) message with discovery info to some known topic - Tasmota is using this way, devices are publishing to tasmota/discovery/id and every time MQTT client connects it gets lastly updated autoconf info.

Just seeing your edit. WeightRaw is changing, so that is a good sign that everything might be hooked up right. I believe weight is in KG so it won't necessary change unless you put over a KG on the scale. I looked at the code for this and couldn't easily figure out what might be causing the calibration failure. I don't have time to figure out what all is going on there.

These are Tuya ones (unfortunately, the specific one on Amazon has been removed now, so can't share a link) reflashed with Tasmota so I can use them natively with Home Assistant rather than bouncing through a third-party cloud service. Bit of logic to manage the transitions from "not using power" to "using power" and convert that into notifications to the various Google Homes.

If it's a simple thing, the Tasmota firmware might do everything you need without a single line of code.

The lesson here is to never buy a smart home product which can only be controlled/montitored/upgraded via a cloud service provided by the hardware vendor. If the product cannot be controlled and monitored from your home network while unplugged from the internet, then there is some risk that this type of experience can happen again. Tasmota [0] allows a user to erase the vendor provided firmware, of ESP chipset devices, with well maintained open source firmware so that is never reliant on the vendor ever again. This is one example. Perhaps there are others.

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

You can use wifi devices, you just have to be careful about it. Anything that is supported by the Tasmota Project (https://tasmota.github.io/docs/) can be re-flashed with their firmware which doesn't make any calls to the internet and will directly talked to by anything that supports the MQTT protocol (Home Assistant, Hubitat, etc)

Here's the list https://github.com/arendst/Tasmota/blob/development/BUILDS.md

Also the Arduino Core is open source, so you can always look at its source code and see how it's built (intended more for OP).

- Requires installation of EPS32 core. See https://github.com/espressif/arduino-esp32/blob/master/docs/arduino-ide/boards_manager.md for details.

The thing is that the GPIO0 actually controls where the code is loaded from at boot time. If it is low at boot time, the ESP32 tries to load code from the serial port (essentially). For an example, see this ticket: https://github.com/espressif/arduino-esp32/issues/2278

What I found was that the board would only crash whenever BluetoothSerial.begin("device_name_here") was called while only using a battery. There are others who have posted about having this issue; minus the battery comment. The crazy thing is, I swapped out the board for a new one and the problem just went away. One battery, two identical boards, same code. One crashes. The other doesn't.

For example, if you want to plug the S3 into a PC, you want USB device mode. See the following for examples. https://github.com/espressif/arduino-esp32/tree/master/libraries/USB/examples

I think I just figured it out, and from my understanding the spiffs begin as false, so I had to set it as true.

You don't need WiFiManager or fetch to make HTTPS calls, for what it's worth. Look into WiFiClientSecure and WiFi.