Not sure how that would impact the drop-down list, but worth a try for people with the same issue.
Yes, I was quite surprised myself. But that is what did it for me (having had no luck for 3 hours before that, even with factory resets etc!).
Yes, that would indeed cause a problem! The PowerMax does not accept dates earlier than 2000. I'll add a check in the code to prevent syncing with an old date.
Great, thank you!
This is quite worrying... User [url=http://forum.micasaverde.com/index.php?action=profile;u=26187]mfp[/url] had the exact same problem. There is something in the start-up sequence that the PowerMax Pro Part model does not like and it gets in a wrong state. This will make it to send the '0D A5 0D 04 00' for 90 seconds after a start of the plugin. It starts doing this after the INIT command. That is why in the latest version (r57) I've stepped away from sending the INIT. What version are you using?
I am on r57 (earlier versions did not work at all with my Powermax in Powerlink mode [Standard mode is fine!]).
Could you please send me the following:
[ul][li]the L_Powermax.lua file you are using[/li]
[li]the LuaUPnP.log file (maybe it has a clue)[/li][/ul]
[/quote]
Sure, both files attached (while that dodgy serial communication is happening too…).
@stridger: the logs files don’t contain much info, only “Unhandled message A5”. This means that the plugin hasn’t started correctly. Probably the variable ‘CommExceptions’ contains a value. This happens after a number of communication problems (like e.g. CRC errors or other communication errors). The plugin then disables itself.
Can you do the following.
[ul][li]list which versions of the code you have used before r57[/li]
[li]empty variable ‘CommExceptions’ in the Advanced tab & save[/li]
[li]capture the LuaUPnP.log file and send it to me (don’t post it on the forum as it can contain sensitive info)[/li][/ul]
[ul][li]list which versions of the code you have used before r57[/li][/ul]
Since the last factory reset I’ve only used r57. Generally I had also tried the App Store version (worked fine) and r55 (didn’t work in Powerlink mode).
[ul][li]empty variable 'CommExceptions' in the Advanced tab & save[/li][/ul]
Done. I have then also rebooted the system, as it didn’t seem to be able to get out of that serial communication loop otherwise.
[ul][li]capture the LuaUPnP.log file and send it to me (don't post it on the forum as it can contain sensitive info)[/li][/ul]
I know, the reason I did this is because the one I posted didn’t have anything sensitive, I think (I’ve removed it anyway now). However, I cannot actually attach anything to PMs, so where would you like me to post it?
@nlrb, thank you. I have everything working including the aux on the keyfob controlling the PGM output. As you mentioned elsewhere the power max panel only has the control, eventlog (which doesn’t work) and the advanced settings. Presumably when I upgrade in future to latest version all will work. Thanks for the wonderful work to all.
[quote=“nlrb, post:439, topic:169028”]Thanks for the useful feedback stridger!
Not sure how that would impact the drop-down list, but worth a try for people with the same issue.[/quote]
OK, I’m sorry, I’ve now definitely reproduced the problem and fixed it. It’s actually going away as soon as you create a room. If you have no rooms initially, then there are no serial ports in the list. As soon as you create a room, the list appears. Sorry I didn’t mention that one first.
nlrb, As suggested, I’ve jumped to 59. Just to try it out, went into Installer mode and exited, no issues of CRC impacting the vera !?. The luup just re-read the panel and sorted itself out. Will update you as to what happens at 2am vera housekeeping.
All I can presume is that you must have found a way to trap the CRC or when the panel goes into Installer mode and kick another sub routine of sort.
Hi,
I’m quite new to the powermax vera plugin, but having spent quite a while on trying to troubleshoot it alone, am still having major issues.
I’m running a vera 3 lite (v1.5.408) with an FTDI usb to serial adaptor (but have tried a pl2303 one also) - and a powermax pro panel (partition ver) running v17 software.
The powermax plugin I’m currently using is 1.0 beta r59.
The issue is that I can’t get the plugin to stay running reliably for anything more than an hour or two.
The status on the web gui seems to flick randomly between powerlink and standard mode (usually starts in powerlink mode and then drops to standard after a bit), but the bigger issue is that after an hour or two, the vera and the powermax seem to stop communicating entirely.
The slightly odd bit is that if I hit the ‘reload’ button on the vera, it all springs back to life again for a while.
I’ve tried disabling the ‘micasa routing’ option on the vera (as mentioned earlier to solve the 2am restarts), as well as turning off ‘auto configure’ and ‘auto set time’ in the plugin, but to no avail.
I’ve even tried - as an earlier post indicated a similar issue - uninstalling the plugin and manually removing any remaining powermax plugin files via ssh.
Any help really appreciated on this as I’m tearing my hair out a bit here! (and happy to post relevant logs or other info if that would help of course).
There are known issues with the code of r59 for panels that have auto-enrollement (e.g. PowerMax Pro with partitions). If you have such a panel then please use the setting ‘Force standard mode’ for now with this version of the code. I am working on fixing this.
If you have a PowerMax+ or earlier PowerMax Pro then the code should be working stable.
There are known issues with the code of r59 for panels that have auto-enrollement (e.g. PowerMax Pro with partitions). If you have such a panel then please use the setting ‘Force standard mode’ for now with this version of the code. I am working on fixing this.
If you have a PowerMax+ or earlier PowerMax Pro then the code should be working stable.[/quote]
Aha, thanks!
OK, that makes perfect sense then, as mine is indeed one of the auto-enroll models. I’ll drop it down to standard mode for the moment.
If you need any more testers for the upcoming version btw, very happy to oblige as I think this plugin is nothing short of amazing !
@nlrb: Just wanted to tell you that for last few days I am not able to get time to get to it (collecting logs for zone 09 not getting created issue); will do it sometime later this week. Apologies for the delay. However, yesterday i was able to resolve the com port not appearing in the Advanced Tab list box by following stridger’s solution about creating rooms in Vera. I would like to thank stridger for this.
Btw, I noticed one more issue: I have configured PGM in Powermax+ which works perfectly using the keyfob AUX button (configured to send active 2s pulse). The virtual device for PGM also gets created automatically by the plugin in Vera. However, pushing on/off buttons in this virtual device on Vera does not seem to switch the PGM output. DO you know, what could be the reason?
[quote=“arfield, post:451, topic:169028”]Aha, thanks!
OK, that makes perfect sense then, as mine is indeed one of the auto-enroll models. I’ll drop it down to standard mode for the moment.
If you need any more testers for the upcoming version btw, very happy to oblige as I think this plugin is nothing short of amazing !
Rupert[/quote]
Hi Rupert, thanks, that is very nice to hear!
I’ve just committed r60 which should fix the auto-enrollment issue. If you could verify what, that would be excellent.
Thanks for letting me know. That was indeed a bug, should be fixed now in r60.
Main changes for r60.
[ul][li]Added delayed sending in separate thread[/li]
[li]Fixed auto-enrollment[/li]
[li]Fixed PGM switching[/li]
[li]Updated list of PowerMax models[/li]
[li]Added special ‘bypass-only’ status message[/li]
[li]Catch debug file write errors[/li][/ul]
[quote=“nlrb, post:453, topic:169028”]Hi Rupert, thanks, that is very nice to hear!
I’ve just committed r60 which should fix the auto-enrollment issue. If you could verify what, that would be excellent.[/quote]
Hi,
I’ve just installed r60 / rc1.
Everything fine so far, but it took a bit of time previously to lose connectivity on r59, so will report back in a few hours!
After installing r60, I did find that I had to switch ‘auto-create devices’ back on for it to switch back into powerlink mode btw.
Are you sure? These 2 are not related. Don’t you mean ‘Force Standard Mode’?[/quote]
Hi,
I switched ‘force standard mode’ off as soon as I’d installed r60, and then after it still showed standard for a while, power-cycled the panel to try and kick it back into powerlink mode.
It was still showing standard after around 10 minutes more however, but within around a minute of switching ‘auto-create’ back on, it proceeded to read the panel settings and switched into powerlink mode.
It could of course have been that the vera was being really slow at deciding to reload the settings from the panel - don’t want to send you on a wild goose chase !
Anyway, the good news is that for me the powerlink mode has stayed on ever since - no dropouts or mode changes at all.
The motion sensors are also now functioning as triggers within vera perfectly (they weren’t working at all in r59)
Oh, and the panel name is also now correctly reported (PowerMax 4_86), so all perfect for the newer panels it seems !
I have a new Powermax Pro panel and current Marketplace download running on a Vera Lite. I have 1 partition and 3 zones configured on panel. The GUI seems to be working as described. I don’t see any status or report for an Intrusion Alarm that I can trigger a scene from. I want to be able to send a text message with zone status when an intrusion alarm is initiated at the panel. Any suggestions?
@Gatorcw: I am a newbie but just been through setting up Vera connecting to Powermax+. I was facing connectivity problem due to unrecognized serial-usb cable. Are you sure your Vera was able to communicate with Powermax? DO you see message like “PowerMax : Ready for use”?
@nlrb: I upgraded to version 1.0 RC1 from trunk-60. It worked perfectly fine for a few mins - auto connected in Powerlink mode, all virtual devices got created (except zone#9) automatically, got “PowerMax : Ready for use” message, was able to arm/disarm and noticed sensor violations. However, after a few mins (within 10 mins), the plugin stopped working with the message “Powermax Alarm Panel[31] : Startup Lua Failed”. I have repeated the process of removing and creating “Powermax Alarm Panel” 5-6 times after that and consistently noticed the same behavior. Do you know what can be the reason?