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
Cannot arm concord232 alarm #5049
Comments
I have made a custom component by duplicating the concord232 component and changing the home arming from 'home' to 'stay' which fixed that, but I couldn't get the exit/away/auto to work. The concord232 server which this runs on seems to have an issue and with the little documentation I found I cant figure out if the alarm panel needs settings changed or if this is a bug in the component/ server |
Try starting to the concord232 manually and watch the log and arm to
what you want via the actual panel. You should see the command go
across the screen. You should be able to adjust from there. I am
doing construction and my panel is disconnected, so I will not be able
to help right now
--
Best Regards,
Jason Carter
m: (813)-516-5861
e: jason@jason-carter.net
"Anyone who stops learning is old, whether at twenty or eighty" -
Henry Ford
On Thu, Dec 22, 2016, at 09:56 PM, CTLS wrote:
I have made a custom component by duplicating the concord232 component
and changing the home arming from 'home' to 'stay' which fixed that,
but I couldn't get the exit/away/auto to work. The concord232 server
which this runs on seems to have an issue and with the little
documentation I found I cant figure out if the alarm panel needs
settings changed or if this is a bug in the component/ server
— You are receiving this because you were mentioned. Reply to this
email directly, view it on GitHub[1], or mute the thread[2].
|
another issue I have now found with this, and this one seems more dangerous, is that if I do not enter a code on the call service it can be disarmed. I am not sure if this is normal with this alarm panel but it seems like something that shouldn't and I am not sure if the server or something somehow saved my code and is using it whenever I call disarm or what. |
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 👍 |
If you go to "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/alarm_control_panel/concord232.py" line 124 and edit the line from self._alarm.arm('home') to self._alarm.arm('stay') everything works great. |
@marbaugh Please provide a pull request with the fix. |
The issue still exists. I havent had a need to get anything other than stay mode to work, but the fix mentioned by @marbaugh is what I had been doing and it works. |
@marbaugh have you figured out how to get the away mode to work. I submitted a PR to fix home/stay mode but haven't figured out the issue with away mode. |
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
):0.35.2
Python release (
python3 --version
):Python 3.4.2
Component/platform:
Concord232 Alarm Control Panel
Description of problem:
Cannot arm alarm from the included arm home or arm away. disarm works fine though. Home assistant is using an incorrect arm type as seen in the log below
I believe this is the exact same issue as seen in the NX584 component issue #2194
Expected:
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info:
@JasonCarter80
The text was updated successfully, but these errors were encountered: