tasmota
Config reliability
No doubt about it, Tasmotizer is the best way to Tasmotize our ESPs, but on several occations I've found the CONFIG section less than reliable. If I use Tasmotizer to flash the chip then flick over to my phone and enter the SSID, pass and ID, the chip hops onto my network every time, but if I choose instead to use the config page on Tasmotizer, it doesn't always work and I sometimes end up having to re-flash the ESP (using Tasmotizer of course). Am I alone?
Peter,
I found that setting too much info at once does not work with Tasmota.
I keep a couple of text lines, which I copy-paste in the console.
- Network settings ( ex. ssid1, password)
- Other network settings ( ex. Ntp, timezone )
- States and Mqtt settings (ex. poweronstate, ledstate, mqtthost, mqttuser )
- Custom names ( ex. Friendlyname, grouptopic )
Tasmota wants to restart on some settings, configuring on baby steps seen to work better for me.
Also I flash a blank, disconnect and leave off for an hour. Then flash (with erase) Tasmota. Connect with terminal, do settings slowly.
Hope it helps.
Logix.
On Sun, 03 May 2020, 17:57 Peter Scargill, [email protected] wrote:
No doubt about it, Tasmotizer is the best way to Tasmotise our ESPs, but on several occations I've found the CONFIG section less than reliable. If I use asmotizer then flick over to my phone and enter the SSID, pass and ID, the chip hops onto my network every time, but if I choose instead to use the config page on Tasmotizer, it doesn't always work and I sometimes end up having to re-flash the ESP (using Tasmotizer of course). Am I alone?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tasmota/tasmotizer/issues/40, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN3EDC2FVNSG5S5MUG5NRF3RPWH5LANCNFSM4MYFXEXQ .
Please test the rewritten send dialog functions from branch develop-1.3
