GaryK4 Posted January 22, 2015 Share Posted January 22, 2015 Is it possible to have a motion sensor turn a scene on only? I set jumper #4 and it does not appear to do anything. All attempts, once the time expires, it turns off the lights. I know a program can do what I want, but it is slower. Link to comment
oberkc Posted January 22, 2015 Share Posted January 22, 2015 If you can figure out how to enable the motion sensor mode where it sends only ON commands, then, yes. What is jumper 5 set to? Is there a reason you are not setting this configuration through the ISY? Link to comment
Teken Posted January 22, 2015 Share Posted January 22, 2015 The jumper number 5 should be set by *default* to allow software to control the MS settings. This is how all new MS come from the factory. Link to comment
GaryK4 Posted January 22, 2015 Author Share Posted January 22, 2015 If you can figure out how to enable the motion sensor mode where it sends only ON commands, then, yes. What is jumper 5 set to? Is there a reason you are not setting this configuration through the ISY? Jumper 4 is documented to only send on commands. However the lights go out. Jumper 5 is set also. I think I found my answer. "The On Only mode: check box should be "unchecked" for the motion sensor to send On Only commands." This did the trick. The only downside is I have to wait for the timer seconds before it will trigger again. I can live with this, but will play with it a little more. Link to comment
LeeG Posted January 22, 2015 Share Posted January 22, 2015 You must be running something other than 4.2.22 so my post in the other topic does not match your motion sensor Options display. Check the Sensing Mode: option. With this option checked along with sending On Only commands the motion sensor does not wait for the timeout value to expire before sending the next motion On message. Link to comment
stusviews Posted January 22, 2015 Share Posted January 22, 2015 Jumper 4 is documented to only send on commands. However the lights go out. Jumper 5 is set also. If jumper 5 is installed, then except for jumper 1 (sensitivity), the other jumpers have no function nor do the dials. Link to comment
GaryK4 Posted January 23, 2015 Author Share Posted January 23, 2015 You must be running something other than 4.2.22 so my post in the other topic does not match your motion sensor Options display. Check the Sensing Mode: option. With this option checked along with sending On Only commands the motion sensor does not wait for the timeout value to expire before sending the next motion On message. I am running 4.2.18. I don't see any notes about 4.2.22 changing the motion sensor behavior. I tried Sensing mode both checked and unchecked - no effect. On only mode is unchecked. Timeout 0.5 minutes. Triggers program only after 30 seconds. Link to comment
oberkc Posted January 23, 2015 Share Posted January 23, 2015 To double check, have you written the changes to the motion sensor as you adjust the settings? Watch for little funny symbols down at the lower left of your program and device listing. They can sometimes indicate the need to write changes to the device. Battery devices are especially important to pay attention to that detail. They cannot be written to without putting them into linking mode. Link to comment
GaryK4 Posted January 23, 2015 Author Share Posted January 23, 2015 To double check, have you written the changes to the motion sensor as you adjust the settings? Watch for little funny symbols down at the lower left of your program and device listing. They can sometimes indicate the need to write changes to the device. Battery devices are especially important to pay attention to that detail. They cannot be written to without putting them into linking mode. I know about the linking mode. Below is the event viewer. I have a spare MS on my desk for testing. I kept waving my hand in front of the MS for a number of triggers. I get some events between the DON 1 events. Previous message ignored. Don't know what these are doing. Triggers are around the .5 timeout but a little less. All exactly (25) seconds. Could something else be causing a slow response and not the timeout at all? Fri 01/23/2015 12:58:55 PM : [iNST-SRX ] 02 50 31.AE.B3 11.02.01 CB 06 01 (01) Fri 01/23/2015 12:58:55 PM : [std-Group ] 31.AE.B3-->11.02.01, Max Hops=3, Hops Left=2 Fri 01/23/2015 12:58:55 PM : [iNST-INFO ] Previous message ignored. Fri 01/23/2015 12:58:55 PM : [iNST-SRX ] 02 50 31.AE.B3 11.02.01 CB 06 01 (01) Fri 01/23/2015 12:58:55 PM : [std-Group ] 31.AE.B3-->11.02.01, Max Hops=3, Hops Left=2 Fri 01/23/2015 12:58:55 PM : [iNST-INFO ] Previous message ignored. Fri 01/23/2015 12:59:04 PM : [iNST-SRX ] 02 50 31.AE.B3 00.00.01 CB 11 01 LTONRR (01) Fri 01/23/2015 12:59:04 PM : [std-Group ] 31.AE.B3-->Group=1, Max Hops=3, Hops Left=2 Fri 01/23/2015 12:59:04 PM : [D2D EVENT ] Event [31 AE B3 1] [DON] [1] uom=0 prec=-1 Fri 01/23/2015 12:59:04 PM : [ 31 AE B3 1] DON 1 Fri 01/23/2015 12:59:04 PM : [D2D-CMP 000E] CTL [31 AE B3 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 12:59:04 PM : [iNST-SRX ] 02 50 31.AE.B3 00.00.01 CB 11 01 LTONRR (01) Fri 01/23/2015 12:59:04 PM : [std-Group ] 31.AE.B3-->Group=1, Max Hops=3, Hops Left=2 Fri 01/23/2015 12:59:04 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 12:59:04 PM : [iNST-SRX ] 02 50 31.AE.B3 30.6A.C6 45 11 01 LTONRR (01) Fri 01/23/2015 12:59:04 PM : [std-Cleanup ] 31.AE.B3-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Fri 01/23/2015 12:59:04 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 12:59:20 PM : [iNST-SRX ] 02 50 31.AE.B3 11.02.01 CB 06 01 (01) Fri 01/23/2015 12:59:20 PM : [std-Group ] 31.AE.B3-->11.02.01, Max Hops=3, Hops Left=2 Fri 01/23/2015 12:59:20 PM : [iNST-INFO ] Previous message ignored. Fri 01/23/2015 12:59:20 PM : [iNST-SRX ] 02 50 31.AE.B3 11.02.01 CB 06 01 (01) Fri 01/23/2015 12:59:20 PM : [std-Group ] 31.AE.B3-->11.02.01, Max Hops=3, Hops Left=2 Fri 01/23/2015 12:59:20 PM : [iNST-INFO ] Previous message ignored. Fri 01/23/2015 12:59:29 PM : [iNST-SRX ] 02 50 31.AE.B3 00.00.01 CF 11 01 LTONRR (01) Fri 01/23/2015 12:59:29 PM : [std-Group ] 31.AE.B3-->Group=1, Max Hops=3, Hops Left=3 Fri 01/23/2015 12:59:29 PM : [D2D EVENT ] Event [31 AE B3 1] [DON] [1] uom=0 prec=-1 Fri 01/23/2015 12:59:29 PM : [ 31 AE B3 1] DON 1 Fri 01/23/2015 12:59:29 PM : [D2D-CMP 000E] CTL [31 AE B3 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 12:59:29 PM : [iNST-SRX ] 02 50 31.AE.B3 00.00.01 CF 11 01 LTONRR (01) Fri 01/23/2015 12:59:29 PM : [std-Group ] 31.AE.B3-->Group=1, Max Hops=3, Hops Left=3 Fri 01/23/2015 12:59:29 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 12:59:29 PM : [iNST-SRX ] 02 50 31.AE.B3 30.6A.C6 41 11 01 LTONRR (01) Fri 01/23/2015 12:59:29 PM : [std-Cleanup ] 31.AE.B3-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Fri 01/23/2015 12:59:29 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 12:59:45 PM : [iNST-SRX ] 02 50 31.AE.B3 11.02.01 CF 06 01 (01) Fri 01/23/2015 12:59:45 PM : [std-Group ] 31.AE.B3-->11.02.01, Max Hops=3, Hops Left=3 Fri 01/23/2015 12:59:45 PM : [iNST-INFO ] Previous message ignored. Fri 01/23/2015 12:59:45 PM : [iNST-SRX ] 02 50 31.AE.B3 11.02.01 CB 06 01 (01) Fri 01/23/2015 12:59:45 PM : [std-Group ] 31.AE.B3-->11.02.01, Max Hops=3, Hops Left=2 Fri 01/23/2015 12:59:45 PM : [iNST-INFO ] Previous message ignored. Fri 01/23/2015 12:59:54 PM : [iNST-SRX ] 02 50 31.AE.B3 00.00.01 CF 11 01 LTONRR (01) Fri 01/23/2015 12:59:54 PM : [std-Group ] 31.AE.B3-->Group=1, Max Hops=3, Hops Left=3 Fri 01/23/2015 12:59:54 PM : [D2D EVENT ] Event [31 AE B3 1] [DON] [1] uom=0 prec=-1 Fri 01/23/2015 12:59:54 PM : [ 31 AE B3 1] DON 1 Fri 01/23/2015 12:59:54 PM : [D2D-CMP 000E] CTL [31 AE B3 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 12:59:54 PM : [iNST-SRX ] 02 50 31.AE.B3 00.00.01 CB 11 01 LTONRR (01) Fri 01/23/2015 12:59:54 PM : [std-Group ] 31.AE.B3-->Group=1, Max Hops=3, Hops Left=2 Fri 01/23/2015 12:59:54 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 12:59:54 PM : [iNST-SRX ] 02 50 31.AE.B3 30.6A.C6 41 11 01 LTONRR (01) Fri 01/23/2015 12:59:54 PM : [std-Cleanup ] 31.AE.B3-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Fri 01/23/2015 12:59:54 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 01:00:10 PM : [iNST-SRX ] 02 50 31.AE.B3 11.02.01 CB 06 01 (01) Fri 01/23/2015 01:00:10 PM : [std-Group ] 31.AE.B3-->11.02.01, Max Hops=3, Hops Left=2 Fri 01/23/2015 01:00:10 PM : [iNST-INFO ] Previous message ignored. Fri 01/23/2015 01:00:10 PM : [iNST-SRX ] 02 50 31.AE.B3 11.02.01 CB 06 01 (01) Fri 01/23/2015 01:00:10 PM : [std-Group ] 31.AE.B3-->11.02.01, Max Hops=3, Hops Left=2 Fri 01/23/2015 01:00:10 PM : [iNST-INFO ] Previous message ignored. Fri 01/23/2015 01:00:19 PM : [iNST-SRX ] 02 50 31.AE.B3 00.00.01 CB 11 01 LTONRR (01) Fri 01/23/2015 01:00:19 PM : [std-Group ] 31.AE.B3-->Group=1, Max Hops=3, Hops Left=2 Fri 01/23/2015 01:00:19 PM : [D2D EVENT ] Event [31 AE B3 1] [DON] [1] uom=0 prec=-1 Fri 01/23/2015 01:00:19 PM : [ 31 AE B3 1] DON 1 Fri 01/23/2015 01:00:19 PM : [D2D-CMP 000E] CTL [31 AE B3 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 01:00:19 PM : [iNST-SRX ] 02 50 31.AE.B3 00.00.01 CB 11 01 LTONRR (01) Fri 01/23/2015 01:00:19 PM : [std-Group ] 31.AE.B3-->Group=1, Max Hops=3, Hops Left=2 Fri 01/23/2015 01:00:19 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 01:00:19 PM : [iNST-SRX ] 02 50 31.AE.B3 30.6A.C6 41 11 01 LTONRR (01) Fri 01/23/2015 01:00:19 PM : [std-Cleanup ] 31.AE.B3-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Fri 01/23/2015 01:00:19 PM : [iNST-DUP ] Previous message ignored. Link to comment
LeeG Posted January 23, 2015 Share Posted January 23, 2015 GaryK4 The 4.2.22 image did not change the way Motion Sensors work. The Motion Sensors Options popup did change how the MS options are presented but the underlying MS functions remain the same. It will take some minutes but I will post the Options popup from 4.2.18. The Motion Sensor was not updated for some reason since it is waiting the .5 second timeout. If the Sensing mode: was checked it did not get written back to the Motion Sensor. With the Motion Sensor in linking mode, uncheck Sensing Mode and write that back to the Motion Sensor. Bring up the Options popup again, check the Sensing mode: and write it back to the Motion Sensor. The ISY does not write changes back to the Motion Sensor unless they are different from what the ISY thinks are already set. The "Previous message ignored" message is displayed for the several Insteon messages that are generated for each Motion On message. They serve no function in terms of triggering a Program and are ignored by the ISY. Link to comment
LeeG Posted January 23, 2015 Share Posted January 23, 2015 This is Motion Sensor Options display from 4.2.18 with the required options checked. Link to comment
GaryK4 Posted January 23, 2015 Author Share Posted January 23, 2015 This is Motion Sensor Options display from 4.2.18 with the required options checked. I always have to put the MS in linking mode to see an accurate options (current). My options are set the same as yours. Does your ISY respond faster? Link to comment
LeeG Posted January 23, 2015 Share Posted January 23, 2015 I had to go back to 4.2.18 to get the Options display that matches yours. The Motion Sensor is not using those options as it would not use the timeout if Sensing mode was checked in the motion sensor. Uncheck Sensing Mode; and click Ok. After the MS updates have been written, click Options, check Sensing Mode and click Ok. This should stop the Motion Sensor from using the timeout value. Link to comment
LeeG Posted January 23, 2015 Share Posted January 23, 2015 This is a trace of the MS sensor with those options set. Fri 01/23/2015 02:32:45 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.01 CB 11 01 LTONRR (01) Fri 01/23/2015 02:32:45 PM : [std-Group ] 13.F2.57-->Group=1, Max Hops=3, Hops Left=2 Fri 01/23/2015 02:32:45 PM : [D2D EVENT ] Event [13 F2 57 1] [DON] [1] uom=0 prec=-1 Fri 01/23/2015 02:32:45 PM : [ 13 F2 57 1] DON 1 Fri 01/23/2015 02:32:45 PM : [D2D-CMP 006D] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 02:32:45 PM : [D2D-CMP 0067] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 02:32:45 PM : [ X10] A1 Fri 01/23/2015 02:32:45 PM : [X10-RSP ] 02 63 66 00 06 Fri 01/23/2015 02:32:45 PM : [ X10] A1/All Lights Off (1) Fri 01/23/2015 02:32:46 PM : [iNST-SRX ] 02 50 13.F2.57 22.80.0B 46 11 01 LTONRR (01) Fri 01/23/2015 02:32:46 PM : [std-Cleanup ] 13.F2.57-->ISY/PLM Group=1, Max Hops=2, Hops Left=1 Fri 01/23/2015 02:32:46 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 02:32:46 PM : [X10-RSP ] 02 63 66 80 06 Fri 01/23/2015 02:32:47 PM : [X10-RX ] 02 52 66 00 Fri 01/23/2015 02:32:47 PM : [ X10] A1 Fri 01/23/2015 02:32:55 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.01 CB 11 01 LTONRR (01) Fri 01/23/2015 02:32:55 PM : [std-Group ] 13.F2.57-->Group=1, Max Hops=3, Hops Left=2 Fri 01/23/2015 02:32:55 PM : [D2D EVENT ] Event [13 F2 57 1] [DON] [1] uom=0 prec=-1 Fri 01/23/2015 02:32:55 PM : [ 13 F2 57 1] DON 1 Fri 01/23/2015 02:32:55 PM : [D2D-CMP 006D] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 02:32:55 PM : [D2D-CMP 0067] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 02:32:55 PM : [ X10] A1 Fri 01/23/2015 02:32:55 PM : [X10-RSP ] 02 63 66 00 06 Fri 01/23/2015 02:32:55 PM : [ X10] A1/All Lights Off (1) Fri 01/23/2015 02:32:56 PM : [iNST-SRX ] 02 50 13.F2.57 22.80.0B 46 11 01 LTONRR (01) Fri 01/23/2015 02:32:56 PM : [std-Cleanup ] 13.F2.57-->ISY/PLM Group=1, Max Hops=2, Hops Left=1 Fri 01/23/2015 02:32:56 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 02:32:56 PM : [X10-RSP ] 02 63 66 80 06 Fri 01/23/2015 02:32:57 PM : [X10-RX ] 02 52 66 00 Fri 01/23/2015 02:32:57 PM : [ X10] A1 Fri 01/23/2015 02:33:06 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.01 CB 11 01 LTONRR (01) Fri 01/23/2015 02:33:06 PM : [std-Group ] 13.F2.57-->Group=1, Max Hops=3, Hops Left=2 Fri 01/23/2015 02:33:06 PM : [D2D EVENT ] Event [13 F2 57 1] [DON] [1] uom=0 prec=-1 Fri 01/23/2015 02:33:06 PM : [ 13 F2 57 1] DON 1 Fri 01/23/2015 02:33:06 PM : [D2D-CMP 006D] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 02:33:06 PM : [D2D-CMP 0067] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 02:33:06 PM : [ X10] A1 Fri 01/23/2015 02:33:06 PM : [X10-RSP ] 02 63 66 00 06 Fri 01/23/2015 02:33:06 PM : [ X10] A1/All Lights Off (1) Fri 01/23/2015 02:33:07 PM : [iNST-SRX ] 02 50 13.F2.57 22.80.0B 46 11 01 LTONRR (01) Fri 01/23/2015 02:33:07 PM : [std-Cleanup ] 13.F2.57-->ISY/PLM Group=1, Max Hops=2, Hops Left=1 Fri 01/23/2015 02:33:07 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 02:33:07 PM : [X10-RSP ] 02 63 66 80 06 Fri 01/23/2015 02:33:16 PM : [iNST-SRX ] 02 50 13.F2.57 00.00.01 CB 11 01 LTONRR (01) Fri 01/23/2015 02:33:16 PM : [std-Group ] 13.F2.57-->Group=1, Max Hops=3, Hops Left=2 Fri 01/23/2015 02:33:16 PM : [D2D EVENT ] Event [13 F2 57 1] [DON] [1] uom=0 prec=-1 Fri 01/23/2015 02:33:16 PM : [ 13 F2 57 1] DON 1 Fri 01/23/2015 02:33:16 PM : [D2D-CMP 006D] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 02:33:16 PM : [D2D-CMP 0067] CTL [13 F2 57 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Fri 01/23/2015 02:33:16 PM : [ X10] A1 Fri 01/23/2015 02:33:16 PM : [X10-RSP ] 02 63 66 00 06 Fri 01/23/2015 02:33:16 PM : [ X10] A1/All Lights Off (1) Fri 01/23/2015 02:33:17 PM : [iNST-SRX ] 02 50 13.F2.57 22.80.0B 46 11 01 LTONRR (01) Fri 01/23/2015 02:33:17 PM : [std-Cleanup ] 13.F2.57-->ISY/PLM Group=1, Max Hops=2, Hops Left=1 Fri 01/23/2015 02:33:17 PM : [iNST-DUP ] Previous message ignored. Fri 01/23/2015 02:33:17 PM : [X10-RSP ] 02 63 66 80 06 Fri 01/23/2015 02:33:18 PM : [X10-RX ] 02 52 66 00 Fri 01/23/2015 02:33:18 PM : [ X10] A1 Link to comment
GaryK4 Posted January 23, 2015 Author Share Posted January 23, 2015 I had to go back to 4.2.18 to get the Options display that matches yours. The Motion Sensor is not using those options as it would not use the timeout if Sensing mode was checked in the motion sensor. Uncheck Sensing Mode; and click Ok. After the MS updates have been written, click Options, check Sensing Mode and click Ok. This should stop the Motion Sensor from using the timeout value. I tried changing the settings (3) times as you suggested and got the same results. My testing is using a program. I changed it to a scene. The 25 seconds went down to 10 seconds. That matches your results. OK, but slower than expected. Link to comment
LeeG Posted January 23, 2015 Share Posted January 23, 2015 My trace was invoking a test Program. The Program issued the X10 traffic. Motion1x - [iD 0067][Parent 0001] If Control 'MotionSensor2-Sensor' is switched On And Status 'SwitchLinc Dimmer' is Off And From 3:00:00PM To 10:00:00PM (same day) Then Set 'SwitchLinc Dimmer' On Wait 10 minutes Set 'SwitchLinc Dimmer' Off Else Send X10 'A1/All Lights Off (1)' Link to comment
GaryK4 Posted January 23, 2015 Author Share Posted January 23, 2015 This makes me think that something is slowing down my system. So I looked at the error log and I see a lot of errors. I need to read up on what may be causing this. Fri 2015/01/23 03:15:54 PM System -170001 <s:Envelope><s:Body><u:MoveNode xmlns:u="urn:ud Fri 2015/01/23 03:15:54 PM System -170001 [HTTP:1-26-5] 192.168.1.nnn:nnnnn->80 Fri 2015/01/23 03:15:54 PM System -170001 [HTTP:1-26]: POST[1]-->/services Fri 2015/01/23 03:15:54 PM System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u= Fri 2015/01/23 03:15:54 PM System -170001 [HTTP:1-26-5] 192.168.1.nnn:61708->80 Fri 2015/01/23 03:15:55 PM System -170001 [HTTP:1-26]: POST[1]-->/services Fri 2015/01/23 03:15:55 PM System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u= Fri 2015/01/23 03:15:55 PM System -170001 [HTTP:0-26-5] 192.168.1.nnn:61709->80 Fri 2015/01/23 03:15:55 PM System -170001 [HTTP:0-26]: POST[1]-->/services Fri 2015/01/23 03:15:55 PM System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u= Fri 2015/01/23 03:16:22 PM System -170001 [HTTP:0-26-5] 192.168.1.nnn:61735->80 Fri 2015/01/23 03:16:22 PM System -170001 [HTTP:0-26]: POST[1]-->/services Fri 2015/01/23 03:16:22 PM System -170001 <s:Envelope><s:Body><u:DeviceSpecific xmlns:u=" Fri 2015/01/23 03:50:35 PM System -170001 [HTTP:0-26-5] 192.168.1.nnn:63621->80 Fri 2015/01/23 03:50:35 PM System -170001 [HTTP:0-26]: POST[1]-->/services Fri 2015/01/23 03:50:35 PM System -170001 <s:Envelope><s:Body><u:GetSystemTime xmlns:u="u Fri 2015/01/23 04:05:29 PM System -170001 [HTTP:0-26-5] 192.168.1.nnn:64456->80 Fri 2015/01/23 04:05:29 PM System -170001 [HTTP:0-26]: POST[1]-->/services Fri 2015/01/23 04:05:29 PM System -170001 <s:Envelope><s:Body><u:GetSystemTime xmlns:u="u Fri 2015/01/23 04:32:48 PM System -170001 [HTTP:0-26-5] 192.168.1.nnn:49622->80 Fri 2015/01/23 04:32:48 PM System -170001 [HTTP:0-26]: POST[1]-->/services Fri 2015/01/23 04:32:48 PM System -170001 <s:Envelope><s:Body><u:GetDebugLevel xmlns:u="u Fri 2015/01/23 04:33:04 PM System -170001 [HTTP:0-26-5] 192.168.1.nnn:49639->80 Fri 2015/01/23 04:33:04 PM System -170001 [HTTP:0-26]: POST[1]-->/services Fri 2015/01/23 04:33:04 PM System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u= Fri 2015/01/23 04:33:04 PM System -170001 [HTTP:0-26-5] 192.168.1.nnn:49640->80 Fri 2015/01/23 04:33:04 PM System -170001 [HTTP:0-26]: POST[1]-->/services Fri 2015/01/23 04:33:04 PM System -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u= Fri 2015/01/23 04:37:00 PM System -170001 [HTTP:0-26-5] 192.168.1.nnn:49856->80 Fri 2015/01/23 04:37:00 PM System -170001 [HTTP:0-26]: POST[1]-->/services Fri 2015/01/23 04:37:00 PM System -170001 <s:Envelope><s:Body><u:GetDebugLevel xmlns:u="u Link to comment
Michel Kohanim Posted January 25, 2015 Share Posted January 25, 2015 Hi GaryK4, Those are not errors. Simply informational messages because you are using event viewer on level 3. With kind regards, Michel Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.