[quote=“akbooer, post:3, topic:198522”]OK, I think that some of this, at least, is a bit more openLuup-related than AltUI, so I will give a partial response.
AltUI’s history id, AFAIK (please correct me @amg0!), extracted from the log file in /var/log/cmh/LuaUPnP.log which you can view the most recent part of from the Misc > OsCommand > Tail Logs button in AltUI. This log gets rotated from time to time, so the only history that you will see is that contained in the current log file. I get, in openLuup, entries like this (showing two scene executions and some variable changes):
08 02/06/18 15:02:46.128 Scene::RunScene running 6 Ping Poll <0x0>
06 02/06/18 15:02:58.170 Device_Variable::m_szValue_set device: 20365 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: ePollOke was: 472896 now: 472897 #hooks: 0
06 02/06/18 15:03:03.630 Device_Variable::m_szValue_set device: 20336 service: urn:akbooer-com:serviceId:EventWatcher1 variable: eMemAvaile was: 34200 now: 34188 #hooks: 1
06 02/06/18 15:03:03.631 Device_Variable::m_szValue_set device: 20431 service: urn:akbooer-com:serviceId:DataYours1 variable: eAppMemoryUsede was: 1681 now: 1472 #hooks: 0
08 02/06/18 15:03:04.491 Scene::RunScene running 7 luup.scene test <0x0>
If your /var/log/cmh/ directory was not created or does not have the right permissions, then you may not see anything.
HOWEVER
I’ve just checked out scene history on openLuup (something I’ve never done before!) and I, too, see nothing. So we need @amg0 to explain to me what 's wrong in this log for scene entries. Variable histories seem to work just fine.
3. When I go ALTUI > Misc > Reload Luup Engine I always get the message "Controller did not respond"
What versions of AltUI and openLuup are you running? There may be an incompatibility if you’re not up to date.
4. Directory structure question. In the OpenLuup documentation it states:
[b]openLuup directory structure and ancillary files[/b]
'''
However in my RPI I have:
‘’’
Am I missing something or is what I have the minimum required structure?
This part of the documentation is, alas, not quite clear / up-to-date. Your file structure should be fine (for all but the most exotic plugins) and is what has been created by the openLuup_install process. The thing not on here, and mentioned above, is the /var/log/cmh/ directory. I have already got an updated document ready for the upcoming next master release of openLuup (but that doesn’t help you right now!)
4. Lastly, how can I make the PI start openLuup on reloads. I have tried to use the examples shown in the openLuup documentation but ALL the files in the root level (where the script needs to be edited) are locked. Is there a way to get root user access? Currently I ssh into the PI as user [PI], not as user [root]. I could not find anything on how to log in as root in any of the documentation.
This is not my area of expertise, alas, and that part of the documentation relies heavily on others’ effort. However, I do have this working. The key, perhaps to accessing root files is to prefix your editing command with ‘sudo’ (q.v.) I have no idea what the root password is to my RPi!
I'm sorry that these questions spanned two different programs and two different authors but I'm hoping that someone here can shed some light on what I'm missing. Thanks
No, I’m sorry too. We do try very hard to coordinate and inform each other of various changes to make this as seamless as possible, but it doesn’t always work perfectly. Vera is a moving target, AltUI has to track it (and does so, very rapidly,) I am just a bit slower.
You’ll notice that I’ve avoided point #2, which I leave for others.
HTH[/quote]
it works on vera, I ll check tonight on openluup. the way it works is : ALTUI runs the following command on log file
“cat /var/log/cmh/LuaUPnP.log | grep '”+‘\t’+“Scene::RunScene running {0} '” where {0} is a num id
then read the result with the regexp
var re = /\d*\t(\d*/\d*/\d*\s\d*:\d*:\d*.\d*).Scene::RunScene running \d+ (.) <.*/g;
Vera logs look like
08 02/06/18 14:23:05.117 Scene::RunScene running 61 UpdateThingspeak <0x73357520>
08 02/06/18 14:31:00.209 Scene::RunScene running 49 Maison Avec Cam <0x73f57520>
) to help you here