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.
S

sebby

@sebby
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
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
There is an alternative to homebridge-mqttthing
CrilleC
Just throwing out a general hint to the people running Homebridge and MQTT. Homebridge MQTT-Thing hasn't been updated in almost 2 years and it falls behind on compatibility with the development of Homebridge. I was looking for a replacement and found Homebridge Easy MQTT and I think it's a good replacement for MQTT-Thing. I particularly find Easy MQTT Value tranformers easier to to understand and use compared to MQTT-Thing Apply function. It took a while to migrate everything but I'm pleased and can recommend.
Software
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
Shelly Wall Display XL
therealdbT
I don't know if you guys are into dashboards, but I am. For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer. Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor. I also have a new build in the works with support for buttons inside HA. I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable). This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Hardware
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
Do you Matter?
akbooerA
Is anyone using the Matter protocol to connect devices?
General Discussion
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Caution: zwave-js-ui docker 11.4.0 is broken
toggledbitsT
About 20 hours ago, the author of zwave-js-ui posted build 11.4.0 of that product, and it contains an error and won't start (at all) under docker. The author is aware and working on a fix. In the meanwhile, stick with 11.3.1 or earlier. Ref: Issue 4401
Software
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
About
Posts
32
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Recommendation for new hub
    S sebby

    thanks all for the feedback. I will check out Hubitat and see how it does.

    Multi-System Reactor

  • Recommendation for new hub
    S sebby

    My trusty vera plus is starting to have some issues that are making me think that it is about to die. i now get constant luup reloads even though i've moved almost everything except for z-wave devices and the iphone locator off that machine. it is even booting off an ssd drive to minimize wear and tear on the internal memory. I've moved all my logic off box to MSR, so it is just a glorified zwave adapter. I would love to hear any ideas that would make moving 60ish devices off that box to something else as painless as possible. the thought of excluding and including the devices sends shivers down my spine, so anything that helps me migrate the network would be greatly welcomed. anyone have any suggestions?

    Multi-System Reactor

  • Set Entity value in expression?
    S sebby
    • The performAction() expression function will perform an action from an expression. If you have an object stored in a variable old_status that contains data like this: [ { id: "vera>Livingroom Fan", status: true }, { id: "vera>Loft Fan", status: false }, { id: "vera>Office Fan", status: true } ], then you can set those statuses in one expression: each d in old_status: performAction( d.id, "power_switch.set", d.status )

    This is exactly what i was looking for! thank you!!!!!! i was looking at the docs and completely glossed over that section...

    Multi-System Reactor

  • Set Entity value in expression?
    S sebby

    no rush, i was able to work around it by inserting the status of the fans as a number:

    {
    "Livingroom Fan" : getEntity("vera>Livingroom Fan").attributes.power_switch.state == false ? 0 : 1, 
    "Loft Fan" : getEntity("vera>Loft Fan").attributes.power_switch.state == false ? 0 : 1, 
    "Office Fan" : getEntity("vera>Office Fan").attributes.power_switch.state == false ? 0 : 1
    }
    

    then used the SetTarget entity action to turn them on or off.

    Multi-System Reactor

  • Set Entity value in expression?
    S sebby

    @sebby Screen Shot 2021-08-06 at 8.59.30 PM.png

    Multi-System Reactor

  • Set Entity value in expression?
    S sebby

    Hi Rigpapa, I updated the build, the variable is a drop-down with only the true/false option and not a variable that can be substituted. do i need to do something else to make it a string entry?

    Multi-System Reactor

  • Set Entity value in expression?
    S sebby

    wow, thank you so much for that, as always greatly appreciated.

    Multi-System Reactor

  • Set Entity value in expression?
    S sebby

    Thanks guys, my problem seems to be even more basic than all of that. what i cannot figure out is the "service" variable to use for the specific actions. I hope this image works, have tried everything i can think of to make it readable to all.

    Screen Shot 2021-08-06 at 4.24.56 PM.png

    Multi-System Reactor

  • Set Entity value in expression?
    S sebby

    I get that, but the power_switch service only has on or off. I am trying to set it from a stored variable, so i don't know if it is on or off to begin, hence my attempt to set it via the SwitchPower1.SetTarget.

    Multi-System Reactor

  • Set Entity value in expression?
    S sebby

    @toggledbits said in Set Entity value in expression?:

    I can't see anything in the screen shot, it's too low res.

    You have to run an action to set the state of a device. Attributes are generally echoes of device state, but you don't modify them directly, just like on Vera (setting a state variable on Vera doesn't change the device, running an action changes the device and updates the state variable).

    Gotcha, and thanks for the explanation. I guess the question would be, is there a way to trigger an action from an expression? Also, kind of related, but what service would i use in set_variable in order to act on x_vera_svc_upnp_org_SwitchPower1.SetTarget? i've tried x_vera_svc_upnp_org_SwitchPower1, vera_svc_upnp_org_SwitcPower1, svc_upnp_org_SwitchPower1 and all combinations i could think of.

    Screen Shot 2021-08-06 at 12.54.42 PM.png

    Multi-System Reactor

  • Set Entity value in expression?
    S sebby

    @sebby Screen Shot 2021-08-06 at 10.06.43 AM.png the object that i am looking at is an expression that gets the current status of all fans (CurrentFanStatus). When the AC kicks off, i copy the current fan status to another variable (lastFanStatus) so i can re-set the fans to what they were set at originally (i.e. if the Office fan was running, i don't want the reset reaction to turn it off. I figure i can set the values from thee object, via the set_variable (as in the image above), but was just wondering if there was a better way to iterate through my object and set the values for the corresponding fans since i have the entity name and the status.

    EDIT: I guess what i am looking for is a setEntity that i may be able to issue from an expression. does that exist?

    Multi-System Reactor

  • Set Entity value in expression?
    S sebby

    Not sure if i am asking this correctly, but here it goes... I am trying to make the ceiling fans run if the AC unit is running for more than a few minutes. That part is easy and done. Now, what i really want to do is that when the AC kicks off, the fans go back to whatever state they were at before they kicked on. I have an expression that captures the before status into a variable, but now i am racking my brain trying to figure out how to iterate through that array (really an object with "fan name" : status) and set the fan variables. I can do it manually via the set_variable for each entity, but I would think there should be an easier way with an expression since i have everything i need to set the values in the object. is there a better way?

    Multi-System Reactor

  • Import question
    S sebby

    FYI, the new release worked like a charm, than you

    Multi-System Reactor

  • Feature Request - Reaction to MQTT
    S sebby
    Multi-System Reactor

  • Import question
    S sebby

    ok, done. very low priority as I'd rather you spend time polishing the builds than dealing with my clusterf**k.

    Multi-System Reactor

  • Feature Request - Reaction to MQTT
    S sebby

    awesome and thanks! sorry for spamming the boards.

    Multi-System Reactor

  • Import question
    S sebby

    having some issues importing, my guess is that my reactors on vera are a complete disaster, but thought i would ask:

    /opt/reactor # node tools/import_reactor_backup.js tools/reactor-config-backup_so.json vera
    Fetching current rulesets...
    Pass 1: Translating...
    ReactorSensor 182 RS-AUTO HOME MODE
    Creating ruleset for ReactorSensor 182 RS-AUTO HOME MODE
    Creating rule rule-182
    (node:3881) UnhandledPromiseRejectionWarning: TypeError: (node.data.value || "").split is not a function
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:94:53)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    (Use node --trace-warnings ... to show where the warning was created)
    (node:3881) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
    (node:3881) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

    /opt/reactor # node --trace-warnings tools/import_reactor_backup.js tools/reactor-config-backup_so.json vera
    Fetching current rulesets...
    Pass 1: Translating...
    ReactorSensor 182 RS-AUTO HOME MODE
    Creating ruleset for ReactorSensor 182 RS-AUTO HOME MODE
    Creating rule rule-182
    (node:3898) UnhandledPromiseRejectionWarning: TypeError: (node.data.value || "").split is not a function
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:94:53)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at emitUnhandledRejectionWarning (internal/process/promises.js:168:15)
    at processPromiseRejections (internal/process/promises.js:247:11)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)
    (node:3898) TypeError: (node.data.value || "").split is not a function
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:94:53)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    at /opt/reactor/tools/import_reactor_backup.js:44:13
    at Array.forEach (<anonymous>)
    at fixConditions1 (/opt/reactor/tools/import_reactor_backup.js:41:35)
    (node:3898) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    at emitDeprecationWarning (internal/process/promises.js:180:11)
    at processPromiseRejections (internal/process/promises.js:249:13)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)

    Multi-System Reactor

  • Feature Request - Reaction to MQTT
    S sebby

    I looked through the forum, but could not find it, so my apologies if this has been asked. It would be nice to be able to push a message to MQTT for further upstream integrations.

    Multi-System Reactor

  • iPhoneLocator: Alternate Map Servers
    S sebby

    could it be that it is getting confused because it is loading the iphone locator devices from the old vera?

    2020-10-05 20:37:28.841 luup.create_device:: [10025] D_IPhone.xml / X / D_IPhone_UI7.json (urn:schemas-upnp-org:device:IPhoneLocator:1)
    2020-10-05 20:37:28.850 luup.create_device:: [10026] D_IPhone.xml / X / D_IPhone_UI7.json (urn:schemas-upnp-org:device:IPhoneLocator:1)

    Plugins

  • iPhoneLocator: Alternate Map Servers
    S sebby

    the previous log was with the standard iphone locator plugin enabled, i removed it, re-copied the files from rafale's repo and this is the new startup after those changes

    2020-10-01 13:06:54.633 :: openLuup STARTUP :: /etc/cmh-ludl
    2020-10-01 13:06:54.633 openLuup.init:: version 2020.05.01 @akbooer
    2020-10-01 13:06:54.682 openLuup.scheduler:: version 2020.01.25 @akbooer
    2020-10-01 13:06:54.726 openLuup.wsapi:: version 2019.08.12 @akbooer
    2020-10-01 13:06:54.726 openLuup.servlet:: version 2020.01.29 @akbooer
    2020-10-01 13:06:54.727 openLuup.client:: version 2019.10.14 @akbooer
    2020-10-01 13:06:54.731 openLuup.io:: version 2019.11.29 @akbooer
    2020-10-01 13:06:54.731 openLuup.server:: version 2020.03.20 @akbooer
    2020-10-01 13:06:54.742 openLuup.scenes:: version 2020.03.16 @akbooer
    2020-10-01 13:06:54.749 openLuup.chdev:: version 2020.03.07 @akbooer
    2020-10-01 13:06:54.749 openLuup.userdata:: version 2020.03.31 @akbooer
    2020-10-01 13:06:54.750 openLuup.requests:: version 2020.04.15 @akbooer
    2020-10-01 13:06:54.751 openLuup.gateway:: version 2020.03.08 @akbooer
    2020-10-01 13:06:54.757 openLuup.smtp:: version 2018.04.12 @akbooer
    2020-10-01 13:06:54.766 openLuup.historian:: version 2020.02.12 @akbooer
    2020-10-01 13:06:54.766 openLuup.luup:: version 2020.03.21 @akbooer
    2020-10-01 13:06:54.769 openLuup.pop3:: version 2018.04.23 @akbooer
    2020-10-01 13:06:54.770 openLuup.compression:: version 2016.06.30 @akbooer
    2020-10-01 13:06:54.770 openLuup.timers:: version 2019.05.03 @akbooer
    2020-10-01 13:06:54.770 openLuup.logs:: version 2018.03.25 @akbooer
    2020-10-01 13:06:54.770 openLuup.json:: version 2020.05.20 @akbooer
    2020-10-01 13:06:54.770 openLuup.init:: using Cjson 2.1.0 for fast decoding
    2020-10-01 13:06:54.887 luup.create_device:: [1] D_ZWaveNetwork.xml / I_ZWave.xml / (urn:schemas-micasaverde-com:device:ZWaveNetwork:1)
    2020-10-01 13:06:54.918 luup.create_device:: [2] D_openLuup.xml / I_openLuup.xml / D_openLuup.json (openLuup)
    2020-10-01 13:06:54.919 openLuup.init:: loading configuration user_data.json
    2020-10-01 13:06:54.932 openLuup.userdata:: loading user_data json...
    2020-10-01 13:06:55.020 luup.variable_set:: 2.openLuup.HouseMode was: EMPTY now: 1 #hooks:0
    2020-10-01 13:06:55.021 openLuup.userdata:: loading rooms...
    2020-10-01 13:06:55.021 openLuup.userdata:: room#1 'MiOS-50001615'
    2020-10-01 13:06:55.021 openLuup.userdata:: room#101 'Room 101'
    2020-10-01 13:06:55.021 openLuup.userdata:: ...room loading completed
    2020-10-01 13:06:55.021 openLuup.userdata:: loading devices...
    2020-10-01 13:06:55.028 luup.create_device:: [1] D_ZWaveNetwork.xml / X / (urn:schemas-micasaverde-com:device:ZWaveNetwork:1)
    2020-10-01 13:06:55.218 openLuup.scheduler.sandbox:: device 3 defined 'string.starts' (a function value)
    2020-10-01 13:06:55.218 openLuup.scheduler.sandbox:: device 3 defined 'string.altui_split' (a function value)
    2020-10-01 13:06:55.218 openLuup.scheduler.sandbox:: device 3 defined 'string.template' (a function value)
    2020-10-01 13:06:55.219 openLuup.scheduler.sandbox:: device 3 defined 'string.trim' (a function value)
    2020-10-01 13:06:55.219 luup.create_device:: [3] D_ALTUI.xml / I_ALTUI.xml / D_ALTUI_UI7.json (urn:schemas-upnp-org:device:altui:1)
    2020-10-01 13:06:55.236 luup.create_device:: [4] D_AltAppStore.xml / I_AltAppStore.xml / D_AltAppStore.json (urn:schemas-upnp-org:device:AltAppStore:1)
    2020-10-01 13:06:55.260 luup.create_device:: [5] D_VeraBridge.xml / I_VeraBridge.xml / D_VeraBridge.json (VeraBridge)
    2020-10-01 13:06:55.370 luup.create_device:: [6] D_Reactor.xml / I_Reactor.xml / D_Reactor_UI7.json (urn:schemas-toggledbits-com:device:Reactor:1)
    2020-10-01 13:06:55.437 luup.create_device:: [8] D_DeusExMachinaII1.xml / I_DeusExMachinaII1.xml / D_DeusExMachinaII1_UI7.json (urn:schemas-toggledbits-com:device:DeusExMachinaII:1)
    2020-10-01 13:06:55.501 luup.create_device:: [9] D_SiteSensor1.xml / I_SiteSensor1.xml / D_SiteSensor1.json (urn:schemas-toggledbits-com:device:SiteSensor:1)
    2020-10-01 13:06:55.504 luup.create_device:: [10] D_BroadLink_Mk2_1.xml / / ()
    2020-10-01 13:06:55.504 openLuup.chdev:: ERROR: unable to read XML file D_BroadLink_Mk2_1.xml
    2020-10-01 13:06:55.575 luup.create_device:: [11] D_Switchboard1.xml / I_Switchboard1.xml / D_Switchboard1_UI7.json (urn:schemas-toggledbits-com:device:Switchboard:1)
    2020-10-01 13:06:55.614 luup.create_device:: [12] D_ReactorSensor.xml / / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:55.686 openLuup.scheduler.sandbox:: device 25 defined 'string.mytemplate' (a function value)
    2020-10-01 13:06:55.686 openLuup.scheduler.sandbox:: device 25 defined 'string.trim' (a function value)
    2020-10-01 13:06:55.687 luup.create_device:: [25] D_IPhone.xml / I_IPhone.xml / D_IPhone_UI7.json (urn:schemas-upnp-org:device:IPhoneLocator:1)
    2020-10-01 13:06:55.725 luup.create_device:: [10002] D_ZigbeeNetwork.xml / X / (urn:schemas-micasaverde-com:device:ZigbeeNetwork:1)
    2020-10-01 13:06:55.740 luup.create_device:: [10003] D_BluetoothNetwork.xml / X / (urn:schemas-micasaverde-com:device:BluetoothNetwork:1)
    2020-10-01 13:06:55.751 luup.create_device:: [10004] D_SceneController1.xml / X / D_SceneController1.json (urn:schemas-micasaverde-com:device:SceneController:1)
    2020-10-01 13:06:55.755 luup.create_device:: [10005] D_SmartHomeHelper.xml / X / (urn:schemas-upnp-org:device:GoogleHome:1)
    2020-10-01 13:06:55.870 luup.create_device:: [10006] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:55.883 luup.create_device:: [10007] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:55.893 luup.create_device:: [10008] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:55.903 luup.create_device:: [10009] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:55.913 luup.create_device:: [10012] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:55.923 luup.create_device:: [10013] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:55.936 luup.create_device:: [10017] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:55.948 luup.create_device:: [10018] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:55.958 luup.create_device:: [10020] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:55.969 luup.create_device:: [10021] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:55.981 luup.create_device:: [10023] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:55.990 luup.create_device:: [10025] D_IPhone.xml / X / D_IPhone_UI7.json (urn:schemas-upnp-org:device:IPhoneLocator:1)
    2020-10-01 13:06:56.000 luup.create_device:: [10026] D_IPhone.xml / X / D_IPhone_UI7.json (urn:schemas-upnp-org:device:IPhoneLocator:1)
    2020-10-01 13:06:56.012 luup.create_device:: [10028] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:56.023 luup.create_device:: [10029] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:56.216 luup.create_device:: [10030] D_HVAC_ZoneThermostat1.xml / X / D_HVAC_ZoneThermostat2.json (urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1)
    2020-10-01 13:06:56.226 luup.create_device:: [10031] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1)
    2020-10-01 13:06:56.236 luup.create_device:: [10032] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1)
    2020-10-01 13:06:56.255 luup.create_device:: [10034] D_HVAC_ZoneThermostat1.xml / X / D_HVAC_ZoneThermostat2.json (urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1)
    2020-10-01 13:06:56.264 luup.create_device:: [10035] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1)
    2020-10-01 13:06:56.269 luup.create_device:: [10036] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1)
    2020-10-01 13:06:56.276 luup.create_device:: [10039] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.284 luup.create_device:: [10107] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.293 luup.create_device:: [10108] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.301 luup.create_device:: [10109] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.309 luup.create_device:: [10110] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.384 luup.create_device:: [10118] D_DoorLock1.xml / X / D_DoorLock1.json (urn:schemas-micasaverde-com:device:DoorLock:1)
    2020-10-01 13:06:56.391 luup.create_device:: [10119] D_DoorLock1.xml / X / D_DoorLock1.json (urn:schemas-micasaverde-com:device:DoorLock:1)
    2020-10-01 13:06:56.399 luup.create_device:: [10121] D_DoorLock1.xml / X / D_DoorLock1.json (urn:schemas-micasaverde-com:device:DoorLock:1)
    2020-10-01 13:06:56.409 luup.create_device:: [10122] D_SiteSensor1.xml / X / D_SiteSensor1.json (urn:schemas-toggledbits-com:device:SiteSensor:1)
    2020-10-01 13:06:56.421 luup.create_device:: [10123] D_Switchboard1.xml / X / D_Switchboard1_UI7.json (urn:schemas-toggledbits-com:device:Switchboard:1)
    2020-10-01 13:06:56.428 luup.create_device:: [10125] D_SiteSensor1.xml / X / D_SiteSensor1.json (urn:schemas-toggledbits-com:device:SiteSensor:1)
    2020-10-01 13:06:56.440 luup.create_device:: [10126] D_SiteSensor1.xml / X / D_SiteSensor1.json (urn:schemas-toggledbits-com:device:SiteSensor:1)
    2020-10-01 13:06:56.450 luup.create_device:: [10131] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.458 luup.create_device:: [10132] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.467 luup.create_device:: [10133] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.476 luup.create_device:: [10134] D_SiteSensor1.xml / X / D_SiteSensor1.json (urn:schemas-toggledbits-com:device:SiteSensor:1)
    2020-10-01 13:06:56.488 luup.create_device:: [10135] D_SiteSensor1.xml / X / D_SiteSensor1.json (urn:schemas-toggledbits-com:device:SiteSensor:1)
    2020-10-01 13:06:56.497 luup.create_device:: [10158] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.504 luup.create_device:: [10159] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.512 luup.create_device:: [10160] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.519 luup.create_device:: [10162] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.527 luup.create_device:: [10163] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.536 luup.create_device:: [10164] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.544 luup.create_device:: [10165] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.552 luup.create_device:: [10166] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.562 luup.create_device:: [10167] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:56.570 luup.create_device:: [10173] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.582 luup.create_device:: [10174] D_LightSensor1.xml / X / D_LightSensor1.json (urn:schemas-micasaverde-com:device:LightSensor:1)
    2020-10-01 13:06:56.589 luup.create_device:: [10175] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.597 luup.create_device:: [10181] D_Reactor.xml / X / D_Reactor_UI7.json (urn:schemas-toggledbits-com:device:Reactor:1)
    2020-10-01 13:06:56.607 luup.create_device:: [10182] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.618 luup.create_device:: [10183] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.628 luup.create_device:: [10184] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.638 luup.create_device:: [10185] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.648 luup.create_device:: [10186] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.658 luup.create_device:: [10187] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.670 luup.create_device:: [10188] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.679 luup.create_device:: [10189] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.689 luup.create_device:: [10190] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.700 luup.create_device:: [10191] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.711 luup.create_device:: [10192] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:56.720 luup.create_device:: [10196] D_DoorSensor1.xml / X / D_DoorSensor1.json (urn:schemas-micasaverde-com:device:DoorSensor:1)
    2020-10-01 13:06:56.728 luup.create_device:: [10198] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.739 luup.create_device:: [10199] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:56.747 luup.create_device:: [10203] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:56.755 luup.create_device:: [10204] D_SmokeSensor1.xml / X / D_SmokeSensor1.json (urn:schemas-micasaverde-com:device:SmokeSensor:1)
    2020-10-01 13:06:56.762 luup.create_device:: [10205] D_SmokeSensor1.xml / X / D_COSensor1_FirstAlert.json (urn:schemas-micasaverde-com:device:SmokeSensor:1)
    2020-10-01 13:06:56.798 luup.create_device:: [10206] D_SonosSystem1.xml / X / D_SonosSystem1.json (urn:schemas-toggledbits-com:device:SonosSystem:1)
    2020-10-01 13:06:57.374 luup.create_device:: [10207] D_Sonos1.xml / X / D_Sonos1_S21.json (urn:schemas-micasaverde-com:device:Sonos:1)
    2020-10-01 13:06:57.389 luup.create_device:: [10208] D_Sonos1.xml / X / D_Sonos1_S1.json (urn:schemas-micasaverde-com:device:Sonos:1)
    2020-10-01 13:06:57.404 luup.create_device:: [10209] D_Sonos1.xml / X / D_Sonos1_S16.json (urn:schemas-micasaverde-com:device:Sonos:1)
    2020-10-01 13:06:57.418 luup.create_device:: [10210] D_Sonos1.xml / X / D_Sonos1_S1.json (urn:schemas-micasaverde-com:device:Sonos:1)
    2020-10-01 13:06:57.433 luup.create_device:: [10211] D_Sonos1.xml / X / D_Sonos1_S14.json (urn:schemas-micasaverde-com:device:Sonos:1)
    2020-10-01 13:06:57.447 luup.create_device:: [10212] D_Sonos1.xml / X / D_Sonos1_S21.json (urn:schemas-micasaverde-com:device:Sonos:1)
    2020-10-01 13:06:57.462 luup.create_device:: [10213] D_Sonos1.xml / X / D_Sonos1_S1.json (urn:schemas-micasaverde-com:device:Sonos:1)
    2020-10-01 13:06:57.481 luup.create_device:: [10214] D_Sonos1.xml / X / D_Sonos1_S12.json (urn:schemas-micasaverde-com:device:Sonos:1)
    2020-10-01 13:06:57.510 luup.create_device:: [10218] D_UPnPProxy1.xml / X / D_UPnPProxy1.json (urn:schemas-futzle-com:device:UPnPProxy:1)
    2020-10-01 13:06:57.530 luup.create_device:: [10219] D_SceneControllerLED1.xml / X / D_SwitchboardSC_219.json (urn:schemas-micasaverde-com:device:SceneControllerLED:1)
    2020-10-01 13:06:57.591 luup.create_device:: [10220] D_VirtualSensor1.xml / X / D_VirtualSensor1.json (urn:schemas-toggledbits-com:device:VirtualSensor:1)
    2020-10-01 13:06:57.599 luup.create_device:: [10221] D_MotionSensor1.xml / X / D_MotionSensor1.json (urn:schemas-micasaverde-com:device:MotionSensor:1)
    2020-10-01 13:06:57.606 luup.create_device:: [10223] D_MotionSensor1.xml / X / D_MotionSensor1.json (urn:schemas-micasaverde-com:device:MotionSensor:1)
    2020-10-01 13:06:57.613 luup.create_device:: [10224] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.624 luup.create_device:: [10225] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:57.636 luup.create_device:: [10226] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:57.648 luup.create_device:: [10227] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:57.685 luup.create_device:: [10229] D_VeraAlexa1.xml / X / D_ComboDevice1.json (urn:bochicchio-com:device:VeraAlexa:1)
    2020-10-01 13:06:57.693 luup.create_device:: [10233] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.700 luup.create_device:: [10234] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.709 luup.create_device:: [10235] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.719 luup.create_device:: [10237] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:57.728 luup.create_device:: [10238] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.736 luup.create_device:: [10239] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.749 luup.create_device:: [10240] D_DimmableRGBLight1.xml / X / D_DimmableRGBLight1.json (urn:schemas-upnp-org:device:DimmableRGBLight:1)
    2020-10-01 13:06:57.752 luup.create_device:: [10241] / X / (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:57.753 luup.create_device:: [10242] / X / (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:57.753 luup.create_device:: [10243] / X / (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:57.761 luup.create_device:: [10246] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:57.768 luup.create_device:: [10247] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1)
    2020-10-01 13:06:57.775 luup.create_device:: [10248] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.787 luup.create_device:: [10249] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:57.796 luup.create_device:: [10250] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.806 luup.create_device:: [10251] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:57.815 luup.create_device:: [10252] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.821 luup.create_device:: [10253] D_SmokeSensor1.xml / X / D_SmokeSensor1.json (urn:schemas-micasaverde-com:device:SmokeSensor:1)
    2020-10-01 13:06:57.827 luup.create_device:: [10254] D_SmokeSensor1.xml / X / D_COSensor1_FirstAlert.json (urn:schemas-micasaverde-com:device:SmokeSensor:1)
    2020-10-01 13:06:57.839 luup.create_device:: [10255] D_DeusExMachinaII1.xml / X / D_DeusExMachinaII1_UI7.json (urn:schemas-toggledbits-com:device:DeusExMachinaII:1)
    2020-10-01 13:06:57.846 luup.create_device:: [10256] D_DoorSensor1.xml / X / D_DoorSensor1.json (urn:schemas-micasaverde-com:device:DoorSensor:1)
    2020-10-01 13:06:57.854 luup.create_device:: [10257] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1)
    2020-10-01 13:06:57.866 luup.create_device:: [10259] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:57.875 luup.create_device:: [10260] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.882 luup.create_device:: [10261] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.893 luup.create_device:: [10262] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:57.905 luup.create_device:: [10263] D_DimmableLight1.xml / X / D_DimmableLight1.json (urn:schemas-upnp-org:device:DimmableLight:1)
    2020-10-01 13:06:57.913 luup.create_device:: [10264] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.922 luup.create_device:: [10265] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.930 luup.create_device:: [10266] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.937 luup.create_device:: [10267] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.944 luup.create_device:: [10268] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1)
    2020-10-01 13:06:57.946 openLuup.userdata:: loading scenes...
    2020-10-01 13:06:57.946 openLuup.userdata:: number of scenes = 0
    2020-10-01 13:06:57.946 openLuup.userdata:: ...scene loading completed
    2020-10-01 13:06:57.946 openLuup.userdata:: loading installed plugin info...
    2020-10-01 13:06:57.947 openLuup.userdata:: [openLuup] openLuup (20.5.22)
    2020-10-01 13:06:57.947 openLuup.userdata:: [AltAppStore] Alternate App Store (20.3.30)
    2020-10-01 13:06:57.947 openLuup.userdata:: [VeraBridge] VeraBridge (20.4.30)
    2020-10-01 13:06:57.947 openLuup.userdata:: [8246] Alternate UI (2.50.)
    2020-10-01 13:06:57.947 openLuup.userdata:: [Z-Way] Z-Way (not.installed)
    2020-10-01 13:06:57.947 openLuup.userdata:: [Arduino] MySensors (not.installed)
    2020-10-01 13:06:57.947 openLuup.userdata:: [9086] Reactor (GitHub.master)
    2020-10-01 13:06:57.947 openLuup.userdata:: [8702] DeusExMachinaII (2.9)
    2020-10-01 13:06:57.947 openLuup.userdata:: [8942] SiteSensor (1.15)
    2020-10-01 13:06:57.947 openLuup.userdata:: [5665def1-9e1b-415b-97c8-7b75565f64c0] BroadLink-Mk2 (1.0)
    2020-10-01 13:06:57.947 openLuup.userdata:: [9194] Switchboard (1.7)
    2020-10-01 13:06:57.947 openLuup.userdata:: ...user_data loading completed
    2020-10-01 13:06:57.947 openLuup.init:: running openLuup_STARTUP
    2020-10-01 13:06:57.948 luup_log:0: startup code completed
    2020-10-01 13:06:57.948 openLuup.init:: init phase completed
    2020-10-01 13:06:57.948 :: openLuup LOG ROTATION :: (runtime 0.0 days)

    Plugins
  • Login

  • Don't have an account? Register

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