What is my point?
I thought you would be interested in unexpected behaviour of your software.
There are a number of questions I had...
Once the value is there how do I get rid of it?
The delete option is no longer there.
Going away from/returning to this page doesn't change it.
If I change it to a DateTime type it accepts it, but with bad DateTime as the value.
Only then do I get the option to delete the row.
Where does the fault get stopped? Does this interface allow for this strange value to be stored within itself? If the value can get in there will it affect other parts of the system?
Presumably groovy deals with it (perhaps it does, perhaps it doesn't - I don't know).
But can the rest of the logic of the system accept an anomalous value like this?
Perhaps people aren't going to do this because in the end it is their system, but could this be accidentally typed in? What if they copy/pasted a large value by accident, and they look at the screen and see the value field has disappeared?
If there is a path for invalid values to be entered could this be exploited by third party code? I don't know if you've followed the path of values and done boundary analysis of your code, but I thought I'd give you a heads up on at least one of the bugs I found.
I recently tried out GarageSale (on my mac) which has been around since at least 2009 and found a bug - they sorted numbers alphabetically, so shoe size measurements would end up as 1, 1.5, 10, 10.5, 11, 11.5, 2, 2.5. How was this overlooked for so long? Did no one say anything? Did they not realise?
I commented about this on their board; they worked on it, gave me access to the beta to test and it was fixed.
I've also worked adjacent to a compiler developer (I ran training sessions to companies using this particular language) and their attitude was that -anything- that was wrong should be reported, including incorrect comments in the compiler so I tend to take that attitude with me.
When I was developing software I was always happy to hear about -any- bug. When I was working as a software tester I found lots of bugs - they would be accepted and decisions made about the priority of fixing them (one had a leap year bug in it - when it was 29th Feb the program would return 1/Jan/1970 - I'm sure you know what was happening there), but I never had people asking "why are you telling me this?".
What sort of errors do you want to know about? Bad links? Documentation? Incorrect behaviour?
I couldn't find a dedicated channel to report bugs on (is this the correct forum for it?), or Hubitat's bug reporting policy.
BTW - another bug (I found this yesterday, a couple of hours after getting my hubitat)
When you are setting a basic rule with "Time of day" > "A certain time ...", have AM/PM set to PM and you click down on the minutes then click "Update", it always switches it back to AM.
Another issue.
Should the auto generated name for a Basic Rule be updated when the rules are changed?
The name shown on the "Apps" page reflects this name, but not the name exposed when you select "Change the Basic Rule Name?" - it seems to be set once, and no more, no matter how many edits are made to the rule.
