Turning off piezo beeps during the ‘exit delay’ in ‘stay’ mode is not my preferred option, unfortunately, because it also turns off the beeps on ‘entry delay’. We’re forgetful enough about the house being armed at night around here, that we’d set off false alarms all the time were it not for those entry delay piezo beeps. Oh well. Perhaps I’ll think of another solution.
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).
Understood, I got myself into a real mess, as I was using the device instead of serviceID in the lua code and was trying out different variables. As there were instances of use of VendorStatus within the various posts within the the programming forum, I settled on it when it started to come together. learn a bit more each day.
Also, I’ve managed to capture the LuaUPnP.log when the mode changes from Powerlink to Stanndard. On this instance, it “looks like” the zwave network audit timed-out and the whole lua engine restarted and reloaded it self and lost the plot on the Powerlink mode. I’ve PM’d the log file to you.
I’m the owner of a PowerMax Pro with integrated PowerLink2.
I’m interested by an ZWave solution integrated to this great security system, and the PowerMax + Vera plugin seems to be a great solution (although “unsupported”).
Can the “real” PowerLink and the “fake” PowerLink work together at the same time ?
I would like to keep my PowerLink 2 but need to know (with the RS232 interface) the alarm panel status to e.g. turn off light when I’m leaving and arming.
I would like to keep my PowerLink 2 but need to know (with the RS232 interface) the alarm panel status to e.g. turn off light when I'm leaving and arming.
Ive done that exactly and more. One instance I had some issues with false alarms on a visonic detector, with the vera integration, I was able to pin-point what was the cause, before spending money on a replacement.
Teaching you to suck eggs here, once the powermax is integrated into vera, all of the detectors become part of vera’s triggers for scenes. You will not regret it.
Fellow Powermax’rs
Have any of you seen any issues or complications with sitting the vera next to the powermax panel under normal 24x365 use, given both devices are operating at 868Mhz. Generally usual advise for other radio based devices is to keep a min of 1meter distance.
Thanks for the new release, the devicelog now works under ie9 also.
I also appreciate the Zones tab in the main device. My Fire (brand) device shows up on Zonestab as a door/window. Should it appear as a smoke sensor or will you add a fire catagory in a next release?
Keypad-1 (2-way) and Siren-1 (PowerMax) appear in Vera in the Other Devices category-Tab. Can you make them appear in the Devices Security category-Tab?
@Mano I have the Vera and Powermax half a meter apart and not seen any trouble in communication.
That is strange… A smoke (fire) sensor should indeed end up in the smoke sensor category. Which zone is it and what is the type nr of the device (MCT-426?)?
You are correct I use a MCT302 connected to an external Fire dectector. On the PowerMax this MCT302 is configured as Zone Type Fire. This Setup works just like a real Visonic Fire detector, altough I don’t get battery updates from the real Fire detector but from the MCT302.
The Vera plugin detects the low level device ID and uses this to fill Zones Tab of PowerMax Alarm Device. MCT302 devices are listed by default as door/window Zones. When you turn off auto create devices on the settings Tab, you can configure every zone Manually.
Release r55 is available in the trunk. This has also been uploaded in the MiOS Marketplace as beta2. The wiki has been completely updated to reflect the current functionality.
@lolodomo: I’ve added 2 specific features on your request.
[ol][li]option to disable arm/disarm without a PIN[/li]
[li]option to display per sensor whether it is ‘armed live’[/li][/ol]
Other feedback and feature requests are always welcome.
[quote=“nlrb, post:411, topic:169028”]@lolodomo: I’ve added 2 specific features on your request.
[ol][li]option to disable arm/disarm without a PIN[/li]
[li]option to display per sensor whether it is ‘armed live’[/li][/ol][/quote]
What’s this second option exactly ?
I am still running the version 0.95 modified by myself to avoid having the plugin modifying the arm/disarm state of my sensors (arm/disarm of the sensors is managed by Vera scenes, not by the plugin).
I have to investiguate a little more but I think I have discovered a strange behaviour: when I open my door, the sensor is tripped twice very shortly.
Is the new version stable even for users without PowerLink module ?
The sensor ‘armed’ status is updated based on the partition status and sensor type. E.g. a fire sensor will always show armed, a PIR tagged ‘interior’ will only be armed when in ‘Armed Away’ mode, etc.
Don’t recognize that.
You don’t need a Powerlink module. The plugin simulates a Powerlink module. But the plugin can also run in ‘Standard’ mode, which is the same behavior as before (without all the fancy bells and whistles). Give it a try.
I just got my Ver2 updated to UI5 and installed the latest trunk (56) on this plug (using PowerMax+). I got it all up and running, can enroll as powerlink, all zones show up, I can arm-disarm etc. However, the status does not update on the panel or Partition 1 device etc. in Vera unless I “Reload” on the UI5 web page. It seems like this should be at least a bit more real-time than this. I wonder if my USB to serial adapter or it’s drivers (not an FTDI) are causing the issues.
Question is, how responsive are the statuses and other info updates when using the UI5 Vera web page and looking at the devices?
It seems that within an hour (30-45 minutes) of the Vera being powered up and/or Luup being started, the communications between Powerlink+ and Vera2 are in real-time. Odd that the Mode status says “standard” rather than Powerlink during these “good-comm” periods, and "Powerlink"upon new startup (or Luup re-start). It’s enrolled as a Powerlink and I’m getting no comm error on the Powerlink side of things.
Is this behavior odd or experienced by any of you?
@Robertyu: this behavior is odd. Status updates should be instantaneous and once in Powerlink mode it should stay in Powerlink mode. It only drops out of Powerlink mode in case the ‘alive’ messages from the Powerlink are not received anymore (they should occur every 30 secs.). Could you turn on plugin debugging and send me the LuaUPnP.log file?
Hello everyone…I am trying to integrate my Vera2 with PowerMax+ using this plugin. While doing that I am facing some issues and hope experts in this forum would provide some help.
I was following the plugin installation steps and reached to the point when it asks to Go to the ‘Settings’ tab of the panel and Select the serial port under ‘Communicate using UART’. The issue is that there is no ‘settings’ tab in the ‘Powermax Alarm Panel’ (I just get Control, Event Log and Advanced tabs). Could you please provide some pointers on what could I be missing.
Thanks for the pointer nlrb. I followed the steps as specified in WikiStart_old – Visonic Powermax Alarm Panel and got the zone devices created in Vera. However, in the Powermax+ panel, activating the Powerlink device is still failing. Also, I am still not able to see ‘settings’ tab in the ‘Powermax Alarm Panel’ in Vera (just Control, Event Log and Advanced tabs). While other zone devices do have settings tab.