Bwalarm (akasma74 edition)

BWalarm, breaks in 0.115 with something to dp with html_url when registering the panel

Reported when the original deprecation notice came out. Akasma has stated he is investigating alternatives.

To be precise, I’m aware of the deprecation thanks to you guys but my investigations were (and will for a bit) far away from HA.
On top of that, Baloobs statement “who created HTML panel can create JS panel” is good and stuff but I honestly don’t know where to start.
So my advice at the moment is not to update HA to 0.115 or higher if you want to use this component.

Do you have any idea on when you might have the component updated to be compatible?

He did say far away so i wouldn’t expect it soon.

30 posts were split to a new topic: Migrating from bwalarm

I am so grateful for all the hard work of those behind most open source projects. I don’t understand why some feel the need to be rude and/or demanding of these guys that share their projects with us often asking little if anything in return.

It is a bummer that it stopped working on .115 hopefully he can get it working again soon, and maybe those that say anyone that does it on HTML can do it on JS panel perhaps they can roll up their sleeves and work on the fix.

No one was being rude. We were discussing contingencies to allow the dev time to work on a solution. I asked a mod to split it into another topic.

1 Like

I’ll definitely have more time from next week so there is much more hope :wink:
Does making a release that does not register the panel make sense as an interim fix (as some already did)?

that was Paulus so I really doubt he will work on it, ever :wink:

2 Likes

It seems to work well from what I can tell and is very easy to do (see split topic). I think it would be worthwhile.

1 Like

yeah, in fact the alarm itself can easily function on its own, the panel brings nice things like overriding sensors on arming and changing settings.
I have been thinking for a long time about splitting them in the light of depreciation of html panels and converting it to LL… will see.

4 Likes

@Ahmadk, please do not think your obliged to make it work, if RL is where you need to spend time, then please do. At the moment it works perfectly fine using the built in alarm panel. so no need to rush

I think one of the original driving factors behind this integration was that fact that we didn’t have the power to easily create a custom card with the old states menu and the html panel was put up in its place. Now we have Lovelace replacing it with either a custom card (or built in ones) certainly bears thinking about. I’d wait until the current lazy loading issue is sorted out though.

Yes please, as long as I can enable/disable with an automation would be great as interim.

I don’t quite get what you mean… 8()

The temporary fix (with no panel) is available for download.

5 Likes

I decided to try to transition to the manual alarm_control_panel, while waiting on the bwalarm update. It requires a bunch of automations, and more config, but in the end it does most of what I needed from bwalarm.
I made a custom Lovelace card (based on the earlier Lovelace alarm panel card), which works with the manual alarm_control_panel, and tries to reproduce the nice appearance of the bwalarm GUI.
I posted the modified card and my entire config, with automations, explanation, etc at: https://github.com/jcooper-korg/AlarmPanel

Here are some screenshots:

5 Likes

so how to fix with panel?

Thank you for this. Just what I was looking for! I have this working.

image

I’m using this as my base design for the wall panels:

The concept is a picture elements card with nested cards

Does anyone have any idea how I can style the alarm card to match my current fonts? This is what I have so far

          - prefix: Alarm System
            <<: *title
            style:
              top: 9.15%
              left: 58.25%
              <<: *title-style
          - type: custom:alarm_control_panel-card
            entity: alarm_control_panel.ha_alarm
            style:
              top: 42.25%
              left: 75.75%
              width: 35vw
              height: 60%
            labels:
              ui.card.alarm_control_panel.arm_away: AWAY
              ui.card.alarm_control_panel.arm_home: NIGHT
              ui.card.alarm_control_panel.clear_code: CLEAR
              ui.card.alarm_control_panel.disarm: DISARM
            scale: 14px
            states:
              - arm_home
              - arm_away

I have tried applying styles like I do with my other nested cards but it has not worked.

Thanks for this!

Roll back to 0.114 or wait.