akasma74 / Hass-Custom-Alarm

It is a fork of "Yet another take on a home assistant custom alarm" that will exist until its author is back to our Earth
79 stars 29 forks source link

Keypad not shown in Lovelace (Wanting to Arm the Alarm with Pin) #40

Closed YoinkZed closed 5 years ago

YoinkZed commented 5 years ago

Your components (from Alarm/Settings/About): This integration: v1.10.1 Home Assistant: v0.96.4 Python: v(3,7,4,final,0)

Platform & Browser:

Describe the bug When setting the option in Alarm --> Settings --> Alarm: Require a passcode to set the alarm, I'm not being presented to a keypad on my Lovelace Alarm Card, when I want to Arm my Alarm. The only way I can get a keypad shown, is if I arm the alarm through the Alarm Menu and when armed, a keypad is then shown to disarm my alarm.

To Reproduce Steps to reproduce the behavior:

  1. Add Alarm-Card to Lovelace
  2. Then it doesn't get shown

Expected behavior I expected the Alarm Card to show a Keypad, due to the setting set in the settings of the Alarm: Alarm --> Settings --> Alarm: Require a passcode to set the alarm

Screenshots Lovelace Alarm Card: image

Alarm Settings: image

Additional context This was working with the old Gazoscalvertos version on the same version with Hassio 0.96.4. I upgraded to this Custom Component following the guide today (once again), and then upgraded it using HACS. Everything else is working with the Alarm.

YoinkZed commented 5 years ago

I just saw your latest post on the community https://community.home-assistant.io/t/bwalarm-akasma74-edition/113666/352 - so do you want me to delete this and create it as a Feature Request instead?

akasma74 commented 5 years ago

No, just leave it as it is

michaelhdmd commented 5 years ago

I am using Lovelace as well, but I have an "iframe" card and point to the BWAlarm URL. I had to use the hard coded IP, rather than the "http://hassio.local:8123/alarm". There are some CSS issues and I have not kept up with recent updates from akasma74, but it works great for me.

akasma74 commented 5 years ago

I am using Lovelace as well, but I have an "iframe" card and point to the BWAlarm URL. I had to use the hard coded IP, rather than the "http://hassio.local:8123/alarm". There are some CSS issues and I have not kept up with recent updates from akasma74, but it works great for me.

do you mean you're using the original bwalarm or just that your version of this integration isn't the latest release? regarding your comment, as it's NOT a Lovelace card but a wrapper around the Alarm view, I'm not surprised that it works. it could do as a workaround for some..

michaelhdmd commented 5 years ago

I am using the BWAlarm branch, but I have not updated since the spring. Correct, I am not using the Lovelace Alarm card or a custom card. Just an iFrame card to display the BWAlarm URL. I do the same for Windy Weather and www.clocktab.com.

WaaromZoMoeilijk commented 5 years ago

I've moved from the old repo with all the summed up fixes (manually) to this repo on HACS and that broke my alarm panel for the lovelace frontend. Been seeing more and more people having this issue.

akasma74 commented 5 years ago

it cannot break your alarm panel