Plugin version 1.1 available in the Marketplace

Apps & Remote Access Unmaintained
1

An updated version of the code is available in the trunk for testing.

Main changes are:

[ul][li]new event log interface, incl. partition info[/li]
[li]added web handlers for retrieving log files[/li]
[li]improved support for wired zones[/li]
[li]improved message handling, incl. variable length[/li]
[li]added handling of 25 and B0 message[/li]
[li]support for multiple panels[/li]
[li]generate crash log file in case of crash[/li]
[li]show which user is being called[/li][/ul]

Log files will now be prefixed with the device id (e.g. 123_powermax_pdu.txt). The variable ‘EventLog’ is no longer used.

The following web handlers can be called to retrieve log files. Examples are for device id 123.

[ul][li]http://<vera_ip>/port_3480/data_request?id=lr_GetLuaLogFile[/li]
[li]http://<vera_ip>/port_3480/data_request?id=lr_GetPduLogFile123[/li]
[li]http://<vera_ip>/port_3480/data_request?id=lr_GetSettingsFile123[/li]
[li]http://<vera_ip>/port_3480/data_request?id=lr_GetCrashFile123[/li][/ul]

2

Great nlrb!

I will test it as soon as possible…

There has been some hickups for me aswell…(lost communication, unresposive Vera GUI). But I think the relate to a faulty/corrupted USB memory plugged in for datamine and error-logging. Sometimes my mount went readonly and this eventually caused all kind of strange things to happen…

3

Interesting… I’ve had similar problems with an USB stick going into read-only mode (also using dataMine). Hence I updated the PowerMax plugin code in 1.0 to handle this correctly (it would crash before).

4

Ok, great that you have spotted this aswell… and fixed the crash-behavior.

It seems to be some hokus going on when vera mounts its logging partition. Mine re-mounted sometimes without reboot (as /dev/sbb1 och /dev/sbc1) leaving everything in a mess. Tried to analyze the vera mounting scripts but they are not that intuitive…to say the least…

5

Two new devices popped up (Z29,Z30) after updating. Utility Room (Non Alarm), Hall (Non Alarm)

Are they the hard wired zones? I have actually never used them… possible to disable?

6

They should only pop up if they are enrolled on the panel. Can you check zone 29,30 enrollment?

7

Just had chance to test 1.1. Wired zones now working.

Many thanks

8

Ok, have read through the manual now. Only wireless zones can be enrolled/deleted. The wired zones (29,30) seems to be permanent but can have different types
Interior, Perimeter, … Fire, Non-alarm.
Non-alarm seems to be default and I have never changed it.

If zone 29/30 is of type Non-alarm they should probably not auto-create devices. But maybe I’ve missed something?

9

Where did you find this in the manual (I could not find it)? On a PowerMax Pro you can disable them by selecting enroll->sensor->zone nr->29->off.

Even if a zone is ‘non-alarm’ it will be shown as it is active (just will never generate an alarm).

10

You can find it here:

http://download.homesecuritystore.com/downloadmanual.aspx?FileName=powermaxplus_im.pdf

11

To be clearer: I did find/read the manual, but could not find back what you claim. Did you try it out in practice? The PowerMax Pro manual also talks only about enrolling wireless sensors, but the procedure works for wired zones as well.

12

Ok, have tried to remove it now. But no luck. I cannot even select zone 29/30 during enrollment.

Maybe there is a difference between Powermax+ and PowerMax Pro.

Hmm… maybe the easiest thing is to set “Auto-create devices” to Off and remove the devices.

13

Or you set the hidden/invisible property of the device in Vera.

14

One of my door sensors act as a smoke sensor in the plugin? Is this a known issue? It auto-discovers it like this. I also deleted it and after auto-discover it does recognize it as smoke sensor again. I checked the powermax and it’s programmed as a door/window sensor, like another door that is configured the same but shows right as door sensor in the plugin. Please assist.

15

Please mail me the powermax_settings file and the zone number you’re referring to.

16

Maybe silly, but where van I find the file? Thanks for your help! :slight_smile:

EDIT:
I tested another door sensor and it works well, so I suppose this specific sensor (old Powermax sensor from BT (British Telecom) makes this strange action? If you let me know howto get the settings file ?'ll reproduce the bug and mail it to you.

17

@ansandro: see the first message of this post.

For the settings file use http://<vera_ip>/port_3480/data_request?id=lr_GetSettingsLogFile123 (replace 123 by the device id of the PowerMax panel plugin id).