-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
name of the alarm #89
Open
AngelofromTurin
wants to merge
355
commits into
gazoscalvertos:master
Choose a base branch
from
akasma74:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
class BwResources: added head method and get method simplified
wrong place
Bring back alarm_arm_xxx service calls (enabling alarm_control_panel.alarm_arm_xxx ones) AND adding safe versions that are configurable via their's parameters and do not set alarm if there are active sensors detected by default, i.e bwalarm.alarm_safe_arm_xxx. Fixes #19
Bring back alarm_arm_xxx service calls
ARM_XXX MQTT commands now behave exactly as alarm_arm_xxx service calls - they ignore open sensors. On the other hand, SAFE_ARM_XXX MQTT commands set alarm only if there is no active sensors detected.
SAFE_ARM_XXX MQTT commands introduced
Replaced [HASC] with [HACS]
Fixed typo
Insted of having different service calls and MQTT commands it's now controlled by ignore_open_sensors attribute. it can be changed manually in bwalarm.yaml, from Settings->Alarm or by calling set_ignore_open_sensors service
HA does not pick up the descriptionof services if they are not registered in bwalarm domain. oh well..
As required by HA 2021.3.0
Add version key
…me Assistant 2021.10 Tested as working on 2021.10.0.b2
Update alarm_control_panel.py to correct removal of ruamel_yaml in Home Assistant 2021.10
Create extra_state_attributes property and call it from device_state_attributes for HA older than 2021.12
check if it helps with issue 141
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi
its possible to change thise : config={"alarmid": "alarm_control_panel.home_alarm"},
in: custom_component/bwalarm/alarm_control_panel.py and edit string 384 in dimac way for personal name? the name of my allarm is different and for every upgrade i need to change manually in the code the "alarmid"
thank you so much :)