Plugin for Visonic Powermax Integration

Verbose logging can be enabled on command line (something like “verboselogging enable”). There is as well a button in the UI.

Did you configure your powermax to have a powerlink attached? There is a menu you can go in and then you have to add the powerlink and the powermax will make an awful beep to confirm. Maybe that is missing?

See:

[quote=“mcvflorin, post:11, topic:168478”]You must enable Verbose Logging first with the following command:
[tt]VerboseLogging enable[/tt]

And disable it after finishing:
[tt]VerboseLogging disable[/tt][/quote]

I have the PowerLink install on the other port but I did disconnect it which did not make any difference. However, I tried to enable PowerLink on the front panel (looong bee) and got the following message:

50 08/03/11 15:14:20.857 luup_log:21: POWERMAX: 0D received from panel <0x4011>
50 08/03/11 15:14:20.858 luup_log:21: POWERMAX: start of new PDU detected <0x4011>
50 08/03/11 15:14:20.859 luup_log:21: POWERMAX: F1 received from panel <0x4011>
50 08/03/11 15:14:20.860 luup_log:21: POWERMAX: unknown PDU of type F1 detected <0x4011>
50 08/03/11 15:14:20.862 luup_log:21: POWERMAX: 07 received from panel <0x4011>
50 08/03/11 15:14:20.863 luup_log:21: POWERMAX: 43 received from panel <0x4011>
50 08/03/11 15:14:20.865 luup_log:21: POWERMAX: 00 received from panel <0x4011>
50 08/03/11 15:14:20.867 luup_log:21: POWERMAX: 00 received from panel <0x4011>
50 08/03/11 15:14:20.869 luup_log:21: POWERMAX: 8B received from panel <0x4011>
50 08/03/11 15:14:20.871 luup_log:21: POWERMAX: 56 received from panel <0x4011>
50 08/03/11 15:14:20.872 luup_log:21: POWERMAX: 0A received from panel <0x4011>
02 08/03/11 15:14:22.019 ZW_Send_Data node 17 NO ROUTE (nil) <0xc04>
50 08/03/11 15:14:23.019 luup_log:21: POWERMAX: no zone Z05 <0x402>
50 08/03/11 15:14:23.023 luup_log:21: POWERMAX: no zone Z09 <0x402>
50 08/03/11 15:14:23.027 luup_log:21: POWERMAX: no zone Z13 <0x402>
50 08/03/11 15:14:23.029 luup_log:21: POWERMAX: no zone Z14 <0x402>
50 08/03/11 15:14:23.031 luup_log:21: POWERMAX: no zone Z15 <0x402>
50 08/03/11 15:14:23.033 luup_log:21: POWERMAX: no zone Z16 <0x402>
50 08/03/11 15:14:23.034 luup_log:21: POWERMAX: no zone Z17 <0x402>
50 08/03/11 15:14:23.037 luup_log:21: POWERMAX: no zone Z18 <0x402>
50 08/03/11 15:14:23.038 luup_log:21: POWERMAX: no zone Z19 <0x402>
50 08/03/11 15:14:23.042 luup_log:21: POWERMAX: no zone Z22 <0x402>
50 08/03/11 15:14:23.043 luup_log:21: POWERMAX: no zone Z23 <0x402>
50 08/03/11 15:14:23.047 luup_log:21: POWERMAX: no zone Z26 <0x402>
50 08/03/11 15:14:23.049 luup_log:21: POWERMAX: no zone Z27 <0x402>
50 08/03/11 15:14:23.051 luup_log:21: POWERMAX: no zone Z29 <0x402>
50 08/03/11 15:14:23.053 luup_log:21: POWERMAX: no zone Z30 <0x402>
02 08/03/11 15:14:25.529 UPnPCallbackEventHandler 4 start PIDLOG2 21231 <0x240a>
02 08/03/11 15:14:25.538 UPnPCallbackEventHandler 4 start PIDLOG2 21230 <0x2009>
02 08/03/11 15:14:25.548 UPnPCallbackEventHandler 4 start PIDLOG2 21231 <0x240a>
02 08/03/11 15:14:25.557 UPnPCallbackEventHandler 4 start PIDLOG2 21230 <0x2009>
02 08/03/11 15:14:25.567 UPnPCallbackEventHandler 4 start PIDLOG2 21231 <0x240a>
02 08/03/11 15:14:25.578 UPnPCallbackEventHandler 4 start PIDLOG2 21230 <0x2009>
02 08/03/11 15:14:25.588 UPnPCallbackEventHandler 4 start PIDLOG2 21231 <0x240a>
02 08/03/11 15:14:25.598 UPnPCallbackEventHandler 4 start PIDLOG2 21230 <0x2009>
02 08/03/11 15:14:25.608 UPnPCallbackEventHandler 4 start PIDLOG2 21231 <0x240a>
02 08/03/11 15:14:25.624 UPnPCallbackEventHandler 4 start PIDLOG2 21230 <0x2009>
50 08/03/11 15:14:41.764 luup_log:21: POWERMAX: 0D received from panel <0x4011>
50 08/03/11 15:14:41.766 luup_log:21: POWERMAX: start of new PDU detected <0x4011>
50 08/03/11 15:14:41.767 luup_log:21: POWERMAX: F1 received from panel <0x4011>
50 08/03/11 15:14:41.768 luup_log:21: POWERMAX: unknown PDU of type F1 detected <0x4011>
50 08/03/11 15:14:41.770 luup_log:21: POWERMAX: 07 received from panel <0x4011>
50 08/03/11 15:14:41.771 luup_log:21: POWERMAX: 43 received from panel <0x4011>
50 08/03/11 15:14:41.773 luup_log:21: POWERMAX: 00 received from panel <0x4011>
50 08/03/11 15:14:41.776 luup_log:21: POWERMAX: 00 received from panel <0x4011>
50 08/03/11 15:14:41.777 luup_log:21: POWERMAX: 8B received from panel <0x4011>
50 08/03/11 15:14:41.779 luup_log:21: POWERMAX: 56 received from panel <0x4011>
50 08/03/11 15:14:41.780 luup_log:21: POWERMAX: 0A received from panel <0x4011>
02 08/03/11 15:14:45.307 UPnPCallbackEventHandler 4 start PIDLOG2 21231 <0x240a>
02 08/03/11 15:14:45.310 UPnPCallbackEventHandler 4 start PIDLOG2 21230 <0x2009>
02 08/03/11 15:14:45.313 UPnPCallbackEventHandler 4 start PIDLOG2 21230 <0x2009>
02 08/03/11 15:14:45.317 UPnPCallbackEventHandler 4 start PIDLOG2 21230 <0x2009>
02 08/03/11 15:14:45.320 UPnPCallbackEventHandler 4 start PIDLOG2 21230 <0x2009>
02 08/03/11 15:14:45.314 UPnPCallbackEventHandler 4 start PIDLOG2 21231 <0x240a>
02 08/03/11 15:14:47.463 ZWaveSerial::GetFrame 0x7f3ff758 timed out now 0 m_listGetFramePending 0 <0xc04>

Ok, what you see there is a message of form 0D F1 07 43 00 00 8B 56 0A coming in. My software does not understand this message of type F1 (the first byte after 0D is the message type) and therefore ignores it. The powermax repeats this message later again because it did not get an ACK message. After 4 repetitions the powermax will think there is no powerlink and all stops. I assume the F1 message is a hello and I have to put it in my code to respond (thats only a few lines). I can do that Thursday night but not right now.

What you can try now is to reload the UI again so that vera sends a hello again from that side (maybe the powermax believes the powerlink is there even without the ack).

Its close, we should get it working …

Ok, I had a few minutes idle here at work so I updated the code in the earlier post. It should now understand that F1 message and send an ACK. The only update is to the I_Powermax.xml file which you need to upload.

Sorry but I do not see the file?

its reply 7 on this thread, a zip file at the end. You need to login otherwise you cant see attachments. BTW, better to upload all three files it contains …

Thank you for your effort! I found the files thanks - just getting a bit slow on my old days…

Got the following message:

02 08/03/11 16:03:56.176 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:03:56.185 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:03:56.194 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:03:56.206 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:03:56.215 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:03:56.224 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:03:56.234 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:03:56.245 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
50 08/03/11 16:03:56.251 luup_log:21: POWERMAX: start of new PDU detected <0x4011>
50 08/03/11 16:03:56.253 luup_log:21: POWERMAX: start of AB PDU detected, expected length 15 <0x4011>
02 08/03/11 16:03:56.258 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
50 08/03/11 16:03:56.267 luup_log:21: POWERMAX: PDU received 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A <0x4011>
02 08/03/11 16:03:56.271 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
50 08/03/11 16:03:56.274 luup_log:21: POWERMAX: sending ACK PDU to panel <0x4011>
50 08/03/11 16:04:03.401 luup_log:21: POWERMAX: start of new PDU detected <0x4011>
50 08/03/11 16:04:03.402 luup_log:21: POWERMAX: start of A5 PDU detected, expected length 15 <0x4011>
50 08/03/11 16:04:03.415 luup_log:21: POWERMAX: PDU received 0D A5 00 02 08 00 00 00 00 00 00 00 43 0D 0A <0x4011>
50 08/03/11 16:04:03.419 luup_log:21: POWERMAX: sending ACK PDU to panel <0x4011>
50 08/03/11 16:04:03.441 luup_log:21: POWERMAX: start of new PDU detected <0x4011>
50 08/03/11 16:04:03.442 luup_log:21: POWERMAX: start of A5 PDU detected, expected length 15 <0x4011>
50 08/03/11 16:04:03.456 luup_log:21: POWERMAX: PDU received 0D A5 00 04 00 20 04 03 00 01 00 00 43 EA 0A <0x4011>
50 08/03/11 16:04:03.460 luup_log:21: POWERMAX: sending ACK PDU to panel <0x4011>
50 08/03/11 16:04:03.462 luup_log:21: POWERMAX: Open Event in Zone 4 Detected <0x4011>
06 08/03/11 16:04:03.464 Device_Variable::m_szValue_set device: 21 service: urn:viewsonic-com:serviceId:AlarmStatus1 variable: AlarmMessage was: EMPTY now: Open Zone 4 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x4011>
06 08/03/11 16:04:03.511 Device_Variable::m_szValue_set device: 25 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: EMPTY now: 1 #hooks: 0 upnp: 0 v:0x87ae88/NONE duplicate:0 <0x4011>
06 08/03/11 16:04:03.516 Device_Variable::m_szValue_set device: 25 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTrip was: EMPTY now: 1312380243 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x4011>
50 08/03/11 16:04:05.741 luup_log:21: POWERMAX: start of new PDU detected <0x4011>
50 08/03/11 16:04:05.743 luup_log:21: POWERMAX: start of A5 PDU detected, expected length 15 <0x4011>
50 08/03/11 16:04:05.757 luup_log:21: POWERMAX: PDU received 0D A5 00 02 00 00 00 00 00 00 00 00 43 15 0A <0x4011>
50 08/03/11 16:04:05.761 luup_log:21: POWERMAX: sending ACK PDU to panel <0x4011>
50 08/03/11 16:04:05.781 luup_log:21: POWERMAX: start of new PDU detected <0x4011>
50 08/03/11 16:04:05.782 luup_log:21: POWERMAX: start of A5 PDU detected, expected length 15 <0x4011>
50 08/03/11 16:04:05.797 luup_log:21: POWERMAX: PDU received 0D A5 00 04 00 21 04 04 00 01 00 00 43 E8 0A <0x4011>
50 08/03/11 16:04:05.801 luup_log:21: POWERMAX: sending ACK PDU to panel <0x4011>
50 08/03/11 16:04:05.803 luup_log:21: POWERMAX: Close Event in Zone 4 Detected <0x4011>
06 08/03/11 16:04:05.804 Device_Variable::m_szValue_set device: 21 service: urn:viewsonic-com:serviceId:AlarmStatus1 variable: AlarmMessage was: Open Zone 4 now: Close Zone 4 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x4011>
06 08/03/11 16:04:05.851 Device_Variable::m_szValue_set device: 25 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 1 now: 0 #hooks: 0 upnp: 0 v:0x87ae88/NONE duplicate:0 <0x4011>
02 08/03/11 16:04:15.127 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:15.132 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:15.134 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:15.137 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:15.139 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:15.130 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:16.151 ZWJob_SendData UPDATE MANUAL ROUTE 8=(nil) <0x803>
02 08/03/11 16:04:16.155 UPDATE MANUAL ROUTE2 8=(nil) <0xc04>
02 08/03/11 16:04:16.156 ZW_Send_Data node 8 NO ROUTE (nil) <0xc04>
04 08/03/11 16:04:16.473 <0x803>
02 08/03/11 16:04:26.012 ZW_Send_Data node 6 NO ROUTE (nil) <0xc04>
04 08/03/11 16:04:26.174 <0x803>
50 08/03/11 16:04:26.249 luup_log:21: POWERMAX: start of new PDU detected <0x4011>
50 08/03/11 16:04:26.251 luup_log:21: POWERMAX: start of AB PDU detected, expected length 15 <0x4011>
02 08/03/11 16:04:26.276 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:26.284 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
50 08/03/11 16:04:26.290 luup_log:21: POWERMAX: PDU received 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A <0x4011>
50 08/03/11 16:04:26.295 luup_log:21: POWERMAX: sending ACK PDU to panel <0x4011>
02 08/03/11 16:04:26.299 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:26.302 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:26.304 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:26.307 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:26.309 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:26.527 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:26.534 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:26.544 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:26.554 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:26.565 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:26.579 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:26.584 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:26.594 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:30.141 UPnPCallbackEventHandler 6 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:36.140 UPnPCallbackEventHandler 6 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:43.018 UPnPCallbackEventHandler 7 start PIDLOG2 1652 <0x300d>
02 08/03/11 16:04:56.022 ZW_Send_Data node 7 NO ROUTE (nil) <0xc04>
04 08/03/11 16:04:56.183 <0x803>
50 08/03/11 16:04:56.249 luup_log:21: POWERMAX: start of new PDU detected <0x4011>
50 08/03/11 16:04:56.250 luup_log:21: POWERMAX: start of AB PDU detected, expected length 15 <0x4011>
50 08/03/11 16:04:56.291 luup_log:21: POWERMAX: PDU received 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A <0x4011>
50 08/03/11 16:04:56.295 luup_log:21: POWERMAX: sending ACK PDU to panel <0x4011>
02 08/03/11 16:04:56.608 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:56.616 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:56.626 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:56.636 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:56.646 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:56.656 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:56.666 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:56.676 UPnPCallbackEventHandler 4 start PIDLOG2 1648 <0x2009>
02 08/03/11 16:04:56.686 UPnPCallbackEventHandler 4 start PIDLOG2 1649 <0x240a>
02 08/03/11 16:04:56.696 UPnPCallbackEventHandler 4 start PIDLOG2 1648

and the newly created powerlink_pdu file:

root@MiOS:/tmp/log/cmh# tail -f powermax_pdu.txt
2011-08-03 16:00:55 1312380055 0D A5 00 07 00 00 00 00 00 33 00 00 43 DC 0A
2011-08-03 16:00:55 1312380055 0D A5 00 08 00 00 00 00 00 00 00 00 43 0F 0A
2011-08-03 16:00:55 1312380055 0D A5 00 09 00 00 00 00 00 00 00 00 43 0E 0A
2011-08-03 16:00:55 1312380055 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:00:55 1312380055 0D A7 01 00 00 60 00 00 00 00 00 00 43 B3 0A
2011-08-03 16:01:25 1312380085 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:01:55 1312380115 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:02:27 1312380147 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:02:56 1312380176 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:03:26 1312380206 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:03:56 1312380236 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:04:03 1312380243 0D A5 00 02 08 00 00 00 00 00 00 00 43 0D 0A
2011-08-03 16:04:03 1312380243 0D A5 00 04 00 20 04 03 00 01 00 00 43 EA 0A
2011-08-03 16:04:05 1312380245 0D A5 00 02 00 00 00 00 00 00 00 00 43 15 0A
2011-08-03 16:04:05 1312380245 0D A5 00 04 00 21 04 04 00 01 00 00 43 E8 0A
2011-08-03 16:04:26 1312380266 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:04:56 1312380296 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:05:26 1312380326 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:05:56 1312380356 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:06:26 1312380386 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:06:56 1312380416 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:07:26 1312380446 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A
2011-08-03 16:07:45 1312380465 0D A5 00 02 00 00 00 00 00 00 00 00 43 15 0A
2011-08-03 16:07:56 1312380476 0D AB 03 00 1E 00 34 34 32 30 00 00 43 25 0A

that looks in principle as it should be. You get quite a lot of these AB messages which I do not get on my system. The interesting messages are the A5 and A7 messages which contain sensor information and panel sate updates.

I concentrated on the little man who I thought should change color when something happened (which is not the case or it change instantly in which case I just don’t see the change) Anyway, the panel shows that zone 4 is opened which was the door I used as a test case so somethings go through. Now I just have to figure how to use it in a trigger. See picture attached

It works!!! The man turns red :o Thanks a lot Utz damn good work!!!

good to hear. I am sure you will discover soon that there is lots of room for improvement. Let me know if you see features that should be implemented and if I find time I will do that then …

There seems to be a minor issue. I can not get motion sensors to trigger events but door switches work OK. The difference seems to be the variables for example:

The door switch has variable

Armed
Tripped
Last Tripped

Where the motion sensor has the variables:
Armed
LastTrip
MotionSensor

Is there something wrong or is it as it should be?

Ups the other file…

Both types of sensor work the same. You should be able to write a scene with the event “A sensor (door, motion, …) is tripped”.

I use the variable MovementSensor to record which zones are actually movement detectors as I have to disable them after a timeout (door sensors send an open event and later a close event; motion detectors only send close but there is no corresponding open)

OK - however, when the motion sensor trigger (red light on sensor lights up) the little man in the VERA panel doesn’t turn red - which i presume is a prerequisite for using the sensor as a trigger?

The red man should turn on if there is movement.
If you stand in front of the movement detector and the red light goes on you should find the following line in the logfile:

POWERMAX: Movement Event in Zone XXX Detected

If this is not the case we have to look into the file powermax_pdu to see if there was a message that indicated movement at the time and I just did not interpret it correctly.

this should work, that is what i am using here all the time at home.

This is the trace:

50 08/03/11 22:51:44.185 luup_log:21: POWERMAX: PDU received 0D A5 00 04 00 25 06 05 00 01 08 00 43 D9 0A <0x3c10>
50 08/03/11 22:51:44.189 luup_log:21: POWERMAX: sending ACK PDU to panel <0x3c10>
50 08/03/11 22:51:44.191 luup_log:21: POWERMAX: Movement Event in Zone 6 Detected <0x3c10>
06 08/03/11 22:51:44.192 Device_Variable::m_szValue_set device: 21 service: urn:viewsonic-com:serviceId:AlarmStatus1 variable: AlarmMessage was: Movement Zone 10 now: Movement Zone 6 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x3c10>
06 08/03/11 22:51:44.195 Device_Variable::m_szValue_set device: 26 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTrip was: 1312404034 now: 1312404704 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x3c10>
06 08/03/11 22:51:44.196 Device_Variable::m_szValue_set device: 26 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: MovementSensor was: 1 now: 1 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1

and the powermax_pdu

root@MiOS:/tmp/log/cmh# tail -f powermax_pdu.txt
2011-08-03 22:27:06 1312403226 0D A5 00 02 00 00 00 00 00 00 00 00 43 15 0A
2011-08-03 22:27:59 1312403279 0D A5 00 02 00 00 00 00 00 00 00 00 43 15 0A
2011-08-03 22:30:31 1312403431 0D A5 00 02 00 00 00 00 00 00 00 00 43 15 0A
2011-08-03 22:36:02 1312403762 0D A5 00 02 00 00 00 00 00 00 00 00 43 15 0A
2011-08-03 22:37:14 1312403834 0D A5 00 02 00 00 00 00 00 00 00 00 43 15 0A
2011-08-03 22:40:34 1312404034 0D A5 00 04 00 25 06 05 00 01 08 00 43 D9 0A
2011-08-03 22:40:46 1312404046 0D A5 00 04 00 25 0C 05 00 01 08 00 43 D3 0A
2011-08-03 22:40:48 1312404048 0D A5 00 04 00 25 0A 05 00 01 08 00 43 D5 0A
2011-08-03 22:41:44 1312404104 0D A5 00 02 00 00 00 00 00 00 00 00 43 15 0A
2011-08-03 22:50:00 1312404600 0D A5 00 02 00 00 00 00 00 00 00 00 43 15 0A
2011-08-03 22:51:44 1312404704 0D A5 00 04 00 25 06 05 00 01 08 00 43 D9 0A

Do you see anything wrong?

looks good

it finds a movement event in zone 6 at 22:51:44.191

the corresponding message from the panel for this is:
0D A5 00 04 00 25 06 05 00 01 08 00 43 D9 0A

normally the 25 in this line should be a 21 but this probably means you have currently a tamper alarm (or alarm in memory) but that does not matter.

Is there further down in the logfile a line like this:
POWERMAX: unable to locate device Z06

do you have a device Z06 in the UI ?

Z06 was the sensor that I triggered and intent to use as trigger in the scene that doesn’t work. No lines with error on Z06?