I notice some behavior of of lower/upper alarm limit that may be improved. not sure they are intended by design or bugs.
Since 4 the limits can be left empty, that I though the empty ones will be consider as None, not being use to calculate stat nor triggering event.
But on my test, the empty ones seem to be consider as 0, being use to calculate stat, but only not not triggering event.
Case 1 : None,None,10,20
when val is -1, the channel stat will become 11 and color will turn blue.
no event (correct, as it should)
Case 2 : -20,-10,None,None
when val is 1, the channel stat will become 11 and color will turn red.
no event (correct, as it should)
Case 3 : 10,20,None,None
when val is 15, the channel stat is still 13, lower limit not triggered
no event, (but it should be low limit event)
Case 4 : 10,20,999,999
when val is 15, the channel stat is still 12, lower limit is triggered
low limit event (correct, as it should be)
Case 5 : -20,None,None,20
when val is -1, the channel stat will become 12 and color will turn light blue.
no event (correct, as it should)
Currently, I filled in all 4 values as safe measures and workaround even though I just want to use 1 or 2 of them, such as:
-20, -20, 20, 20 when only lower alarm limit and upper alarm limit needed
-999,-999, 10, 20 when only upper limit and upper alarm limit needed
10, 20, 999, 999 when only lower limit and lower alarm limit needed