Skip to content
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

Notify user if arming or disarming totalconnect alarm fails #36085

Merged
merged 8 commits into from
Jun 3, 2020

Conversation

austinmroczek
Copy link
Contributor

Proposed change

Create a persistent notification to tell a user that their attempt to arm or disarm their TotalConnect alarm system failed. Add tests for arm/disarm.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

No changes to configuration.

# Example configuration.yaml

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • [n/a] Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

  • No score or internal
  • 🥈 Silver
  • 🥇 Gold
  • 🏆 Platinum

@austinmroczek
Copy link
Contributor Author

austinmroczek commented May 27, 2020 via email

@bdraco
Copy link
Member

bdraco commented May 27, 2020

Does raising that exception result in feedback to the user in the UI?

Yes

@austinmroczek
Copy link
Contributor Author

@bdraco I redid the code like you suggested. I can see the exception being raised in a log entry, but there is no immediate feedback in the user interface. Am I missing something?

@bdraco
Copy link
Member

bdraco commented May 28, 2020

Screen Shot 2020-05-27 at 10 22 03 PM

Screen Shot 2020-05-27 at 10 25 20 PM

Here is an example of what you should see. This is from doorbird.switch.DoorBirdSwitch:turn_off. The example are from the main UI, and the services dev tools

Copy link
Member

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@MartinHjelmare MartinHjelmare merged commit 98a056f into home-assistant:dev Jun 3, 2020
@austinmroczek austinmroczek deleted the arm-feedback branch June 6, 2020 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

totalconnect provides no user feedback when arming fails
4 participants