lgilsenberg

@dbwarner5 Nice touch on the last program. I have had guests mention that my lights won't stay off.

I’m guess I should explain what I’m trying to do. I’m using a battery operated motion sensor to turn on a light. I want the on level to be different at different times of the day. I tried using adjust scene but it seems to not work if I do not have the motion sensor plugged in.

I see I can change On Level and Ramp Rate manually within EISY and I can change it programmatically by using adjust scene. Is there a way to programmatically adjust the device directly?

Guard mode is no longer supported. But if you used it in the past, it set up your home and away settings

After I turned on Alexa Plus, I found the devices were randomly turning on. I tried turning off Alexa Plus, renaming the spoken, using scenes instead of devices, turned off routines, turned off hunches and finally turned off the "spoken" on the devices so my wife wouldn't kill me. The only thing that worked was removing the spoken so it was clearly Alexa related. Today, I found out that somewhere in my history with Alexa and ISY, I had turned on Guard which uses Away and Home modes. Away mode allows you to select up to 3 devices to turn on and off at random times. One of the new options in Away mode with Alexa plus is to automatically include new devices. I turned off this capability, removed the devices and everything is working great. Here is how to turn it off: in Alexa app, go to devices pick a device that is turning on randomly select gear on top right click on "away lighting" below device name select choose lights uncheck any or all devices uncheck automatically add newly connected lights and Bob's your uncle

I guess you're right about checking the logs. BTW, I turned off hunches. (I had a hunch you'd say that) I don't have any of these devices in a routine. It is odd the way the devices randomly turn on, not only when Alexa plus is turned on but for a several days after reverting to regular Alexa too. (I think she was pissed at me) The random turn on has now stopped though.

@Geddy Do you have a recommendation for a different voice activation method? I hate to lose the capability to use Alexa reliably without a replacement.

I ran across the same thing a year or two ago. I believe what I changed the designation of the spoken command to device instead of scene or scene instead of device and that room care of it. I'm not a hundred percent sure, but it's worth a shot.

I feel like Alexa and EISY have broken up or at least pissed off at each other. I changed over to Alexa Plus, I really like how I can easily ask questions abut any topic and drill into details. If I have a question about any topic, Alexa hits me with the right answer more often than not . . . but the integration with EISY is no longer rock solid. I am finding that random lights come on. I remove the "Spoken name" and it stops. Sounds like an Alexa program. I add it back, it happens again. I change the name, same thing. I create a scene with the device in it, same problem. It turns it on randomly. I tried with a different switch, it worked fine. Why? I don't know. I tried going back to Alexa regular, the switch was made, same results. I love having voice control of the devices, but I'm stuck. Does anybody have a suggestion on how to fix it? Is there a different voice control that you recommend?

I noticed that three lights came on at random times. I have been able to remedy this by removing the spoken name for each of those devices. The rest of the house (a lot of devices) are still working flawlessly. When I reconnect with a spoken name, the devices will randomly turn on again. Dopes anybody have a suggestion other than keep the spoken name off? Thank you.

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.