-
Notifications
You must be signed in to change notification settings - Fork 96
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
Can i get some help #1
Comments
your other project ParadoxMulti-MQTT works just fine |
What Panel do you have? Can you enable full debug, including packet dumps? |
I am using a sp4000 I havent gotten around to debugging whats going on. will get back soon |
If you wish, provide a log here or by email. |
I think i see your problem, SP panels need to be authenticated through serial communication. |
Message 0x00 Command 0x00 : Initialize communication
|
Great find. The ops manual is available somewhere? |
SPXXXX-Serial-Port-Protocol.docx |
I dont know what will happen if you pass the connection as NEware and use I think this would be better as an everyday user would know his user code, but may not now the pc password (911 register password) |
I will try changing SerialInitialization byte(33) of message 0x5f to 0x05 NEware direct, and get back to you. |
Hi Maragelis, |
@SilviuMarchidanu what exactly do you mean by inverting. If you mean sending your own event using the paradox protocol thats easy, just use the above document. Where can I help you exactly. |
Have you managed to connect? |
@maragelis I have a new branch with many other states being reported and with authentication. |
Will try and get back to you. |
In one case, a password of 0000 required sending 0xaaaa. No idea why, but I still not analysed the issue properly. |
I have created a new issue to deal with the authentication |
Home Assistant auto-discovery - set "code required" flags to false - Fix tests
I have got to a point where I am getting this error :
2018-04-30 18:30:33,697 - INFO - PAI - Starting Paradox Alarm Interface
2018-04-30 18:30:33,700 - INFO - PAI - Console Log level set to 20
2018-04-30 18:30:33,703 - INFO - PAI - Using MQTT Interface
2018-04-30 18:30:34,354 - INFO - PAI.mqtt_interface - MQTT Broker Connected
2018-04-30 18:30:35,304 - INFO - PAI - Using Serial Connection
2018-04-30 18:30:35,315 - INFO - PAI - Starting...
2018-04-30 18:30:35,322 - INFO - PAI.paradox - Connecting to panel
2018-04-30 18:30:35,650 - INFO - PAI.paradox - Connected!
2018-04-30 18:30:35,652 - INFO - PAI.paradox - Updating Labels from Panel
2018-04-30 18:30:35,759 - ERROR - PAI.paradox - Connect error
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/construct/lib/containers.py", line 100, in getattr
return self[name]
KeyError: 'data'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/pi/pai/paradox.py", line 73, in connect
self.update_labels()
File "/home/pi/pai/paradox.py", line 183, in update_labels
template=partition_template)
File "/home/pi/pai/paradox.py", line 247, in load_labels
payload = reply.fields.value.data
File "/usr/local/lib/python3.5/dist-packages/construct/lib/containers.py", line 102, in getattr
raise AttributeError(name)
AttributeError: data
2018-04-30 18:30:35,781 - ERROR - PAI - Unable to connect to alarm
2018-04-30 18:30:35,787 - INFO - PAI.mqtt_interface - MQTT Broker Disconnected
2018-04-30 18:30:36,803 - INFO - PAI - Good bye!
The text was updated successfully, but these errors were encountered: