Requests for binaries..

[smadds]

I continue to be a supporter of using the binaries and OTA updates as the normal way of deploying and updating Tasmota.

@arendst would you consider the following, in order to make their use easier?

1. Remove your MQTT host details so that the systems search for mDNS host

2. Remove your home wifi details from the builds so that the devices need to go into AP mode

3. Same for logging host

4. Consider changing the default OTA URL to the public one I host (http://sonoff.maddox.co.uk/tasmota/sonoff.ino.bin)

I realise these changes might be less convenient for you, but for the many others of us using your excellent code it would make life a little easier.

Finally, on a different subject, could the default "long press for reset" be changed from 4 secs to 60 secs? I think 4 secs is fine for techie white boxes that are generally hidden away, but I have recently started using the touch switches and it's very easy for someone to hover their finger on a button for 4 seconds! I don't think a minute is too long for the rare occasions we really do need to wipe the devices.

[arendst]

I will consider your suggestions. I guess I finally have to start using user_config_override.h ;-)

For the last comment SetOption13 1 should make a difference.

[smadds]

thanks for considering that, Theo.

Yes, there is SetOption13, but when you need to do a full reset it's good to have the ability - without having to get to the unit through a software link to turn the option on again. Rather defeats the object of having a hardware button reset.

Is a minute too long to wait before wiping all the local config?

[arendst]

No it's a matter of documentation. I'll change it to 60 seconds.

Shite. It's user configurable already. Use SetOption32 100 (current max) allowing up to 10 seconds and you're done. I'll change it to max 25 seconds. How about that?

[smadds]

Sounds like you're brokering a compromise deal ;)

The important thing for me is that the default is much higher, so that out-of-the-box it's high enough to avoid accidental usage. If the max is going to be 25sec then my plea would be to make that the default in the binaries.

[smadds]

On a similar note of 'making it easy', I wonder how many other people spend time setting hostname, waiting for reboot, setting mqtt name (the same), waiting for reboot, setting friendly name (the same), waiting for reboot. It would be a better experience if the initial configuration at the AP stage set all 3 ( e.g. just having a "Set device name" field). You could go back and reset individual names if needed, but my guess would be that most people wouldn't need to.

[arendst]

They could have opted for the backlog command allowing to change all at once with just one restart but then they don't have a webpage....

[smadds]

Don't get me wrong, Theo. The system can do so, so much these days it's incredible. I'm just looking at it from a "how simple can we make it" perspective.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem.