Plugin for Visonic Powermax Integration

Plugins & Plugin Development Unmaintained
381

Hi,

I am a new here and hope to get some help. I Have a PowerMax Pro Partion and a Vera3. To connect the PowerMax I use a FTDI USB RS232 device. The PowerMax connects on this USB RS232 interface with PowerMax Remote Programmer Windows Software From Visonic and can be programmed without issues. So the cable works.

I tried to install the plug in. First I installed Plug In 0.95 available under apps.
When I open the PowerMax Alarm Panel Device, I see buttons and fields to give in settings.
When I enter my user code, I can Arm an Disarm. The connection is therefore OK.
I get no devices. See attached image: Plugin095.

So I decided to upgrade to the Trunk version 48, which gives version 1.0 Alpha. Nothing changes untill I enable “Automatically configure=yes”
Briefly I see the Powermax Alarm Panel Device display the right information.
See attached image: Paneltemp.

It then loads all the icons for all Visonic Senors/devices, which get the default look.
See attached image: Plugin100a.

If I open the Powermax Alarm Panel device, all settings on the control tab are gone.
See attached image: empty01.
On the PowerMax Pro I get a message BBA Com Lost message.

I have more details which will be added in my next post.

Mark

382

This is the second part of my message.

If I open the Powermax Alarm Panel advanced tab, I see it still contains details of my system.
See attached image: empty2.

I also made log files during the setup steps when I installed this device. The are:
powermax_pdu.txt
powermax_settings.txt

Any hints, what can I do?

Mark

383

Hi Mark,

With the 0.95 it is normal you don’t get any devices by default. You will have the specify the zone numbers in the variables DoorZones, MotionZones, SmokeZones.

For the version in the trunk: do you happen to have a Siren device? If so, you also need to upload the files of post #376.

Or maybe in your case the Keypad is the issue. If you email/PM me your LuaUPnP.log file I can take a look, or try ‘grep “^01” LuaUPnP.log’ and look for a clue.

384

Hi,

Thanks for the reply. Adding The Sirene device solved my issue. The BBA COM lost error disapeared from my PowerMax. Now all devices get the required icons. I only miss all the buttons eg for on and off. See attached picture nobuttons.

Mark

385

Hi again.

I just needed tot wait. I reloaded the VERA UI, the buttons are there! Thank you nlrb!

Mark

386

Nirb,
trunk 49, loaded on Xmas-eve has been stable.

  1. Reload now continues to read the panel after loading and Running the lua when Stay and Armed, where as before only worked in Stay.
  2. Have noticed the Alarm Panel, dropping from Powerlink mode back to Standard couple of times. Not sure of the impact this has as Alarm - Partition status is accurate.
  3. The event log on the shows Opening Event Log… forever on Firefox and Safari on the OS-X Mac 10.8 . It used to give problems on IE on Windows, however works fine under Firefox in Windows. I think utz did state its something to do with java. ?. Could the Panel event log also be displayed as that shows slightly more different info.

I’ll check if there is a pattern to (2) over the next few days. Other than that it all looks and runs good, including no additional load on the function of the vera.

yes, Major leap in functionality.

387

Hi mano, thanks again for testing.

This normally only happens when the ‘Keep alive’ messages are not sent anymore from the PM. This should not happen. I’m guessing this could happen after a download in Armed mode & with sync time on. But would need to check the logs.

This is a bug in the MCV firmware. I’ve got ticket 97199 open for this. I also have the problem with Firefox on Windows. Problem is that although they include the javascript in some fancy way into the HTML, the function can still not be resolved in the DOM.

My panel does not support this, only newer ones do. So I cannot check what it looks like and how the info can be retrieved. Same as multiple partition support.

388

Hi Nirb,
I’ll monitor this to see if there is a pattern,

This normally only happens when the 'Keep alive' messages are not sent anymore from the PM. This should not happen. I'm guessing this could happen after a download in Armed mode & with sync time on. But would need to check the logs.

I have only seen the panel_logs when using the Powermax_remote utility. Using this utility with a PC and then perform a upload from the alarm panel->PC, these logs become visible on couple of the tabs. When I get a bit of quite time, I’ll perform a capture of the RS232 comms, if it will help.

389

Hi,

I had the same problem but on FireFox on the Windows platform: it took forever to show the log file or didn’t show at all. The javascript file had some old code in it. Did some small changes to the javascipt J_Powermax.js eg reactivated the update button. It now works under Windows with Firefox for me. Under IE it still doesnt work.

Mark

390

Hi Mark,

Thanks a lot for the fix! So the “” was creating the problem… this has been in there for ages… Note that the pincode field is still needed in Standard mode.

The correct version is now be available in r50.

391

Nrlb,

Will you also add the siren files to the Trunk? It is usefull to have a complete package in the Trunk.

Mark

392

Hi Mark, No. These files are part of the firmware - not the plugin.

The latest version of the plugin will check if the xml files are there. If not, the siren will not be created. So the plugin will work without the files. People that cannot wait for the next official release can ask MCV for the beta firmware.

393

I just installed version 50 and it seems to be working well in Powerlink mode, but I have the following issues/questions (none of them are big deals for me, just minor annoyances):

  1. My wired zone 29 (motion detector) is not being created. If I add it manually, it just disappears after a reload. The logs seem to indicate that events are being received from zone 29, but since there’s no corresponding device, I can’t make use of them.

  2. I can’t permanently delete any automatically-created devices, since they come back after a reload. I’m not sure too many people would need to do this, and they’re easy enough to hide. In my case, I want to delete a number of X10 devices I’ve defined in Powermax. The X10 devices at issue are actually Insteon lights that I’m having Powermax trigger upon certain events. I’m using altsteon to control the Insteon lights in Vera, however, making the corresponding Powermax-created X10 devices redundant with (and inferior to) my altsteon-based Insteon devices. Of course, I suppose the real work around would be to set up Vera to trigger all of my lighting events instead of Powermax, but I’m lazy.

  3. Is there any way to quick arm in home/stay mode? I want to auto arm my home at, say, midnight, but don’t want to deal with the piezzo beeps.

  4. Did I miss it, or is there no easy way to disarm from a scene? On the other hand, I suppose it was useful to learn a little bit about luup code. In case anyone is trying to disarm from a scene, this is the luup code I used:

local lul_arguments = {} lul_arguments["State"] = "Disarmed" lul_resultcode, lul_resultstring, lul_job, lul_returnarguments = luup.call_action("urn:micasaverde-com:serviceId:AlarmPartition2","RequestArmMode",lul_arguments,105)

(105 is the device number of the partition device, not the panel)

394

I just figured out that what I really mean is that I want to “skip exit delay”. I can do this with my keyfob by configuring the AUX button on the keyfob to correspond to “skip exit delay.” Then, by pressing the AUX button during the exit delay, it will skip the rest of the exit delay.

Is it possible to create a function that allows me to send the “skip exit delay” command using luup code? Of course, even better would be a special control/button that arms in home mode and sends the skip exit delay command a second later.

Let me know if there’s anything I can do to help support this feature. The feature is almost worth enough to me to figure out how to hack something up, but if someone with more familiarity with the code knows how to do this pretty quickly, I’d be very grateful.

395

You first need to set the ‘AutoCreate’ variable to ‘0’ before editing the zone strings. Then you can add ‘Z29’.

Yes, you can. But do set the ‘AutoCreate’ variable to ‘0’ first.

No, I haven’t found a way to do that. All you can do is turn them off in the panel setting (see section 4.4.10). Normally you arm ‘Stay’ at night, so you can set the option not have the beeps for ‘Stay’.

This is relatively easy. Just go to the ‘Advanced’ tab when creating a scene, select the partition and set ‘RequestArmMode’ to ‘Disarm’.

396

Hi Guys,

This plugin is really fantastic … thank for this !

I’ve installed the latest R50 on my Vera 2 and it’s working pretty well except for 2 things:

  • Fire Detector are not tripped in the Vera when I press the test button (of course it’s working on the PowerMax itself)
  • I have wired 1 Motion Detector in Zone Z29 which is not auto created by the plugin

Some info on my systems:

  • Vera 2 with FW 1.5.532

  • Plugin info:
    Version:1.0 alpha
    Mode:Powerlink
    Panel type:PowerMax Pro Part
    Panel name:PowerMax 4_81
    Serial: xxx-removed-xxx
    Eprom:J-700857 C15.015
    Software:JS702063 C15.013

Any help you can provide will be highly appreciated !
Thanks

397

Could you check in the LuaUPnP.log that the sensor is tripped? For me that works fine and I also get the notification of a fire alarm.

I’ve checked the ‘D_SmokeSensor1.json’ file (which is part of the firmware) and it seems to be missing the following.

"state_icons":[ "Motion_Sensor_0.png", "Motion_Sensor_100.png" ],
This is probably why you don't see the sensor changing. You should file a bug with MCV for that (and have them change the icon to 'SmokeSensor.png' as well plus create a tripped version of the SmokeSensor icon).

See the post above. First set ‘AutoCreate’ to ‘0’ and then add ‘Z29’ to the ‘MotionZones’ variable.

398

Z29 is working with manua creation - Thanks fort this
I will open a ticket with MCV for the icons

399

Nlrb, the VendorStatus variable, has an additional space with the "Disarmed " value when a _get is used. eg…
– local alarmstatus = luup.variable_get(“urn:micasaverde-com:serviceId:AlarmPartition2”, “VendorStatus”, 63)
I was testing for if alarmstatus == “Disarmed” and was failing until a length check showed up the error. Not sure, where the extra space is being introduced.
Had a look at the History Event Log and Panel Event Log on the Remote Powermax control program, History is 250 lines long where as Panel is 100. The Panel log includes additional details such as when the panel is enters into Installer mode and both logs gets filled when the upload command is initiated. Checked this out on a “RF broken” Powermax Pro of 4 years of age. I’ll do a check on my current working box, soon as I get some time. It may be… its NOT worth pursuing this any further for the info it gives.

400

[quote=“mano, post:399, topic:169028”]Nlrb, the VendorStatus variable, has an additional space with the "Disarmed " value when a _get is used. eg…
– local alarmstatus = luup.variable_get(“urn:micasaverde-com:serviceId:AlarmPartition2”, “VendorStatus”, 63)
I was testing for if alarmstatus == “Disarmed” and was failing until a length check showed up the error. Not sure, where the extra space is being introduced.[/quote]This is correct - there is an extra space as the status flags are added to the ‘VendorStatus’ variable (has always been like this).

To check the armed status you should use ‘ArmMode’ (= [Disarmed|Armed]) or ‘ArmModeNum’ (= [0|1]). If it is ‘Armed’ (or 1) this means it is not disarmed (i.e. can be Stay, StayInstant etc.).

Or you can use the detailed arm mode ‘DetailedArmMode’ (= [Disarmed|Armed|ArmedInstant|Stay|StayInstant|Force|Ready|NotReady|EntryDelay|ExitDelay]). These are the same for any alarm panel (not vendor specific).