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.
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?
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.
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.
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 for your reply!!
I have read the configuration but i don’t understand how can I chose which sensors use the custom state and also how can I tell at the alarm the specific state to turn on the trigger
Stefano
there’s no need to. you just declare any additional custom ON states and OFF states and ANY sensor that has such a state will be recognised properly.
add your sensors to an immediate/delayed group of appropriate alarm more (armed_away, armed_home or armed_night) and declare custom on/off statuses if needed, it should do the job.
I’ve asked this once before, just asking again in case any new blood has any ideas on how to do this.
I occasionally have problems with a rogue sensor triggering erroneously. It would be really nice to be able to have my automations and ‘triggered’ state ONLY fire if two sensors trigger within, say, a five minute period. That way if my door/window sensor is playing up, I don’t get a scary alert in the middle of the night UNLESS a PIR also triggers within five mins.
You can set a template binary sensor which is to be fed by the two sensors and expose that to the alarm.
Through automation you can then both i) control the time interval between the two firings and ii) manually override it in the frontend without having to change the alarm settings.
With the current system, I don’t think you can directly.
However, you can create “dummy sensor” that would be used to trigger the alarm if they are “on”. To put the dummy sensor on “on” state you can use automation with your real sensors. Eg. if real sensor A and B are both On, then dummy is on (and then trigger the alarm). The idea is to create some intermediate fake sensors. Hope this helps.
GV
johnplanetz:
