Good point. After pondering that I can say that any sensor should be in immediate or delayed groups to trigger the alarm, and can optionally be in override group to ignore its active state when setting the alarm.
Does it make sense?
Yes !
Exactly that.
Thanks Ahmad for supporting this component!
I’m finally upgrading to the “new ui” after running my fork of the previous gazoscalvertos for the last year. Updating my konnected firmware and HA version to current has forced me into updating!
One of things I changed in my previous fork was to increase the button sizes and fonts for the Home and Away buttons, and the digits buttons. I find the current implementation way too small on my landscape Fire tablet. Font sizes don’t appear to be part of the new customizable Theme feature.
Has anyone done any work on this? I’ve spent some time trying to tweak the css but without much luck so far.
Also, on HA 0.96.5, the sidebar doesn’t properly hide. Any fix for that?
Thanks,
-John
Interestingly, some people on this forum and myself have completely opposite issue - it’s too large on small screens and one need to scroll down to tap on Disarm, for example.
Perhaps it depends on your screen resolution as the alarm.css has several settings.
In the latest original version it was harder to adjust some of the parameters, especially the bottom bit with keypad, sensors, log and settings shortcuts.
I haven’t played with themes yet, have you tried to change anything via Settings → Design?
I haven’t updated my HA to the version in which they changed the sidebar’s behaviour so cannot test. If anyone has a fix, they can create a PR on Github and I’ll eventually merge it. Or just wait until September 
Thanks for the reply!
As far as I can tell, there’s nothing in Settings>Design that will help with sizes. I experimented modifying the CSS and HTML: in the CSS, i tweaked the div.digits values within the “SM > 768” (min-width: 768px) section, adjusting the height to reduce the spacing there. But I still haven’t found a way to increase the size of the mwc-button, or to increase the size of the fonts. (my experiments with the font-size and mwc-button size had no effect - there must be something I’m missing).
I also changed the HTML to use the 123/456/789/c0d pattern, even on larger screens (I just can’t get used to having the 0 on the right like that!)
What’s the plan for the sidebar in September?
Thanks again,
John
For the sidebar issue, go to your Profile settings in HA and select “Always hide the sidebar”. That will stop it from showing up in the Alarm page.
As for the button size, the best I’ve been able to do is play with the Zoom and Scaling settings in Fully Kiosk to get the panel so I don’t have to scroll. The original code used paper-button for the keys, but HA went to mwc-button as a replacement and it seems to have some issues with the ability to change the font size and height at least with the alarm code.
A couple release back of Ahmad’s fork, I successfully included this code:
https://github.com/ammmze/button-card/blob/23bc58cda2ea2022e09ec278c906f9c0d25cafdb/button-card.js
and changed everything back to paper-button. I then had the nice big buttons back. Ahmad made a lot of changes in the later releases and I wasn’t successful in the later releases.
Aha! That works- thanks.
I see. It would be nice to figure this out. I’ll try zooming in Fully, but that’s not the greatest solution, so I’ll plan on experimenting some more.
-John
yeah, I mixed it up with colours. css for sizes. don’t remember what exactly I changed, but it looks better than the original version on my 7" tablet.
could you post your screen so I have an idea?
I don’t quite get it…
could you tell us how exactly to use your code, even with the original component? then I might be able to integrate your solution.
probably you included your code before the “New UI” release because I think I did only cosmetic changes in alarm.css/html.
yeah, I mixed it up with colours. css for sizes. don’t remember what exactly I changed, but it looks better than the original version on my 7" tablet.
could you post your screen so I have an idea?
johnplanetz:
It’s difficult to photograph without reflections, but here you go.
You can see i’ve rearranged the buttons to have four rows, with ‘1 2 3’ in the first row and ‘CLEAR 0 DISARM’ in the bottom row, instead of three rows with ‘1 2 3 CLEAR’ at the top, etc You can also see that on this screen, there’s a lot of wasted space. The buttons and text could all be much larger. As it is, they’re too small and hard to read.
And in the disarmed screen, it’s just a huge open expanse with two tiny buttons “HOME” and “AWAY”… I actually prefer the old way where it showed the open sensors on the the arming screen so you could immediately see what you need to close before leaving. Has anyone tried to bring that back (maybe as an option?)
Thanks for the pictures.
In the last original release from November 2018 (?) the bottom part occupies much more than it needs (you can see the greyish rectangle), that’s one of the reasons. The bottom bit is a bit oversized, too, but it’s easier to shrink.
So what’s your ideal Armed screen then?
I don’t remember that - do you happen to have a picture?
Hi Ahmad,
I included the button-card.js after you forked the project. Basically I just went in and changed all the mwc-button back to paper-button. I also reverted back to all the lines that had “/DS/” changes (author of those mods?). That all worked fine and I had the big block keypad that displayed nicely on the tablets. The release you made to change to HACS,I believe you also made some changes to help with screen size? I tried to do the same changes against that release and the keypad got jumbled together. I’m not a css/html programmer, so it was probably a simple error on my part. I just haven’t had a chance to figure it out and I went back to the release code. If you or someone else can look at it, the button-code.js does/did work and returns the nice readable buttons we had before HA changed to MWC.
Greg
I don’t have a picture handy - and unfortunately it’s not easy to get back to running the old version. But it was just a HOME and AWAY button at the top, with the list of sensors beneath it, so you could easily see “oh, i forgot i left that window open”, before arming.
Similar to what I showed in the picture, but the digits buttons should be much larger so they’re easier to press, and the number text should be much bigger so it’s easier to read.
where did you save button-card.js for HA to pick it up?
These are my changes to get the latest release look “ok” on my 7" tablet
I doubt so, that was just change of the way we add custom panel to HA.
Anyway, I’ll definitely give your mod a try when I’m back to my system and report back.
In theory that shouldn’t be that difficult to implement… Will have a look at the original code to get the idea.
Could you create a Feature Request on GitHub for this as it’s easier to deal with issues/requests that way?
Sorry, what number text?
Ahmad,
I put the button-card.js file in the lib directory with the rest of the .js files and included it in panel.html as a script just like countdown360.js and the other lib .js files.
Greg
1 Like
I can’t use the Xiaomi Vibration sensor, someone have used the alarm panel with this sensor?
They are sensor not binary, the action are Vibration or Tilt not ON or OFF.
Regards
Stefano
P.S. If are not implemented please implement this AK74 
I mean the font used inside the buttons for the digits 1,2,3,etc and “clear” and “disarm”.
Similarly the font used for the words “home” and “away” in the arming screen buttons.
Also, last night my wife asked me, very confused, how to disarm the alarm now from the phone – the word “disarm” was replaced with a fingerprint icon in that view, and she was trying to use her fingerprint sensor on the iPhone. Honestly, it’s not a very attractive icon anyway, and should probably be made optional in the theme. I’ll add that as a feature request on GitHub, along with the the arming screen sensor list.
Thanks again!
-John
It should be listed, can you see it in the list of available sensors?
You need to use custom_states_on/off configuration attributes to integrate your sensors properly.
I was confused as well when I saw it for the first time in new UI release - the idea behind it was apparently to save space on small screens (as it takes less space that two buttons with text).
Thanks a lot!!!
i need to read how to create a custom states… where can i see the guide?
Thanks a lot