full devices reset

[akbooer]

…is that ALL ??!

[DesT]

[akbooer]

Ah, same module as your original error.

[akbooer]

Sorry to be a pain, but what does this say…?

local lfs = require "lfs"
for a in lfs.dir "openLuup/" do
  if a: match "%.lua$" then
    local f = io.open ("openLuup/" .. a)
    if f then
      local v = f:read "*a"
      f: close()
      print(v: match 'VERSION.-"([^"]+)', a)
    end
  end
end

[DesT]

@akbooer no worries

2023.01.01 api.lua
2024.02.23 init.lua
2022.12.20 historian.lua
2019.07.19 http.lua
2023.02.18 panels.lua
2023.03.04 console_util.lua
2022.11.05 chdev.lua
2021.05.08 gateway.lua
2023.02.10 wsapi.lua
2024.01.06 loader.lua
2019.10.14 client.lua
2024.02.09 mqtt.lua
2020.03.30 L_AltAppStore.lua
2024.05.01 scheduler.lua
2024.02.11 L_ShellyBridge.lua
2023.03.04 userdata.lua
2018.07.28 backup.lua
2021.03.05 shelly_cgi.lua
2024.02.26 L_openLuup.lua
2022.12.20 whisper.lua
2018.04.23 pop3.lua
2021.01.03 L_VeraBridge.lua
2021.06.14 L_TasmotaBridge.lua
2023.01.06 luup.lua
2024.01.05 devices.lua
2024.02.22 virtualfilesystem.lua
2021.08.21 whisper-edit.lua
2024.02.25 servertables.lua
2018.07.28 sysinfo.lua
2021.05.01 json.lua
2018.03.25 logs.lua
2024.02.12 timers.lua
2021.02.20 requests.lua
2022.12.11 L_Zigbee2MQTTBridge.lua
2016.06.30 compression.lua
2021.04.23 xml.lua
2023.03.03 scenes.lua
2018.01.27 hag.lua
2021.03.25 http_async.lua
2019.08.12 graphite_cgi.lua
2024.01.03 tcp.lua
2024.01.03 io.lua
2024.01.03 server.lua
2016.06.23 rooms.lua
2018.04.12 smtp.lua
2021.04.30 servlet.lua
2024.02.26 console.lua

[akbooer]

@DesT

I did find something amiss in one of the files, although I'm not convinced it's the problem.

Latest development (v240229 – the Leap Year edition) has a fix... I wonder if this gets us any further?

[DesT]

yeah it's working

[DesT]

@akbooer about RulesEngine... I think I found something... if I modify a rule, it work except, the data is not saved. That mean, if I "edit" again, it's the old data and if I reload openLuup, of course it's again the old data.

The problem is the "save" function.

[akbooer]

Excellent.

For the Rules Engine, I looked previously, and I think it’s a JavaScript issue, but I’ll try and take another look.

[akbooer]

Yes, the code for saving rules is here…

ALTUI_RulesEngine1.js

In some cases, it should write error messages to the browser console…

[DesT]

I just check again, and I'm never having any kind of error in the console, not even a warning.

[DesT]

@akbooer just did a little test... and in the browser console, I can see in the network, that, when saving a rule... it call upload_upnp_file.sh

I just did some test again and the file C_RulesEngine_Rules.xml is modified properly...

Is it possible that's related to the issue with openLuup console ?

[akbooer]

Oh, that’s interesting. There’s several versions of that file: @Vosmont wrote the original; I collaborated in making the CGI version of it, specifically for openLuup.

You’re saying this all works now?

[DesT]

yeah I made a couple of changes and save them, I confirm the file got updated too, I reloaded openLuup, still having my changes...

The only little issue I have it's a cache issue, when I change a rule, save it, re-open it, sometime it's the old version BUT the file timestamp is newer and opening a new browser show me the right version.

so there's something in your last openLuup version Feb 29 that fixed that too

[akbooer]

You only get that lucky once in every four years!