lgilsenberg

Thank you, I thought my system might be corrupted. I appreciate the insight.

I was doing some work in the admin console and left for a while. When I came back, I saw this error. This is the second time it has happened. Does anybody have any insight into it? Thanx

Thank you @paulbates. The restore after the factory wipe did the trick.

I have the 4814 Rev 2.6 Insteon Motion Sensor which has been working fine for many years. Recently it has not been accepting scene modifications, so I tried viewing the links table to compare it to the PLM. I got the following error: I tried removing the device and got this error: Is it time to scrap it and buy a new motion sensor or is there a fix? I tried a factory reset and that did not help. If it is time to get a new motion sensor, any recommendations?

@larryllix You nailed it. It was a 0 that looked like an 8. Thank you @Brian H and @paulbates

I've been trying to add the Insteon Dimmer Outlet 2472DLAL to the EISY and keep getting the message "Cannot determine Insteon engine". Any suggestions on getting it to work?

I would likely write it like this just for clarity North Gate OPEN - [ID 0019][Parent 0031] If ( 'Main House / Sensors / North Gate' is switched On Or 'Main House / Sensors / ZY 033 North_Gate' Access Control is Window/door is open ) And $Gates_ProgON is 0 Then $North_Gate_Open = 1 Run Program '_North Gate' (If) Else - No Actions - (To add one, press 'Action')

Is there a way to change the time allowed before the Admin Console times out?

I found an alternative way to delete scenes in the Alexa app . . . You would need to add the scene to a Group, then delete it from there. Open the Alexa App. Select Devices, then select a Group and hit "Edit" in the top right corner. Scroll all the way down and add these extra Scenes to the Group and save. While looking at the Group, scroll down and tap on the Scene and then you'll see the trash can icon to delete it. Not elegant, but it works

In version 4.x, I believe there was a checkbox in the scene that would "Apply changes to all devices" and copy the attributes to controllers [on page 103 in the Cookbook]. Was that capability removed in v5.x?

@Geddy I did change the network configuration, swapping from one wireless router to another. I just turned off port forwarding and everything has quieted down. I appreciate the guidance. @Techman I would have opened a ticket, but I'm still on 994 until the ZWave and Matter board are back in stock.

Just a bump. Does anybody have any suggestions on how to get rid of the errors popping up in the log? Is this somebody trying to hack me or did I mess up the network configuration or ?????

Below is my error log from today. Am I being hacked or just being stupid? Any thoughts on how to clean it up? Sun 2023/11/05 01:16:07 AM System -5011 uuid:0 Sun 2023/11/05 01:46:18 AM System -170001 [Auth:-10104] 68.69.185.50:50950->80, Num=7 Sun 2023/11/05 01:46:18 AM System -10108 Check log Sun 2023/11/05 01:49:06 AM System -170001 [Auth:-10104] 2.57.122.233:51112->80, Num=8 Sun 2023/11/05 01:49:06 AM System -10108 Check log Sun 2023/11/05 01:00:07 AM System -7123 ID 000F :err=0, tag='status', num=44, nest=4, o Sun 2023/11/05 01:00:07 AM System -7115 ID 0022 :err=0, tag='cmd', num=4, nest=4, offse Sun 2023/11/05 01:00:08 AM System -7115 ID 0034 :err=0, tag='cmd', num=4, nest=4, offse Sun 2023/11/05 01:00:10 AM System -7115 ID 0096 :err=0, tag='cmd', num=4, nest=4, offse Sun 2023/11/05 01:00:11 AM System -7123 ID 00AB :err=0, tag='status', num=44, nest=4, o Sun 2023/11/05 01:00:11 AM System -7123 ID 00BA :err=0, tag='status', num=44, nest=4, o Sun 2023/11/05 01:39:34 AM System -170001 [Auth:-10104] 64.226.98.14:43958->80, Num=9 Sun 2023/11/05 01:39:34 AM System -10108 Check log Sun 2023/11/05 01:39:37 AM System -170001 [Auth:-10104] 64.226.98.14:43962->80, Num=10 Sun 2023/11/05 01:39:37 AM System -10108 Check log Sun 2023/11/05 02:05:22 AM System -170001 [Auth:-10104] 184.105.139.70:16952->443, Num=1 Sun 2023/11/05 02:05:22 AM System -10108 Check log Sun 2023/11/05 02:05:51 AM System -170001 [Auth:-10104] 184.105.139.70:34834->443, Num=1 Sun 2023/11/05 02:05:51 AM System -10108 Check log Sun 2023/11/05 02:16:05 AM System -5011 uuid:0 Sun 2023/11/05 03:22:36 AM System -170001 [Auth:-10104] 107.175.212.32:49180->80, Num=13 Sun 2023/11/05 03:22:36 AM System -10108 Check log Sun 2023/11/05 04:16:06 AM System -5011 uuid:0 Sun 2023/11/05 04:37:14 AM System -170001 [Auth:-10104] 209.201.15.190:38322->80, Num=14 Sun 2023/11/05 04:37:14 AM System -10108 Check log Sun 2023/11/05 04:37:14 AM System -170001 [Auth:-10104] 209.201.15.190:38354->80, Num=15 Sun 2023/11/05 04:37:14 AM System -10108 Check log Sun 2023/11/05 05:20:02 AM System -170001 [Auth:-10104] 192.241.236.81:39558->443, Num=1 Sun 2023/11/05 05:20:02 AM System -10108 Check log Sun 2023/11/05 06:16:07 AM System -5011 uuid:0 Sun 2023/11/05 06:17:43 AM System -170001 [Auth:-10104] 34.78.54.63:38046->443, Num=17 Sun 2023/11/05 06:17:43 AM System -10108 Check log Sun 2023/11/05 07:40:49 AM System -170001 [Auth:-10104] 69.162.243.124:60896->80, Num=18 Sun 2023/11/05 07:40:49 AM System -10108 Check log Sun 2023/11/05 07:40:49 AM System -170001 [Auth:-10104] 69.162.243.124:60914->80, Num=19 Sun 2023/11/05 07:40:49 AM System -10108 Check log Sun 2023/11/05 07:42:08 AM System -170001 [Auth:-10104] 147.78.103.170:60019->80, Num=20 Sun 2023/11/05 07:42:08 AM System -10108 Check log Sun 2023/11/05 07:42:08 AM System -170001 [Auth:-10104] 147.78.103.170:60019->80, Num=21 Sun 2023/11/05 07:42:08 AM System -10108 Check log Sun 2023/11/05 07:42:08 AM System -170001 [Auth:-10104] 147.78.103.170:60019->80, Num=22 Sun 2023/11/05 07:42:08 AM System -10108 Check log Sun 2023/11/05 07:42:09 AM System -170001 [Auth:-10104] 147.78.103.170:60954->80, Num=23 Sun 2023/11/05 07:42:09 AM System -10108 Check log Sun 2023/11/05 07:42:10 AM System -170001 [Auth:-10104] 147.78.103.170:61570->80, Num=24 Sun 2023/11/05 07:42:10 AM System -10108 Check log Sun 2023/11/05 07:42:10 AM System -170001 [Auth:-10104] 147.78.103.170:62189->80, Num=25 Sun 2023/11/05 07:42:10 AM System -10108 Check log Sun 2023/11/05 07:42:10 AM System -170001 [Auth:-10104] 147.78.103.170:62189->80, Num=26 Sun 2023/11/05 07:42:10 AM System -10108 Check log Sun 2023/11/05 07:42:11 AM System -170001 [Auth:-10104] 147.78.103.170:62189->80, Num=27 Sun 2023/11/05 07:42:11 AM System -10108 Check log Sun 2023/11/05 07:42:11 AM System -170001 [Auth:-10104] 147.78.103.170:62189->80, Num=28 Sun 2023/11/05 07:42:11 AM System -10108 Check log Sun 2023/11/05 07:42:11 AM System -170001 [Auth:-10104] 147.78.103.170:62189->80, Num=29 Sun 2023/11/05 07:42:11 AM System -10108 Check log Sun 2023/11/05 07:42:11 AM System -170001 [Auth:-10104] 147.78.103.170:62189->80, Num=30 Sun 2023/11/05 07:42:11 AM System -10108 Check log Sun 2023/11/05 07:42:11 AM System -170001 [Auth:-10104] 147.78.103.170:62189->80, Num=31 Sun 2023/11/05 07:42:11 AM System -10108 Check log Sun 2023/11/05 07:51:30 AM System -170001 [Auth:-10104] 94.142.138.104:45722->443, Num=3 Sun 2023/11/05 07:51:30 AM System -10108 Check log Sun 2023/11/05 07:51:46 AM System -170001 [Auth:-10104] 94.142.138.104:44362->443, Num=3 Sun 2023/11/05 07:51:46 AM System -10108 Check log Sun 2023/11/05 08:16:07 AM System -5011 uuid:0 Sun 2023/11/05 09:56:46 AM System -170001 [Auth:-10104] 164.92.232.89:53526->443, Num=34 Sun 2023/11/05 09:56:46 AM System -10108 Check log Sun 2023/11/05 09:56:49 AM System -170001 [Auth:-10104] 164.92.232.89:56792->443, Num=35 Sun 2023/11/05 09:56:49 AM System -10108 Check log Sun 2023/11/05 10:16:08 AM System -5011 uuid:0 Sun 2023/11/05 10:57:38 AM System -7123 ID 000F :err=0, tag='status', num=44, nest=4, o Sun 2023/11/05 10:57:38 AM System -7115 ID 0022 :err=0, tag='cmd', num=4, nest=4, offse Sun 2023/11/05 10:57:39 AM System -7115 ID 0034 :err=0, tag='cmd', num=4, nest=4, offse Sun 2023/11/05 10:57:41 AM System -7115 ID 0096 :err=0, tag='cmd', num=4, nest=4, offse Sun 2023/11/05 10:57:42 AM System -7123 ID 00AB :err=0, tag='status', num=44, nest=4, o Sun 2023/11/05 10:57:42 AM System -7123 ID 00BA :err=0, tag='status', num=44, nest=4, o Sun 2023/11/05 12:01:09 PM System -170001 [Auth:-10104] 78.153.140.221:32814->80, Num=36 Sun 2023/11/05 12:01:09 PM System -10108 Check log Sun 2023/11/05 12:16:03 PM System -5011 uuid:0 Sun 2023/11/05 01:00:49 PM System -170001 [Auth:-10104] 83.97.73.87:43642->80, Num=37 Sun 2023/11/05 01:00:49 PM System -10108 Check log Sun 2023/11/05 02:16:03 PM System -5011 uuid:0 Sun 2023/11/05 03:05:01 PM System -170001 [Auth:-10104] 83.97.73.87:41304->80, Num=38 Sun 2023/11/05 03:05:01 PM System -10108 Check log Sun 2023/11/05 04:11:01 PM System -170001 [Auth:-10104] 107.170.253.36:49884->80, Num=39 Sun 2023/11/05 04:11:01 PM System -10108 Check log Sun 2023/11/05 04:16:03 PM System -5011 uuid:0 Sun 2023/11/05 04:29:28 PM System -170001 [Auth:-10104] 207.154.194.231:34266->443, Num= Sun 2023/11/05 04:29:28 PM System -10108 Check log Sun 2023/11/05 04:29:30 PM System -170001 [Auth:-10104] 207.154.194.231:34278->443, Num= Sun 2023/11/05 04:29:30 PM System -10108 Check log Sun 2023/11/05 04:29:42 PM System -170001 [Auth:-10104] 207.154.194.231:52664->443, Num=

paulbates, you are my hero. I'm back in the saddle. Thank you

It looks like a messed up the network settings on my ISY since I am no longer able to start the admin console. I am able to reach the ISY via UDI Mobile and via the web, but don't know how to adjust the ports that I changed. Must I do a factory reset and then a restore to get back to working? BTW, I changed the ports because I was generating errors in the error log after replacing the router.

I apologize if this is a stupid question, but . . . I replaced a dying router with Eero Mesh router. (I don't know much about networking). Since then, my ISY has been generating a lot of errors. I am getting the following errors in the error log: - 5011 (Process Device State Change SID not found) - 5012 (UPNP Subscriber NOREPLY to event 1) I'm not very good at networks, does anybody have a suggestion?

What brand of router did you change to? Eero 6+ Are you running any firewall software on your computer? No Did you get an advanced router that you setup different v-lans? Just went through the basic setup in Eero Have you tried with the computer hard wired to the same router? I have not, but I can access the ISY by calling it's IP address and also by UD Mobile. Can you pint the ISY IP from your computer? Yes Log into your router and look for “connected devices” and find the IP of the ISY994 then add it manually to the finder to be sure you can connect locally. Done I do not see it with the Launcher and don't know how to access the program without it. The "not found" error went away after I followed the instructions to clear java cache (all 3 buttons) then remove start and admin jnlp's and relound the launcher.

After clearing my cache (all three boxes) Removing all start.jnlp and all admin.jnlp Downloading https://isy.universal-devices.com/start.jnlp I can no longer find my ISY. Also during this process, I replaced my router. Any thoughts on how I can get access to my ISY994 again? Ideas would be greatly appreciated. I am still able to access it through UDI mobile.

Thank you for the diagnosis. Would you have any recommendations? Should I downgrade the launcher? Can I upgrade the ISY? Should I live with it?

When I start IoX Launcher I get a Not found message. I click OK, I get another. Then it seems to work fine. Any suggestions?

@MrBill I just checked the error log. Wow, there's a lot going on. I'm running 994 v5.3.4. The error log is below, not sure how to even begin to figure this out. Mon 2022/11/14 12:56:22 AM System -100 [DHCP] state=RENEW Mon 2022/11/14 03:00:37 AM System -5012 0 Mon 2022/11/14 03:00:45 AM System -170001 UDQ: Queue(s) Full, message ignored Mon 2022/11/14 03:00:42 AM System -140000 sub.isy.io Mon 2022/11/14 03:00:42 AM System -5013 0 Mon 2022/11/14 03:00:52 AM System -5012 35 Mon 2022/11/14 03:01:10 AM System -140000 my.isy.io Mon 2022/11/14 03:01:45 AM System -140000 my.isy.io Mon 2022/11/14 03:02:26 AM System -100 No network connection Mon 2022/11/14 03:03:06 AM System -170001 [Network] Established Mon 2022/11/14 10:25:44 AM System -5012 36 Mon 2022/11/14 11:01:04 AM System -5012 37 Mon 2022/11/14 11:41:58 AM System -100 [DHCP] state=RENEW Mon 2022/11/14 02:13:28 PM System -170001 [UDSockets] PSub:42 error:6 Mon 2022/11/14 02:13:32 PM System -5012 0 Mon 2022/11/14 10:41:41 PM System -100 [DHCP] state=RENEW Tue 2022/11/15 09:11:40 AM System -100 [DHCP] state=RENEW Tue 2022/11/15 03:18:55 PM System -5012 0 Tue 2022/11/15 03:19:01 PM System -5013 0 Tue 2022/11/15 04:57:46 PM System -5 Start Tue 2022/11/15 04:57:48 PM System -110022 /CONF/INSTENG.OPT Tue 2022/11/15 04:57:48 PM System -110012 /CONF/INSTENG.OPT Tue 2022/11/15 04:57:53 PM System -110022 /DEF/F6/I1/NLS/EN_US.TXT Tue 2022/11/15 04:57:53 PM System -110022 /CONF/UXT.BIN Tue 2022/11/15 04:57:53 PM System -110012 /CONF/UXT.BIN Tue 2022/11/15 04:57:56 PM System -7153 ID 0052 :err=0, tag='/node', num=28, nest=5, of Tue 2022/11/15 04:58:02 PM System -170001 [Network] Established Tue 2022/11/15 04:59:07 PM System -170001 UDQ: Queue(s) Full, message ignored Tue 2022/11/15 04:59:07 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Tue 2022/11/15 04:59:17 PM System -170001 UDQ: Queue(s) Full, message ignored Tue 2022/11/15 04:59:40 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Tue 2022/11/15 05:00:04 PM System -170001 UDQ: Queue(s) Full, message ignored Tue 2022/11/15 05:00:07 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Tue 2022/11/15 05:00:15 PM System -170001 UDQ: Queue(s) Full, message ignored Tue 2022/11/15 04:59:36 PM System -5011 uuid:0

Happy Tuesday, I've been noticing that Alexa and UDI Mobile periodically stop working with my ISY. I reboot the ISY and it starts working again. 2 questions: 1) Is there a way to schedule a daily reboot? 2) Any suggestions to try so I don't have to reboot?

Just found out from Michel that you have to set the motion sensor (or any battery device) into communication mode and write the changes once. After that it works fine. Thank you all for your help.

When I make the controller "Motion Sensor" I start teeing up writes to the motion sensor. If I do this several times a day with a myriad of motion sensors, I don't know what will happen.

Now I understand. Thank you. Another question comes to mind . . . Since the motion sensor is the controller of the scene being adjusted and the motion sensor is a battery device, how do you put the motion sensor in "communications mode" programmatically?