search

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
80 stars 31 forks source link

0.115 no longer supports html_url for registering panel #124

Open aidbish opened 3 years ago

aidbish commented 3 years ago

The component:

Your setup:

Describe the bug in 0.115 the html_url is no longer valid for regsitering the panel and bwalarm doesnt load

https://github.com/home-assistant/core/pull/39799

callahan17 commented 3 years ago

Same here, latest version 0.115.0 has breaking changes. Also don't know if this helps AgentDVR's update also has a new alarm panel alarm_control_panel.nvr_alarm_panel does this conflict? Logger: homeassistant.components.alarm_control_panel Source: custom_components/bwalarm/alarm_control_panel.py:395 Integration: Alarm Control Panel (documentation, issues) First occurred: 7:20:56 (1 occurrences) Last logged: 7:20:56

Error while setting up bwalarm platform for alarm_control_panel Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 193, in _async_setup_platform await asyncio.shield(task) File "/config/custom_components/bwalarm/alarm_control_panel.py", line 395, in async_setup_platform await hass.components.panel_custom.async_register_panel( TypeError: async_register_panel() got an unexpected keyword argument 'html_url'

BigHomie90 commented 3 years ago

Same here.. The funny thing is that i was on 114 version when i found this integration. I was super excited to test it so i installed it and had a quick look at the web interface etc. At the same time the 0.115 update notification appeared. I did the update and its not working cause they did some breaking changes and i didn't even have 5 minutes to test the integration. xD.

ronniebee commented 3 years ago

Same here.... since 1.15 no working alarm anymore. Entity not availability..... please advice...

aidbish commented 3 years ago

Either rollback to 0.114 or wait till updated by developer when he can get to it or use another alarm component https://community.home-assistant.io/t/bwalarm-akasma74-edition/113666/852

ronbrou commented 3 years ago

Same here since 0.115 not working alarm anymore. Entity not available. Is there a chance there will be an update on bwalarm ?

isabellaalstrom commented 3 years ago

If you are not using the panel, or rather have the alarm working at all without the panel, you can just comment out that line and the integration should work. Without the panel.

ronbrou commented 3 years ago

Thank you for he workaround. I comment out the line for the panel and that did the trick for me.

Met vriendelijke groet,

Ron Brouwers

Gsm: +31 653 86 21 04 Mail: ron.brouwers@outlook.commailto:ron.brouwers@outlook.com

From: Isabella Gross Alström notifications@github.com Sent: vrijdag 18 september 2020 18:56 To: akasma74/Hass-Custom-Alarm Hass-Custom-Alarm@noreply.github.com Cc: ronbrou ron.brouwers@outlook.com; Comment comment@noreply.github.com Subject: Re: [akasma74/Hass-Custom-Alarm] 0.115 no longer supports html_url for registering panel (#124)

If you are not using the panel, or rather have the alarm working at all without the panel, you can just comment out that line and the integration should work. Without the panel.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/akasma74/Hass-Custom-Alarm/issues/124#issuecomment-694976472, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOZUJRODM3XD6CSMK654E6TSGOGJXANCNFSM4RHNLVBA.

e2m32 commented 3 years ago

FYI, here are the lines that need to be commented out:

custom_components\bwalarm\alarm_control_panel.py: lines 392 to 402

# Register the panel
# url = "/api/panel_custom/alarm"
# resources = os.path.join(_resources_folder(hass), PANEL_FNAME)
# hass.http.register_static_path(url, resources)
# await hass.components.panel_custom.async_register_panel(
    # webcomponent_name='alarm',
    # frontend_url_path="alarm",
    # html_url=url,
    # sidebar_title='Alarm',
    # sidebar_icon='mdi:shield-home',
    # config={"alarmid": "alarm_control_panel.house"},
# )
CancunManny commented 3 years ago

If you are not using the panel, or rather have the alarm working at all without the panel, you can just comment out that line and the integration should work. Without the panel.

I am having the same problem after one of the recent updates. Basically the Alarm link on the left column is gone. I am guessing the section blocked on the code will make the rest of the alarm function properly, like the keypad on the overview screen, but how would we make changes to the alarm setting, like if I get a new motion sensor.

e2m32 commented 3 years ago

You can directly edit the resources\bwalarm\bwalarm.yaml file that the web UI produces. This was used originally before the web UI was built out. You probably have to restart HA in order to load changes... I think the UI updates on the click save buttons.

marine1988 commented 3 years ago

Any news on this matter my home was no alarm now :(

akasma74 commented 3 years ago

@marine1988 mate, roll back HA to 0.114 until I fix it, that's the only option ATM. I know you guys want it back but I'm still way too busy and will definitely come back and fix it as soon as I have time.

e2m32 commented 3 years ago

Any news on this matter my home was no alarm now :(

@marine1988, you can either do what @akasma74 suggested and downgrade or you can upgrade to the latest version of this alarm and install the lovelace alarm panel. It's super simple to setup, it takes like 2 clicks if your using the UI based (default) version of lovelace. It works great with this custom component, I've used it this way before @akasma74 graciously forked and took ownership of this project and still use it this way.

akasma74 commented 3 years ago

Yes, some people use the standard LL alarm card to control this alarm. There are some limitations though, namely:

jes1417 commented 3 years ago

@akasma74 and it's too small on a 7" display...

akasma74 commented 3 years ago

Well, I think size is fixable using card-mod.. but it's additional work. This integration can automatically scale its content so it takes up whole panel.

e2m32 commented 3 years ago

The alarm will still arm if there are open sensors, but your right on the other points. Not saying that it's a fix, but it's a work around in the mean time if you need to be on HA 0.115+

marine1988 commented 3 years ago

The alarm will still arm if there are open sensors, but your right on the other points. Not saying that it's a fix, but it's a work around in the mean time if you need to be on HA 0.115+

yes me too sadlay I cant use this alarm anymore :( is there any ETA @akasma74 for the fix?

akasma74 commented 3 years ago

The alarm will still arm if there are open sensors

Only if ignore_open_sensors is set to true.

yes me too sadlay I cant use this alarm anymore

I don't quite unedrstand.. you have options for both pre 0.115 and 0.115+ so why exactly can't you use the alarm anymore?

is there any ETA @akasma74 for the fix?

I don't want to give false promises mate.. at least because a) I'm still working every day to complete my offline project and b) it's not a simple fix - it most likely will require for me to learn how to create custom Lovelace cards, not a quick task.

So as I previously said - stay tuned, I'll come back to it as soon as I can.

akasma74 commented 3 years ago

I think it's too early to close this issue ;)