The delay command you are referring to is the one in activities, correct? Whatever time value it has, the RS will “stall,” either untipped or tripped until the timers up.
So, I updated my device info, I forgot the value, but it was far out of date. Like you said, I can now store a value for NewChimeProperty, however I don’t know what it is. I went back to importing the scene, and it shows 0x87-0x1-0x01. It stores this value when I input it, but the action never works. It does not work right after importing either like it did before- only a prompt saying an Error occured, please try again, vera may be busy.
*************************************************** REACTOR LOGIC SUMMARY REPORT ***************************************************
Version: 3.2 config 301 cdata 19082 ui 19143 pluginDevice 90
System: Vera version 1.7.4454 on Sercomm G550; loadtime 1560304869; systemReady 1560304888; Lua 5.1
Local time: 2019-06-11T22:19:04-0400; DST=1
House mode: plugin 1; system 1; tracking on
Sun data: { "stamp": 2019162, "civdawn": 1560243660, "nautdawn": 1560240949, "sunset": 1560300742, "nautdusk": 1560305549, "latitude": 42.7678, "astrodusk": 1560308863, "longitude": -78.6134, "civdusk": 1560302839, "astrodawn": 1560237635, "sunrise": 1560245756 }
Geofence: running in long mode, last update 18:12:00, data version 2
User 2464412 ishome=1 inlist= since=18:12:00
Raw: { "updated": 1560305940, "users_settings": [ { "id": 2464412, "ishome": 1 } ], "mode": -1, "users": [ { "id": 2464412, "Level": 1, "Name": "derekkirsch", "IsGuest": 0 } ], "usergeofences": [ { "geotags": [ ], "iduser": 2464412 } ] }
Power: utility, battery level 99
====================================================================================================================================
Reactor Sensor 20 (#295)
Version 19082.21 06/11/19 22:18:58
Message/status: Not tripped
Condition group "Reactor Sensor 20" (AND) false as of 20:39:43 <root>
&-F-service DOOR SENSOR - FRONT (234) urn:micasaverde-com:serviceId:SecuritySensor1/Tripped = 1 [0 at 20:39:43; F/F as of 20:39:43/20:39:43] <cond0>
Activity root.true
Device 275 (DOME ALARM - DOWNSTR Chime) action urn:micasaverde-com:serviceId:Dome1/SetChimeProperty( NewChimeProperty="0x87-0x1-0x01" )
Device 273 (DOME ALARM - UPSTAIR Chime) action urn:micasaverde-com:serviceId:Dome1/SetChimeProperty( NewChimeProperty="0x87-0x1-0x01" )
Events
06/11/19 22:01:22 start:
06/11/19 22:05:39 configchange:
06/11/19 22:06:06 configchange:
06/11/19 22:06:07 variable: newval=133, variable=e
06/11/19 22:06:24 configchange:
06/11/19 22:06:54 configchange:
06/11/19 22:10:58 action: action=Trip
06/11/19 22:10:58 sensorstate: state=true
06/11/19 22:10:58 startscene: scene=root.true, sceneName=root.true
06/11/19 22:10:58 runscene: scene=root.true, sceneName=root.true, group=1, notice=Starting scene group 1
06/11/19 22:10:58 endscene: scene=root.true, sceneName=root.true
06/11/19 22:11:03 action: action=Reset
06/11/19 22:11:03 sensorstate: state=false
06/11/19 22:11:16 configchange:
06/11/19 22:11:29 configchange:
06/11/19 22:11:36 action: action=Trip
06/11/19 22:11:36 sensorstate: state=true
06/11/19 22:11:36 startscene: scene=root.true, sceneName=root.true
06/11/19 22:11:36 runscene: scene=root.true, sceneName=root.true, group=1, notice=Starting scene group 1
06/11/19 22:11:36 endscene: scene=root.true, sceneName=root.true
06/11/19 22:11:39 action: action=Reset
06/11/19 22:11:39 sensorstate: state=false
06/11/19 22:12:52 configchange:
06/11/19 22:13:34 configchange:
06/11/19 22:13:35 notify: delay=1560302015, cond=conde8t40vv, message=Detected missed interval Wed Dec 31 20:00:00 1969
06/11/19 22:13:35 condchange: newState=true, cond=conde8t40vv
06/11/19 22:13:35 evalchange: newState=true, cond=conde8t40vv
06/11/19 22:13:50 condchange: newState=false, cond=conde8t40vv, oldState=true
06/11/19 22:13:50 evalchange: newState=false, cond=conde8t40vv, oldState=true
06/11/19 22:16:28 configchange:
06/11/19 22:18:56 configchange: