Everything posted by LeeG
-
"Request Failed" Motion Sensor Device Options
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/
-
Changing Insteon TStat Temp and Humid offset using ISY994i
Unfortunately not. Need to use the procedure described in the TStat documentation.
-
"Request Failed" Motion Sensor Device Options
That was getting Firmware and UI to the same point. Thanks for the update.
-
"Request Failed" Motion Sensor Device Options
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.
-
"Request Failed" Motion Sensor Device Options
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
-
"Request Failed" Motion Sensor Device Options
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
-
"Request Failed" Motion Sensor Device Options
That is from 31.F3.4E, not 31 F3 64.
-
"Request Failed" Motion Sensor Device Options
Post an event trace of the Motion On/Off messages.
-
"Request Failed" Motion Sensor Device Options
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.
-
"Request Failed" Motion Sensor Device Options
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.
-
Keypad linc procedure, 8 button to 6?
Happy to help.
-
Keypad linc procedure, 8 button to 6?
Keypad Owner's Manual page 16-17 has description for moving from 8 to 6 and 6 to 8 Changing to 6-Button Configuration 1)Replace the 8-button plate with the 6-button plate - Attach the change-out plate to the switch body by aligning the tabs and snapping into place 2)Gently pull the Set button out as far as it will go 3)Wait 10 seconds 4)While simultaneously holding the On and Off buttons, carefully push the Set button back in, flush with the trim frame 5)Once the Set button is pushed in, continue holding the On and Off buttons for 3 seconds, and then release KeypadLinc will (Beep) KeypadLinc is now in 6 Button Mode
-
Using mini remote how do you add fast on off to a scene?
Running in non-toggle mode means only On/Fast On commands are desired. If the Mini Remote should send On and Off commands it must run in toggle mode. EDIT: unlike a KeypadLinc which supports a non toggle On or a non toggle Off, the Mini Remote supports a non toggle On only. The Mini Remote does not support a non toggle Off mode.
-
Using mini remote how do you add fast on off to a scene?
Not sure what the question is. This is an 8 button RemoteLinc2 (Mini Remote) in non-toggle mode. The trace shows two normal On commands to indicate non-toggle mode followed by a Fast On Sat 02/28/2015 12:14:35 PM : [iNST-SRX ] 02 50 1C.27.E3 00.00.02 CB 11 00 LTONRR (00) Sat 02/28/2015 12:14:35 PM : [std-Group ] 1C.27.E3-->Group=2, Max Hops=3, Hops Left=2 Sat 02/28/2015 12:14:35 PM : [D2D EVENT ] Event [1C 27 E3 2] [DON] [0] uom=0 prec=-1 Sat 02/28/2015 12:14:35 PM : [ 1C 27 E3 2] DON 0 Sat 02/28/2015 12:14:35 PM : [iNST-SRX ] 02 50 1C.27.E3 00.00.02 CB 11 00 LTONRR (00) Sat 02/28/2015 12:14:35 PM : [std-Group ] 1C.27.E3-->Group=2, Max Hops=3, Hops Left=2 Sat 02/28/2015 12:14:35 PM : [iNST-DUP ] Previous message ignored. Sat 02/28/2015 12:14:36 PM : [iNST-SRX ] 02 50 1C.27.E3 22.80.0B 41 11 02 LTONRR (02) Sat 02/28/2015 12:14:36 PM : [std-Cleanup ] 1C.27.E3-->ISY/PLM Group=2, Max Hops=1, Hops Left=0 Sat 02/28/2015 12:14:36 PM : [iNST-DUP ] Previous message ignored. Sat 02/28/2015 12:14:42 PM : [iNST-SRX ] 02 50 1C.27.E3 00.00.02 CB 11 00 LTONRR (00) Sat 02/28/2015 12:14:42 PM : [std-Group ] 1C.27.E3-->Group=2, Max Hops=3, Hops Left=2 Sat 02/28/2015 12:14:42 PM : [D2D EVENT ] Event [1C 27 E3 2] [DON] [0] uom=0 prec=-1 Sat 02/28/2015 12:14:42 PM : [ 1C 27 E3 2] DON 0 Sat 02/28/2015 12:14:42 PM : [iNST-SRX ] 02 50 1C.27.E3 00.00.02 CB 11 00 LTONRR (00) Sat 02/28/2015 12:14:42 PM : [std-Group ] 1C.27.E3-->Group=2, Max Hops=3, Hops Left=2 Sat 02/28/2015 12:14:42 PM : [iNST-DUP ] Previous message ignored. Sat 02/28/2015 12:14:42 PM : [iNST-SRX ] 02 50 1C.27.E3 22.80.0B 41 11 02 LTONRR (02) Sat 02/28/2015 12:14:42 PM : [std-Cleanup ] 1C.27.E3-->ISY/PLM Group=2, Max Hops=1, Hops Left=0 Sat 02/28/2015 12:14:42 PM : [iNST-DUP ] Previous message ignored. Sat 02/28/2015 12:14:47 PM : [iNST-SRX ] 02 50 1C.27.E3 00.00.02 CB 12 00 LTON-F (00) Sat 02/28/2015 12:14:47 PM : [std-Group ] 1C.27.E3-->Group=2, Max Hops=3, Hops Left=2 Sat 02/28/2015 12:14:47 PM : [D2D EVENT ] Event [1C 27 E3 2] [DFON] [0] uom=0 prec=-1 Sat 02/28/2015 12:14:47 PM : [ 1C 27 E3 2] DFON 0 Sat 02/28/2015 12:14:47 PM : [iNST-SRX ] 02 50 1C.27.E3 00.00.02 C7 12 00 LTON-F (00) Sat 02/28/2015 12:14:47 PM : [std-Group ] 1C.27.E3-->Group=2, Max Hops=3, Hops Left=1 Sat 02/28/2015 12:14:47 PM : [iNST-DUP ] Previous message ignored. Sat 02/28/2015 12:14:47 PM : [iNST-SRX ] 02 50 1C.27.E3 22.80.0B 41 12 02 LTON-F (02) Sat 02/28/2015 12:14:47 PM : [std-Cleanup ] 1C.27.E3-->ISY/PLM Group=2, Max Hops=1, Hops Left=0 Sat 02/28/2015 12:14:47 PM : [iNST-DUP ] Previous message ignored. Sat 02/28/2015 12:14:48 PM : [iNST-SRX ] 02 50 1C.27.E3 22.80.0B 43 12 02 LTON-F (02) Sat 02/28/2015 12:14:48 PM : [std-Cleanup ] 1C.27.E3-->ISY/PLM Group=2, Max Hops=3, Hops Left=0 Sat 02/28/2015 12:14:48 PM : [iNST-DUP ] Previous message ignored.
-
Wiring a 2476D to a Transformer
There is an Icon on the bottom of the Event Viewer, next to last on bottom right, that copies trace to Clipboard. Then Paste the trace into a post.
-
Wiring a 2476D to a Transformer
Can you add the device to the ISY with Tools | Diagnostics | Event Viewer at LEVEL 3 running. It will show what device type the device is reporting. Make sure there has not been an error in reading the Insteon address; 8 for B, etc. Odd that a new 2476D would identify itself as an ICON device no longer in production.
-
Programming Issues
There is no Scene On/Off test in Insteon. Could set a State Variable in Program 1 that Program 2 tests.
-
Can you make a dimmer, beep by a program?
Duration is not yet supported by SwitchLinc or Keypad
-
Question about the garage control kit
Only send a Relay On when door is Open.
-
Adjust Scene - with 3-Way switches
The Insteon devices support 1,000,000 updates. No chance of causing a problem beyond the devices normal life cycle.
-
Repeat statement not working
The ISY Wiki is a good source. This link covers various Program statements including Wait and Repeat that allow If section to reevaluate. http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Program_Commands
-
How to assign "scene" to a button on KeypadLinc Dimmer in ISY
Insteon dimmers are not designed for use with CFLs.
-
Garage Door / Switch not responding.
Tap the PLM Set button 4 times to start the RF beacon test. Look at the color of the LED blinking on the OutletLinc. I would expect it to be blinking Green. This test is to explain why the Hops Left=1 is occurring. When done tap the PLM Set button once to complete the beacon test. If not blinking or blinking Red there is something to look at.
-
Triggering Events to send messages
The Program will trigger with a False evaluation invoking the Else clause. EDIT: at a minimum a change in Garage-Sensor state will trigger the Program. The variables $Garage_Light_On and $GarageDoorOpen could trigger the Program as well if they are State variables.
-
Garage Door / Switch not responding.
Feet does not mean much. My detached garage is some 300 wire feet away and works okay. Has more to do with what is also powered from that circuit. The event trace is showing Max Hops Hops=3, Hops Left=1 which is fine if on the opposite 120v leg as the PLM. Run the 4 tap Set button beacon test to see if OutletLinc is on opposite 120v leg. The Hops Left=0 is a duplicate copy of the message from the I/O Linc. The Hops Left count is 1 on the primary response. Tue 02/24/2015 04:44:11 PM : [iNST-TX-I1 ] 02 62 2B F8 FE 0F 19 00 Tue 02/24/2015 04:44:11 PM : [iNST-ACK ] 02 62 2B.F8.FE 0F 19 00 06 LTSREQ (LIGHT) Tue 02/24/2015 04:44:12 PM : [iNST-SRX ] 02 50 2B.F8.FE 2A.A2.D3 27 00 00 (00) Tue 02/24/2015 04:44:12 PM : [std-Direct Ack] 2B.F8.FE-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 02/24/2015 04:44:12 PM : [iNST-SRX ] 02 50 2B.F8.FE 2A.A2.D3 23 00 00 (00) Tue 02/24/2015 04:44:12 PM : [std-Direct Ack] 2B.F8.FE-->ISY/PLM Group=0, Max Hops=3, Hops Left=0