Ness Alarm Aux not triggering since 2022.7.0

[EntityOZ]

The problem

It seems that since 2022.7.0 aux output triggering is not working in Ness Alarm.

I have a script to trigger the Aux when a button is pressed but ever since the issue with Ness Alarm in 2022.7.0 it never worked. I also tried via Developer tools - Service - Ness Alarm: Aux service but doesn’t work either. Can you please have a look at it?

What version of Home Assistant Core has the issue?

All since core-2022.7.0

What was the last working version of Home Assistant Core?

core-2022.6.7

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ness Alarm

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ness_alarm/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @nickw444, mind taking a look at this issue as it has been labeled with an integration (ness_alarm) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ness_alarm can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign ness_alarm Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

ness_alarm documentation ness_alarm source _{^{(message by IssueLinks)}}

[EntityOZ]

Hi @nickw444

Any chance you can have a look at this one please?

Thanks.

[nickw444]

Not yet, sorry. The issue for me is that I don't have a Ness alarm panel at my place of residence, so it's difficult for me to develop/test changes in this integration. I do have limited access to the Ness alarm system at my parent's home, but it's difficult to do development as

a) I don't want to accidentally trigger the alarm whilst working remotely on the integration (and subsequently annoy my family) b) And I have to travel there in order to do any local dev/debug on the physical panel (e.g. checking state transitions are correct)

Furthermore I have little appetite to install a panel in my own place of residence as I already have a working "alarm" using off the shelf Zigbee hardware, which works arguably better and far cheaper/easier to extend than a Ness panel.

Perhaps I should try to scrounge together some sponsorship money on the integration to purchase a panel for development (https://homesecurityonline.com.au/shop/alarm-systems/alarm-kits/d8xd-deluxe-panel-white-lcd-keypad/)

[hcross13]

@nickw444 if you set up a funding page, I'll happily contribute to help get you a Ness system

[ouchkilljoys]

@nickw444 Likewise would be happy to contribute to the funding page if thats what helps get some of these stickler issues resolved, The arm_home one is one I'd love to contribute to to get fixed 😁 if testing hardware is whats needed then happy to help!

[nickw444]

I have raised a work in progress to resolve arm_home issues: https://github.com/home-assistant/core/pull/94351. Once that is complete, I will likely move onto debugging this issue.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[nickw444]

Still active, not stale.

[hmousaab]

@nickw444 Any updates ?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.