[quote=“vosmont, post:39, topic:187412”]As I am on Windows, I’m not sure that the script “.sh” will work.
For the moment I’ve modified the function getIP in L_ALTUI.lua, and it’s OK.[/quote]
I never imagined that openLuup would be run on a Windows machine! A fair number of plugins will be written with the assumption that the underlying system is Unix. In particular, anything with an [tt]os.execute(…)[/tt] call will likely fail. Your ALTUI fix is what I originally did - hooray for open source!
[quote=“vosmont, post:40, topic:187412”][quote=“vosmont, post:39, topic:187412”]The plugin RGB Controller doesn’t work :
http://ip:3480/data_request?id=action&output_format=json&DeviceNum=41&serviceId=urn:upnp-org:serviceId:RGBController1&action=GetColorChannelNames
returns “-1”[/quote]
I think the problem is that this action is for the distant Vera (the plugin is installed on it). So when it is executed on openLuup, it can’t respond.
So for the javascript in the tab of the distant plugin, it lacks perhaps a proxy.[/quote]
A couple of points here:
[ul][li]An action call to a device bridged by VeraBridge will be re-routed to the remote machine device - this is how turning on lights, etc., works. So the underlying mechanism should be working. Actions which have return variables are not fully working at this time. The definition of which variables to return is given in the service .xml files and I’ve been trying to avoid them, since this brings me too close to UPnP syntax nonsense. The same with scene triggers.[/li]
[li]Obviously, a plugin which assumes that it’s manipulating the local machine GUI is going to struggle when bridged. The solution is surely, simply to run RGB Controller on the openLuup machine - this is what it’s for, to offload things from the original Vera. **** see edit below ***[/li][/ul]
Sounds like you’ve made a lot of progress. Interested in hearing further.
Edit: having re-read my reply, I suddenly realise that the action call you are making, which needs to be handled by VeraBridge, is NOT in its list of implemented actions (as given in the implementation file.) This is perhaps what you implied by mentioning a proxy. It would be a step forward to insert that action into I_VeraBridge.xml, but you may still have difficulties with the JavaScript. Running it locally still makes sense to me.