After upgrading to 0.88.0 there are several problems… the MDI update was covered in the post above under the panel-custom change. The custom component directory and python file will need their names swapped to clean up some errors, and I changed up a TON of CSS code to make things more responsive before upgrading but after, it looks like this:
After looking at the breaking changes it seems that they have discontinued use of paper-button and are using mwc-button now. After changing everything over to the new supported version of the button, it places a button within the frame of the existing button and nothing works properly. I reverted and am looking for a fix yet, but this and the image posted a few above is caused by dropping support for paper-button.
Anyone have ideas for getting the replacement working for now, ir ideas for importing paper-button.js back into this component until the new non-polymer UI is released?
Thanks
Have latest files as of the 10th, but some the above still needed to be done thanks
But when you use Lovelace Alarm Panel there is still n Keypad
I’ve just upgraded Hass.io and the only difference I can see is that text is not centered within buttons, but they are still round. Cleared cache before checking.
and yes, it says “WARNING (MainThread) [homeassistant.loader] Integrations need to be in their own folder. Change alarm_control_panel/bwalarm.py to bwalarm/alarm_control_panel.py. This will stop working soon.”
Thanks but have done all the changes with main ones around fixing keypad but still no go @property
def code_format(self):
“”“One or more characters.”""
if self._code is None:
return None
if isinstance(self._code, str) and re.search(’^\d+$’, self._code):
return alarm.FORMAT_NUMBER
return alarm.FORMAT_TEXT
warning, I am not a programmer, developer, or even like to write code
can someone explain something to me. I have hass.io working with the Konnected boards and running this security system. Am I supposed to write an automations.yaml file to actually sound the alarm when this is “triggered” I’ve been trying to write one, but then when I look in the developer tools, state section it appears that most of what I am doing is already there…
sorry for such an elementary question, but I must be missing something here.
here is what I have written so far. is this necessary or am I reinventing the wheel.
I still can’t get it to set off the siren when I open the door and when it does I can’t get it to disarm.
Mate, the idea is you need to react to the state of alarm panel as it itself takes care of the sensors configured via alarm.yaml/webinterface.
Therefore for your siren you can use something like:
That’s basically it, apart from the fact that you need to switch off your siren somehow when the alarm is disarmed OR goes back to armed away/home state.
Regarding alarm beep when door opened or closed - you need to monitor appropriate sensors yourself and react to their state. Your trigger section should contain - platform sections, not - entity_id, read the docs
Error while setting up platform bwalarm
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py”, line 128, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.7/asyncio/tasks.py”, line 416, in wait_for
return fut.result()
File “/usr/local/lib/python3.7/asyncio/coroutines.py”, line 120, in coro
res = func(*args, **kw)
File “/config/custom_components/alarm_control_panel/bwalarm.py”, line 316, in async_setup_platform
alarm = BWAlarm(hass, config, mqtt)
File “/config/custom_components/alarm_control_panel/bwalarm.py”, line 341, in init
self.init_variables()
File “/config/custom_components/alarm_control_panel/bwalarm.py”, line 441, in init_variables
self.immediate = self._states[self._state][“immediate”]
KeyError: ‘disarmed’
Would this be an idea? Apparently it won’t work for the HTML files etc but would work for the “custom component” element of it. I guess if it won’t update as a whole it might be counterproductive and confusing.
For those who wants to get rid of the following warning in HA log
[homeassistant.loader] Integrations need to be in their own folder. Change alarm_control_panel/bwalarm.py to bwalarm/alarm_control_panel.py. This will stop working soon.
Just do what they say, namely: in create /config/custom_components/bwalarm folder, move bwalarm.py there and rename it to alarm_control_panel.py. Then it’s safe to remove /config/custom_components/alarm_control_panel folder
IMPORTANT UPDATE: if you set logging level for the alarm, it’s affected by this change and you need to change its full name. For example, in configuration.yaml it should be:
default: warning
logs:
# old style naming, doesn't work
# custom_components.alarm_control_panel.bwalarm: debug
custom_components.bwalarm.alarm_control_panel: error
My config was functional on 0.88.0, but after upgrading to 0.88.1 I found few automations not working exactly because they had no explicit initial_state.
