-
Notifications
You must be signed in to change notification settings - Fork 14
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
Issue arming and disarming panel from Home Assistant #36
Comments
Please change line 155 in TotalConnectClient.py to |
That should be all one line of code |
I apologize for the slow response. I was having some difficulty with it initially for some reason (it wasn't displaying the response code). It worked this time.
|
I just realized I posted that from /var/log/messages. Here is the result from home-assistant.log (a bit cleaner):
|
@ratsputin do you have a lyric controller security panel? |
@uchagani Nope. It's a Vista-21IP with cellular and Internet access. I believe this used to work in the 0.8x versions of Home Assistant. |
The response -4114 is not covered by our current code, so @ratsputin is hitting the Exception at line 155. |
@ratsputin please try one more time for me. Change line 155 to the below and try again.
The ResultData is essentially an error message coming from Total Connect. It will hopefully explain what -4114 means. |
@austinmroczek Thank you so much for following up on this. I think this is going to clarify the issue:
So, that actually gave me something to go from. I just checked my TC 2.0 app and it was set to prompt me for my User ID. I disabled that and it seems to be working better, although interestingly that didn't affect how the app behaves on the phone--it still prompts me. I need to do some further testing as there appears to be a communication problem with my panel; however, it looks like this may have been the root cause of the issue. I can't really test this further until I address the comm problem but I am no longer getting the -4114 error since I disabled prompting in my profile. |
Okay, I straightened out the communication problem with my panel. It turned out to be a bad Ethernet cable. Things are working much better now. I did some further troubleshooting and am able to reliably reproduce (and eliminate) the -4114 result code. It appears to be the result of the profile setting "Prompt for user code" in the TC 2.0 app on the "My Profile" page. If I turn that field on and save my profile, attempting to arm (or disarm) the panel from Home Assistant will give the -4114 error. Turning it back off makes the error go away. Thank you so much for working with me on this. I don't know if you plan to make a code change and need my assistance testing or not. I'll leave this open if you do, otherwise, feel free to close this ticket. Kind regards, Brett |
That makes sense. We don't require a code to disarm/arm so if the profile
expects a code then it will fail. Personally I created a profile just for
home assistant that I use in HA.
…On Sat, May 18, 2019 at 6:41 PM ratsputin ***@***.***> wrote:
Okay, I straightened out the communication problem with my panel. It
turned out to be a bad Ethernet cable. Things are working much better now.
I did some further troubleshooting and am able to reliably reproduce (and
eliminate) the -4114 result code. It appears to be the result of the
profile setting "Prompt for user code" in the TC 2.0 app on the "My
Profile" page. If I turn that field on and save my profile, attempting to
arm (or disarm) the panel from Home Assistant will give the -4114 error.
Turning it back off makes the error go away.
Thank you so much for working with me on this. I don't know if you plan to
make a code change and need my assistance testing or not. I'll leave this
open if you do, otherwise, feel free to close this ticket.
Kind regards,
Brett
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#36?email_source=notifications&email_token=AAIBHEBNGOXWWRP725QMPE3PWCA2JA5CNFSM4HL5IPRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVWXHXY#issuecomment-493712351>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIBHEBGKYJUDDOWXSYEWETPWCA2JANCNFSM4HL5IPRA>
.
|
I don't recall explicitly setting it to prompt so I'm guessing this was a feature added to the TC 2.0 client sometime in the last 3-4 months. That would have been the last time I tried (and succeeded) arming the system from HA. |
#39 will help us diagnose similar issues more quickly in the future. |
I posted this issue over in Home Assistant and it was suggested this may be an issue with the total connect client. I think this was working correctly in the home assistant v80-v89, but it seems it broke around v90 (I didn't previously use this very much).
If I attempt to make a call to arm the panel from the UI or from an HA service call, I get the following error:
The suggestion was made that I run test.py; here are the results from that run:
I have a Vista-21IP panel and the Total Connect 2.0 client works fine. Do you think this is an issue with this client or HA calling it?
I should note that communications are just fine. HA always accurately knows the state of the panel and responds appropriately. It just can't arm the panel.
The text was updated successfully, but these errors were encountered: