Tertiush / ParadoxIP150v2

Python-based IP150 'middle-ware' that uses the IP module's software port for monitoring and control of the alarm via an MQTT Broker.
Eclipse Public License 1.0
73 stars 35 forks source link

SP6000 Panel Control - Disarm/Arm #18

Open psyciknz opened 6 years ago

psyciknz commented 6 years ago

Here's the debug log when attempting to disarm Partition 1. Looks like the command is being accepted.

2017-08-31 10:21:17,086 DEBUG 0->
2017-08-31 10:21:20,339 DEBUG 0->
2017-08-31 10:21:23,593 DEBUG 0->
2017-08-31 10:21:26,845 DEBUG 0->
2017-08-31 10:21:30,098 DEBUG 0->
2017-08-31 10:21:33,350 DEBUG 0->
2017-08-31 10:21:36,604 DEBUG 0->
2017-08-31 10:21:38,863 INFO MQTT Message: Paradox/C/P1 disarm
2017-08-31 10:21:38,865 INFO Alarm control partition: 1
2017-08-31 10:21:38,865 INFO Alarm control state: disarm
2017-08-31 10:21:39,857 DEBUG 0->
2017-08-31 10:21:41,858 INFO State04: Alarm Control Action: Alarm loging and starting events
2017-08-31 10:21:41,859 INFO Logging into alarm system...
2017-08-31 10:21:42,109 INFO Login to alarm panel successful
2017-08-31 10:21:44,114 INFO Sending Alarm Control: Partition: 1, State: disarm
2017-08-31 10:21:44,114 INFO Sending generic Alarm Control: Partition: 1, State: DISARM
2017-08-31 10:21:44,115 INFO Control message: @
2017-08-31 10:21:44,115 DEBUG 64->   0xaa 0x25 0x0 0x4 0x8 0x0 0x0 0x14 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x40 0x0 0x5 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x45 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee
2017-08-31 10:21:44,365 DEBUG 53<-   0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x70 0x0 0x10 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x80
2017-08-31 10:21:44,366 INFO State04:Listening for events...
PuTTY2017-08-31 10:21:45,617 DEBUG 0->
2017-08-31 10:21:48,872 DEBUG 0->
2017-08-31 10:21:52,125 DEBUG 0->
2017-08-31 10:21:55,379 DEBUG 0->
2017-08-31 10:21:58,632 DEBUG 0->
2017-08-31 10:22:01,885 DEBUG 0->
2017-08-31 10:22:05,138 DEBUG 0->
2017-08-31 10:22:08,393 DEBUG 0->
Tertiush commented 6 years ago

I see a difference between my MG5050 and your alarm's response for the same packet:

Command (same - disarm): 0xaa 0x25 0x0 0x4 0x8 0x0 0x0 0x14 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x40 0x0 0x5 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x45 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee

Reply (note 0x42 0x0 0x5): 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x42 0x0 0x5 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x47

Try the following. Stop the script and login to the web console. Once logged in start the script and then try to arm/disarm. I've heard this working for some, it might allude to something else wrong in the script. Worth a shot to try and get to the bottom of this.

Tertiush commented 6 years ago

Also see: https://github.com/Tertiush/ParadoxIP150v2/issues/8

psyciknz commented 6 years ago

I'll give that a go

psyciknz commented 6 years ago

Being logged in seemed to work. Not sure how readable this will be, but here's the log outut.

2017-09-04 17:15:54,673 DEBUG 53<-   0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x1 0xc 0x0 0x0 0x0 0x0 0x0 0x0 0x4d 0x61 0x69 0x6e 0x20 0x64 0x6f 0x6f 0x72 0x20 0x50 0x49 0x52 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0x4
2017-09-04 17:15:54,673 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x1 0xc 0x0 0x0 0x0 0x0 0x0 0x0 0x4d 0x61 0x69 0x6e 0x20 0x64 0x6f 0x6f 0x72 0x20 0x50 0x49 0x52 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0x4
2017-09-04 17:15:55,925 DEBUG 0->
2017-09-04 17:15:57,200 DEBUG 53<-   0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x0 0xc 0x0 0x0 0x0 0x0 0x0 0x0 0x4d 0x61 0x69 0x6e 0x20 0x64 0x6f 0x6f 0x72 0x20 0x50 0x49 0x52 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0x3
2017-09-04 17:15:57,201 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x0 0xc 0x0 0x0 0x0 0x0 0x0 0x0 0x4d 0x61 0x69 0x6e 0x20 0x64 0x6f 0x6f 0x72 0x20 0x50 0x49 0x52 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0x3
2017-09-04 17:15:58,452 DEBUG 0->
2017-09-04 17:16:01,706 DEBUG 0->
2017-09-04 17:16:04,958 DEBUG 0->
2017-09-04 17:16:08,210 DEBUG 0->
2017-09-04 17:16:09,057 INFO MQTT Message: Paradox/C/P1 Arm
2017-09-04 17:16:09,057 INFO Alarm control partition: 1
2017-09-04 17:16:09,057 INFO Alarm control state: Arm
2017-09-04 17:16:10,213 INFO State04: Alarm Control Action: Alarm loging and starting events
2017-09-04 17:16:10,213 INFO Logging into alarm system...
2017-09-04 17:16:10,463 INFO Login to alarm panel successful
2017-09-04 17:16:12,467 INFO Sending Alarm Control: Partition: 1, State: Arm
2017-09-04 17:16:12,467 INFO Sending generic Alarm Control: Partition: 1, State: ARM
2017-09-04 17:16:12,467 INFO Control message: @
2017-09-04 17:16:12,468 DEBUG 64->   0xaa 0x25 0x0 0x4 0x8 0x0 0x0 0x14 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x40 0x0 0x4 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x44 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee
2017-09-04 17:16:12,718 DEBUG 53<-   0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x41 0x0 0x4 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x45
2017-09-04 17:16:12,718 INFO State04:Listening for events...
2017-09-04 17:16:13,970 DEBUG 0->
2017-09-04 17:16:13,970 DEBUG 212<-   0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0xe 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0x4f 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x3 0x2 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x38 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x8 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0x49 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x9 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0x4a
2017-09-04 17:16:13,971 DEBUG Multiple data: ['\xe1\x14\x11\t\x04\x11\x0f\x02\t\x00\x00\x00\x00\x00\x02     Area 1     \x00\x00\x00\x00\x00J', '\xe1\x14\x11\t\x04\x11\x0f\x02\x08\x00\x00\x00\x00\x00\x02     Area 1     \x00\x00\x00\x00\x00I', '\xe1\x14\x11\t\x04\x11\x0f\x03\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x008', '\xe1\x14\x11\t\x04\x11\x0f\x02\x0e\x00\x00\x00\x00\x00\x02     Area 1     \x00\x00\x00\x00\x00O']
2017-09-04 17:16:13,971 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x9 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0x4a
2017-09-04 17:16:13,971 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x8 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0x49
2017-09-04 17:16:13,971 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x3 0x2 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x38
2017-09-04 17:16:13,971 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0xe 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0x4f
2017-09-04 17:16:15,223 DEBUG 0->
2017-09-04 17:16:16,333 DEBUG 53<-   0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0xb 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0xc 0x0 0x0 0x0 0x0 0x58
2017-09-04 17:16:16,334 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0xb 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0xc 0x0 0x0 0x0 0x0 0x58
2017-09-04 17:16:17,585 DEBUG 0->
2017-09-04 17:16:17,586 DEBUG 265<-   0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x3 0x3 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xc 0x0 0x0 0x0 0x0 0x45 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x8 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0xc 0x0 0x0 0x0 0x0 0x55 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x9 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0xc 0x0 0x0 0x0 0x0 0x56 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x8 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0xc 0x0 0x0 0x0 0x0 0x55 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x9 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0xc 0x0 0x0 0x0 0x0 0x56
2017-09-04 17:16:17,586 DEBUG Multiple data: ['\xe1\x14\x11\t\x04\x11\x0f\x02\t\x00\x00\x00\x00\x00\x02     Area 1     \x0c\x00\x00\x00\x00V', '\xe1\x14\x11\t\x04\x11\x0f\x02\x08\x00\x00\x00\x00\x00\x02     Area 1     \x0c\x00\x00\x00\x00U', '\xe1\x14\x11\t\x04\x11\x0f\x02\t\x00\x00\x00\x00\x00\x02     Area 1     \x0c\x00\x00\x00\x00V', '\xe1\x14\x11\t\x04\x11\x0f\x02\x08\x00\x00\x00\x00\x00\x02     Area 1     \x0c\x00\x00\x00\x00U', '\xe1\x14\x11\t\x04\x11\x0f\x03\x03\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0c\x00\x00\x00\x00E']
2017-09-04 17:16:17,586 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x9 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0xc 0x0 0x0 0x0 0x0 0x56
2017-09-04 17:16:17,586 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x8 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0xc 0x0 0x0 0x0 0x0 0x55
2017-09-04 17:16:17,586 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x9 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0xc 0x0 0x0 0x0 0x0 0x56
2017-09-04 17:16:17,587 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x2 0x8 0x0 0x0 0x0 0x0 0x0 0x2 0x20 0x20 0x20 0x20 0x20 0x41 0x72 0x65 0x61 0x20 0x31 0x20 0x20 0x20 0x20 0x20 0xc 0x0 0x0 0x0 0x0 0x55
2017-09-04 17:16:17,587 DEBUG Event data: 0xe1 0x14 0x11 0x9 0x4 0x11 0xf 0x3 0x3 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0xc 0x0 0x0 0x0 0x0 0x45
psyciknz commented 6 years ago

So I think you linked to the 53 response before which should be thins entry from my log: 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x41 0x0 0x4 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x45

The two from above: Command (same - disarm): 0xaa 0x25 0x0 0x4 0x8 0x0 0x0 0x14 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x40 0x0 0x5 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x45 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xee

Reply (note 0x42 0x0 0x5): 0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0x42 0x0 0x5 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x47

Tertiush commented 6 years ago

Interesting, not sure how to proceed though... In another post I thought of combining the v1 and v2 code (leveraging v1's web login), but that just seems very cumbersome, and also I only have an MG panel to test with so it will be very "hit and miss"...

psyciknz commented 6 years ago

So do we think that there's some flag being set in the web ui that is not being set with our use of the software port?

I don't have winload nor a prt3 for serial communication, and I was never able to figure out the codes in the ParadoxMap by using babyware and wireshark.

I wonder if the dotNet SDK would yeild any results on what is being passed to the module.

psyciknz commented 6 years ago

Ok, So I had some code that uses the api, and it actually connects and receives events (very similar ot the script).

Would it be useful if I connected and let events come back and wireshark the interactions? Then we can see if they match what is posted, and from there we can look at the arm/disarm code.

Attached should be a really short capture of an already connected panel, where I think zone 12 opens and closes Paradox_Poss_zone12_openclose.zip

This should theoretically match up to this somehow - but I'm not sure I see it:

2017-09-06 07:36:07,282 DEBUG 53<-   0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe0 0x14 0x11 0x9 0x6 0x7 0x23 **0x1** _0xc_ 0x0 0x0 0x0 0x0 0x0 0x0 **0x4d 0x61 0x69 0x6e 0x20 0x64 0x6f 0x6f 0x72 0x20** 0x50 0x49 0x52 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0xf
2017-09-06 07:36:07,282 DEBUG Event data: 0xe0 0x14 0x11 0x9 0x6 0x7 0x23 0x1 0xc 0x0 0x0 0x0 0x0 0x0 0x0 0x4d 0x61 0x69 0x6e 0x20 0x64 0x6f 0x6f 0x72 0x20 0x50 0x49 0x52 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0xf
2017-09-06 07:36:07,283 DEBUG Event: "Main door PIR"
2017-09-06 07:36:07,283 INFO Publishing event "Paradox/Zone" for Main door PIR =  ON
2017-09-06 07:36:07,284 DEBUG Event:Zone open;SubEvent:Zone 12
2017-09-06 07:36:08,538 DEBUG 0->
2017-09-06 07:36:08,828 DEBUG 53<-   0xaa 0x25 0x0 0x2 0x72 0x0 0x0 0x0 0x0 0xee 0xee 0xee 0xee 0xee 0xee 0xee 0xe0 0x14 0x11 0x9 0x6 0x7 0x23 0x0 0xc 0x0 0x0 0x0 0x0 0x0 0x0 0x4d 0x61 0x69 0x6e 0x20 0x64 0x6f 0x6f 0x72 0x20 0x50 0x49 0x52 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0xe
2017-09-06 07:36:08,828 DEBUG Event data: 0xe0 0x14 0x11 0x9 0x6 0x7 0x23 0x0 0xc 0x0 0x0 0x0 0x0 0x0 0x0 0x4d 0x61 0x69 0x6e 0x20 0x64 0x6f 0x6f 0x72 0x20 0x50 0x49 0x52 0x20 0x20 0x20 0x0 0x0 0x0 0x0 0x0 0xe
2017-09-06 07:36:08,828 DEBUG Event: "Main door PIR"
2017-09-06 07:36:08,828 INFO Publishing event "Paradox/Zone" for Main door PIR =  OFF
2017-09-06 07:36:08,829 DEBUG Event:Zone OK;SubEvent:Zone 12

In the wireshark I've only got return communication from the panel to my machine. And I can see the 0xaa 0x25 0x0 0x2 but then it's always 0x33 rather than 0x72. And I'm not sure there in these debug strings from the script where the zone number appears. I think IIRC the 0x4d 0x61 onwards etc is "Main Door" And the bold 0x01 is that it's ON, but I think the zone number is the italics?

Was there some encyption is part of their protocol?

Tertiush commented 6 years ago

Sorry for the delay, was away on business, going to be next week as well....

I had a look at the zip file, but the contents of the data in the steam appears to be encrypted. I think the SDK encrypts by default so there's no way we can really use it to decode any data.

The only way would be to download winload and disable the encryption flag (in its COM.ini file), then wireshark the link whilst you do a arm/disarm. We can then look at what is being sent and figure out the issue.

psyciknz commented 6 years ago

Hmm winload doesn't seem to know what an IP connection is. It's all modem based.

psyciknz commented 6 years ago

I notice the messages being sent to the panel is "@" - is that consistent with yours?

Tertiush commented 6 years ago

In winload the IP connection is in another tab, next to the modem connection. Once the new alarm/panel is created there's a drop-down on the right top of the page. Select IP there.

I haven't noticed any @ signs. Most transfers are not ASCII, so I only really look at the hex.

psyciknz commented 6 years ago

Yeah I saw that. But under the connection methods it only lists modems/gprs modems which are all COM based.

I've actually managed to do everything I need with a c# sharp based program using their sdk.

I managed to figure out the arm and disarm commands today.

Unfortunate to moved away from the python solution though. So I should keep plugging away. Also what the sdk has shown me is that the panel quite often posts a ready, or armed status. So if the script misses the arming command, there's a periodic reporting of the area status.

psyciknz commented 6 years ago

I finally got winload to run. So when i get a chance I'll wireshark an arm or disarm.

maragelis commented 6 years ago

Tried it today the script works ok with the SP6000 except for control. Checking the control section it is sending correct data I think it has to do with the PCpassword. I will try resetting it to 0000 and try again

psyciknz commented 6 years ago

Get anywhere on this? When you talk about resetting the password do you mean in the script, or actually in the IP150- module?

maragelis commented 6 years ago

No actually gave up on it. I was talking about the 911 register on the panel it’s self. That register is whats used to authenticate winload and other devices connected to the panel. I use it to authenticate through uart connection.

psyciknz commented 6 years ago

Yeah I wonder what in the set up communication is the pc password and panel id. In wireshark I can see the ip modile password unencrypted, but can't see where these other values are. I wouldn't want to remove them from my panel (the 911 register etc)