Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
D

Donato

@Donato
openLuup console disappeared - 500 - Internal Server Error
A
Love openLuup - it just keeps working perfectly. I started looking at trying to add a gen4 Shelly device to the Shelly plugin via L_ShellyBridge.lua. The plugin is a little uncooked (no rudeness intended), so a bit of a rabbit hole for me. All of a sudden no console pages available in either Firefox or Chrome. AltUI works perfectly and all the log files indicate no errors. openLuup still running everything works as it should - just no console pages. I possibly screwed something up but any recently changes files show no problems. The original/ backup of L_ShellyBridge.lua was reinstated but still no console. Bit stumped on this one. Not sure how to debug. Any ideas?
Plugins
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
Ezlo Paid Subscription for Vera Cloud Services
toggledbitsT
It appears that Ezlo is going to new levels of paid subscription for cloud services supporting Vera hubs. I have to congratulate them. It will soon be 8 years since Ezlo acquired Vera, and despite their purported financial and "intellectual" capital, they have to date not produced a viable full replacement for Vera. Now they are going to charge extra for services for a platform that they stopped updating years ago. If you know anyone who hasn't yet fully moved on from Captain Ahab's White Whale Chase, please remind them that my Decouple project is still up on Github to decouple a Vera Plus/Secure/Edge from Vera/Ezlo's cloud services. Veras have been said to misbehave when they can't reach the mother ship. I have also written my first new Vera plugin in... six years? more?... the AlertPushover project will send Vera hub alerts to Pushover, so you can still get messages generated by your Vera hub without paying for Ezlo's cloud service. It's crude but functional (i.e. better than nothing/worth every penny paid). These two projects won't replace the functionality of their cloud service and app for those who need those things. But any that don't, this may help bridge the gap. Hopefully these stragglers who have waited so long and been disappointed so often will get the idea that it's time to move on.
General Discussion
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
[Solved] build 26150 - engine not starting
G
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline. The log looks like it ends with 26143. [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Multi-System Reactor
Farewell, oh good and faithful servant!
CatmanV2C
Today marks another milestone in my Home Automation journey. After tripping the main breaker once, and shedding more blood than is normally recommended, the underfloor heating (which was the last Z-wave device on my system) has been replaced with a Zigbee one. Edited reactor.conf Disabled z-way-server Disabled Openluup Z-wave is no more.... C
General Discussion
http request action & digest auth
tunnusT
I’m using the HTTP Request action in MSR and need to authenticate against an endpoint that uses HTTP Digest authentication. Now that endpoint was changed to use SHA-256 in digest auth, so I would like to know if MSR supports it, or is it limited to MD5-based digest auth?
Multi-System Reactor
Cloning actions in reactions does not work
tunnusT
With build 26140 (on Docker) I'm not able to clone any actions in reactions. Using Chrome if it has any relevance.
Multi-System Reactor
Has ping command been removed?
tunnusT
Topic thumbnail image
Multi-System Reactor
ReferenceError with Home Assistant data & build 26140
tunnusT
Topic thumbnail image
Multi-System Reactor
About
Posts
39
Topics
2
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial

  • openLuup log files - LuaUPnP.log and LuaUPnP_startup.log
    D Donato

    @akbooer

    here in the community app in the reply box

    openLuup

  • openLuup log files - LuaUPnP.log and LuaUPnP_startup.log
    D Donato

    @akbooer

    in my actual user_data file double quotes are preceded by \.

    when I paste the file as text and submit the reply here the \ symbol is eliminated .

    Following I paste as code :

    "StartupCode":"\n-- You can personalise the installation by changing these attributes,\n-- which are persistent and may be removed from the Startup after a reload.\nlocal attr = luup.attr_set\n\n-- Geographical location\nattr (\"City_description\", \"Rome\")\nattr (\"Country_description\", \"Italy\")\nattr (\"Region_description\", \"Lazio\")\nattr (\"latitude\", \"51.48\")\nattr (\"longitude\", \"0.0\")\n\n-- other parameters\nattr (\"TemperatureFormat\", \"C\")\nattr (\"PK_AccessPoint\", \"99000007\")\nattr (\"currency\", \"£\")\nattr (\"date_format\", \"dd/mm/yy\")\nattr (\"model\", \"Not a Vera\")\nattr (\"timeFormat\", \"24hr\")\n\n-- Any other startup processing may be inserted here...\nluup.log \"startup code completed\"\n\n",
    
    

    sorry for my error

    openLuup

  • openLuup log files - LuaUPnP.log and LuaUPnP_startup.log
    D Donato

    @akbooer

    attached a copy of startup lua

    startlua.png

    and the few lines around the error :

    "Mode":"1",
    "ModeSetting":"1:DC*;2:DC*;3:DC*;4:DC*",
    "PK_AccessPoint":"99000007",
    "Region_description":"Lazio",
    "ShutdownCode":"",
    "StartupCode":"\n-- You can personalise the installation by changing these attributes,\n-- which are persistent and may be removed from the Startup after a reload.\nlocal attr = luup.attr_set\n\n-- Geographical location\nattr ("City_description", "Rome")\nattr ("Country_description", "Italy")\nattr ("Region_description", "Lazio")\nattr ("latitude", "51.48")\nattr ("longitude", "0.0")\n\n-- other parameters\nattr ("TemperatureFormat", "C")\nattr ("PK_AccessPoint", "99000007")\nattr ("currency", "£")\nattr ("date_format", "dd/mm/yy")\nattr ("model", "Not a Vera")\nattr ("timeFormat", "24hr")\n\n-- Any other startup processing may be inserted here...\nluup.log "startup code completed"\n\n",
    "TemperatureFormat":"C",
    "ThousandsSeparator":",",
    "currency":"£",
    "date_format":"dd/mm/yy",

    openLuup

  • openLuup log files - LuaUPnP.log and LuaUPnP_startup.log
    D Donato

    @a-lurker

    the 176 line above is inside the user_data file and every parameter is separated by "," . Following some lines around 176 :

    "Region_description":"Lazio",
    "ShutdownCode":"",
    "StartupCode":"\n-- You can personalise the installation by changing these attributes,\n-- which are persistent and may be removed from the Startup after a reload.\nlocal attr = luup.attr_set\n\n-- Geographical location\nattr ("City_description", "Rome")\nattr ("Country_description", "Italy")\nattr ("Region_description", "Lazio")\nattr ("latitude", "51.48")\nattr ("longitude", "0.0")\n\n-- other parameters\nattr ("TemperatureFormat", "C")\nattr ("PK_AccessPoint", "99000007")\nattr ("currency", "£")\nattr ("date_format", "dd/mm/yy")\nattr ("model", "Not a Vera")\nattr ("timeFormat", "24hr")\n\n-- Any other startup processing may be inserted here...\nluup.log "startup code completed"\n\n",
    "TemperatureFormat":"C",
    "ThousandsSeparator":",",

    openLuup

  • openLuup log files - LuaUPnP.log and LuaUPnP_startup.log
    D Donato

    @akbooer

    This is the line 176 of User_Data Json file :

    "StartupCode":"\n-- You can personalise the installation by changing these attributes,\n-- which are persistent and may be removed from the Startup after a reload.\nlocal attr = luup.attr_set\n\n-- Geographical location\nattr ("City_description", "Rome")\nattr ("Country_description", "Italy")\nattr ("Region_description", "Lazio")\nattr ("latitude", "51.48")\nattr ("longitude", "0.0")\n\n-- other parameters\nattr ("TemperatureFormat", "C")\nattr ("PK_AccessPoint", "99000007")\nattr ("currency", "£")\nattr ("date_format", "dd/mm/yy")\nattr ("model", "Not a Vera")\nattr ("timeFormat", "24hr")\n\n-- Any other startup processing may be inserted here...\nluup.log "startup code completed"\n\n",

    I modify these parameter through the console openluup app and these are the values :

    -- You can personalise the installation by changing these attributes,
    -- which are persistent and may be removed from the Startup after a reload.
    local attr = luup.attr_set

    -- Geographical location
    attr ("City_description", "Rome")
    attr ("Country_description", "Italy")
    attr ("Region_description", "Lazio")
    attr ("latitude", "51.48")
    attr ("longitude", "0.0")

    -- other parameters
    attr ("TemperatureFormat", "C")
    attr ("PK_AccessPoint", "99000007")
    attr ("currency", "£")
    attr ("date_format", "dd/mm/yy")
    attr ("model", "Not a Vera")
    attr ("timeFormat", "24hr")

    -- Any other startup processing may be inserted here...
    luup.log "startup code completed"

    Is there any error ?

    tnks

    openLuup

  • openLuup log files - LuaUPnP.log and LuaUPnP_startup.log
    D Donato

    Hi akbooer,

    sometimes openluup restore the file user_data.json to the default and I need to restore the configured one. I notice in the LuaUPnP_startup.log these msgs :

    2024-07-18 07:46:19.585   :: openLuup STARTUP :: /etc/cmh-ludl
    2024-07-18 07:46:19.586   openLuup.init::        version 2022.11.28  @akbooer
    2024-07-18 07:46:19.595   openLuup.scheduler::   version 2021.03.19  @akbooer
    2024-07-18 07:46:19.723   openLuup.io::          version 2021.03.27  @akbooer
    2024-07-18 07:46:19.723   openLuup.mqtt::        version 2022.12.16  @akbooer
    2024-07-18 07:46:19.727   openLuup.wsapi::       version 2023.02.10  @akbooer
    2024-07-18 07:46:19.727   openLuup.servlet::     version 2021.04.30  @akbooer
    2024-07-18 07:46:19.727   openLuup.client::      version 2019.10.14  @akbooer
    2024-07-18 07:46:19.729   openLuup.server::      version 2022.08.14  @akbooer
    2024-07-18 07:46:19.737   openLuup.scenes::      version 2023.03.03  @akbooer
    2024-07-18 07:46:19.750   openLuup.chdev::       version 2022.11.05  @akbooer
    2024-07-18 07:46:19.750   openLuup.userdata::    version 2021.04.30  @akbooer
    2024-07-18 07:46:19.751   openLuup.requests::    version 2021.02.20  @akbooer
    2024-07-18 07:46:19.751   openLuup.gateway::     version 2021.05.08  @akbooer
    2024-07-18 07:46:19.757   openLuup.smtp::        version 2018.04.12  @akbooer
    2024-07-18 07:46:19.764   openLuup.historian::   version 2022.12.20  @akbooer
    2024-07-18 07:46:19.764   openLuup.luup::        version 2023.01.06  @akbooer
    2024-07-18 07:46:19.767   openLuup.pop3::        version 2018.04.23  @akbooer
    2024-07-18 07:46:19.768   openLuup.compression:: version 2016.06.30  @akbooer
    2024-07-18 07:46:19.768   openLuup.timers::      version 2021.05.23  @akbooer
    2024-07-18 07:46:19.769   openLuup.logs::        version 2018.03.25  @akbooer
    2024-07-18 07:46:19.769   openLuup.json::        version 2021.05.01  @akbooer
    2024-07-18 07:46:19.774   luup.create_device:: [1] D_ZWaveNetwork.xml /  /    ()
    2024-07-18 07:46:19.774   openLuup.chdev:: ERROR: unable to read XML file I_ZWave.xml
    2024-07-18 07:46:19.800   luup.create_device:: [2] D_openLuup.xml / I_openLuup.xml / D_openLuup.json   (openLuup)
    2024-07-18 07:46:19.800   openLuup.init:: loading configuration user_data.json
    2024-07-18 07:46:19.801   openLuup.userdata:: loading user_data json...
    2024-07-18 07:46:19.805   openLuup.userdata:: JSON decode error @[8173 of 8192, line: 176] unterminated string
       ' = luup.attr_set\n\n   <<<HERE>>>   -- Geographical loca'
    2024-07-18 07:46:19.805   openLuup.userdata:: ...user_data loading completed
    2024-07-18 07:46:19.805   openLuup.init:: running _openLuup_STARTUP_
    2024-07-18 07:46:19.805   luup_log:0: startup code completed
    2024-07-18 07:46:19.806   openLuup.init:: init phase completed
    2024-07-18 07:46:19.806   :: openLuup LOG ROTATION :: (runtime 0.0 days)
    

    Is this a my error in some configuration files ?

    tnks

    openLuup

  • Openluup: Datayours
    D Donato

    Hi akbooer,

    excuse me for late answer. Tnks for your precious support as usual.
    I'll test your code asap.
    A question for my clarity: does the routine register only a value every minute in the whisper file (average of values in a minute) ? Are the different values in a minute momentarily memorized in a DY cache ?

    tnks

    Plugins

  • Openluup: Datayours
    D Donato

    Yes, but all the variables with the name "Variable" (local target = "Variable")

    Plugins

  • Openluup: Datayours
    D Donato

    In my installation sensors measure at least a value every 20/30s (in my case is electric power) and I'd like to register the average value every minute (if possible).
    Can I change the retention schemas of the actual whisper files without loosing the actual data or do I have to start from zero?

    Over hour and daily period the aggregation is different for the whisper files created by L_DataUser routine :

    [Power_Daily_DataWatcher]
    pattern = .kwdaily
    xFilesFactor = 0
    aggregationMethod = sum
    [Power_Hourly_DataWatcher]
    pattern = .kwhourly
    xFilesFactor = 0
    aggregationMethod = sum
    [Power_MaxHourly_DataWatcher]
    pattern = .kwmaxhourly
    xFilesFactor = 0
    aggregationMethod = max

    For the "Variable" whisper files seems correct the average calculation for 5m, 10m, 1h .. etc based on :

    retentions = 1m:1d,5m:90d,10m:180d,1h:2y,1d:10y

    and the value registered every minute.

    Plugins

  • Openluup: Datayours
    D Donato

    Hi akbooer,

    tnks now things is going well for me too.

    You wrote for me the following L_DataUser.lua that I'm using :

    local function run (metric, value, time) 
    
      local target = "Variable"
      local names = {"kwdaily", "kwhourly", "kwmaxhourly"}
    
      local metrics = {metric}
      for i, name in ipairs (names) do
        local x,n = metric: gsub (target, name)
        metrics[#metrics+1] = n>0 and x or nil
      end
    
      local i = 0
     
      return function ()
        i = i + 1
        return metrics[i], value, time
      end
    end
    
    return {run = run}
    

    that write for every value of "Variablex" variable to other whisper files with different aggregation and schemas.

    Plugins

  • Openluup: Datayours
    D Donato

    Hi akbooer,
    i hope all is well.

    I've a question about datayours and the aggregation e schemas parameters.
    I've these configurations :

    1. aggregation :
      [Power_Calcolata_Kwatt]
      pattern = .Variable
      xFilesFactor = 0
      aggregationMethod = average

    2. schemas:
      [Power_Calcolata_Kwatt]
      pattern = .Variable
      retentions = 1m:1d,5m:90d,10m:180d,1h:2y,1d:10y

    In the cache history of openluup console for example i see these values :

    2024-06-27 09:17:57 46.73
    2024-06-27 09:17:25 16.55

    and in the whisper file (it contains a point every minute) i see :

    1719472620, 46.73 (17119472620 is 09.17 time for my zone)

    It seems that is considered the last value and not the average of two value registered at 9.17 time.

    Is it correct ?

    tnks

    donato

    Plugins

  • Openluup: Datayours
    D Donato

    @akbooer
    Hi akbooer, I've simulated on a test installation a network outage of the remote DY and I've produced two sets of whisper files : one updated (remote DY) and the other one to update (central DY) if possible with a routine similar to Whisper-fill.py from Graphite tool.
    In the files I'll send you by email you find :

    1. whisper file Updated ;
    2. whisper file To Update ;
    3. L_DataUser.lua used for both that processes and creates different metric names;
    4. Storage-aggregation.conf and Storage-schema.conf files.
      I remain at your disposal for any clarification.

    tnks

    donato

    Plugins

  • Openluup: Datayours
    D Donato

    @akbooer excuse me how can i send you the schema ?

    Plugins

  • Openluup: Datayours
    D Donato

    @akbooer
    a stand-alone command line utility is ok possibly with the option to indicate a date interval. The files to fill for a remote DY may be more than one all with the same Openluup/Whisper ID.
    At the moment I haven't an example of files to fill . I'll simulate a network outage so I produce the files.

    Can I send you meanwhile the schema to verify if the openluup/DY configuration remote and centralized are correct (destinations, udp receiver ports, line receiver port)

    tnks

    donato

    Plugins

  • Openluup: Datayours
    D Donato

    Hi akbooer,

    I've an installation with a centralized openluup/DY on Debian 11 where're archived and consolidated several remote openluup/DY on RPI. I'm also using a user-defined (defined with your support) "DataUser.lua" to process metrics and creating different metric names. I've a schema of this configuration but I can't upload on forum.
    I'd like to manage outage network connections between remote and centralized system while the remote DY is running and archives data locally.
    I see the whisper-fill.py python routine (https://github.com/graphite-project/whisper/blob/master/bin/whisper-fill.py) from Graphite tool. I know that DY/whisper format is different from Graphite/whisper (CSV vs. binary packing), but based on your deep knowledge and experience is it hard to adapt the fill routine to DY/whisper format ?

    tnks

    donato

    Plugins

  • Unexpected stop of openLuup
    D Donato

    tnks akbooer for your fix.

    About VPN, my server is on a cloud hosting and the web app is accessed by authenticated users so I suppose the only solution is to activate some fw rule on the openluup/datayours server.

    openLuup

  • Unexpected stop of openLuup
    D Donato

    Hi akbooer,

    in order to set firewall rules can you give me some info on the openluup log records ? Following there are few normal log lines of datayours read/write :

    2022-08-13 12:52:21.921 luup.variable_set:: 4.urn:akbooer-com:serviceId:DataYours1.AppMemoryUsed was: 6568 now: 6871 #hooks:0
    2022-08-13 12:52:26.570 openLuup.io.server:: HTTP:3480 connection from xx.xx.xx.xx tcp{client}: 0x556c474b0348
    2022-08-13 12:52:26.571 openLuup.server:: GET /data_request?id=lr_render&target=Vera-yyyyyyyy.024.urn:upnp-org:serviceId:VContainer1.Variable3&from=-2h&format=json HTTP/1.1 tcp{client}: 0x556c474b0348
    2022-08-13 12:52:26.571 luup_log:4: DataGraph: Whisper query: CPU = 0.405 mS for 121 points
    2022-08-13 12:52:26.572 openLuup.server:: request completed (3359 bytes, 1 chunks, 1 ms) tcp{client}: 0x556c474b0348
    2022-08-13 12:52:26.572 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x556c474b0348
    2022-08-13 12:52:26.574 openLuup.io.server:: HTTP:3480 connection from xx.xx.xx.xx tcp{client}: 0x556c47810548
    2022-08-13 12:52:26.574 openLuup.server:: GET /data_request?id=lr_render&target=Vera-yyyyyyyy.024.urn:upnp-org:serviceId:VContainer1.Variable3&from=2022-08-13T00:00&format=json HTTP/1.1 tcp{client}: 0x556c47810548
    2022-08-13 12:52:26.576 luup_log:4: DataGraph: Whisper query: CPU = 2.085 mS for 773 points
    2022-08-13 12:52:26.580 openLuup.server:: request completed (20228 bytes, 2 chunks, 6 ms) tcp{client}: 0x556c47810548
    2022-08-13 12:52:26.581 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x556c47810548
    2022-08-13 12:52:35.363 openLuup.io.server:: HTTP:3480 connection from xx.xx.xx.xx tcp{client}: 0x556c4756a4b8
    2022-08-13 12:52:35.364 openLuup.server:: GET /data_request?id=lr_render&target=Vera-yyyyyyyy.024.urn:upnp-org:serviceId:VContainer1.Variable3&from=-2h&format=json HTTP/1.1 tcp{client}: 0x556c4756a4b8
    2022-08-13 12:52:35.364 luup_log:4: DataGraph: Whisper query: CPU = 0.418 mS for 121 points
    2022-08-13 12:52:35.366 openLuup.server:: request completed (3359 bytes, 1 chunks, 1 ms) tcp{client}: 0x556c4756a4b8
    2022-08-13 12:52:35.366 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x556c4756a4b8
    2022-08-13 12:52:35.368 openLuup.io.server:: HTTP:3480 connection from xx.xx.xx.xx tcp{client}: 0x556c47294958
    2022-08-13 12:52:35.368 openLuup.server:: GET /data_request?id=lr_render&target=Vera-yyyyyyyy.024.urn:upnp-org:serviceId:VContainer1.kwdaily3&from=2016-07-01&format=json HTTP/1.1 tcp{client}: 0x556c47294958
    2022-08-13 12:52:35.375 luup_log:4: DataGraph: Whisper query: CPU = 6.521 mS for 2235 points
    2022-08-13 12:52:35.392 openLuup.server:: request completed (62445 bytes, 4 chunks, 23 ms) tcp{client}: 0x556c47294958
    2022-08-13 12:52:35.397 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x556c47294958
    2022-08-13 12:52:35.398 openLuup.io.server:: HTTP:3480 connection from xx.xx.xx.xx tcp{client}: 0x556c47158248
    2022-08-13 12:52:35.398 openLuup.server:: GET /data_request?id=lr_render&target=Vera-yyyyyyyy.024.urn:upnp-org:serviceId:VContainer1.Variable3&from=2022-08-13T00:00&format=json HTTP/1.1 tcp{client}: 0x556c47158248
    2022-08-13 12:52:35.401 luup_log:4: DataGraph: Whisper query: CPU = 2.409 mS for 773 points
    2022-08-13 12:52:35.406 openLuup.server:: request completed (20228 bytes, 2 chunks, 7 ms) tcp{client}: 0x556c47158248
    2022-08-13 12:52:35.406 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x556c47158248
    2022-08-13 12:53:26.581 openLuup.io.server:: HTTP:3480 connection from xx.xx.xx.xx tcp{client}: 0x556c4877f9d8
    2022-08-13 12:53:26.581 openLuup.server:: GET /data_request?id=lr_render&target=Vera-yyyyyyyy.024.urn:upnp-org:serviceId:VContainer1.Variable3&from=-2h&format=json HTTP/1.1 tcp{client}: 0x556c4877f9d8
    2022-08-13 12:53:26.582 luup_log:4: DataGraph: Whisper query: CPU = 0.735 mS for 121 points

    The read commands of whisper files are all of kind "http://server-ip:3480......."

    the following log record :
    openLuup.io.server:: HTTP:3480 connection from xx.xx.xx.xx tcp{client}
    is from a http read ?

    Can I see UDP write log record ?

    The write commands come from remote datayours through UDP to "server-ip" .

    All consolidated whisper files I read/write are on "server-ip".

    Is it correct in this scenario that all the regular and normal commands (read/write) must come from "server-ip" ?

    tnks

    openLuup

  • Unexpected stop of openLuup
    D Donato

    Hi akbooer,

    randomly openluup hangs but today I noticed in the log (attached) something strange :

    2022-08-13 12:54:35.283 openLuup.server:: GET /data_request?id=lr_render&target=Vera-45108342.024.urn:upnp-org:serviceId:VContainer1.Variable3&from=2022-08-13T00:00&format=json HTTP/1.1 tcp{client}: 0x556c471741f8
    2022-08-13 12:54:35.286 luup_log:4: DataGraph: Whisper query: CPU = 2.068 mS for 775 points
    2022-08-13 12:54:35.289 openLuup.server:: request completed (20282 bytes, 2 chunks, 6 ms) tcp{client}: 0x556c471741f8
    2022-08-13 12:54:35.290 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x556c471741f8
    2022-08-13 12:54:57.889 openLuup.io.server:: HTTP:3480 connection from 92.255.85.183 tcp{client}: 0x556c482cf138
    2022-08-13 12:54:57.889 openLuup.server:: /*: mstshash=Administr tcp{client}: 0x556c482cf138
    2022-08-13 12:54:57.889 openLuup.context_switch:: ERROR: [dev #0] ./openLuup/server.lua:238: attempt to concatenate local 'method' (a nil value)
    2022-08-13 12:54:57.889 luup.incoming_callback:: function: 0x556c4753ff20 ERROR: ./openLuup/server.lua:238: attempt to concatenate local 'method' (a nil value)

    at 12:54 openluup stopped to write and read the datayours files

    Is a possible attack ?

    openLuup

  • Help with Z-Way plugin
    D Donato

    Hi akbooer,

    I've defined in z-way controller a Virtual Device (a virtual binary switch) but I can't see it on openluup with z-way plugin installed while I can see a real switch.

    Is it correct ? Are the z-way virtual device using different API not implemented in openluup ?

    tnks

    donato

    Zway Bridge
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved