thanks all for the feedback. I will check out Hubitat and see how it does.
S
sebby
@sebby
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO:
Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1.
Then, configure these endpoints as needed:
On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on
Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off
Dim:
For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent}
For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent}
Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b}
Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier.
This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa!
If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
Just for the record, in case anyone is following, I'm really rather impressed.
I have installed one of these:
https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1
That's connected (physically) to the VM running on my Synology, with a 2m USB extension.
The same host also runs Openluup, Mosquito, HA Bridge.
Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions.
Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor
I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA.
https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title
The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so...
https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title
Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt.
And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one).
A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....)
Commended to the house. Thanks for everyone that got me on the right lines.
C
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Good evening all,
For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time.
Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed.
Thanks.
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations.
Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction?
Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for.
I guess it's something of an edge case so no huge issue.
TIA!
C
I'm sure this has been asked, and answered, but damned if I can figure it out
Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage.
Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts.
After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!)
What I would like is for the 3 minute delay until the lights go off to start from the latest door open event.
That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity.
I've tried 'hacking' with a virtual switch, but can't seem to stop the delay.
Any pointers?
TIA
C
Hello oh great ones.
After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi
Can connect to the front end and everything
Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this:
[Unit]
Description=zigbee2mqtt
After=network.target
[Service]
Environment=NODE_ENV=production
Type=notify
ExecStart=/usr/local/bin/node index.js
WorkingDirectory=/opt/zigbee2mqtt
StandardOutput=inherit
# Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5)
StandardError=inherit
WatchdogSec=10s
Restart=always
RestartSec=10s
User=pi
[Install]
WantedBy=multi-user.target
Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using.
Running manually pnpm start
in /opt/zigbee2mqtt works fine
However:
catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service
Job for zigbee2mqtt.service failed because the control process exited with error code.
See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details.
Which I have
catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago
Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER)
Main PID: 3093 (code=exited, status=217/USER)
and
-- A start job for unit zigbee2mqtt.service has begun execution.
--
-- The job identifier is 17477.
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process
-- Subject: Process /usr/local/bin/node could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /usr/local/bin/node could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit zigbee2mqtt.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 217.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'.
Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt.
-- Subject: A start job for unit zigbee2mqtt.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zigbee2mqtt.service has finished with a failure.
Which strikes me as very odd.
Any blindingly obvious things I'm missing?
TIA!
C
Obviously a quiet forum, but perhaps it's time
I'm looking at rolling Zigbee into my system, in large part for the Aqara FP300 presence sensors which seem to finally provide a solution to if the wasp is actually in the box.
My current set up is as follows:
One Debian VM on Synology NAS running:
Z-wave Server
Open Luup
Multi system reactor
HA bridge
Mosquito MQQT broker
This machine has a UZB Z-wave stick connected via the USB port on the NAS
Another HAOS VM on the same NAS running HAOS
I've got some older Z-wave stuff that I keep around until it fails.
I have some Tuya stuff integrated in HA
My thought was to get either a SMLIGHT SLZB-06M
or an Aqara Hub M2
Integrate them via Zigbee2MQQT (running on the Debian machine) and then expose them in HA so I can continue to automate in MSR.
Thoughts on which of those devices wold be preferable long term. Both are POE capable which is good. It also appears I could add a USB dongle to the NAS and expose it to the HAOS machine.
Any thoughts from the assembled experts here? TIA
C
Another question to the hive mind. Prompted by the fact that I lost yet another z-wave device over the weekend due to a power issue. It looks like z-way server is reporting another device failed (although it's working fine) and message queue is far too long IMHO. Also the failed device has been removed in the expert interface, but still there in the 'normal' one. Sigh.
Currently I have z-wave, Tuya, thinking about Zigbee.... Does anyone use one single protocol for everything? Right now I'm feeling that as the z-wave stuff dies, I'm just gonna replace it with something else....
C
Not really Smart Home stuff, but going to ask as we have smart people...
Bear with me on this one. Asking here because of the font of knowledge!
For many eek years I have had a Virgin V6 box and a Raspberry Pi running Kodi connected to my TV through a cheap *** HDMI switch. It all worked beautifully but the absolutely critical thing was that the TV remote passed the signals back to the Pi to allow remote control of Kodi.
Couple of changes of late:
Installed a soundbar on the TV using the ARC (audio return channel). That then turns the soundbar on and off when the TV turns on and off and the TV volume control controls the soundbar volume direct.
Everything continues to work
Upgraded the software of the Tivo box to Virgin 360. This is literally software only. You get sent a snacky new Bluetooth remote hit 'upgrade' on the screen and off it goes.
Now, things are not playing well. Typically when I turn on to watch Kodi the soundbar comes on (as it should) but the TV either puts out sound through its own speakers and the soundbar, or just the soundbar. It's not possible to control the volume of the soundbar through the TV. Also it's not longer possible to control Kodi using the TV remote.
If I turn the TV360 box off, i.e. power it down, before turning on to watch Kodi, everything is fine.
This makes little to no sense to me. My assumption is that the cheap *** HDMI switch is getting something from the TV360 connection that it didn't used to get when the software was Tivo and that's screwing up the HDMI communications. I'm upgrading the switch to something a little less chap, but wondered if anyone could validate my theory at all?
TIA
C
Posts
-
Recommendation for new hub -
Recommendation for new hubMy 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?
-
Set Entity value in expression?- The
performAction()expression function will perform an action from an expression. If you have an object stored in a variableold_statusthat 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...
- The
-
Set Entity value in expression?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.
-
Set Entity value in expression? -
Set Entity value in expression?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?
-
Set Entity value in expression?wow, thank you so much for that, as always greatly appreciated.
-
Set Entity value in expression?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.
-
Set Entity value in expression?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.
-
Set Entity value in expression?@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.
-
Set Entity value in expression?@sebby
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?
-
Set Entity value in expression?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?
-
Import questionFYI, the new release worked like a charm, than you
-
Feature Request - Reaction to MQTT
-
Import questionok, done. very low priority as I'd rather you spend time polishing the builds than dealing with my clusterf**k.
-
Feature Request - Reaction to MQTTawesome and thanks! sorry for spamming the boards.
-
Import questionhaving 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)
(Usenode --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) -
Feature Request - Reaction to MQTTI 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.
-
iPhoneLocator: Alternate Map Serverscould 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) -
iPhoneLocator: Alternate Map Serversthe 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)
