<div>
<div>Thanks, Samer… I appreciate all your work on the project. You do great work.
</div>
I got things working OK by adding the additional parameters, but it sure is complicated . It seems kind of dangerous that a badly formed GET command would shut down all access to controller.</div>
<div>
The way that it is set up, a program that just wants to change the water level has to also manage the NTP, DHCP, ignore password, rain sensor, and type of rain sensor states. Kind of goes against the whole spirit of a REST interface.
</div>
It seems to me that a better way would to make the state of each parameter independent of the others. If a parameter is not mentioned in the GET command, it is not changed. If it is set =0, it is off, and =1 it is set to on. That way there is no confusion about unintended side effects of a state change, and a program does not have to be concerned with managing all the other states in the command.
Does this sound reasonable?