raymondjiii

I always thought you got 2 entries per device by default because one was using the device's user and pw and the other using the UD portal name and pw. But on both device's admin console it's: Network-->EISY as the second entry in the tree. (I do see that it can be renamed though). Well, I guess this will remain a mystery maybe on how IoX gets assigned. I could maybe understand for the ones that I add manually - since they are not found on the local LAN, perhaps.

Every time I launch the admin console. I get a popup window "New Insteon Devices" which always shows the same device each time. But it's not new, I've dismissed the window each time I run the app. Other than deleting the device and then trying to re-add it - but I have no idea why this keeps happening. Always appears when admin console starts: But this device is not new - it's always listed and always works properly

Sometimes under the name column it's labled as EISY and other IoX. This values never change once they are set, but I installed the start.jlnp on another machine, and all 4 are labled as IoX. Just really curious why this is - why it can be either EISY or IoX. Below it shows 4 entries for my 2 devices. (each device has the /desc and the :8443/desc - so four rows makes sense). On another computer they all came up as IoX. The last 2 rows I have to add manually because they are not on my LAN but are reachable via my vpn to other house.

This is awesome, thanks!

Hi, that's what I have now, but it keeps the order static (light 1, light 2, light 3) and not random. So I created multiple of these programs changing the permutation in each one, then in a main program - use a random value (1, 2, 3) (the number of permutations) then call that one of the programs based on the random value and exit. This way only 1 program ever runs. This works. But if you increase the number of lights beyond 3 then the fan-out of the number of possible permutations grows to be quite large. The key is that I want to randomly iterate over the set of lights - the order of lights activated is random.

Hi there, I understand your second message - the repeat while greater than 0 - I do that now. But your first message...the randomness of the order is caused by the conditional? But if everything is currently off then I think nothing would ever activate (deadlock) ? The other thing that I was never sure of is the "IF time is sunset" - what if the other programs have to run multiple times and let's say it's now 5 minutes past sunset - will they ever run again past their first time (does the "IF time is sunset" conditional still stay TRUE if it's 1 minute past sunset ? Would it be: If (time is sunset) AND (if light x OR if light y OR if light z) Maybe not....because the "master" program is enabling them so it's close to sunset...hmm I want to think about this...you apparently have it working so I want to understand the logic (timing of events) Thanks for your response.

I have a basic program where I wait Random minutes, turn on Light X then wait Random minutes turn on Light Y, ... etc. I modified this program to create a random value for a variable that serves as the permutation order so that the order of lights coming on differs each day. But once you have more than say 3 lights, the list of permutations gets a bit out of control. I would prefer not to have a set of programs (one program for each light) where they all trigger off of sunset, wait X minutes, do Action Y, because doing this could cause, in theory anyway, all lights to come at the exact same (or even close to) time. Image you have a set of lights, you want to randomly iterate over them one by one, waiting X random minutes before turning it on. You want this to happen sequentially.

Yes, that's exactly what I'm saying. "EISY" listed without the port and "IoX" listed with the port. I have never edited (nor wanted to) anything related to this.

Now I see why IoX lists the same device twice - one is for using your ISY portal creds and the other is for using your local creds. I have always just been using the first entry.

All of the above says nothing about why the R2 could not see its PLM. I have no idea what was causing that. I had both devices right in front of me on the desk (both plugged into an electrical outlet). I did have Insteon support checked on the admin console for my R2.

I never said that they did not have different MAC addresses - of course they were different. I was talking about the UIDs listed on the ISY Portal not the MAC addresses on the LAN. I did say that on the ISY Portal - I had 2 entries for the same EISY. The ISY portal lists your device by it's MAC address (aka UID). There clearly was a duplicate UID on the ISY portal: one with OS 6.0.2 and the other with OS 6.0.4 With MAC addresses guaranteed to be unique this should not be possible to list the same device more than once. In my opinion, there should be no way to list the same EISY on the ISY Portal - but in this case it seems to be including the OS version as part of the "primary key" for that table. The ISY portal is obviously not on my network so it has nothing to do with IP addresses or MAC addresses (which is the same thing as the UID). When I say ISY portal I am talking about the UD site where you can see your list of devices, pay for accounts, etc. Yes, the fact that one was an R1 and the other R2 is not relevant, I never said it was. I was simply distinguishing which was which in describing the issue I was experiencing. The device does not come out of the box with the free license, you have to go through some steps (THIS is the confusing part) - "and then" accept it. This is the part where having 2 devices on the same LAN seems to have become a problem. How does "eisy.local" resolve when you have more than one device? Probably the one with the lower IP address? I think this leads to the problem I was having. The other part that is confusing is why does the admin console start up with 2 entries for the same device? One for "IoX" and the other "EISY" - both are the same device (same UID). Now, once you are in the IoX admin console and you go to the portal tab it will give you a link to go to - I believe that the URL it puts on the screen has "esiy.local" in it. Using the specific IP address would resolve that issue I think. This is the screen from the ISY portal, Sheryle's House 6.0.4 was "thee" R2. It seems to me that the portal license is associated with the combination of UID AND OS version. Since UID is unique there should never be a duplicate of "Sheryle's House" You can see that Sheryle's House 6.0.2 is offline AND Sheryle's House 6.0.4 does not have the ISY portal license (the little "!" icon)

Okay. I think I got this resolved. I had my R1 EISY online here at the house. I was trying to get a head start on setting up my R2 which will located at another residence - I was not going to link any devices, etc. Just wanted to get it configured before I head out tomorrow to the other house. It looks like having 2 EISYs on the same network is problematic...they each have their own IP address but still issues. I shutdown the R1 and then R2 was able to see its PLM. It was also problematic trying to get ISY portal access for the R2. My R2 had 6.0.2 out of the box, I paid the $24 for the portal, I then did the upgrade to 6.0.4 and then lost portal access. My R2 6.0.2 was listed as "offline" and my R2 6.0.4 was listed as not having ISY portal access (needed to pay for it). Thankfully I was able to "Migrate" the R2 6.0.2 to the R2 6.0.4 which are the exact same MAC ID units so it was odd to migrate MAC-ID-1 to MAC-ID-1. In the dropdown, it lists the same MAC ID from which you are migrating from. Odd, but glad that's resolved. Let's see tomorrow if I have any issues with UD Mobile. Anyone else by chance own more than one EISY located at different residences? BTW, I am not trying to link devices across houses.

So, in IoX Admin Console, Tools-->Diagnostics-->PLM Info Status I get a Java window with " / Not Connected"

I just got my new R2 and I'm going to be setting it up at a 2nd residence. Looking at it (compared to version 1) - does it matter where the Insteon USB Modem is plugged into? I ask because on the R1, I always used the USB port on the back of the unit for Insteon USB modem. Now with R2 - it's USB-C on the back, but on the sides it's 2 blue (USB3) and 1 black USB (USB2) Does it matter which port for Insteon USB modem? It's been years since I setup the R1 that I thought the USB Modem had to use the back port?

Yes, I get what you are saying but Optimum (Altice) does not allow anyone access to any such advanced settings. For the same reason that UD insists that EISY uses DHCP - to limit support calls. I'm going to request Optimum put my fiber modem into broadcast mode and I'll use my own router to manage things.

Ahhh, I think that is what I am remembering! In IoX the "Use DHCP" check-box is greyed out (can't be turned off, at least easily) - and (see below) EISY always gets the first (lowest valid value) DHCP IP address. And now that I adjusted my fiber router I find that eisy always takes the first IP address in the DHCP range. This happened in the past regardless of the internet provider modem I was using - EISY ALWAYS grabbed the lowest DHCP address. I wonder how EISY does that. I thought DHCP was like: "hey, give me an IP address", "okay, here you go, it's valid for x minutes", "okay, thank you". I did not realize that this new Optimum router I got, which you can only manage through the optimum.com website, has only 1 setting where you can set "the valid range of IP addresses" - unfortunately, what they should have said was "DHCP range of IP addresses". By default, the range (dhcp range) starts at x.x.x.15. I was having crazy camera problems where a camera would go down and then the washing machine would grab that IP address, and then the camera never works again (and worse). I did not know all of this was happening until today. All of my cameras use static IPs for nvr. So today I changed this config setting to start at x.x.x.151 upward for DHCP. And then I got all of the dishwashers, laundry machines, Feit floodlights, Chamberlain garage door openers, etc to give up their IP addresses and make new DHCP requests and get everything out of what I thought I was using as the static IP range. I finally have full inventory of every network interface MAC address, wifi or wired, static or DHCP. Most importantly, every camera works once again. This wasn't the point of this original post, I was just surprised that my EISY was at a very low IP address...lower than I had ever seen before....which thankfully then led me to discover this "mislabeled IP range". I then started querying all MAC addresses and map them to the corresponding IP address. I figured out what was going on by, I would get the MAC addresses of one camera and then I found its corresponding MAC address mfg-ui was not for the mfg that I thought was using that IP address - because another device was taking over the IP address of what I thought was a static IP. Finally, I was able to fix every issue with every network device (most problems were for the outside cameras). And now I can watch every bird at all of the feeders and bird houses (I have a large bird environment outside). In summary, EISY led me down the correct path for fixing this camera insanity.

I am sorry to ask the question, my EISY has been running pretty flawlessly for years and I simply cannot remember where I saw this: "Somewhere" I remember seeing that EISY "must" use a specific IP address or use an IP address that is greater than ??? I remember when I first bought my eisy years ago I had to fiddle with the router and change the DHCP range so that EISY could use the address that it needed. I remember something about that it was at a static address so people wouldn't mess with it and cause a ton of support tickets for UD when they screw it up. I cannot remember where I saw this! I can find the eisy on the network, with IoX, eisy works - everything is good - nothing is wrong with the eisy. I do not want to change the IP address but I thought it was like a static address of like X.X.X.150. I just remember a screen where it showed that either the eisy IP address had to be X or had to be greater than X but for the life of me I cannot remember where I saw that. I don't think it I saw this via ssh (I do not believe that I have ssh enabled). I do not have an hdmi monitor connected (nor USB keyboard or mouse) to my eisy. I have a new fiber modem and I want to find that setting that I saw years ago so I can set the static IP range and DHCP range appropriately on this new modem. Do I need to plug the eisy into my TV? I do not remember ever attaching the eisy to my tv to view anything. Thank you. Just to clarify, according to my router the eisy is at 192.168.1.41. I'm not asking what address my eisy has, I'm asking what range does it need to reserve it's IP address.

I definitely did not reset the eisy. But when I did not see the "wet off" status (kept seeing "wet on") - then I pulled the battery, put it back waited a bit but nowhere near an hour. I guess next time, I will let it "sit". I just wanted to make sure the sirens didn't go off again during my zoom call. I could have ran around the house unplugging them I guess but I'd rather just learn how they reset automatically or if I need to do anything manually.

So I had a small leak. Found the leak detector that was triggering the alarm - everything worked perfectly. I cleaned the contacts of the leak detector but 1) could not figure out how to reset it that it was no longer wet - I guess you can't. 2) I saw no way in IoX to reset or query anything. Eventually I got the "wet" status to go from On to <blank> I deleted this sensor, re-linked it, added it back as a controller for my sirens. Is there an easier way to do this? Is it just a matter of waiting a period of time maybe? Thank you

Wait a minute....I woke up at 4am, all of the outdoor lights were on. I opened UD Mobile, went to Favorites and hit the Outside lights button and that was it - done. It could be intermittent thing I guess.

7 low voltage (12V AC) transformers and two strings of LED lights - each item is plugged into it's own outlet (the Insteon dual controlled outlets top and bottom). They all couldn't have gone bad at once. But I can try to unplug one every night and see if that makes a difference.

Maybe....but it's been same load since I owned an Isy994 and now and Eisy.

I've had the Eisy for about a year maybe - every thing was fine until 2 nights ago. When I saw that things were not working I did a hard reset, restored from backup and waited to see. The next night things still did not turn off. The thing is other "turn off at" programs are running fine. Just not the outdoor one, there are about 10 devices in that program. From the days of X10 I would always make a second one to run in case the furnace was on when the first one ran (runs like 15 minutes later). Oddly, that one did not shut things off either. Then I wondered, it's cold out - but they do respond to the turn-on program. But, one of the 10 devices is inside (a switch that powers an outside receptacle) and that one did not turn off either. So I am ruling out the cold weather, which I found hard to believe since it was all devices. I'll see what happens tonight and tomorrow night to see if that quirk resolves (but the other turn-off time of days programs are working fine). I believe the firmware was updated to .4 on that hard-reset, but then again the one turn-off program stopped working at .3. The only thing I can think of is too many devices in the program (which was never a problem before).

These is just a sample of what's there. I started looking at this file because a couple of my programs to turn off devices at a particular time do not appear to be running since 2 nights ago despite IoX showing them enabled at start-up. The 'turn-on' at sunset programs works but the 'turn-offs' at 10:45pm do not seem to run. So I was curious what would be in this file. Since it is an "error" file I would generally expect this file to be empty - things are running fine. I also wasn't sure when someone would want to run the "Restore PLM" option in IoX, as if would running that fix all of these random errors? I did not want to try since that requires all battery devices be turned on and to gather them all would be a hassle. In the end I just want my "turn-off" programs to run (which do not involve any battery powered devices) and am very curious why there is so much content in the error file. Also curious why the filename is called ISY Error Log and not EISY Error Log at 2024/12/07 04:26:40 AM 0 -170001 <s:Envelope><s:Body><u:GetISYConfig xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetISYConfig></s:Body></s:Envelope> Sat 2024/12/07 04:26:46 AM 0 -170001 Authenticate Sat 2024/12/07 04:26:47 AM 0 -170001 <s:Envelope><s:Body><u:GetStartupTime xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetStartupTime></s:Body></s:Envelope> Sat 2024/12/07 04:26:47 AM 0 -170001 <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_IoX_Service:1"><name>/CONF/INTEGER.VAR</name></u:GetSysConf></s:Body></s:Envelope> Sat 2024/12/07 04:26:48 AM 0 -170001 <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_IoX_Service:1"><name>/CONF/STATE.VAR</name></u:GetSysConf></s:Body></s:Envelope> Sat 2024/12/07 04:26:48 AM 0 -170001 <s:Envelope><s:Body><u:GetVariables xmlns:u="urn:udi-com:service:X_IoX_Service:1"><type>1</type></u:GetVariables></s:Body></s:Envelope> Sat 2024/12/07 04:26:48 AM 0 -170001 <s:Envelope><s:Body><u:GetVariables xmlns:u="urn:udi-com:service:X_IoX_Service:1"><type>2</type></u:GetVariables></s:Body></s:Envelope>

No, it's not there when you right click. "Open With" is still there but nothing in the list worked for start.jnlp. I just searched for how to get around the restriction on running a jnlp file on Sequoia and .... "AI" found running it on the command line.