This is a fork intended to maintain the abandoned original bwalarm custom component until its author is back.
Feel free to post your question/ideas/suggestion/feedback here.
This topic is NOT intended for reporting issues so please create a new issue or a pull request at GitHub providing as much relevant information as possible.
When opening a new issue, please include versions of your component - it can be found in Settings -> About:
I have had good success with the BWAlarm install and the branch corrections. I am somewhat new to HA, but have all of my Alarm components configured and working via the Konnected boards. At this point I am working on my UI and have started playing with a custom Lovelace UI. I have added an iFrame card (in the ui-lovelace.yaml)
The BWAlarm displays fine via the Lovelace UI from my Mac (Firefox) and iPhone, but I get ERR_NAME_NOT_RESOLVED on the Fire Tablet, which will be my main display. It still works from the left menu. I realize this is somewhat off topic. But if I can get the Fire Tablet to work, I was intending on looking at the CSS to update since the current version does not quite fit into the iFrame card. If anyone has any ideas why I am getting the error I would appreciate the help.
Automation for panic mode --> show error : Configuration invalidCHECK CONFIG
Invalid config for [automation]: [value_template] is an invalid option for [automation]. Check: automation->trigger->0->value_template. (See ?, line ?). Please check the docs at https://home-assistant.io/components/automation/
- alias: '[Alarm] Panic Mode'
trigger:
platform: state
entity_id: alarm_control_panel.house
value_template: '{{ state.attributes.panic_mode }}'
to: 'ACTIVE'
action:
- data:
message: 'Tôi đang gặp nguy hiểm hãy về nhà ngay'
service: notify.thongbao
Please format your code correctly in the forum. Don’t post an image. The gif shows step by step how to do this. Posting an image makes it difficult for people to copy and amend your code in a reply to help you.
Thanks for making a fork and progressing this great component. I have a problem where on the sensors page when I select a sensor it ticks it then unticks it. All other setting seem to save ok.
I’ve never heard about things like that. Have you tried a different OS/browser?
If that doesn’t help, please create a new issue on Github indicating versions of your component and OS/browser you’re using.
MQTT integration looks to be broken with 0.92.1. Taking a working bwalarm (v1.1.4_ak74) confguration and enabling MQTT produces no alarm component upon a restart. The logs show the following message:
“Signature of MQTT msg_callback ‘custom_components.bwalarm.alarm_control_panel.message_received’ is deprecated”