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?
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).
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.
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 …
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
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?
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.