Security Sensor LastTrip behavior
-
Ahhh, now I remember one more thing which bugged me about this. It is that ALTUI displays the LastTrip value for the sensors by default and the fact that it would display a time which did not correspond to the last trip event mislead me. In openLuup, this behavior is coded in the luup.variable_set function which means that I can't just modify it for specific devices using a different device implementation file. Maintaining the original behavior and just adding an extra variable would mean that modifications of ALTUI would be needed to change what it displays... right now the variable doesn't even relate to the time the variable last changed or was last tripped. It just shows the time of the last "luup.variable_set" for the tripped variable event.
-
Ahhh, now I remember one more thing which bugged me about this. It is that ALTUI displays the LastTrip value for the sensors by default and the fact that it would display a time which did not correspond to the last trip event mislead me. In openLuup, this behavior is coded in the luup.variable_set function which means that I can't just modify it for specific devices using a different device implementation file. Maintaining the original behavior and just adding an extra variable would mean that modifications of ALTUI would be needed to change what it displays... right now the variable doesn't even relate to the time the variable last changed or was last tripped. It just shows the time of the last "luup.variable_set" for the tripped variable event.
-
You are right, I just went back to the ALTUI code and I can see that it's hard to do. I am not so verse in JS so I tried avoiding it. It makes for more changes but it is the safer route.
to answer your question, let me test further to see if we can think of even better ways to do it.