Michaelco

I didn't make any changes to the Favorite's Span - went with whatever the default setting. I am using IOS devices, ... if that makes a difference.

Thanks for the detailed instructions. Works, ... will look forward to using custom icons when they are supported

I have added devices to Favorites and trying to figure out how to: I want, when tapping on the icon, for it to do the action directly. When I tap the lower portion of the icon, it brings up another screen (pic 2 below). I would like to disable this action, and have it just turn on the device associated with the icon. Allow custom colors depending on switch or sensor status Change the icon to show the device state Question 1: Is there a way to do this when setting up favorites on an iPhone? As an example, tapping the lower half region of the Gate relay (encircled in Pic 1) brings up the screen shown in Pic 2. Is there a mode where all the items in Favorites can be set to treat this lower region the same as the top portion? In other words, just open or close the gate Pic 1 Pic 2 Question 2 How can one, conditionally, set the color of the gate icon to some color (like Red) when it's open, and a different color (like Green) when it's closed? I have seen where I can change the icon color, but not conditionally based on the gate state. Question 3 Using the Gate Open-Close as an example, how best to switch between two images for the icon? i.e., have the closed gate icon (Pic 3) displayed when the gate is in closed position, and open gate icon (Pic 4) when gate is opened Pic 3 Pic 4

@DNewkirk Thanks for your help - all is working with the exception of an Insteon Motion sensor - deleted, and re-linked, without success.

The good thing about the ISY 994 was its stability. Haven’t had to fuss with it much over the 10 years, except when I've added functionality. The downside, is it’s a challenge to get back into it. I’m only using Insteon devices, which should make it simpler to upgrade to the EISY, but hit a problem early on. The reason I am upgrading to the EISY right now is for a new i3 paddle switch I am adding. The first issue occurred after scanning the QR code and UD Mobile trying to locate controllers on my network - I suspect I won’t have success until it has been resolved, but don’t have a clue on what the error message means. Anyone know why this occurs, and how to resolve? It seems the further I go into this, the more questions I have 🤫 I went another couple steps to see what is working and what isn’t. When I try to connect via UD Mobile, the message indicates the portal is waiting for my device to connect to the internet. When I look at the account via UD Mobile, it shows both UUIDs for the 994i and the new EISY, and saw that the ISY 994i, and EISY are both listed. So, wondered if the devices never connected to UD portal, how did the UUIDs become known? I'm guessing, UD Mobile found the controllers, and passed that on to the portal. But, for some reason, the controllers didn't proceed to connect. Are there any logs that would shed light on the problem? I didn’t proceed to Migrate the 994i to the EISY after seeing the warning that I won't be able to migrate the license back. Also have questions on what happens during migration? I see the list of license and spokens being moved to the EISY. Does it also move all the ISY 994 settings, variables and programs from to the EISY? If so, why is the backup called for in https://www.universal-devices.com/4x-migration/? Does restoration from backup come into play after clicking on the Migrate button, or is it simply a way to recover in the event of issues? Oh, ... so many questions. Has anybody done a screen recording of the complete process?? Thanks, in advance, for any help that you can provide

I'm getting ready to upgrade from 994i - it looks like the OpenADR Eisy can do more than just deal with power demand requests. Is that accurate? Is the Eisy Home a subset of Eisy OpenADR? Can the added functionality of the OpenADR be unused until the need exists? Is Eisy OpenADR only useful to allow utilities to signal power demand changes? Is there a comparison document/chart between the two? Can the EISY|Home be upgraded to include OpenADR at a later date? Not sure I would trust our utility to control our solar generation and power storage, but could see allowing the connection once there is evidence they are doing it well. Appreciate any help and insights 🙂

Thanks for the quick response and guidance. I'll search the forum for commands on controlling cameras. Thanks again

I understand cameras can detect motion and have seen some indication they can initiate an email - hadn't seen they could message. I wanted the ISY to initiate the process to avoid nuisance alerts - e.,g people or deer walking by. I'm only interested in getting the picture when a vehicle drives onto the driveway, and had intended to rely on the loops under the driveway to sense the vehicles presence. I am currently using the Insteon motion detector along with the signal from the loop detector to give context to a message - e.g, "Vehicle leaving the property", or "Vehicle entering the property". I thought there was a chance to do what I want if I used an Insteon ip camera in conjunction with the ISY, but I haven't seen any Insteon cameras that expose the functionality to message/email. Had hoped Insteon cameras could accept Insteon commands to message the current image. Regarding the wifi range - I can avoid providing environmental protection and power for a wifi extender if I can get a camera with range comparable to an iPad, but it wouldn't be the worst problem to deal with those issues. Do you know of any cameras out there that can be controlled by the ISY - either directly, or through some other piece of hardware? Would like to limit the search if possible - lots of choices

I would like to archive a picture(s) of cars that drive onto the driveway, and be able to review video before and after the time the image was sent. I'm thinking an outdoor wifi camera with storage (either internal, or SD card) would support what I want to do. Are there any cameras that would allow transmitting an image under ISY control? Are there some cameras with better wifi range than others, or are most of the wifi cameras pretty much the same? My network can reach the area for devices like iPads, and laptops, but don't know the sensitivity of the cameras. I don't want to use up network bandwidth for the video as a general course of action. But, if there is some activity that needs further review, I'd want to be able to scan through video stored in the camera's memory. I would want to have the camera transmit an image at time of an event. Ideally via messaging, but email would be a good second choice. Events would be initiated by change of state of Insteon I/O Linc devices, and Insteon motion detectors. Appreciate any camera recommendations that would accomplish what I'm trying to do.

For what it's worth, no unusual behavior today - after, changing the ISY Query runtime to later in the morning. Any reasons not to update to the latest ISY firmware? I held off updating, as I didn't have the time to deal with any issues that might have come up. If there aren't any big issues with the latest version, I may go ahead and install - now that I'm somewhat back into the mindset. I'd still wait a few days, to verify the two days were just an aberration.

I'm running firmware version 4.2.15 on the ISY 994i Pro.

I have 38 programs. No other programs run when I execute the 'Then' section of code of the ISY Query - I don't "get it".

Thanks, for the suggestion that I verify the "Trigger Reverse" - it is still de-selected. I forgot to say, the system has been running well, and the last programing changes I made was March 9th - and, in a different area. Up until yesterday, it has behaved as I would have expected. This morning, for whatever reason, the gate status changed state 14 seconds after the 3 am ISY Query was run. And, the outdoor lights turned on (as they should if the gate status went to 100%). I don't believe the "Status 'The Gate Status' is not off" is the reason the gate opened (or why the driveway lights came on yesterday). If the code was "Status 'The Gate Status' is On" I would expect the lights to come on (as they did). For me, the two mysteries are 1) Why the gate status changed state after the ISY Query this morning, 2) and why the Driveway lights came on after the ISY Query ran the day before. When I ran the ISY Query 'Then' code this morning (11:03 am), nothing else ran - e.g., looking at the log, or the program list in the console. The gate didn't open, nor did the driveway lights come on. Maybe more data points will come tonight :~{

I have had some of the outdoor lights coming on during the last two days. Both this morning and yesterday morning, at 3:00 am. This time period corresponds to the ISY Query, however, I only have three scenes I've set up, and any correlation to the ISY Query doesn't make sense. Furthermore, the entrance gate showed a status of opening right after the ISY Query ran - there should be no connection between the ISY Query and the entrance gate opening, so this event doesn't make sense. I've color coded three different events in the log entries (below) - I also attached the excerpt of the log because of format issues with the forum post. Any insights, or suggestions would be appreciated. I have changed the time the ISY Query fires off - from 3 AM to 8 AM, to reduce the risk of dear walking through the entrance - which is the primary reason we have enclosed the property. History for : Yesterday morning: Driveway lights came on at 3 am - they were the only lights that came on The only scene the driveway lights are associated with is "Scene OutDoor Path Light", which affects the following 4 sets of lights. 1) Driveway Lights 2) Entry Porch Lights 3) Garage Outside North 4) Garage Outside West So, if the "Scene OutDoor Path Light" triggered, I would have expected more than the 5 driveway lamp posts to turn on. This morning, was a different situation. 14 seconds after the ISY Query ran, the entrance gate status changed state. This triggered the "Scene OutDoor Path Light" on, and the set of lights embedded in the sidewalk (Paver Lights) to turn on as well. 5 minutes later, the GateIsOpenCloseIt program tries to close the gate without success - the GateIsOpenCloseIt program's objective is to ensure the gate is closed during the evening after 8 pm. I haven't seen any explanation/reason for the gate opening at 3 am, but upon opening, I would have expected the path lights to come as they did - and stay on until the gate status changed to closed. Quite baffling! I am using the "sense" side of the Insteon 2450 I/O module to monitor the gate closed limit switch, and the normally open contact of the same module to open/close the gate. ==================== Applicable portion of Logs ====================== Yesterday: Scene:ISY Status Query Tue 2015/04/21 03:00:00 AM Program Log Driveway Lights Status 100% Tue 2015/04/21 03:00:13 AM System Log Today: Scene:ISY Status Query Wed 2015/04/22 03:00:00 AM Program Log The Gate Status Status 100% Wed 2015/04/22 03:00:14 AM System Log Scene:Scene OutDoor Path Light On Wed 2015/04/22 03:00:15 AM Program Log Garage Outside West Status 100% Wed 2015/04/22 03:00:16 AM System Log Garage Outside North Status 100% Wed 2015/04/22 03:00:16 AM System Log Entry Porch Light Status 100% Wed 2015/04/22 03:00:16 AM System Log Driveway Lights Status 100% Wed 2015/04/22 03:00:16 AM System Log Sidewalk Paver Lights On Wed 2015/04/22 03:00:16 AM Program Log Sidewalk Paver Lights Status 100% Wed 2015/04/22 03:00:17 AM System Log Gate Open-Close Off 0 Wed 2015/04/22 03:05:15 AM Program Log ========================= End of logs ========================================= ========= Referenced Programs ============ TempPathLightsOn =========================================== If Status 'The Gate Status' is not Off Then Set Scene 'Scene OutDoor Path Light' On Run Program 'SidewalkLights Temp On' (If) $intAllPathLightsAreOn = 1 Else - No Actions - (To add one, press 'Action') =========================================== GateIsOpenCloseIt =========================================== If Status 'Gate Open Status' is On And $sBetween8PmAnd5Am is 1 Then Send Notification to 'TextMichael' content 'Closing Gate' Send Notification to 'TextJane' content 'Closing Gate' Wait 5 minutes Set 'Gate Open Control' Off Else - No Actions - (To add one, press 'Action') Wait 5 minutes to close gate - in case coming home between 8 pm and 5 am - want to allow enough time to get through the gate before this gate keeper program closes the gate automatically =========================================== ================== End of Referenced Programs ====================== UD Log.pdf

Thanks - makes sense, now that you provide the answer :~}

I'm finally getting around to incorporating one of the Insteon 2842 motion sensor I bought back in January, and getting odd results during setup. I went to link the sensor (via Liink Sensor menu item) with the ISY 994, and entered in the devices address, and a friendly name "Driveway Motion". The name was altered by the ISY to "Driveway Motion - Low Bat". The battery should be new, but replaced it to rule out a potential low battery problem. Deleted the device and added it back in via Link Sensor menu choice. Same thing happened - friendly name I gave it was altered as before. The sensor didn't appear to work at first, but seems to be doing fine now. Just want to ensure the "- Low Bat" addendum to the name I entered isn't indicating some issue. Normal, or questionable?

Thanks

So, if I had used "Status 'Gate Outside Safety Loop Sens' is On" instead, it would create a change of state on both the "driving over the sensor" and "driving off the sensor"? Would it be accurate to say the code after the Wait command would not execute, if the "driving off the sensor" occurred prior to the Wait period completing? Thanks for all of the responses - the subtleties are not always in the forefront of my mind...

Are you sure? ==== LeeG posted the following when I posted having problems with code not executing after the Wait command (back in early December) ===== When a Wait or Repeat statement is executed the If clause can run again when any of the trigger conditions change. For the statements after the Wait not to execute it means a trigger condition changed while inthe Wait causing the If to execute again with a False result causing the Else clause to execute. ======================================= I also got confirmation from UDI support that the ISY re-evaluates the conditional (the “IF”) of the program, and if it has changed during the Wait period, the “Then” code won’t continue executing from the line of code following the Wait. This seemed to be the case prior to a couple of weeks ago - not sure what changed, but the behavior is different.

I thought I understood the nuances of using the Wait command, but apparently I don't. I noticed a couple weeks ago, something that had been working correctly for well over a month no longer did. The program that no longer works correctly was to detect if a vehicle parked for more than 20 seconds in an area outside our gate. If so, a counter (intTotStoppedAtGate) would be incremented. Another program automatically opens the gate when my phone comes within range of my home, but only if the intTotStoppedAtGate is zero - The ISY will send a text notification to my phone letting me know of possible deliveries if intTotStoppedAtGate is greater than zero. The reason I want to inhibit the gate from automatically opening is companies like Fedex and UPS will leave the packages on the inside of the gate where the potential for damage could occur when the gate opens. Not sure how they get packages over the gate, but I’m sure they are gently placed on the driveway :~}. I’m using an Insteon I/O module (model 2450) to relay a signal to the ISY when the sensor (inductive loops) in the road detects a vehicle. In order to try to understand what’s going on, I simplified the way I was detecting the parked vehicle -so this is not the code that had been working for months, however I can’t see why the intTotStoppedAtGate counter is incremented when I am only driving over the sensors for a period of 3 seconds. My understanding, is the code following the Wait command won't execute if the condition ( Control 'Gate Outside Safety Loop Sens' is switched On) is no longer true when the Wait period is over. This baffles me as the Loop Sens is only on for 3 seconds, and the Wait period is set for 20 seconds. Any insights on this would be appreciated. ========= Here is the code I am using =========== If Control 'Gate Outside Safety Loop Sens' is switched On Then Wait 20 seconds $intTotStoppedAtGate += 1 Send Notification to 'TextMichael' content 'Someone At the Gate' Run Program 'FlashLight' (If) Else - No Actions - (To add one, press 'Action') ========================================== Here is the section of the log which shows the sensor detecting the car as I drove down the driveway. Yet, the intTotStoppedAtGate counter was incremented. Gate Outside Safety Loop Sens Status 100% Sat 2015/03/07 04:33:18 PM System Log Gate Outside Safety Loop Sens Status 0% Sat 2015/03/07 04:33:21 PM System Log

Not accessing the admin console via a browser - I'm using the ISY994 Administrative Console java app

There were a couple areas where I have needed to quit ISY to continue working. One area is when saving a newly created program, which is fairly repeatable. I'm not as clear on the sequence which requires a "Admin restart" for the second area - which is, creating a new variable. In both cases, I don't believe it's limited to creating a new program or variable, and most likely applies to editing an existing program or var. Sequence for first issue: Create "New Program", add Condition code (IF), and Action (THEN), edit New Program name, and Save without leaving the New Program text box. Get the Save Programs dialog, but the dialog doesn't release and stays visible (and empty - without thermometer). Have to quit the ISY to continue - there may be some kinder way to recover, but I haven't found it. Add "New variable", set Init, and Value, and edit the variable name. Save without leaving the variable Name text box. This will, at a minimum, fail to allow me to switch to Details tab without first changing focus to another field on the variable window. Sometimes, need to quit ISY Admin to continue.

Thanks for the reminder - thought this was a newbie related issue well suited for the forums. I think I know how the issue was created. The Admin console doesn't appear to work well when saving without first exiting a field which has been modified. It has been slowly "training" me to exit the fields I have been editing prior to saving, but I'm slow to train

I wrote the following, and it worked as I would have expected: ============= Test code ============== If Control 'Living Room Lamplink' is switched On Then $Int_TestVar7 += 1 Wait 15 seconds $Int_TestVar8 += 1 Else - No Actions - (To add one, press 'Action') =================================== I went back to my TempPathLightsOn program and changed the line of code (Wait command) - changed both the minute and second spinner values it to 0 minutes and 16 seconds respectively. Looks like the problem with the wait command was some sort of corruption, as executing the "Then" worked as I would have expected. I then changed back to 10 minutes and 15 seconds, and reran the "Then" section - worked fine. A bit frustrating to have this happen the first time using the Wait command, as I would not have expected a problem with a line of code created by selecting drop downs and spinners. Thanks for your confirmation on how the Wait should work - I should have created the little test program, when I first hit the problem

I'm looking for a relay contact closure (which is connected to the I/O Linc sensor input). I'm new to ISY and Insteon, but thought if I'm monitoring the sensor side of the I/O Linc module, I should look at the Status. Is this not the case? When I view the logs, I can see the Status does change when I drive over the safety loops, and the "Then" section of code in TempPathLightsOn executes. However, It appears the code after the "Wait 10 minutes and 15 seconds" fails to execute. The line of code ($Int_TestVar3 += 1) which precedes the Wait command executes, but a similar line of code ($Int_TestVar2 += 1) which is after the Wait command fails to change. When I look at the variables when I select the program tab in Admin I see the "last change" to $Int_TestVar2 was Nov 30th, which was the date when I created the var - the value hasn't been altered in the dozen times I've run my tests. I would have thought the code prior to the wait command would have executed, and after 10 minutes and 15 seconds specified by the Wait command, the ISY would continue with the next line of code - e.g., $Int_TempPathLightsOn = 1 I have little doubt I'm doing something that the ISY doesn't like, but have no idea what it is. I will play around with a new program that does little more than increment a var before a wait command and increments a second var after the wait command. And, view the "last changed" column to see if both increments occur.