Plugin for Visonic Powermax Integration

masterscot · December 8, 2011, 3:11pm

Anybody know why this code isn’t working in a scene?
The idea is to stop disarming the alarm when it’s already in the ‘Disarmed’ state.

local alarm_status = luup.variable_get(“urn:micasaverde-com:serviceId:AlarmPanel1”, “AlarmStatus”, 51)

if (alarm_status == “Disarmed”) then
return false
end

return true

utz · December 8, 2011, 5:31pm

Did you look at the logfile to see what the error output is (just by looking at it I do not see the error (but I am not a lua programmer))

anker · December 9, 2011, 7:49am

Maybe you need a break statement. I am not a programmer, but I do think that your code always returns true…

Ref manual: Lua 5.1 Reference Manual

Search for “break” within a for structure.

ajlennon · December 9, 2011, 8:39am

I would log the value of the variable you are setting with luup.log(“xx”)

Then what exactly is the difference between a return value of true and of false? What should occur based on those return values. You could add a couple more logging statements to check what you are returning

masterscot · December 9, 2011, 8:50am

There is nothing in the logs, seems the scene with the Lua code in it is completed successfully.
I will try the tips you both gave. Thanks!

Regards,
Ms

lolodomo · December 13, 2011, 8:59pm

Hi utz.

Do you plan to upgrade to UI5 and update your plugin accordingly ?
Does somean already check if the current version is working with UI5 ?

Regards

utz · December 14, 2011, 12:19am

[quote=“lolodomo, post:126, topic:169028”]Hi utz.

Do you plan to upgrade to UI5 and update your plugin accordingly ?
Does somean already check if the current version is working with UI5 ?

Regards[/quote]
i have a vera2 with ui4. If i am able to update to ui5 i will adapt the plugin as well. Currently i have no means to test ui5 (is it available for upgrade?)

ajlennon · December 14, 2011, 9:36am

Currently i have no means to test ui5 (is it available for upgrade?

Yes, it’s on the firmware upgrade page. I’d make sure you have a good backup first though utz

lolodomo · December 22, 2011, 9:32pm

Hi

[quote=“utz, post:96, topic:169028”]I added support for the AUX button on the powermax keyfob. This allows you to use the button with the “*” to control devices/scenes in vera. This feature is currently added to version 0.72 in the svn trunk.

To use this you need to configure the powermax such that pressing of the AUX button is directed to the PGM output (see powermax manual). You can then define that with each AUX button press the state is toggled.

In the powermax device you have to add to the variable altid the PGM; for example: “Z01,Z02,Z03,Z11,PGM”. This will then create a PGM device similar to the zone devices that represents the button on the keyfob. When you press aux the red man comes on; second press and it goes away. The PGM device can then be used for scenes (e.g. switch light on/off).[/quote]

On MCT237 remote control, there are two AUX buttons: AUX A and AUX B. Do you know if there is a way to create two separate PGM devices ?
I imagine the answer is no as there is probably only one PGM output in the Powermax ?

utz · December 23, 2011, 8:27am

On MCT237 remote control, there are two AUX buttons: AUX A and AUX B. Do you know if there is a way to create two separate PGM devices ? I imagine the answer is no as there is probably only one PGM output in the Powermax ?

The Powermax+ I have only has keyfobs with one button. The powermaxpro that has a different keyfob with more buttons but I cant test this one. In the manual it says you can program 4 different functions on the two buttons (status, instant, skip exit, pgm). PGM produces a message on the serial port (can be found in the pdu logfile); if any of the other functions produces a distinct message as well then it can be done and we can have 2 buttons. But I am not sure if status produces a message (I think not) and instant/skip produces the same message used for general arming so we would not know it was the button.

mano · January 7, 2012, 3:01pm

Hi utz and fellow PowermaxPro to Vera2 (UI5) experts,
Just got my Vera2 working on UI5, (absolute novice) and exploring the level of automation that can be performed including integration into Visonic PowermaxPro. I’ve come to a total halt on trying to get the Powerlink enrolled on the panel to the Vera2.
I’ve loaded the pluggin and followed utz’s instructions and cannot get beyond the enroll on my panel. The panel is on V4.2.20 (2yearsold), with Dual RS232 module. It works fine on both ports to a laptop via a ftdi-USB adapter.
When the USB cable is moved to the Vera2, it recognises it as ftdi_sio and I can associate the Powermax Alarm Panel in the Serial Port Config.
The LED’s on the FTDI adapter, just flashes momenterely.
What can I do next ? Plse suggest.

utz · January 7, 2012, 5:43pm

[quote=“mano, post:131, topic:169028”]Hi utz and fellow PowermaxPro to Vera2 (UI5) experts,
Just got my Vera2 working on UI5, (absolute novice) and exploring the level of automation that can be performed including integration into Visonic PowermaxPro. I’ve come to a total halt on trying to get the Powerlink enrolled on the panel to the Vera2.
I’ve loaded the pluggin and followed utz’s instructions and cannot get beyond the enroll on my panel. The panel is on V4.2.20 (2yearsold), with Dual RS232 module. It works fine on both ports to a laptop via a ftdi-USB adapter.
When the USB cable is moved to the Vera2, it recognises it as ftdi_sio and I can associate the Powermax Alarm Panel in the Serial Port Config.
The LED’s on the FTDI adapter, just flashes momenterely.
What can I do next ? Plse suggest.[/quote]

Seems to me the serial communication is ok. To find out what is not working

Look at the file I_Powermax.xml at the line “LOG_DEBUG = false” and change this to “LOG_DEBUG = true”. After change you may have to upload the file again. Now we should get some information that may help us debug
ssh to vera and enable debugging by typing “VerboseLogging.sh enable”
go to directory /var/log/cmh/ (Here is the file LuaUPnP.log which contains debug information)
type “tail -f LuaUPnP.log | grep POWERMAX”. Now when you do any action with the powermax we should see some output that may help us to figure out what goes wrong. For example, you could restart the UI which should initiate communication and we can see what is going on.

mano · January 8, 2012, 2:03pm

Utz,
Grateful for responding so quick. Anyhow, when I looked into the I_powermax.xml for the LOG_DEBUG = false statement could not find it in the installed files. Looked a bit lacking detail when compared to the files in the 0.7 tags folder.
So I unistalled the app in UI5 and re-instlled as per UI4. Followed set up as UI4, enrolled powerlink on Alarm Panel and its working now. And when I look at the I_Powermax.xml on Vera its a lot fuller in content and the LOG_DEBUG statement is there after the ripout and reinstall using the UI4 steps. Strange.

Next steps,
I want to read through the posts on how to using schedule
a) Disarm/Home with PIN through the scheduler.
b) Send X10 via this interface into the AlarmPanel to control existing X10 devices, while I save up to migrate to Zwave devices.

Eventlog tab just continues show, Opening Event bar, its not grabing the event log. Need to look through the posts on hints.
Brilliant piece of code and Vera 2. I getting close to replacing the faithful Homevision, which has been perfect for the last 15odd years.

Nearly forgot, I clicked on one of the Zones, where the ARM/BYPASS buttons were the same LIGHT_BLUE colour. Now one of them is Dark Blue. Should I click on Arm button to ensure they are enabled ?

utz · January 8, 2012, 8:46pm

I have not used UI5 so I do not know what the powermax UI5 app is like or which version it is. I am a bit afraid of moving to UI5 as there seem to be a number of smaller issues. There is a version 7.3 which is in the trunk directory. You could install that version it should be running ok.

Next steps, I want to read through the posts on how to using schedule a) Disarm/Home with PIN through the scheduler. b) Send X10 via this interface into the AlarmPanel to control existing X10 devices, while I save up to migrate to Zwave devices.

a) is possible. I use scenes as well to arm the system.
b) is not possible. We had to figure out the powermax protocol and the protocol elements regarding X10 are still not known. We would need someone with a powerlink device sending these commands to the powermax and then intercepting what is on the serial line. As I do not own a powerlink I cant do this myself (The powerlink is a £200 rubbish alternative to vera and I am not buying it for testing).

Eventlog tab just continues show, Opening Event bar, its not grabing the event log. Need to look through the posts on hints.

A known UI4 problem with js tabs. Just click on the tab once then move to another tab and when you click on it a second time it should work

Brilliant piece of code and Vera 2. I getting close to replacing the faithful Homevision, which has been perfect for the last 15odd years.

Nearly forgot, I clicked on one of the Zones, where the ARM/BYPASS buttons were the same LIGHT_BLUE colour. Now one of them is Dark Blue. Should I click on Arm button to ensure they are enabled ?

The Arm/BYPASS is only important when you use the sensor as input in a scene. Are they blue in UI5?

mano · January 8, 2012, 9:50pm

a) is possible. I use scenes as well to arm the system.

Would really appreciate the snippet of code for the schedule for Arm/Disarm, as I still trying to read and figure out when the call is made, which of the D_Po* I_Po* files are utilised as the function call

On X10:
I was hoping, well I will just have to wait for someone to crack this or, wait for the european version of the Insteon USB powerline adapter to be available. (2012)

A known UI4 problem with js tabs. Just click on the tab once then move to another tab and when you click on it a second time it should work

As I am still getting to grips with using Vera, I'll have a go at 7.3 as, the event_tab still continues not to work, regardless of toggling. [Opening eventLogTab...] may be 7.3 will sort it.

The Arm/BYPASS is only important when you use the sensor as input in a scene. Are they blue in UI5?

The ARM/Bypass are Blue.

mano · January 19, 2012, 7:27am

Hi,
Given up, any help on luup code to arm/disarm the Powermax in a scene or schedule.
Tried various combinations cannot crack it.

Looks like I have to drop back to UI4, as the event log view tab does not work even on the latest version from the trunk.

Also, getting my hands on a Powerlink2. May be I’ll see if I can capture the RS232 codes for X10 manipulation.

utz · January 19, 2012, 8:01am

[quote=“mano, post:136, topic:169028”]Hi,
Given up, any help on luup code to arm/disarm the Powermax in a scene or schedule.[/quote]
would be something like this (not tested)

lul_arguments = {}
partition_dev = 15
lul_arguments[“State”]=“Armed” – could be Armed, Disarmed, Stay
lul_arguments[“PINCode”]=“1111”
luup.call_action(“urn:schemas-micasaverde-com:service:AlarmPartition2”, “RequestArmMode”, lul_arguments , partition_dev)

Looks like I have to drop back to UI4, as the event log view tab does not work even on the latest version from the trunk.

I have not tried UI5 now, there seems to be too much trouble.

Also, getting my hands on a Powerlink2. May be I'll see if I can capture the RS232 codes for X10 manipulation.

That would be good …

mano · January 21, 2012, 5:51pm

Utz.
Thanks for the help, I’ve dropped back to UI4, tried your latest code 0.73, dropped back to 0.727 now on 0.73. The Event Log is displaying as enclosed. The text field for PIN and Update buttons are not shown at all as per your install instructions.

On the scene code to turn the Powermax t Stay/Disarm this is the debug output from the Lu*log…

0801/21/12 15:55:21.665JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=5 <0x2c0c>
0801/21/12 15:55:21.666Scene::RunScene running 5 ttt <0x2c0c>
0801/21/12 15:55:21.667JobHandler_LuaUPnP::HandleActionRequest device: 9 service: urn:schemas-micasaverde-com:service:AlarmPartition2 action: RequestArmMode <0x2c0c>
0801/21/12 15:55:21.667JobHandler_LuaUPnP::HandleActionRequest argument State=Stay <0x2c0c>
0801/21/12 15:55:21.668JobHandler_LuaUPnP::HandleActionRequest argument PINCode=1234 <0x2c0c>
0101/21/12 15:55:21.668JobHandler_LuaUPnP::HandleActionRequest can’t find urn:schemas-micasaverde-com:service:AlarmPartition2 <0x2c0c>
5001/21/12 15:55:25.019luup_log:8: POWERMAX: sending ACK PDU to panel: 0D A2 00 00 00 00 00 00 00 00 00 00 43 1A 0A <0x402>
5001/21/12 15:55:25.022luup_log:8: POWERMAX: PDU sent 0D A2 00 00 00 00 00 00 00 00 00 00 43 1A 0A <0x402>

So I changed the call to

luup.call_action(“urn:micasaverde-com:serviceId:AlarmPartition2”, “RequestArmMode”, lul_arguments , partition_dev)

and now it works a treat.

I should get hold of the powerlink2 unit next week, and over the weekend I’ll try and get the X10 traces.

mano · January 23, 2012, 5:07pm

Reloaded all from Scratch from Trunk, the Event Log works on 0.73, after trying the click on the tab Once and Somewhere else

mano · January 23, 2012, 5:16pm

Further on the EventLog. It seems it only works with Firefox with the tab flick as suggested by utz. Tried the same with IE9 and Chrome and does not work at all. Frustrating waste of time with IE and Chrome, another lesson to chisel in.