-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Add Interlogix Ultrasync Alarm System Integration #15482
Conversation
Please rebase this pull request to the |
9d367cd
to
35dcdb3
Compare
@klaasnicolaas Thanks for your feedback; done! 👍 |
description: Instructions on how to integrate your Interlogix UltraSync Hub within Home Assistant. | ||
ha_category: | ||
- Alarm | ||
logo: informix.png |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a logo to our brands repository, you can remove the line here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done; updated comments. Here is a quick link to brands/1994
You also brought forth another bug, it shouldn't have read informix.png
, but interlogix.png
instead. Sorry about that; this is also fixed in latest push to this branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll need to remove the logo
manifest from this PR.
|
||
Go to the integrations page in your configuration and click on new integration -> UltraSync. | ||
|
||
**Note**: You can only be logged into the ZeroWire/UltraSync hub with the same user once; a subsequent login with the same user logs out the other. Since Home Assistant (HA) actively polls and maintains a login session to this Hub, it can prevent you from being able to log into at the same time elsewhere (via it's website). It is strongly recommended that you create a second user account on your Hub dedicated for just HA. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't abbreviate HA.
ha_domain: ultrasync | ||
--- | ||
|
||
The `ultrasync` platform will allow you to monitor and control your Interlogix UltraSync Hub from within Home Assistant and setup automation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The `ultrasync` platform will allow you to monitor and control your Interlogix UltraSync Hub from within Home Assistant and setup automation. | |
The Ultrasync integration will allow you to monitor and control your Interlogix UltraSync Hub from within Home Assistant and setup automation. |
|
||
## Sensor | ||
|
||
This component will create these sensors in the format of `{ultrasync_hubname}_{sensor}`; The below example assumes you accept the default name of `UltraSync` (which is still represented in lowercase): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The names entity names can be changed by the user, right? They are also visible in the device overview, right?
So the device entity name hint should not be needed.
|
||
## Sensor | ||
|
||
This component will create these sensors in the format of `{ultrasync_hubname}_{sensor}`; The below example assumes you accept the default name of `UltraSync` (which is still represented in lowercase): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additionally, we don't use double spacing.
- `ultrasync_area3state`: The Area 3 State | ||
- `ultrasync_area4state`: The Area 4 State | ||
|
||
There are several states each sensor can be at, but usually they will be one of the following: `Unknown`, `Ready`, `Not Ready`, `Armed Stay`, and `Armed Away`. The `Unknown` state is assigned to sensors that are not reporting; they usually sit in the spots of the Area's you're not monitoring. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are several states each sensor can be at, but usually they will be one of the following: `Unknown`, `Ready`, `Not Ready`, `Armed Stay`, and `Armed Away`. The `Unknown` state is assigned to sensors that are not reporting; they usually sit in the spots of the Area's you're not monitoring. | |
There are several states each sensor can be at, but usually, they will be one of the following: `Unknown`, `Ready`, `Not Ready`, `Armed Stay`, and `Armed Away`. The `Unknown` state is assigned to sensors that are not reporting; they usually sit in the spots of the areas you're not monitoring. |
|
||
## Event Automation | ||
|
||
When an Zone or Sensor changes it's state an event usable for automation is triggered on the Home Assistant Bus. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: add support for device automations to the integration?
When an Zone or Sensor changes it's state an event usable for automation is triggered on the Home Assistant Bus. | |
When a zone or sensor changes its state an event is triggered. Those events are usable for automations. |
- `ultrasync_sensor_update`: The event includes the sensor no, name, and new status it changed to. | ||
- `ultrasync_area_update`: The event includes the area no, name, and new status it changed to (if it did). **Note**: Area's are sent periodic heartbeats in which case the state will not change at all. | ||
|
||
Example automation to send a message via [Apprise](https://www.home-assistant.io/integrations/apprise/) on a sensor change in your home: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Example automation to send a message via [Apprise](https://www.home-assistant.io/integrations/apprise/) on a sensor change in your home: | |
Example automation to send a message via [Apprise](/integrations/apprise/) on a sensor change in your home: |
Available services: | ||
|
||
- `stay`: Set alarm scene to Stay Mode | ||
- `away`: Set alarm scene to Away Mode (fully activate Alarm) | ||
- `disarm`: Disarm the alarm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't these services dictated by the alarm control panel entity component?
I pushed a new change and that some how triggered a close on this branch 🤷♂️ |
Proposed change
Added documentation for new integration: Interlogix UltraSync Hub
Type of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.