Mucked about with getting the wireless connection between Vera and PowermaxPro for a couple of weeks. Ended up using couple of XBEE’s which just worked 1st time. Absolutly reliable and would recommend. Only if there was a Zwave version of an RS232 comms link for these sorts of connectivity.
The Radio link is half duplex units, the Zigbee units probably have a better buffer to imitate a full-duplex connection between the Vera and Powermax for the handshake timings.
Will still have a play to get the XRF’s working on this.
Finally I receive my USB/RS232 converter.
I installed the plugin from the APP market (UI5 version).
That is working, I have my sensors and sensors status is updated as expected. 8)
Only problem is that this version is without partition management (no files D_PowermaxPartition2.*). I imagine that Micasaverde has taken a very very old version of your plugin to build this UI5 version. As a résult, no parition device is created and of course I cannot arm or disarm the panel as these commands are in the missing devices. I find nowhere what you show in your two last screenshots ( Visonic Powermax Alarm Panel )
So what to do now ? Install your last UI4 version ? Is there a chance to work ? Do you know exactly what Micasaverde has adjusted in your plugin ?
What’s a pity to not have one unique version for UI4/UI5 managed by you.
I imagine that now 90% of users have moved from UI4 to UI5 and unfortunately we are forced to use an obsolete version of your plugin.
When I arm the Visonic panel, I see (after WEB navigator refresh) that a variable is updated on the main Powermax device but the individual zone devices are not armed. Is it the expected behavior ?
So how can I trigger a Vera scene when the PowerMax panel is armed ?
When I want to define a trigger, the Powerma device is not in the list; it is probably normal as this device is not a sensor.
Do I need to use a scheduled scene (every 5 minutes for example) and check the variable in the luup part ? There would be a time delay of several minutes between arming the panel and triggering the Vera scene.
I assume that the difference between UI4 and UI5 would only be one file (the json). The rest should be the same. The problem is that I cannot test a UI5 implementation as I do not have it. I dont want to start programming stuff I cant test.
I plan to upgrade to UI5 as soon as I know that the essential stuff I need is supported (dataMine, HSM100, HRT-ZW, HRT-ASR, …). The main problem is that the system controls my heating and if it fails I sit in the cold. So I guess I have to wait for warmer weather until I attempt an upgrade.
I will try to install manually the last UI4 version.[/quote]
Latest UI4 version will only work if the json file is adapted to UI5[/quote]
What would happen if I don’t install json files ?[/quote]
Bsically, the syntax of these files has changed (see http://wiki.micasaverde.com/index.php/UI4_UI5_Migration). I would assume if you use the UI4 files for UI5, the sections where syntax changed will not work anymore. For example, trigger events.
I can try to make some UI5 json files for you and you can try but it is not guaranteed to work as I cant test it.
I fixed the UI5 version of the plugin. I forgot to replace some curly brackets with square brackets. Sorry for that.
Next time something like this happens and I don’t react quickly enough please send me a PM or an e-mail.
[quote=“mcvflorin, post:191, topic:169028”]I fixed the UI5 version of the plugin. I forgot to replace some curly brackets with square brackets. Sorry for that.
Next time something like this happens and I don’t react quickly enough please send me a PM or an e-mail.[/quote]
The fixed version is available on the app store ?
Can you please tell us which version of utz was the start point for this UI5 version.
[quote=“mcvflorin, post:191, topic:169028”]I fixed the UI5 version of the plugin. I forgot to replace some curly brackets with square brackets. Sorry for that.
Next time something like this happens and I don’t react quickly enough please send me a PM or an e-mail.[/quote]
Thanks for doing this (I did not want to bother mcv as I think there may be more pressing issues with the new UI5 release than this plugin which not that many people rely on).
Where could I find the UI5 json files? I would like to put them in the mios svn together with the UI4 files. This way I could keep it all nicely together. The only thing left then would be for someone to push the svn content into the UI5 app space (or however this is called) when there are changes. I could even look after that if I would know howto.
As soon as I am able to upgrade to UI5 I will continue to develop the plugin for UI5 and just maintain the current UI4 version.
[quote=“lolodomo, post:192, topic:169028”][quote=“mcvflorin, post:191, topic:169028”]I fixed the UI5 version of the plugin. I forgot to replace some curly brackets with square brackets. Sorry for that.
Next time something like this happens and I don’t react quickly enough please send me a PM or an e-mail.[/quote]
The fixed version is available on the app store ?
Can you please tell us which version of utz was the start point for this UI5 version.[/quote]
If you install it the plugin should show a version number in the UI (If it is not based on a very old version).
It should be “V 0.80” if it is recent code from the svn.
Commited tag 0.81 which is version 0.80 of the plugin updated to be compatible with both UI4 and UI5. I also published this version in the MiOS Marketplace.
Using these files I get now in UI4 a window on the screen when pressing the ArmHome button (see attached). After pressing OK on this window the system arms. Where does this window come from (I cant find the code in the json file that does this)? How can I get rid of it (Or populate it with some useful content?)
Here is my positive feedback on the plguin (UI5 version) 8)
Version nimber has not been updated, V 0.80 is displayed on the main device => not important at all
I have only one partition created My Powermax Pro can manage 4 partitions (3 partitions + 1 covering all zones) and I have already assigned zones in partition 1 and partition 2. Are the partition devices created automatically ? If yes, what are the conditions ? If no, how to create them manually ?
in a first time my door sensors were not updated when I close the door. But now, it seems to work well. So forget it.
Arming and disarming is working well. If I press the buttons on the partition device, I see a “Wrong PIN U…” displayed (text is truncated). Very well, I have to open the panel device and enter my PIN code. But why keeping these buttons on the device if they cannot be used ?
What is the role of “Status code” and “Status data” information displayed in the partition panel ? They don’t change.
I see that status is automatically updated, that is very cool. Even some variables are updated in the advanced settings panel even without refreshing the Web browser. I don’t know if it is something specific to this plugin or a new feature of the new firmware but it is cool
When I arm the panel, should I not have the buttons on each zone device updated, like it is done on the partition device ?
8 ) Could we have a door sensor device (does it exist ?) for door/window sensors, instead of a motion sensor device ?
On the main device, I can get the event logs with a correct display but the date/times are wrong.
Event logs seems to not get all the events dispayed on the alarm panel. Does it filter certain events ?
PGM does not work. Note that on Powermax Pro, we have two AUX buttons, Aux A and Aux B. I setup the two to PGM.
I find nowhere what you show in your two last screenshots (