I see.
Was asking because there is an open issue and I have changed the code (and it works for me), but it still doesn’t work for him for some reason…
Yeah, I saw that 
I wont have time to update my code to your repo until next week, but I can test it then.
Hi,
Is there a way to increase the keypad button size to approximately what it was in the “pre mwc-button” days? I have to put my reading glasses on to arm and disarm from a Fire tablet now!!!
Thanks
Try to search www/alarm/alarm.css for “div.digits” and increase height/width values.
Don’t forget to save changes and clear your browser’s cache and then reload the panel.
I tried that, but once you start getting to the size needed to see without glasses, it starts bringing up the scroll bars even on a desktop Chrome browser. I also played with the width and height settings in div.arm to make those more readable but had the same results.
2019-05-09 12:51:53 ERROR (MainThread) [frontend.js.latest.201904270] http://hassio.local/api/panel_custom/alarm:2029:37 Uncaught TypeError: Cannot read property ‘classList’ of undefined
2019-05-09 12:51:54 ERROR (MainThread) [frontend.js.latest.201904270] http://hassio.local/api/panel_custom/alarm:2029:37 Uncaught TypeError: Cannot read property ‘classList’ of undefined
Is it possible to use custom_updater?
restart and cache clear fixed the issue. thanks
I’m not familiar with custom_updater at all… is it something that people might need?
@rgregrowe I see… will look into it when I have time 
@jenmonk yeah, it’s always good to restart HA and clear cache of all of your browsers before opening a new issue
I’ve just uploaded patched www/alarm/lib/jscolor.js and for me there is no more fronted errors when using iOS app.
Thanks AhmadK,
Not sure if this helps, but there seems to be multiple discussions going on with the mwc-button changes:
https://github.com/custom-cards/button-card/pull/60
and:
I’m just installed this and I’m having a problem. I’m not familiar with this I’ll need some help getting it going:
First is a screen shot of my initial alarm screen:
Any help is greatly appreciated.
Could you post here your component and panel versions, OS and browser versions?
Have you tried to open it locally, i.e http://hassio.local:8132/alarm and/or use different browser?
Your Versions:
Home Assistant: v0.92.2
This Panel: v1.3.6_ak74
Component (Bwalarm): v1.1.4_ak74
Python: v(3,7,3,final,0)
Host system
|System|CentOS Linux 7 (Core)| - All software up to date from the mirrors.
Chrome Browser: Version 74.0.3729.131
Does anyone else get the sensor which tripped the alarm showing up in their logs?
I thought I fixed it months ago, but upon checking I can see no sensor’s name in my log - simply because the was a PR that hasn’t been merged into the original component’s code…
I’ve just uploaded a new version of /config/panels/alarm.html that fixes this bug, please check it out.
I tried to open a pull request to add custom_updater support, but I get a permission denied error.
This is my first swing at writing code for it, so not sure if it’ll work, but should be a good starting point. You can find more about it here and here.
Basically I added separate json’s for the bwalarm.py and the alarm.css. There is a way to do it all together, but how everything is organized I don’t think it’ll work (i.e. folder structure). So users would have to add two separate entries to the custom_updater, one for bwalarm.py and another for alarm.css. If any other files get frequently updated then it shouldn’t be hard to add support for them as well.
Thanks for the information, I’ll have a look.
FYI- I opened a feature request so I could send you the files.
I removed all traces of bwalarm, reinstalled it, cleared all caches and now it’s working. Tharks for the hard work on this!
What’s the best way to track this thread to see when updates occur?