PhanTomiZ Posted March 1, 2015 Share Posted March 1, 2015 Hi, I have almost finished migrating from HL to ISY994izw. I moved two 2842-222 motion sensors from HL, first by deleting all links, which I didn't have any because I was using them in events only, and then doing a factory reset. Linking them to the ISY was accomplished by using the drop down menu for Motion sensor. I enabled linking mode for the each individual sensor and entered the address and name for each device. Looks like the ISY recognized them both and added them to the left side device pane. What I want to do next is change the device options. After enabling the linking mode on the device, I can't get the motion sensors to save the options. Each time I set any option I get "Request Failed". The option gets changed, but I believe not saved to the device. It seems that as long as the Admin console is running, the values stay, but as soon as I close the program and re-open, the Device Options go back to the default... The devices look to be functioning correctly, but only with the default settings. Any information would be greatly appreciated... PhanTomiZ Link to comment
LeeG Posted March 1, 2015 Share Posted March 1, 2015 Run Tools | Diagnostics | Event Viewer at LEVEL 3. Put the Motion Sensor into linking mode. Attempt Option change and post event trace. There is an Icon, next to last at the bottom right of event viewer window, to Copy to Clipboard. Paste the trace into the post Is the Motion Sensor near a Dual Band device? I suggest being close to the 2413 PLM for this test. Link to comment
PhanTomiZ Posted March 1, 2015 Author Share Posted March 1, 2015 It is currently within 3' of both PLM and On/off device. I find it easier to remove the MS from its location and bring to my computer room for setup.... I will Run Tools | Diagnostics | Event Viewer at LEVEL 3. as soon as I arrive home from work. Thanks Link to comment
PhanTomiZ Posted March 1, 2015 Author Share Posted March 1, 2015 Here's the info...Not sure what it all means... Sun 03/01/2015 03:36:58 PM : [All ] Writing 33 bytes to devices Sun 03/01/2015 03:36:58 PM : [iNST-TX-I1 ] 02 62 31 F3 64 0F 0D 00 Sun 03/01/2015 03:36:58 PM : [iNST-ACK ] 02 62 31.F3.64 0F 0D 00 06 (00) Sun 03/01/2015 03:37:07 PM : [iNST-TX-I1 ] 02 62 31 F3 64 0F 0D 00 Sun 03/01/2015 03:37:07 PM : [iNST-ACK ] 02 62 31.F3.64 0F 0D 00 06 (00) Sun 03/01/2015 03:37:16 PM : [iNST-TX-I1 ] 02 62 31 F3 64 0F 0D 00 Sun 03/01/2015 03:37:16 PM : [iNST-ACK ] 02 62 31.F3.64 0F 0D 00 06 (00) Sun 03/01/2015 03:37:20 PM : [D2D EVENT ] Event [31 F3 64 1] [ERR] [1] uom=0 prec=-1 Sun 03/01/2015 03:37:20 PM : [ 31 F3 64 1] ERR 1 Sun 03/01/2015 03:37:35 PM : [All ] Writing 0 bytes to devices Sun 03/01/2015 03:37:46 PM : [All ] Writing 0 bytes to devices Sun 03/01/2015 03:37:55 PM : [All ] Writing 0 bytes to devices Sun 03/01/2015 03:38:58 PM : [iNST-SRX ] 02 50 29.25.2C 33.5E.55 05 6F 21 (21) Sun 03/01/2015 03:38:58 PM : [std-Direct ] 29.25.2C-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Sun 03/01/2015 03:38:58 PM : [D2D EVENT ] Event [29 25 2C 1] [CLIHUM] [33] uom=0 prec=-1 Sun 03/01/2015 03:38:58 PM : [ 29 25 2C 1] CLIHUM 33 Sun 03/01/2015 03:38:58 PM : [D2D-CMP 0010] STS [29 25 2C 1] CLIHUM op=3 Event(val=33 uom=0 prec=-1) > Condition(val=50 uom=0 prec=-1) --> false This after setting the timeout to 20 Then Brightness to 35 Then Darkness to 35 Then LED On Then Query Thanks... Link to comment
LeeG Posted March 1, 2015 Share Posted March 1, 2015 Make sure 31.F3.64 is the device that was put into linking mode. The trace shows that Insteon address did not respond to the commands sent to that address. Link to comment
PhanTomiZ Posted March 1, 2015 Author Share Posted March 1, 2015 Yes, that is the correct device/address...Ok, if it is not responding, then how can it still be functioning. It shows the current state of On and Off when motion sensed for .5 min This is when motion is triggered, Current State ON then OFF Sun 03/01/2015 04:27:16 PM : [iNST-SRX ] 02 50 31.F3.4E 00.00.01 CF 11 01 LTONRR (01) Sun 03/01/2015 04:27:16 PM : [std-Group ] 31.F3.4E-->Group=1, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:27:16 PM : [D2D EVENT ] Event [31 F3 4E 1] [DON] [1] uom=0 prec=-1 Sun 03/01/2015 04:27:16 PM : [ 31 F3 4E 1] DON 1 Sun 03/01/2015 04:27:16 PM : [D2D EVENT ] Event [31 F3 4E 1] [sT] [255] uom=0 prec=-1 Sun 03/01/2015 04:27:16 PM : [ 31 F3 4E 1] ST 255 Sun 03/01/2015 04:27:17 PM : [iNST-SRX ] 02 50 31.F3.4E 00.00.01 CF 11 01 LTONRR (01) Sun 03/01/2015 04:27:17 PM : [std-Group ] 31.F3.4E-->Group=1, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:27:17 PM : [iNST-DUP ] Previous message ignored. Sun 03/01/2015 04:27:17 PM : [iNST-SRX ] 02 50 31.F3.4E 33.5E.55 45 11 01 LTONRR (01) Sun 03/01/2015 04:27:17 PM : [std-Cleanup ] 31.F3.4E-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Sun 03/01/2015 04:27:17 PM : [iNST-DUP ] Previous message ignored. Sun 03/01/2015 04:27:17 PM : [iNST-SRX ] 02 50 31.F3.4E 11.01.01 CF 06 00 (00) Sun 03/01/2015 04:27:17 PM : [std-Group ] 31.F3.4E-->11.01.01, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:27:17 PM : [iNST-INFO ] Previous message ignored. Sun 03/01/2015 04:27:17 PM : [iNST-SRX ] 02 50 31.F3.4E 11.01.01 CF 06 00 (00) Sun 03/01/2015 04:27:17 PM : [std-Group ] 31.F3.4E-->11.01.01, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:27:17 PM : [iNST-INFO ] Previous message ignored. Sun 03/01/2015 04:28:16 PM : [iNST-SRX ] 02 50 31.F3.4E 00.00.01 CF 13 01 LTOFFRR(01) Sun 03/01/2015 04:28:16 PM : [std-Group ] 31.F3.4E-->Group=1, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:28:16 PM : [D2D EVENT ] Event [31 F3 4E 1] [DOF] [1] uom=0 prec=-1 Sun 03/01/2015 04:28:16 PM : [ 31 F3 4E 1] DOF 1 Sun 03/01/2015 04:28:16 PM : [D2D EVENT ] Event [31 F3 4E 1] [sT] [0] uom=0 prec=-1 Sun 03/01/2015 04:28:16 PM : [ 31 F3 4E 1] ST 0 Sun 03/01/2015 04:28:16 PM : [iNST-SRX ] 02 50 31.F3.4E 00.00.01 CF 13 01 LTOFFRR(01) Sun 03/01/2015 04:28:16 PM : [std-Group ] 31.F3.4E-->Group=1, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:28:16 PM : [iNST-DUP ] Previous message ignored. Sun 03/01/2015 04:28:16 PM : [iNST-SRX ] 02 50 31.F3.4E 33.5E.55 45 13 01 LTOFFRR(01) Sun 03/01/2015 04:28:16 PM : [std-Cleanup ] 31.F3.4E-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Sun 03/01/2015 04:28:16 PM : [iNST-DUP ] Previous message ignored. Sun 03/01/2015 04:28:17 PM : [iNST-SRX ] 02 50 31.F3.4E 13.01.01 CF 06 00 (00) Sun 03/01/2015 04:28:17 PM : [std-Group ] 31.F3.4E-->13.01.01, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:28:17 PM : [iNST-INFO ] Previous message ignored. Sun 03/01/2015 04:28:17 PM : [iNST-SRX ] 02 50 31.F3.4E 13.01.01 CF 06 00 (00) Sun 03/01/2015 04:28:17 PM : [std-Group ] 31.F3.4E-->13.01.01, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:28:17 PM : [iNST-INFO ] Previous message ignored. Link to comment
LeeG Posted March 1, 2015 Share Posted March 1, 2015 Post an event trace of the Motion On/Off messages. Link to comment
PhanTomiZ Posted March 1, 2015 Author Share Posted March 1, 2015 I thought I did? Motion Sensed Current State On Sun 03/01/2015 04:34:17 PM : [iNST-SRX ] 02 50 31.F3.4E 00.00.01 CF 11 01 LTONRR (01) Sun 03/01/2015 04:34:17 PM : [std-Group ] 31.F3.4E-->Group=1, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:34:17 PM : [D2D EVENT ] Event [31 F3 4E 1] [DON] [1] uom=0 prec=-1 Sun 03/01/2015 04:34:17 PM : [ 31 F3 4E 1] DON 1 Sun 03/01/2015 04:34:17 PM : [D2D EVENT ] Event [31 F3 4E 1] [sT] [255] uom=0 prec=-1 Sun 03/01/2015 04:34:17 PM : [ 31 F3 4E 1] ST 255 Sun 03/01/2015 04:34:17 PM : [iNST-SRX ] 02 50 31.F3.4E 00.00.01 CF 11 01 LTONRR (01) Sun 03/01/2015 04:34:17 PM : [std-Group ] 31.F3.4E-->Group=1, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:34:17 PM : [iNST-DUP ] Previous message ignored. Sun 03/01/2015 04:34:17 PM : [iNST-SRX ] 02 50 31.F3.4E 33.5E.55 45 11 01 LTONRR (01) Sun 03/01/2015 04:34:17 PM : [std-Cleanup ] 31.F3.4E-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Sun 03/01/2015 04:34:17 PM : [iNST-DUP ] Previous message ignored. Sun 03/01/2015 04:34:18 PM : [iNST-SRX ] 02 50 31.F3.4E 11.01.01 CF 06 00 (00) Sun 03/01/2015 04:34:18 PM : [std-Group ] 31.F3.4E-->11.01.01, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:34:18 PM : [iNST-INFO ] Previous message ignored. Sun 03/01/2015 04:34:18 PM : [iNST-SRX ] 02 50 31.F3.4E 11.01.01 CF 06 00 (00) Sun 03/01/2015 04:34:18 PM : [std-Group ] 31.F3.4E-->11.01.01, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:34:18 PM : [iNST-INFO ] Previous message ignored. Motion Timeout Current State Off Sun 03/01/2015 04:37:57 PM : [iNST-SRX ] 02 50 31.F3.4E 00.00.01 CF 13 01 LTOFFRR(01) Sun 03/01/2015 04:37:57 PM : [std-Group ] 31.F3.4E-->Group=1, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:37:57 PM : [D2D EVENT ] Event [31 F3 4E 1] [DOF] [1] uom=0 prec=-1 Sun 03/01/2015 04:37:57 PM : [ 31 F3 4E 1] DOF 1 Sun 03/01/2015 04:37:57 PM : [D2D EVENT ] Event [31 F3 4E 1] [sT] [0] uom=0 prec=-1 Sun 03/01/2015 04:37:57 PM : [ 31 F3 4E 1] ST 0 Sun 03/01/2015 04:37:57 PM : [iNST-SRX ] 02 50 31.F3.4E 00.00.01 CF 13 01 LTOFFRR(01) Sun 03/01/2015 04:37:57 PM : [std-Group ] 31.F3.4E-->Group=1, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:37:57 PM : [iNST-DUP ] Previous message ignored. Sun 03/01/2015 04:37:57 PM : [iNST-SRX ] 02 50 31.F3.4E 33.5E.55 45 13 01 LTOFFRR(01) Sun 03/01/2015 04:37:57 PM : [std-Cleanup ] 31.F3.4E-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Sun 03/01/2015 04:37:57 PM : [iNST-DUP ] Previous message ignored. Sun 03/01/2015 04:37:57 PM : [iNST-SRX ] 02 50 31.F3.4E 13.01.01 CF 06 00 (00) Sun 03/01/2015 04:37:57 PM : [std-Group ] 31.F3.4E-->13.01.01, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:37:57 PM : [iNST-INFO ] Previous message ignored. Sun 03/01/2015 04:37:58 PM : [iNST-SRX ] 02 50 31.F3.4E 13.01.01 CF 06 00 (00) Sun 03/01/2015 04:37:58 PM : [std-Group ] 31.F3.4E-->13.01.01, Max Hops=3, Hops Left=3 Sun 03/01/2015 04:37:58 PM : [iNST-INFO ] Previous message ignored. Link to comment
LeeG Posted March 1, 2015 Share Posted March 1, 2015 That is from 31.F3.4E, not 31 F3 64. Link to comment
PhanTomiZ Posted March 1, 2015 Author Share Posted March 1, 2015 31 F3 64 is another MS...31 F3 4E is the one I put into linking mode... 31 F3 64 must have gotten triggered some how when I put 31 F3 4E in linking mode....Here is the Event Viewer.... Sun 03/01/2015 04:59:45 PM : [All ] Writing 0 bytes to devices Sun 03/01/2015 05:00:01 PM : [All ] Writing 0 bytes to devices Sun 03/01/2015 05:00:04 PM : [All ] Writing 0 bytes to devices Sun 03/01/2015 05:00:08 PM : [All ] Writing 0 bytes to devices Every time I select an option I get this Writing 0 bytes... Link to comment
LeeG Posted March 1, 2015 Share Posted March 1, 2015 Looks like the trace was not at LEVEL 3 or no changes were made to the Options. No changes were attempted/traced. The first trace was trying to update 31.F3.64. Perhaps the wrong MS was selected when Options clicked. Sun 03/01/2015 03:36:58 PM : [All ] Writing 33 bytes to devices Sun 03/01/2015 03:36:58 PM : [iNST-TX-I1 ] 02 62 31 F3 64 0F 0D 00 Sun 03/01/2015 03:36:58 PM : [iNST-ACK ] 02 62 31.F3.64 0F 0D 00 06 (00) Sun 03/01/2015 03:37:07 PM : [iNST-TX-I1 ] 02 62 31 F3 64 0F 0D 00 Sun 03/01/2015 03:37:07 PM : [iNST-ACK ] 02 62 31.F3.64 0F 0D 00 06 (00) Sun 03/01/2015 03:37:16 PM : [iNST-TX-I1 ] 02 62 31 F3 64 0F 0D 00 Sun 03/01/2015 03:37:16 PM : [iNST-ACK ] 02 62 31.F3.64 0F 0D 00 06 (00) Sun 03/01/2015 03:37:20 PM : [D2D EVENT ] Event [31 F3 64 1] [ERR] [1] uom=0 prec=-1 Sun 03/01/2015 03:37:20 PM : [ 31 F3 64 1] ERR 1 Link to comment
PhanTomiZ Posted March 1, 2015 Author Share Posted March 1, 2015 Yes, the first time I must have selected the wrong MS. The one in question is 31.F3.4E...Any ideas? Link to comment
LeeG Posted March 1, 2015 Share Posted March 1, 2015 Are there any Icons to the left of the Motion Sensor nodes for 31.F3.4E? What is being changed on the Options popup? Click Help | About. What is displayed for Firmware What is displayed for UI Link to comment
PhanTomiZ Posted March 1, 2015 Author Share Posted March 1, 2015 Trying to change Timeout from .5 to 20 LED Brightness to 35 Darkness Sensitivity to 35 LED On Firmware is V4.2.18 UI is V4.2.23 Thanks I just deleted it from the ISY and linked it using HL and I'm able to change the timeout values....Sending emails to myself as a test and it works fine with HL. I can synchronize device using HL while it is in linking mode...What's up with that????? Link to comment
LeeG Posted March 1, 2015 Share Posted March 1, 2015 Either move the ISY Firmware to 4.2.23 or the UI to 2.2.18 Options is not working as expected. which may be the result of having Firmware and UI at different levels. "I can synchronize device using HL while it is in linking mode...What's up with that?????" What is the question? Linking mode keeps the device from going to sleep for 4 minutes. Link to comment
stusviews Posted March 1, 2015 Share Posted March 1, 2015 After coordinating the firmware and UI, what;s the result if you change the timeout using HL and then add the MS to the ISY? Link to comment
PhanTomiZ Posted March 2, 2015 Author Share Posted March 2, 2015 Either move the ISY Firmware to 4.2.23 or the UI to 2.2.18 Options is not working as expected. which may be the result of having Firmware and UI at different levels. "I can synchronize device using HL while it is in linking mode...What's up with that?????" What is the question? Linking mode keeps the device from going to sleep for 4 minutes. Question being, why does it work with HL and not with the ISY? I'm able to set the "motion countdown duration" with HL, but yetI cannot with the ISY...Just went throught the firmware upgrade so both UI and Firmware are both V.4.2.23. We'll see if that makes a difference... Link to comment
PhanTomiZ Posted March 2, 2015 Author Share Posted March 2, 2015 After coordinating the firmware and UI, what;s the result if you change the timeout using HL and then add the MS to the ISY? You are correct. I deleted the HL MS device and went over to the ISY Admin console and hit "Options" and the same settings that were in HL are now in the ISY... So, one step further: now when I change the settings with ISY, they are written to the device as soon as I click on the option... Problem solved...Thanks again... Link to comment
LeeG Posted March 2, 2015 Share Posted March 2, 2015 That was getting Firmware and UI to the same point. Thanks for the update. Link to comment
PhanTomiZ Posted March 2, 2015 Author Share Posted March 2, 2015 That was getting Firmware and UI to the same point. Thanks for the update. Yes, that was the fix...Thanks for all of your input... Link to comment
PhanTomiZ Posted March 2, 2015 Author Share Posted March 2, 2015 How do I mark this topic off as "Answered"? Link to comment
LeeG Posted March 2, 2015 Share Posted March 2, 2015 Never have, most folks don't, but I think the initial topic post can be updated changing the topic Title. See link below. http://forum.universal-devices.com/topic/13617-leak-detector-problems-solved/ Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.