Unintall Reactor

kyle.dawson · December 24, 2018, 5:41pm

What is the correct process to uninstall Reactor?

I installed via UI7 App store. I then wanted to remove but it did not show up in “My Apps”. So I removed all reactor files on the Vera but still getting this error in ALTUI:

the module or function Reactor_ALTUI.getStyle does not exist, check your configuration

rigpapa · December 24, 2018, 6:55pm

Well, first, deleting the plugin files for when there still may be related devices and other configuration is the wrong way to remove any plugin under Luup. That will almost surely leave unhappy stuff behind. I would recommend you reinstall Reactor for moment while we sort the rest out.

There is an ongoing issue with Reactor (and other of my plugins) under AltUI where I have created custom dashboard cards. I believe I have followed the documented procedures for doing this, but there are some problems when uninstalling the plugins. Even on openLuup with AltUI (where I do a lot of development), the process of removing a plugin the “right” way leaves things behind, and usually getStyle() is the culprit that creates the most trouble.

So I think we’re going to have to call for the help of @amg0 on this one. I see two issues:

AltUI should never lose control and crash entirely when a plugin dependency takes an error or cannot be loaded (IMO);
The current register function does not, that I can see, provide a way to unregister, and I can’t find any other way to do it. My first guess was to try the register action with blank module/function names to deregister those functions, but that doesn’t work–it just ignores blank parameters. And I don’t see another way to do it, short of editing the AltUI plugin JSON directly. Ideally, if we could do the following in the “Test Lua” window, we could easily get out of jail:

luup.call_action("urn:upnp-org:serviceId:altui1", "RegisterPlugin", { newDeviceType=RSTYPE, newScriptFile="", newDeviceDrawFunc="", newStyleFunc="" }, devnum )

or better still, simply:

luup.call_action("urn:upnp-org:serviceId:altui1", "UnregisterPlugin",{ deviceType=RSTYPE }, devnum )

@amg, can you provide some feedback and assistance here?

amg0 · December 24, 2018, 9:07pm

[quote=“rigpapa, post:2, topic:200306”]Well, first, deleting the plugin files for when there still may be related devices and other configuration is the wrong way to remove any plugin under Luup. That will almost surely leave unhappy stuff behind. I would recommend you reinstall Reactor for moment while we sort the rest out.

There is an ongoing issue with Reactor (and other of my plugins) under AltUI where I have created custom dashboard cards. I believe I have followed the documented procedures for doing this, but there are some problems when uninstalling the plugins. Even on openLuup with AltUI (where I do a lot of development), the process of removing a plugin the “right” way leaves things behind, and usually getStyle() is the culprit that creates the most trouble.

So I think we’re going to have to call for the help of @amg0 on this one. I see two issues:

AltUI should never lose control and crash entirely when a plugin dependency takes an error or cannot be loaded (IMO);
The current register function does not, that I can see, provide a way to unregister, and I can’t find any other way to do it. My first guess was to try the register action with blank module/function names to deregister those functions, but that doesn’t work–it just ignores blank parameters. And I don’t see another way to do it, short of editing the AltUI plugin JSON directly. Ideally, if we could do the following in the “Test Lua” window, we could easily get out of jail:

luup.call_action("urn:upnp-org:serviceId:altui1", "RegisterPlugin", { newDeviceType=RSTYPE, newScriptFile="", newDeviceDrawFunc="", newStyleFunc="" }, devnum )

or better still, simply:

luup.call_action("urn:upnp-org:serviceId:altui1", "UnregisterPlugin",{ deviceType=RSTYPE }, devnum )

@amg, can you provide some feedback and assistance here?[/quote]

You can use Use default config button in altui settings. Then reload. Any programmatically added configuration will not be there any more providing the plugin has been fully removed.
I ll implement a unregister upn0 later but that won?t avoid the problem with plugin removed manually.

rigpapa · December 24, 2018, 9:22pm

@kyle.dawson, also this… @amg0 mentioned in reply to my PM that the getStyle() problem should be fixed in the latest AltUI, so you might also make sure you’re up on the latest code there.

kyle.dawson · December 25, 2018, 4:50am

Thanks. The reason I removed the files manually is because the app did not show up in “My Apps” in UI7 or in Plugins via ALTUI. Should this plugin show up there? Assumed something was wrong and wanted to clean it up. Thanks for info and background.

@amg0, if I use the “Default Config” Button, will I lose and break any other plugins? Or will it regen based on what is still installed?

amg0 · December 25, 2018, 9:08am

[quote=“kyle.dawson, post:5, topic:200306”]Thanks. The reason I removed the files manually is because the app did not show up in “My Apps” in UI7 or in Plugins via ALTUI. Should this plugin show up there? Assumed something was wrong and wanted to clean it up. Thanks for info and background.

@amg0, if I use the “Default Config” Button, will I lose and break any other plugins? Or will it regen based on what is still installed?[/quote]

Any plugin which is part of altui distrib will be three
Any plugin which dynamically register itself to altui as part of the startup will also be there
You might only lose a plugin which was manually added in the altui plugin config variable which I expect 0 plugin ( except as part of testing ) would do
( Use Default button , then use the set button, then reload Luup )
In case if issue look at plugin I dig variable with a json pretty viewer.

amg0 · December 25, 2018, 7:38pm

[quote=“amg0, post:6, topic:200306”][quote=“kyle.dawson, post:5, topic:200306”]Thanks. The reason I removed the files manually is because the app did not show up in “My Apps” in UI7 or in Plugins via ALTUI. Should this plugin show up there? Assumed something was wrong and wanted to clean it up. Thanks for info and background.

@amg0, if I use the “Default Config” Button, will I lose and break any other plugins? Or will it regen based on what is still installed?[/quote]

Any plugin which is part of altui distrib will be three
Any plugin which dynamically register itself to altui as part of the startup will also be there
You might only lose a plugin which was manually added in the altui plugin config variable which I expect 0 plugin ( except as part of testing ) would do
( Use Default button , then use the set button, then reload Luup )
In case if issue look at plugin I dig variable with a json pretty viewer.[/quote]

I have published in GitHub - amg0/ALTUI: Enhancement Interface for VERA home automation system a version which includes a UPNP action [b]UnregisterPlugin/b

it remains though that this needs to be called to remove that particular plugin
the alternative method is to call the Reset UPNP action to restore the default Device plugin config

nevertheless on latest ALTUI version, a missing plugin should not block it, you should get an error message in the javascript console about it