walkman9999

Ok, summing up: will hold off on upgrading allowing overall restore to continue (and won’t do that again) will reset device and restore the specific device the device is set to be off in scene, problem is it doesn’t turn off when it is on when scene runs Will update topic after restore and trying above. Very much appreciate discussion

I'm in the middle of restore devices now - seems like I should let it continue? If so, when it is completed I will both upgrade and factory reset/restore as suggested. Thank you.

I did a restore on the specific device and it didn't change anything. I am now in process of restoring everything (file>restore devices). I really don't know enough to say why I'm doing this, but it is processing now.

Also, just noticing that if I test the Scene using Tools>Diagnostics it works fine. Problem only occurs when I trigger the scene from a button on a keypad. Scene test results attached ISY-Events-Log.v4.9.0__Sat 2022.12.03 12.31.40.txt

Hello, ISY994i PRO v.4.9.0 ISY (Help->About screenshot attached ) Existing installation, problem seems to be with one switchlink dimmer (2476d v40). The switch works fine using the physical control. First problem I noticed is that the switch doesn't respond to scene control, it is supposed to turn off when scene is triggered, but doesn't. Then I tested the switch from the admin console and noticed that "Fast On" turns device on, but "On" doesn't. Event viewer output below: "Fast ON" (works as expected) Sat 12/03/2022 11:56:24 : [INST-TX-I1 ] 02 62 1A 3D 87 0F 12 00 Sat 12/03/2022 11:56:24 : [INST-ACK ] 02 62 1A.3D.87 0F 12 00 06 LTON-F (00) Sat 12/03/2022 11:56:24 : [INST-SRX ] 02 50 1A.3D.87 52.65.4C 2B 12 00 LTON-F (00) Sat 12/03/2022 11:56:24 : [Std-Direct Ack] 1A.3D.87-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/03/2022 11:56:24 : [D2D EVENT ] Event [1A 3D 87 1] [ST] [255] uom=0 prec=-1 Sat 12/03/2022 11:56:24 : [ 1A 3D 87 1] ST 255 "ON" doesn't turn the device on Sat 12/03/2022 11:56:05 : [INST-TX-I1 ] 02 62 1A 3D 87 0F 11 00 Sat 12/03/2022 11:56:05 : [INST-ACK ] 02 62 1A.3D.87 0F 11 00 06 LTONRR (00) Sat 12/03/2022 11:56:06 : [INST-SRX ] 02 50 1A.3D.87 52.65.4C 2B 11 00 LTONRR (00) Sat 12/03/2022 11:56:06 : [Std-Direct Ack] 1A.3D.87-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 (seems to be missing the stuff above in RED) Not sure what to look at from troubleshooting perspective. Any suggestions for tests or info to gather? Thanks for reading.

THis seems to be the case. Thank you.

Hello - Existing installation with no recent configuration changes. Lately I've been getting text notifications with the expected/proper timestamp in the message body (created with the ${sys.time12} variable), but a text message time of many hours later. I would assume carrier problem (Verizon), but other texts - including tests from ISY - don't have this problem. Is there a way to enable logging on ISY to show when the message is sent to the SMTP server? Trying to determine where the delay is. Thanks for any advice. :Mike

Is there a way to tweak it to try more times? I am pretty sure the RF distance is an issue, but that is where the door is so not sure what else I can do? Open to suggestions, but I realize there may not be a way around my problem. Thanks LeeG

The motion detector is working again, but I am still trying to figure out if the communication between the motion senso and the nearest dual-band device is the cause of the problem. I was able to capture the attached debug when the program was triggered. Wondering if anyone can look at it and assess the communication on the network? The motion detector is 2D.64.89. The program that gets triggered: door-programs.txt The log file: ISY-Events-Log.v4.1.2__Fri 2014.10.03 12.21.03.txt Thanks! ISY-Events-Log.v4.1.2__Fri 2014.10.03 12.21.03.txt door-programs.txt

HI larryllix, Thank you. I will enable the level3 debug and set the unit to 'off' disabled. My program logic doesn't use the 'off' command anyway - I'm using the "control" function to trigger the program. Will report back.

Sorry for ambiguous title, not sure what the actual problem is. The motion sensor occasionally reports as "on" in the ISY console regardless of its actual status. I can place it right next to a dual-band receiver (to account for possible RF distance issues), put it in a drawer (to account for spurious motion detection), and even take the battery out (for who knows why) but ISY still reports as "on". When this problem isn't happening, ISY reports the detector as off. This happens about once every two weeks Notes: I have on/off checked in "options" so that off command is sent when timeout value expires. When I check status from ISY (after pressing "set" button), it reads the motion detector fine. I've changed batteries. Any troubleshooting tips?

Thank you for the suggestion. Philosophically, it is a little hard for me to justify buying another piece to supplement a piece (presumably the PLM) that isn't working correctly, but from a tech standpoint the idea is a good one. I'm going to bark up the Insteon tree and see what they say. I'll report back as appropriate. Great forum, thanks again all.

Thanks all.

Thanks for the info, hoping to get some more details. Beta test: is the beta a new piece of hardware, or just firmware (I assume hardware). If so, any suggestions on how to get my hands on it? Program to query i/o sensor: any idea what interval would work? And perhaps some sample code? Any help is appreciated as I just saw on the camera that my damn garage door is up unexpectedly.

Hi all, I have an occasional problem where all the devices in my network are triggered on, apparently by an Insteon motion detector (link to this problem here). Although I did narrow it down to a motion detector-triggered event, the problem was never solved. Most of the devices that get triggered during this anomalous event are just lights and are of little consequence, but one of the devices that gets triggered is a Insteon relay that I use to open/close the garage door which is a bit more of an issue for me. To mitigate the unsolvable problem, I would like to receive a notification if the garage door relay is triggered. Unfortunately, the rouge commands that triggers all my devices on (and consequently opens the door) isn't the result of a program and I'm not sure how to do this or if it is possible. TLDR; I have notifications setup for program-triggered events, but I'd like to have a status change of a device send a notification if possible. Thanks for any input. :Mike

Here are the preceeding events. The "Beeps" are triggered by the motion sensor on the door and are used as an alert. Main House / Keypads / Front Door Status 50% Wed 2014/06/04 16:03:41 System Log Main House / Keypads / Front Door Off 0 Wed 2014/06/04 16:04:41 Program Log Scene:South Gate Open Off 0 Wed 2014/06/04 16:04:41 Program Log Main House / Keypads / Front Door Status 0% Wed 2014/06/04 16:04:42 System Log Main House / Keypads / Bedroom / Bedroom E Status 0% Wed 2014/06/04 16:04:42 System Log Main House / Motion-Door Sensors / Motion Sensor - Sensor Status 0% Wed 2014/06/04 16:04:48 System Log Main House / Motion-Door Sensors / Motion Sensor - Sensor Status 100% Wed 2014/06/04 16:16:57 System Log Main House / Keypads / Front Door On 255 Wed 2014/06/04 16:16:57 Program Log Scene:South Gate Open On Wed 2014/06/04 16:16:58 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:16:58 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:16:58 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:16:58 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:16:58 Program Log Main House / Keypads / Front Door Status 100% Wed 2014/06/04 16:16:58 System Log Main House / Keypads / Bedroom / Bedroom E Status 100% Wed 2014/06/04 16:16:58 System Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:16:59 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:01 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:01 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:01 Program Log Main House / Keypads / Front Door On 255 Wed 2014/06/04 16:17:01 Program Log Scene:South Gate Open On Wed 2014/06/04 16:17:02 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:02 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:02 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:02 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:02 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:03 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:04 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:07 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:08 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:08 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:09 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:09 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:10 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:10 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:12 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:12 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:13 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:13 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:14 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:17:14 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:17:14 Program Log Main House / Keypads / Front Door On 127 Wed 2014/06/04 16:17:44 Program Log Main House / Keypads / Front Door Status 50% Wed 2014/06/04 16:17:44 System Log Main House / Motion-Door Sensors / Motion Sensor - Sensor Status 0% Wed 2014/06/04 16:18:01 System Log Main House / Keypads / Front Door Off 0 Wed 2014/06/04 16:18:44 Program Log Scene:South Gate Open Off 0 Wed 2014/06/04 16:18:44 Program Log Main House / Keypads / Front Door Status 0% Wed 2014/06/04 16:18:44 System Log Main House / Keypads / Bedroom / Bedroom E Status 0% Wed 2014/06/04 16:18:45 System Log Main House / Motion-Door Sensors / Motion Sensor - Sensor Status 100% Wed 2014/06/04 16:19:55 System Log Main House / Keypads / Front Door On 255 Wed 2014/06/04 16:19:55 Program Log Scene:South Gate Open On Wed 2014/06/04 16:19:56 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:19:56 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:19:56 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:19:56 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:19:56 Program Log Main House / Keypads / Front Door Status 100% Wed 2014/06/04 16:19:56 System Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:19:57 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:19:57 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:19:58 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:00 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:00 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:00 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:01 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:03 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:03 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:04 Program Log Main House / Keypads / Front Door On 255 Wed 2014/06/04 16:20:04 Program Log Scene:South Gate Open On Wed 2014/06/04 16:20:05 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:05 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:05 Program Log Main House / Keypads / Bedroom / Bedroom E Status 100% Wed 2014/06/04 16:20:06 System Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:07 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:08 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:08 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:09 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:09 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:10 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:10 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:12 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:12 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:13 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:13 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:14 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:14 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:16 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:16 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:17 Program Log Main House / Garage Door Beep 250 Wed 2014/06/04 16:20:17 Program Log Main House / Keypads / Bedroom Beep 250 Wed 2014/06/04 16:20:17 Program Log

Yes, all devices triggered. Battery status shows OK, but I can replace easily enough so I'll try that. Sorry for poor formatting, but these are the relevant log entries. All listed in black whereas other log entries are blue. I haven't read enough about logs yet to know what is wht, but I'm reading now. Main House / Keypads / Office Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Keypads / Office / Office H Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Bathroom N Status 100% Wed 2014/06/04 16:20:39 System Log Outside / South Lights Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Living Room Track Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Kitchen Track Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Keypads / Back Door Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Keypads / Back Door / Back Door H Status 100% Wed 2014/06/04 16:20:39 System Log Outside / North Lights Status 100% Wed 2014/06/04 16:20:39 System Log Outside / West Lights Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Bathroom S Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Keypads / Bedroom Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Keypads / Bedroom / Bedroom H Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Living Room Lamp Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Keypads / Front Door / Front Door H Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Kitchen Accents Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Kitchen Cabinet Cans Status 100% Wed 2014/06/04 16:20:39 System Log Main House / Kitchen Island Cans Status 100% Wed 2014/06/04 16:20:39 System Log Shed / Track 1 Shed Status 100% Wed 2014/06/04 16:20:39 System Log Shed / Track 2 Shed Status 100% Wed 2014/06/04 16:20:39 System Log Shed / Front Porch Shed Status 100% Wed 2014/06/04 16:20:39 System Log Shed / Back Porch Shed Status 100% Wed 2014/06/04 16:20:39 System Log Shed / Desk Shed Status 100% Wed 2014/06/04 16:20:39 System Log Shed / Desk Shed / Desk Shed H Status 100% Wed 2014/06/04 16:20:39 System Log [i added this break for clarity. Not sure what was going on, but a pause of ~3 seconds] Main House / Keypads / Office Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Keypads / Office / Office H Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Bathroom N Status 0% Wed 2014/06/04 16:20:42 System Log Outside / South Lights Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Living Room Track Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Kitchen Track Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Keypads / Back Door Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Keypads / Back Door / Back Door H Status 0% Wed 2014/06/04 16:20:42 System Log Outside / North Lights Status 0% Wed 2014/06/04 16:20:42 System Log Outside / West Lights Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Bathroom S Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Keypads / Bedroom Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Keypads / Bedroom / Bedroom H Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Living Room Lamp Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Keypads / Front Door Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Keypads / Front Door / Front Door H Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Kitchen Accents Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Kitchen Cabinet Cans Status 0% Wed 2014/06/04 16:20:42 System Log Main House / Kitchen Island Cans Status 0% Wed 2014/06/04 16:20:42 System Log Shed / Track 1 Shed Status 0% Wed 2014/06/04 16:20:42 System Log Shed / Track 2 Shed Status 0% Wed 2014/06/04 16:20:42 System Log Shed / Front Porch Shed Status 0% Wed 2014/06/04 16:20:42 System Log Shed / Back Porch Shed Status 0% Wed 2014/06/04 16:20:42 System Log Shed / Desk Shed Status 0% Wed 2014/06/04 16:20:42 System Log Shed / Desk Shed / Desk Shed H Status 0% Wed 2014/06/04 16:20:42 System Log Ignore / Unused Error 0 Wed 2014/06/04 16:20:45 System Log

Hi all, Obligatory thank yous in advance, this forum has been a great source of information. Over the last few days, the lights in my house have been triggered on without my input. Sometimes it is one light (on a keypad link), and most recently it was every device on my network all at once (approx 20 devices of various types, including an I/O link used to control garage door!). The events do not occur at any regular time or in concurrence with any other activity on the Insteon network that I know of. And, there are no programs that include every device, so I can't imagine it was a programmed event. When I look at the logs, it shows the events occurring, but I cannot tell what triggered them. Is it possible that some local RF source is causing the problem? Or possibly that the ISY box is being accessed from outside (I have a static NAT setup thru router, but do not use the default user/password). Quite disturbing, any ideas how to troubleshoot? Thanks!

You are right, I screwed-up the name of the module. Insteon says: "Please note that INSTEON Wireless Open/Close Sensor (2843-222) is the new product name and number of TriggerLinc (2421)." So, it is a triggerlinc not a togglelinc. That said, I think your solution will work - it makes sense logically. Let me give it a try and see. Thank you

Hi all, I have a togglelinc on my front door, and a motion sensor on front gate. Both work fine, but I'd like to combine them in a way that the condition of the togglelinc determines what program runs when the motion sensor is triggered. That is, if the front door (togglelinc) is open and motion detector is triggered then action1 is performed, but if front door (togglelinc) is closed and motion detector is triggered then action12 is performed. I'm not sure how to do this because togglelinc doesn't seem to indicate a current state (open or closed), it just reports a change in state (when door is opened or closed). I'm not sure how to write the program do "check" the togglelinc. I am looking at docs, but thought I'd ask the forum to see if there is a "smart" way to do this. Thanks any/all. :Mike

The beeps are not loud, but they can be made to happen in a lot of places so that helps! I'm using the beeps as a stopgap measure for chimes, but still looking for a more comprehensive solution. The idea of an I/Olinc and doorbell is a good one and I may try that later. Right now, I'm going ot try to figure somehting out with no new equipment as my SO continues to see these packages from Irvine, CA on the doorstep. Anyway I'll say again, this forum is great. Thanks for the help. :Mike

OK, thanks to all. I've got that program working, and learned a bit while doing it.

I see a "beep duration" setting, is there a way to make one or more of my Insteon devices beep? I have switchlincs, outletlincs and keypads. And, back to the original problem (Sorry for jumping around). I can't get the trigger/response to work correctly by following the examples above. I have a program "Door Trigger" that says: If Motion Sensor is on and light1 is at 100% Then Run "Door Responder" The "Door Responder" program says: set lamp1 fast on wait 2 seconds set lamp1 fast off wait 2 seconds set lamp1 fast on wait 2 seconds set lamp1 100% (to return lamp1 to its previous level of 100%) Problem is, lamp1 continues to cycle on/off way beyond the 3 blinks I have asked for. I think Door Trigger program gets triggered again b/c the motion sensor is still ON. I tried setting timeout for MS at .5, and I tried sending a "set motion sensor off" command through the program, but I don't think the device supports those options. Sorry if I'm being thick.

This is not technically on-topic, but maybe someone has already come-up with a creative solution for how to use the motion sensor for a "doorbell"? Blinking a household light is somewhat effective (above problems notwithstanding), but it isn't an exact fit. Maybe a sound as well? I have an outletlinc that I can plug something into, but not sure what to plug into it. Thoughts?

Thank you for the replies. I'm going to play with these ideas and see what I can make happen. Will report back. :Mike