geetron
(Adrian)
March 2, 2023, 12:12am
342
I see that entity when I go to Settings > Devices & Services > Entities.
I think the issue is that, I wont be able to create an automation using the UI wizard e.g. Settings > Automations: Triggers, Conditions, Actions.
Looks like it all needs to be done via YAML.
EDIT: I was able to get this to trigger notifications. I have a new issue but not related to NESS.
- alias: 'NEWSend notification when alarm is Arming'
trigger:
- platform: state
entity_id:
- alarm_control_panel.alarm_panel
to: "arming"
action:
- service: notify.notify
data:
message: "ALARM! The alarm is arming {{ states('sensor.date_time') }}"
title: "Alarm is arming"
Does anyone know if there is a way with this integration to only arm specific zones in the house? I was going to use the Arm Home for this as we have our pet sometimes in one part of the house when out, however arming home has a known bug
aumatt
March 5, 2023, 3:17am
344
The arming home feature still works as normal on mine but it just reports back saying its fully armed.
Yeah I know about that way but I was hoping I could either fix it so that it properly says armed home or at the very least exclude certain sensors via an automation Iād love to try help but I dont even know where to begin
Ohh looks like the fix is eventually gonna be added to HA
Does anyone know how I can sideload this change because it looks like its been in limbo for a little bit already
home-assistant:dev
ā nickw444:nwhyte/nessclient-arm-home
opened 01:08PM - 09 Jun 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO Nā¦ OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Fixes the alarm panel incorrectly displaying as `armed_away` when it has been put into another state (e.g. `armed_home`)
The dependency (`nessclient`) has had changes to fix this issue: https://github.com/nickw444/nessclient/releases/tag/1.0.0
| Before | After |
|---|---|
| ![2023-06-15 20 31 55](https://github.com/home-assistant/core/assets/1289759/5af2cf4d-9863-4595-a3bc-12e77bdb2fa3) | ![2023-06-15 20 30 09](https://github.com/home-assistant/core/assets/1289759/d491c9dd-4fa0-4a4b-ae10-79bd602b3350)|
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #93310, #42329
- This PR is related to issue: N/A
- Link to documentation pull request: N/A
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] ~Documentation added/updated for [www.home-assistant.io][docs-repository]~
If the code communicates with devices, web services, or third-party tools:
- [x] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [x] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
nickw444
(Nick Whyte)
August 16, 2023, 7:08am
347
Eventually! haha. Finally found some time to make the requested changes so fingers crossed we can get it into the next release.
Would be great if someone could test it out when itās in beta!
1 Like
Can confirm the update has fixed up the home/away issues thanks again for all your work on this pluging we use it so much! Plus the sensors come in handy for the lighting automations.
nickw444
(Nick Whyte)
August 21, 2023, 11:21pm
349
Glad to hear the update is working for you! Thanks for testing/confirming.
ricky56789
(ricky56789)
March 31, 2024, 11:16pm
350
Hi, does anyone know how to trigger a panic alarm via HA? Canāt seem to figure it out
I can set off a panic alarm via the Ness aComms Android app but calling Ness Alarm: Panic in HA doesnāt do anything
Zachoz
(Zach)
April 7, 2024, 2:33am
352
I fixed this (along with a few other panic status related things) in my nessclient fork .
If you want to give it a try, download this directory and put it in your HA custom_components directory, restart and see if youāre still having the issue.
I didnāt submit a PR at the time since while these changes work for my panel version, I wasnāt sure if it would break for other peopleās.
1 Like
ricky56789
(ricky56789)
April 12, 2024, 9:53am
353
Cheers for that, gave it a go but still canāt get the panic alarm happening. I think mine is a panel version 5.8. If you know of any other fixes or workarounds to try, that would be awesome!
OzGav
(Oz Gav)
April 12, 2024, 3:21pm
354
Did you look at my hardware/esphome option?
ricky56789
(ricky56789)
April 12, 2024, 7:55pm
355
No sorry I missed that. Thanks! Iāll look into it
Surely there has to be a way to do it without a hardware solution if it can be triggered via the Ness aComms app