Now I seem to have HE working as I'd like it, I'm starting to optimise the hub.
How would I go about turning off debugging for a couple drivers that I have ported across from ST. One in particular, my home alarm (internal motion sensors) floods my logs with debug messages, and there is no option to turn off debugging in the device pages.
All developers should be doing that to all their drivers, in my opinion
A consistent user interface would be enjoyable.
There's an additional part where the many log.???? needs to be reviewed and adjusted.
log.info seems to be exactly that.. info needed when debugging is off.
log.warn would be for problems (including "please update this code")
log.error That's obvious.
I have this imaginary limit.. there should be 2-3 log.info's per driver. They are the ones that show in live logs and tell us things are working right. Can't have zero, but more than 3 is just clogging the logs, again, in my opinion. If we see a WARN, then I think turning on debug is advised, in order to give the best info to the developer.
If you put something like that as the first line(s) of code, then updating is simply a matter of copying that URL from "yesterday's code" into the Driver/App Import Field. "Are you sure?" and click you're updated.