Upgrading UI4 to UI5

Plugins & Plugin Development Unmaintained
1

@Futzle

I recently upgraded from ui4 to ui5 on the vera2 and I deleted the old plugin (rev. 62 i think) and downloaded the new one through apps.mios. (rev. 67?) 3 weeks ago. I have set it up and everything is communicating properly to display the sensors opening/ closing and system arms/ disarms from the dashboard. everything is as it was before.

Except:

  1. I do not see a status on the dashboard and when I click the wrench it still doesn’t show the status in the controls box. this also presents an issue for automator.app when it tries to pull the alarm status (see attached)

  2. scenes don’t activate when I set them based on alarm state triggers.

  3. I no longer receive arming or disarming notifications via email even though I have notifications set and based on armed state “yes” or “no” (attached)

You have done amazing things with this plugin.

Hopefully, this is a quick fix and maybe I have done something wrong as I am still learning the ways of ui5.

Any assistance is appreciated. Thank You!

2

Hi drew,

The prime suspect would be a leftover file from the old plugin. The Partition service ID changed somewhere along the way, so if you still have the old file sitting around then it could lead to partition info going AWOL.

You will need to SSH into the Vera and inspect two directories. Run

ls /etc/cmh-lu
ls /etc/cmh-ludl

You should get two lists of files. There should be no duplicates. If there is a duplicate it might be masking the “correct” file. Rename the one in /etc/cmh-ludl to keep it out of the way.

cd /etc/cmh-ludl
mv the-offending-file.lzo some-madeup-string

Or, there may be the same file twice in cmh-ludl, once with an .lzo extension and once without. Rename the non-lzo one out of the way.

Report back and we will see what to do next.

3

I think I found the files. I have attached a screenshot.

How do I rename this file in ssh?

Is the MV command to move a file?

what is the proper command string to rename the file?

thanks

4

mv current-filename new-filename

Edit: once you are happy that you fixed it you can remove the file permanently with

rm victim-filename

This is very permanent. Hence why I recommend renaming with mv first.

(Yes, I think you found the problem. You may find that your partition devices automatically delete and re-create. I can’t do anything to stop this, sorry.)