Maybe you should add some info in the wiki about manual and automatic enrollment of the Powerlink.
Correct me if I’m wrong, but isn’t this about rigth?:
On the older software versions of the Powermax the powerlink enrollment needs to be done manually on the Powermax.
So if you don’t enroll the Powerlink on the Powermax the plugin will operate in standard mode, and if enrolled in powerlink mode.
On the newer software versions of the Powermax the powerlink enrollment is automatic, and the plugin should only operate in powerlink mode(if enrollment is successful).
nirb, I have some lua scripts, which work off the various powermax devices, hence the revert to 0.95 . I’ve just enabled the debug and captured the details. Did not auto discover and populate or give the alarm panel details. Still in Standard mode.
Changed the pin to XX XX.
uptill - 21:16, just enabled the serial port and reloaded.
after 21:17 , tried option to auto-discover and create
at 21:19 tried to disarm/arm sequence - seemed to ignore commands.
@audunv: thanks, will add that to the wiki. @mano: thanks for the logs, will have a more detailed look at it tonight. You have the exact same version as audunv, but still yours behaves differently… Looks like enrollment is OK, but it doesn’t go into download mode.
nirb, loaded 43 this morning.
06:54 with Autoconfig Yes and Debug On for the PDU came up as standard with Powerlink not enrolled.
06:57 set Autoconfig to default, Powerlink mode for a little while on status, Auto discovery of devices, some of the found panels were default.
Then it looks like everything locked up, Movement detectors not registering on Vera any movements,
connection mode blank, details on Alarm Panel blank.
Reload vera, with Autoconfig in various states no luck.
Reset Powermax - Installer and exit, no luck.
Will PM the debug file
@mano: not sure if you got my email, but let me comment on your findings.
[ul][li]The AutoConfig setting has no influence on the communication flow. Only thing it controls is whether the …Zones & Devices variables are overwritten with the devices we find in the settings.[/li]
[li]If the communication stops completely, then there are two possible causes.[/li]
[list]
[li]The plugin has crashed. To find this out we have to look in the LuaUPnP.log file. The powermax_pdu.txt file won’t show this. Try ‘grep “^01” LuaUPnP.log’ or ‘grep -i powermax LuaPnP.log’.[/li]
[li]The UART interface is malfunctioning. Experience shows that PL2303 can be less reliable than the FTDI ones, so make sure you have the latter. Communication has become more complex, so even if it did not give issues before, it might now.[/li]
[/list][/ul]
Other thing I’ve noticed that if you have a dual RS232 interface and another device is downloading info from the PowerMax, the download mode will not be possible on the Powerlink connection.
nirb, sent an email lastnight with all the details of failure on both modes of failues with all the traces…
exract–
Enclosed 2 files.
1st is the trace of Lua and powermax, when I initially loaded the device
with Debug and AutoConfigure = default. Came up as standard and panel
started troubling. file=43-debug-default-discovery
reset all and the 2nd trace
Initially, Debug and Autodiscovery = yes, comes up as standard, does not
auto configure/populate. Once stabilized changed the AutoConfigure to
default and save/reload. The mode enters into Powerlink, starts to
auto-populate with the powermax devices, default icon and locks up.
file=43-debug-2
The USB is a ftdi device, a little bit complex in setup. As the panel and
Vera are 10 meters apart, the two are linked by couple of ZIGBEE modules to
replace the RS232 cable.
From the alarm Panel, 3.3V TTL Rs232 signals go straight into a ZIGBEE
XBEE module, set at 9600Baud full duplex mode over the air to its partner
ZIGBEE module connected at 3.3V TTL to a ftdi USB device into the back of
the vera. Works very well, into the Vera and also, when shifted to the PC
using the powermax remote software no issues of any sort with re-transmit
or dropped packets. I am using the sparkfun adapters.
I’ve sent the full trace on both tests I did, just in case there may be
some more clues.
I’ll pm this again, or put the files in a place for you to pick up.
@mano: don’t know what goes wrong with your email ???. Did not get the log file and am sure the file I’ve sent is OK. I’ve now also checked it into the trunk, so you can get it there as well.
nirb: Just loaded what was in trunk.
1)Report of :Plugin Not correctly installed does not happen.
2) Just enabled Debug mode and Save/Reload.
Goes through, Standard then Powerlink mode and starts to perform Download…
Vera Goes to busy mode and then the newly populated icon’s are default and Movement detection not registering.
just about to send you the three trace files
-rw-r–r-- 1 root root 410563 Dec 12 22:02 LuaUPnP.log
-rw-r–r-- 1 root root 33825 Dec 12 21:49 powermax_pdu.txt
-rw-r–r-- 1 root root 12361 Dec 12 21:49 powermax_settings.txt
@mano: thanks. The logs confirm that we have fixed the main issue (download mode not starting). The remaining issue is easy to fix - will do that tonight. Can you please confirm that you did not enter the panel installer menu on the panel manually? There is a A7 message with system reset and I need to know that this happened because of the auto enrollment and not a manual action.
nirb:Definatly confirm, I did not touch the Powermax panel to go into Installer mode. Loaded the plugin, set the serial port and Debug, and hit Save and watched it perform the auto download.
Is it possible to trigger the alarm powermax?
I would use detectors z-wave door with my alarm.
I tried to create a scene in advanced tab with a status RequestPanicMode. But it does not work.
Do you know how?
No, unfortunately this is not possible today with the PowerMax. We have not yet found a way to create an alarm via the serial interface (e.g. panic, fire etc.).
In the meantime version 48 is available in the trunk. This one even works for mano :D. Thanks to him for putting so much debugging time in! @audunv: would it be possible to check if this version is still OK for you as well?
The latest version has a new variable called ‘ForceStandard’, as explained on the wiki.
For people trying the trunk code with the latest official Firmware: you might have a problem with the Siren, as the Siren device is not available in 1.5.408. You need to have a beta FW to have these. As a workaround, the files are attached to this post.
[quote=“nlrb, post:376, topic:169028”]In the meantime version 48 is available in the trunk. This one even works for mano :D. Thanks to him for putting so much debugging time in! @audunv: would it be possible to check if this version is still OK for you as well?
The latest version has a new variable called ‘ForceStandard’, as explained on the wiki.[/quote]
I have installed the latest version and can confirm that it’s still working great.
I was wondering why the event log tab only works in Firefox and not in Chrome og IE?
[quote=“audunv, post:378, topic:169028”][quote=“nlrb, post:376, topic:169028”]In the meantime version 48 is available in the trunk. This one even works for mano :D. Thanks to him for putting so much debugging time in! @audunv: would it be possible to check if this version is still OK for you as well?
The latest version has a new variable called ‘ForceStandard’, as explained on the wiki.[/quote]
I have installed the latest version and can confirm that it’s still working great.
I was wondering why the event log tab only works in Firefox and not in Chrome og IE?[/quote]
There is something special to do for IE. @nirb: if you have not yet done, please check how I modified the call_action function in the Sonos plugin.
What problem do you have with the EventLog? Do you only see ‘Opening eventLogTab…’? Since recently I have this problem (both on IE and Firefox), so cannot check that functionality. A support call is open for this @MCV.