I was looking at some javascript in the firmware for the Vera UI7 and I noticed it is making a call to /data_request?id=static&rand=0.42764871031977236
I looked in the Luup_Requests documentation and there is no documentation for it. openLuup returns No Handler when I try the same request on it. I am currently running on UI5 for my vera and it does not appear that the handler exists on UI5?
Will some who is running UI7 report back on what data is returned when making a request to the endpoint and maybe this can be added to openLuup?
This is just a subset of the [tt]&id=user_data[/tt] request, which contains the static data. It’s also available as [tt]&id=lu_static[/tt] on UI7. I can’t think of a good reason to implement, since it’s presumably only used by Vera JS code, which we don’t really need.
However, if you did need it, it’s trivial to add. Well spotted!
@akbooer, thanks for the confirmation.
I had modified my requests.lua and added it in right below user_data2 thinking it was pretty much the same.
I actually almost have the original UI running on my debian system with apache. I set up reverse proxy for
/port_3480 to localhost:3480 as well as install the haserl package for the /cgi-bin scripts.
Its really a futile effort because AltUi is actually nicer. I do want to expand the Add devices modal to allow adding IP address when creating a new device. Right now the only way to add a device that uses ip is to use startup.lua
Remind me of the problem, since it’s clear that Vera doesn’t have this problem. There must be a simple fix for openLuup.
The issue is with networked devices such as the VeraBridge.
in AltUI go to devices and click create device. There are only three fields. Name, Device, Implementation. I have completed the fields and reloaded openLuup. For the device to work it needs to have the luup.ip set. In AltUI if I edit the device and set the ip it doesn’t actually save for me.
I haven’t debugged it any further than that if it is an issue with AltUi or openLuup. setting the ip address in the startup.lu with
luup.ip_set ("192.168.0.100", dev)
solves the problem and the ip sticks between restarts, etc.
I have not tested updating the ip address via the AltUi either.
Yes, that’s the workaround to use.
The underlying reason is a CORS issue, IIRC, arising from the fact that openLuup needs to use :3480 port syntax, but I think that the attribute change code in AltUI uses /port_3480 for that one. You should see that if you look at the log of your port 80 HTTP system server.
[quote=“akbooer, post:6, topic:190708”]Yes, that’s the workaround to use.
The underlying reason is a CORS issue, IIRC, arising from the fact that openLuup needs to use :3480 port syntax, but I think that the attribute change code in AltUI uses /port_3480 for that one. You should see that if you look at the log of your port 80 HTTP system server.[/quote]
I just recently added a reverse proxy for /port_3480 so may this will then start working as expected. Nice!