Can somebody explain to me how to manually install a plugin in openLuup? I can’t find it on the forum. I would like to have the MultiSwitch plugin, but it is not available in the AltApp store.
Or can somebody maybe make it available in the AltApp store (even better)?
BTW I found the post with working plugins on openluup, but I think there are instructions on how to do it.
This is just a question of putting the device files into the files/ directory and using the +Create button on the Devices page to bring up a form in which you enter device name, and device and implementation .xml filenames.
Or can somebody maybe make it available in the AltApp store (even better)?
Our policy on the AltAppStore has been not to put anything there except written by ourselves or put there by the original author. Although it’s only a meta-data store and the actual code resides on GitHub, this seemed the right approach.
Very happy to help someone put their stuff there, or to do it for them given express permission to do so from the author.
It is as akbooer has written. It’s just that simple, but if you haven’t done it before, a couple of the steps can give you pause. Expanding to give a little more detail for reference…
I use this simple approach on both openLuup and Vera, by the way…
[ul][li]Copy the plugin files up to the device. For Vera, you can use the uploader at Apps > Develop apps > Luup files (turn off Reload luup until you upload the last file), or use SCP and place them in [tt]/etc/cmh-ludl[/tt]. For openLuup, I use SCP and place them in the files directory (you’ll usually find ALTUI installed there as well–look for [tt]J_ALTUI_uimgr.js[/tt] for example).[/li]
[li]Reload Luup[/li]
[li]Use the “create device” function to create the first device instance. On Vera, that’s in Apps > Develop apps. On openLuup, it’s right on the dashboard. For Vera, you will need the device type, which is easily found in the [tt][/tt] element of the [tt]D_device.xml file[/tt] (referred to as the device file), or usually near the bottom of the [tt]D_device.json[/tt] file (referred to as the static JSON file). Both Vera and openLuup will ask for a device name (obvious but keep it short), and the “device file” name ([tt]D_device.xml[/tt] – the XML one, not the JSON one), and the implementation file name, which is the [tt]I_device.xml[/tt] file. The Vera form has more fields, but you don’t need to worry about them usually.[/li]
[li]Hit the submit button on the create form[/li]
[li]Reload Luup again[/li]
[li]Do a full refresh/cache flush of the browser. You may need to do this more than once.[/li][/ul]
Note that if you use SCP to copy the files to a Vera, you may need to delete a previously installed, compressed version of the plugin files. These have the plugin file names with [tt].lzo[/tt] added at the end. If you don’t delete them, the Vera will use them in preference to your newly uploaded files. When you use the Apps > Develop apps > Luup files uploader is LZOs everything you upload, so that’s not a problem, but when using SCP you bypass this, so you’ll need to SSH to the box and carefully delete (only) the old LZO files for the plugin you are uploading.
Thanks, both of you. It looks pretty straightforward, but I run into a problem with openluup.
I’ve created the device and it seemed to be OK, but I couldn’t edit the button names. So I found a post that said I probably had an old version of the plugin. Now I have removed and reinstalled the plugin on Vera and then I used the GetVeraFiles action of VeraBridge (I also removed the old files from openluup). I assumed openluup would get the new plugin files from vera, but the files of the MultiSwitch plugin are not being copied to openluup.
Any ideas?
I can put them on manually, but I want to know why this doesn’t work.
OK, but tell me how you know. Is there an error in the log? I have changed this recently, trying to anticipate Vera security changes. I’ve tested on old versions of Vera, but am not prepared to update to the latest yet!
Any ideas?I can put them on manually
Indeed, you can always download these manually from the UI7 Develop Apps > Files pages and then transfer to openLuup.
...but I want to know why this doesn't work.
So do I. Logs/more info will help. Thanks in advance.
So do I. Logs/more info will help. Thanks in advance.
[/quote]
Sorry, should have attached them immediately, but I was not sure what the expected result should have been. I’m getting 404s so it seems.
UPDATE
There is a “/” missing in the URLs in the log.
So there is. Fixed now in Development branch (hopefully not breaking something else…)
Do please let me know!
So there is. Fixed now in Development branch (hopefully not breaking something else…)
Do please let me know![/quote]
Seems to be working now. Thanks for the quick support!
One last question. Does it matter whether the files are in cmh-ludl or in cmh-ludl/files/?
I’m having difficulties installing the MultiSwitch and I think I’m getting different results.
That’s great.
One last question. Does it matter whether the files are in cmh-ludl or in cmh-ludl/files/?
No, openLuup looks in both places (and more besides.) However, I normally put the majority of files in the files/ directory to keep cmh-ludl/ tidier. Additionally, I have a symbolic link called cmh-lu/ from …/cmh-ludl to cmh-ludl/files/ which mimics the Vera directory structure where both cmh-ludl/ and cmh-lu/ sit in the same parent directory, and both hold device files. Hope that makes sense!
Ok, thanks. Makes sense.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules