GaryK4

Brian, That is what I did. I had a spare device that I set up as well. The spare worked fine. I tried the factory reset in the same outlet on the old one. It did the reset, but will NOT do the link step (double beep) Same procedure, same outlet different results.

Both of mine are: Insteon74551 Rev: 2.3 2214 on the label. I know how to solder, but I am not an electronic component guy. Are you suggesting to try replacing the C7 component? capacitors? If so where do i get it - Amazon? What part number do I search for? I think it is hard to read from the component. I'm retired, so I like projects to augment my golf & tennis ?

I have (2) IO Links for my garage doors and they both failed at the same time. I just want concurrence before I toss the in the garbage. I had a spare device and replaced one of the failed devices and it worked fine. Next, I took the failed units to my office and tried to do a factory reset. The manual says it should flash after (3) seconds. My flashed and beeped after (10) seconds. While there seems to be some life in them, I am unable to get then into the link mode! I press the set button for (3) plus seconds and nothing. Is there anything that I am missing? Or is it time to toss them?

All name have a red x next to them. Google says that it can not reach universal devices. I tried sending spoken to Google and got "Error sending your spokens. Google home API returned: INTERNAL Internal error encountered." Rebooted my computer and ISY. Made sure java was up to date. Troubleshooting reports "Everything appears to be configured correctly!" Now what? OK, I got it working. I had to go into the Google Home App, then unlink Universal devices. Fortunately, there was an option to reconnect. That worked and I did not have to actually unlink the devices.

I don't think my response was complete. I converted from V4 to V5 in late Oct 2020 timeframe. Was running V5 until this issue occurred. I used a new 32GB sd card and installed insteon_5_3_0.zip. I created a V5 backup file when I did the original upgrade (Oct). The restore was with the V5 backup. So, I did not use a v4 backup to get up and running again. Sorry for the confusion. Everything appears to be working fine, except a flaky Motion sensor which I don't think is related.

No, I did not even think of that! When I updated from V4 to V5, I followed the forum instructions. I have the file insteon_5_3_0.zip in my download folder. Then I did a manual upgrade using that file. Afterwards, I restored the last backup that I did. There were a couple of minor changes that was not in the backup which I fixed. Is that process OK? Next time, I will use the portal. I need to put that in my notes. Regards, Gary

OK, I looks like the 32GB cards work. I did have a backup file after all. It was a couple of months old. Mean while, I ordered (2) 8GB cards from Amazon thinking that I need them. Wow a whole $10. Finally, I think that I am under control. Not seeing any errors and my programs are back. I just have to test every thing to make sure. I created my own Raspberry Pi control panel and that is working again. Thanks for the help.

I think it is the sd card. Now it will not come up at all. Error led is lit and the memory led is blinking. I got bit to come up by connecting to a different switch. I'll figure that out later. Per the instructions, ISY only supports 16GB and all I have is a lot of 32GB! I will have to get a smaller card first.

Suddenly, ISY is having a number of issues. Ex: lights going on by themselves. Now, when I go into the console, none of the programs display. When I go into diagnostics, system status, Ii seems to give a different message each time. It is complicated by message boxes being on top of each other and you can't click OK because the active message is covered up. I rebooted the ISY a number of times. At least it is not going crazy and REST commands are working. I upgraded to v5.3 in late Nov. Unfortunately, the old guy forgot to make a backup once it was complete:-( Now what? Any suggestions?

I have a motion sensor that triggers a light on. If I disable the sensor, it still triggers and the light goes on. As a temporary work around, I set the On Level to off. The sensor is in a scene with a light switch and nothing else. Am I looking at this wrong? I'm assuming disable will ignore the trigger. I don't know if this is a version issue. Updated to 5.3 yesterday. Sensor: 2842-222 v.44 My wife does not want the porch lights to go on for Halloween To many bulbs to unscrew.

Goose66, That is exactly what I was trying to do. I was experimenting with variable, multi-programs and pulling my hair out (which I can't afford) ? Your solution is way too simple. It works great! I did not know that you could have a null if statement. I am still fuzzy on the reentry handling, but I will save that for another day. Thanks alot!

Wow, I am not used to a language doing this. I will have to figure out a workaround.

Currently, I use IFTTT and my own REST programs to handle voice control. Now I am testing Google Home with the portal. Scenes don't have feedback, so you may have to trigger it twice to get the desired results. I created a test program to control the media room lights. I only want the program to run once, then stop / exit. I put a stop program command at the end of the then & else, but that does not work. It just keeps running. While testing, I use the stop menu command and that does not stop it either. I have to disable an re-enable the program. What am I doing wrong? I am on version 4.8

I don't use the ISY Portal. I pass a PHP command to a Raspberry Pi's web server and that passes the REST command to ISY. I am not tech enough to know the dangers of this method, but at least there are no account info in the IFTTT applets. On the same Raspberry Pi, I developed a Python program that displays key devices. It has led's to warn if the garage doors are open. That way a casual look at the display tells you the status. I do use Mobilinc rarely and it is a very poor program. I don't mind paying for an app, but I don't like recurring costs. I also use Tiny Cam Pro to display my security cameras. How dangerous is this?

Thanks, I will try these options.

I have a program that sends me an email when a low battery is triggered. (send Notification to ...). This works well, however all I get is the address to the device. Is it possible to add the device name tp the message?

I have a shortcut on my desktop for admin.jnlp. Are there any command line arguments to allow automatic login? (username, password). Thanks,

I was checking out the error and there are a lot of errors being recorded. The documentation does not list -170001. What is causing this and how do I fix it? Thanks, ISY Error Log.v4.2.18__Sat 2015.01.24 03.17.20 PM.txt

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

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.

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?

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.

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.

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.

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.