Updating Progam Logic Plugins

Plugins & Plugin Development Program Logic (PLEG)
1

Open your Vera control panel in a browser window. You can monitor the status of Vera reloading from here.
Open up a separate browser window. With this window issue each of the following commands … waiting for Vera to reload before issuing a subsequent command.
The response from each command will be an OK
Refresh the contents of the Vera Control Panel, before using it.
[hr]
To Update Program Logic Timer Switch
http://YourVeraIP:3480/data_request?id=update_plugin&Plugin=3018

To Update Program Logic Event Generator
http://YourVeraIP:3480/data_request?id=update_plugin&Plugin=3066

To Update Program Logic Core
http://YourVeraIP:3480/data_request?id=update_plugin&Plugin=3086

Make sure you do this one LAST
[hr]
This can also be done remotely (UI5 Only) by using the form:

https://VeraFwdAddress/VeraUserName/VeraPassword/VeraID/data_request?id=update_plugin&Plugin=[b]XXX[/b]
Where:

[ul][li]VeraFwdAddress - can be found by issuing the web request:
http://sta1.mios.com/locator_json.php?username=[b]YourVeraUserName[/b][/li]
[li]VeraUserName is your username at cp.mios.com[/li]
[li]VeraPassword is your password at cp.mios.com[/li]
[li]VeraID is your Vera ID, also available from the request a few lines up.[/li][/ul]

[hr]
If you accidentally upgrade your Vera running UI5 to a UI7 version, you can recover by restoring the latest UI5 version:

http://YourVeraIPAddress:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=PLUGIN#&Version=VERSION#

Where:[table]
[tr][td]Plugin Name[/td][td]Plugin #[/td][td]Version #[/td][/tr]
[tr][td]PLEG[/td][td]3066[/td][td]28004[/td][/tr]
[tr][td]PLTS[/td][td]3018[/td][td]28001[/td][/tr]
[tr][td]PLC[/td][td]3086[/td][td]27991[/td][/tr]
[/table]

Do PLC Last!
This should get you back to Version 7.47 of each of these plugins. Make sure you wait for Vera to Reload beween each. Do one more Reload when you are all done … then refresh your browser.

2

Hi Richard -
Do you have a quick set of instructions for how to upgrade these files on a remote vera? I’ve got 3 of them remotely that would benefit from an update of your apps.

Thanks.

3

I saw your post … I have not had a chance to check out the process for remote updates.

4

OK. Sorry to have pestered. Isn’t it as easy as uploading the files to this board and then we just upload them to the controller using the Develop Apps tab?

5

Couldn’t you have a scene to invoke an update through Luup?

local http = require("socket.http")
result, status = http.request("http://YourVeraIP:3480/data_request?id=update_plugin&Plugin=3018", "run=run")

And then just run the scene manually as needed? You could set up a scene to update each plugin you have.

There may be a reason that this won’t work that I’m just not seeing…

6

I updated the first message to indicate how to update the [b]PL[b] plugins, or any other plugin remotely.

7 
local http = require("socket.http")
result, status = http.request("http://<YourVeraIP>:3480/data_request?id=update_plugin&Plugin=<Plug In Number>", "run=run")

I ran a test of this method and it seems to work well. I created a scene with the code above–changing the IP address and plugin number–and invoked the scene manually. Vera installed the latest version of the plugin and then restarted the Luup engine afterwards. To do all of the PL plugins at once, just repeat the two lines for each plugin in one scene, or create separate scenes.

I wouldn’t suggest putting the scene on a timer (because there may be times that you want to wait on updating to a new version) and there may be other drawbacks that I’m not aware of. With this method, I figure that you can run the scene from where ever you have access to the Dashboard, and from any mobile app that supports scenes.

Dave

8

Richard,
Just a quick thought… Maybe under the ‘Plugin Control’ tab on Apps you could put the update links? Not sure if they can be dynamic - auto detecting the Vera’s IP?

9

Nice idea. There’s no interface for the core though.

10

[quote=“DaveL17, post:7, topic:175015”] local http = require("socket.http") result, status = http.request("http://<YourVeraIP>:3480/data_request?id=update_plugin&Plugin=<Plug In Number>", "run=run")

I ran a test of this method and it seems to work well. I created a scene with the code above–changing the IP address and plugin number–and invoked the scene manually. Vera installed the latest version of the plugin and then restarted the Luup engine afterwards. To do all of the PL plugins at once, just repeat the two lines for each plugin in one scene, or create separate scenes.

I wouldn’t suggest putting the scene on a timer (because there may be times that you want to wait on updating to a new version) and there may be other drawbacks that I’m not aware of. With this method, I figure that you can run the scene from where ever you have access to the Dashboard, and from any mobile app that supports scenes.

Dave[/quote]

i changed 3480 to my Vera IP #. then i put the plugin # 3066 which is PLEG; its version remained 5.1 instead of 5.3. i manually ran the scene several times and reloaded vera and nothing happened with the version number.

11

3480 is the port number. Your IP goes before that…

12

thanks, i would not know this if you did not give me this info. now PLEG shows version 5.4 from 5.1. another stupid mistake i did was using my vera2’s serial number instead of IP address. thanks again.

13

Yes. Replace the text:

with the actual IP of the unit. It should look like this:

192.168.0.101:3480

Of course, your IP will probably be different. Sorry if that was unclear.

14

Is updating supposed to update all previous instances of the PLEG and PLTS?

I successfully updated to version 5.8 for the PLC, PLEG and PLTS (according to the “My Apps” in UI5), however I’m still getting a “Version Mismatch! PLEG Version: 5.7 PLC Version 5.8” when attempting to access any of the tabs in existing PLEGs or PLTSs.

Is it required that I migrate the setup within existing PLEG or PLTS instances to a newly instantiated PLEG or PLTS?

Thanks,
Don

15

I got the same error as Don

16

You might have to Manually Upgrade … I have changed the settings at the APP store to only allow PLEG/PLTS to download on UI5.
That might not be working well with the Auto Upgrade feature. I did not do it on the Program Logic Core. That might be causing the problem where some plugins are auto updating and others are not.

You can safely ignore the messages about 5.7 and 5.8 … These versions are compatible … 5.8 fixes a few bugs in 5.7 … and all of the fixes are actually in the Program Logic Core.

17

I got the same message so I did a manual update… The interesting bit is that I have two Vera Lites and I updated both. Both now show 5.8 for both PLEG and PLC in the Apps menu but I still get the error message on one of them. I tried reseting, reloading but still the same result…

Any ideas?

Thanks

/Sigge

18

Did you reload the BROWSER ? SHIFT-F5!

19

Apparently the previous existing instances of PLEG and PLTS that were version 5.7, were automaticlly updated to Ver. 5.8, since the dialog warning about the PLC being a different version no longer appears.

Problem solved!! ???

I guess I just need to be more patient!! (That’s always been one of my numerous shortcomings.)

20

@RichardT:

Will updating my instances of PLEG from 5.7 → 5.8 cause my to loose any PLEGs I have installed along with their associated inputs/conditions…etc? The core auto-updated for me and I manually deleted the PLTS and downloaded 5.8 but I don’t want to loose my PLEGs during the update. Is there any safe way to do this??