Home alarm status management (armed/disarmed)

[Archive] Feature request
, ,
81

Yeah, that’s not a bad idea, actually :sweat_smile:

82

@pierre-gilles,

I tested the image — just a quick note about the settings

For handling the access code parameter, I think we should force entering a numeric value or change the error message during validation
image

image

Same if a code is too short — change the error message because we always get the same one.
image

For the widget, I find it rather logical that the button is active when clickable.

83

The thing is that if it’s active when it’s clickable then it looks like this by default :

image
image563×480 11.9 KB

And like this when it’s armed (for example) :

image
image563×480 11.6 KB

In this case I find that even if it’s logical, it doesn’t highlight the current state of the alarm.

84

Thanks for your feedback! I’m working on all the feedback today.

For the clickable buttons, I’ll run tests and see what to do since I can see there’s no consensus on the matter :slight_smile:

85

I still have a question about the disarm part.
At my parents’ house, to disarm the alarm you have to enter the code. And I think that’s good. It should be possible on all Gladys instances to disarm with the code in one way or another.

The tablet-mode view is fine, but for me the classic-mode view should, when clicked, show us a screen with the code to disarm.

86

No, I don’t think so. The classic non

87

Added more validations on code creation :

88

On that point, I realized Firefox is a nightmare to get to respect the autocomplete=\"off\" directive (it doesn’t respect it)

The only solution I found is to add a second password field, hidden, so that it autocompletes that hidden field :tired_face:

89

Indeed, on iPad the buttons looked a bit small!

I tried a « bigger buttons Â» approach so it’s less easy to make a mistake :slight_smile:

IMG_4560
IMG_45601920×1872 130 KB

90

Oh yeah, that’s really great, we can go without hesitation :wink:

91

Continuing with the features, now after 3 failed attempts, the tablets are locked for 5 minutes. (It is still possible to unlock the alarm via your phone):

Screenshot 2023-10-27 at 11.44.27
Screenshot 2023-10-27 at 11.44.271284×1100 33 KB

In scenes, a trigger allows executing a scene on this event:

Screenshot 2023-10-27 at 11.50.36
Screenshot 2023-10-27 at 11.50.361456×724 39.2 KB

92

Regarding the active buttons, after testing I agree that it’s clearer to have the currently active state as « filled Â»:

93

New Docker image available for testing!

:warning: Warning, do not run in your production environment, this feature modifies the database :warning:

gladysassistant/gladys:alarm-mode
94

I just tested the image.
I find that the part of the code to enter is better proportioned like this :+1:

As for the widget, I find this version of active / inactive buttons more intuitive. However, I would have liked a label change once clicked:

  • ARM –\u003e ARMED
  • DISARM –\u003e DISARMED
  • PARTIAL ARMING –\u003e PARTIALLY ARMED
  • PANIC –\u003e no change

That way it’s more in line with the small status text we see above. My 2 cents :wink:

Final feedback regarding the little alert that indicates an incorrect code.

  • If I enter a wrong code, the message appears.
    I then type the first digit of my code out of habit as if to start over, but the field is not reset, so if I’m not careful I’ll type my code many times without ever starting « from zero Â» in the input field.

  • Same wrong-code scenario: when I enter the first digit after the message has appeared, it makes the message disappear
 but that shifts the keyboard keys upward which makes typing a bit awkward. The message should appear in a place that does not change the positioning of the keyboard keys.

That’s it!!

95

Thanks for the feedback @guim31 :clap:

Mmm not sure that makes sense, to me they remain action buttons rather than « state Â» buttons.

Indeed, I’ll fix that :smiley: good catch!

If I keep the message while you type, would that do the job? Because displaying the message in a place that doesn’t change the vertical positioning is tricky — there’s only below the keys and it would really look bad

96

Proposal:

(The text field is clear + the message remains to avoid layout shifts)

97

Indeed, if the message remains, that solves the problem :+1:

98

It’s fixed :slight_smile: I restarted a build

99

I’ve just tested and everything seems to be working normally on my side.
I haven’t tested the triggers « The alarm is being armed Â» and « Alarm: Too many invalid codes Â»

Well done :clap:

100

I just tested the latest image, it’s perfect for the keyboard that no longer shifts and for the text field that resets :+1::+1:

I can’t wait to be able to put all this in place at home, it will be much better than my current hack!! :grin: