johnnyt

thanks for replying. sorry, but i'm not quite following. what does xxx.xx.xx.xxx represent if not the IP address? do you mean i have use the universal-devices.com/99i to start the console to avoid this? are you also pointing out that I should avoid using the outside-the-browser java web start way (.jnpl)?

"14.83.D8 v92 / Connected"... I also validated that ISY and PLM are talking by turning a few lights on/off around me using the console. It's a bit strange because as soon as I logged in this morning I did a "New Program" just to test and it worked, then undid changes, did a bit of browsing around (didn't create or add anything, didn't shutdown console), came to forum to post a question about having to login twice then went back to test New Program again and the second time around it again didn't show up in detail tab. FWIW, I mostly use a Windows 7 64-bit machine though it also happens when I use my 32 bit Vista machine. I have v2.8.4, Java build 1.6.0_20-b02, and use admin.jnpl to start console

I often, but not always, need to login twice. The first time it appears to be coming from Java before the ISY console shows up on the screen, the second is clearly from ISY. I can click a "save password in list" option in the first instance, which I do, and it seems to stick for a few starts but then clears and asks me again. Is there a way to avoid one of the 2 logins? And while I'm at it, is there a way to bypass login in or auto-login all the time? I don't allow connections from the internet and am not worried about someone inside the house doing nefarious things (other than me, that is )

I have a 2 month old KPL6 configured with a few scenes and programs and, after experimenting with another KPL8 that I use as what I'll call a KPL 7 (linked the top 2 for one large load controlling button and the rest all small secondary buttons), I was thinking of tweaking this KPL 6 to free up the large bottom button so it isn't a dedicated "off" button, in other words turning it into a (true) 6-scene KPL6... Do I have to remove (or will I lose) all scenes (and have to fix the programs) currently configured in/for my KPL6 if I reprogram it to be a KPL8? I realize it will do a factory reset so I mean if I restore a KPL8 with the previous KPL6 scenes will things get all mucked up or fail outright? Am debating the cost of doing this before doing. Any advice would be appreciated.

the problem was still happening for me after I completely turned off the Java caching (at the Java control panel). Restarting the console would work sometimes but not others (with the caveat that the New Program always shows up in parent folder, not in the folder where it was created). Of course, rebooting ISY has always fixed it too for me.

sorry I meant to say can I turn off/cleanout cache for ISY admin console related files (so I don't have to turn it off for all Java apps).

So the New Program not showing up in Program Details tab is happening with significant regularity. I need to restart the admin console for it to show up (under parent folder, even though I created it while in a subfolder) I've been chalking it up to the fact that I often work on a laptop that may go to sleep and/or hibernate with the console open, which has caused the console to lose it's bearings and need to be restarted after a wake up but this problem has happened several times today without the laptop going through any sleep/wake cycle. (just moved yesterday to 2.8.4 from 2.8.1 for what that's worth) Can I turn off the Java cache, or make it clear itself at startup, or can an option be added to ISY admin to do it at startup? It's a real PITA.

so I guess I have to log this feature request with Smarthome - although that won't help with the kpl's I have now.

Would just like to check something that's giving me a little grief and doesn't seem quite right (although I assume there's a good reason for it) From what I've observed and read in a few posts it looks like I need to create separate scenes and programs in order to manage grouped mutually exclusive KPL secondary buttons that are called by ISY rather than a KPL controller button. When I create a scene in ISY with 3 secondary buttons as controllers, the parent (ISY) scene does not allow me to control the ON level for any of the 3 buttons, yet each of the buttons themselves allows me to set the ON level of the other 2 buttons, which I set to 0/Off to make the mutex work on the kpl. So if I press any of the 3 buttons the button lights up, the scene activates and the other buttons turn off if on. However, if I use ISY to activate the scene, while the loads do what they're supposed to none of the buttons do what they're supposed to. From what I can tell I need to create parallel ISY scenes that have the secondary buttons as responders and write some programs to manage the mutual exclusion. Is that right? Could ISY (or is it a KPL h/w issue?) not talk to KPL secondary buttons as responders and allow me to set their On levels when they are controllers the way both ISY and KPL allow that to happen internally within the KPL? I guess before I filed this as a feature request I wanted to see if there was something I was missing.

Well "manually" meant more the IOLinc, but I guess it means both really, using the IOLinc button, which will be downstairs near the unit (in my man cave ) or using the KPL button, which will be upstairs near the kitchen. I realize if I use the KPL, everything will be fine. However, if I understand the situation, using the IOLinc won't be telling my KPL or ISY so I'm going to have to query that KPL scene (or can I get away with just querying the IO Linc?) periodially to light the KPL button and tell ISY/HomeSeer. Is that right?

maybe I'll write a program that queries the IOlincs every 15 or 30 minutes...

Too bad, I thought it relayed its status. Does it report back if I make it part of scene? Two of the 6 have a voltage probe on them detecting thermostat calls and they do activate the relay (I did check the "relay follows input"config option). The problem I have with status non-reporting is that for some, well actually, most, I wanted to be able to manually activate them and have my ISY programs (and HomeSeer) know about it. For example, I bought the HRV without a controller (putting the $100 toward IOLincs and ISY instead) so this is my only way right now to activate it non programmatically. Also I was going to link them to buttons on a KPL in the living area and wanted them to show the actual up-to-date status. Is there a way around this? I notice that while the relay can follow the sensor, the opposite is not true so I can't check the sensor for 4 that don't have one.

I have a 6-pack of IO Lincs, all in latching mode to control HVAC things (Fan High Speed, HRV, duct dampers, etc.). When an IOLinc is turned on at the device, either manually or through sensing a low voltage probe going ON, the status is not updated in ISY unless I do a query. The six IO Lincs are on a long (non surge protected) power bar on a dedicated circuit (for the HRV), a short path to my electrical panel, where my PLM and ISY are plugged in, and within 10 ft of an Access Point (which I went so far as to put on the same power bar to see if it helped.) ISY does seem to otherwise see the devices. Certainly I can query and config them, as well as turn them on and off with ISY. Is this normal or could this be an Insteon network problem despite the proximity to the PLM and Access Point?

Thanks for the info. Helps explain things. I don't remember now if there was a 22 in there (I fixed the problem before reading the last post) but I did learn how the "compare" button confirmed that ISY did not have the links in its table. I also got another lesson out of this. I tried unlinking the devices again (at the devices) and tried device restores a number of times but the link remained in both devices. So I ended up deleting both devices then doing factory resets on both, re-linking to ISY, then having to re-populate all the impacted programs with the "new" devices (D'oh!). More importantly, though, I think I learned how to avoid this in the future. It goes back to the prime directive - let ISY do the linking. I suspect (it wasn't intentional) that my motion sensor was still in linking mode when I linked the switch to the ISY, which would have re-established the physical link between the two devices that ISY didn't know about (unless I'm missing something.) The takeaway for me is to either get the motion sensor out of linking mode before linking the next device, or do the motion sensor last. But if this is what caused my problem, it makes me wonder 2 things. 1. Is linking more than one device at a time to ISY dangerous? i.e. will other types of devices cross link between themselves or is it just a problem with motion sensors? 2. Assuming for the moment they would have shown 22 - deleted. When would they have been removed from the device table? Or will they just end up taking up a row in the table forever?

I did have an ISY scene for it and that's what created the link in the first place, however I deleted that scene some time ago in favour of using a program to control the light because I didn't want the motion sensor directly deciding when the light went off. What I'm thinking might have happened (correct me if I'm wrong) is that when I deleted the scene I didn't have the motion sensor in programming mode so it didn't delete the link in it as far as the device is concerned. The thing I don't understand is why the switch has the link in it's table with the scene gone. Might it have been out of range when I deleted the scene? (I had limited devices in at the time and was still finding the right places for my Access Points so maybe it was too far?) Partly this is trying to understand what happened but more importantly, how do I clean the mess up? Is there a way to delete a device link through ISY when a scene deletion didn't do it and a physical unlinking (outside ISY) doesn't do it?

ISY is reporting a link (at the device level) between one of my motion sensors and a light switch despite my having unlinked the two devices (twice now) following the instructions below from the motion sensor quick start guide and observing the stated behavior (i.e. light doesn't go on when I tap the set button on the motion sensor). There's no visible link between the two devices in the admin console. Have tried to "restore" both devices from the console but the link between the 2 devices keeps coming up when I check their respective link tables within ISY. What might I be doing wrong or not understanding? Any info would be appreciated. ---------------- UNLINKING FROM INSTEON RESPONDERS: 1. Press & hold the Set button on Motion Sensor for 5 seconds (until red LED behind sensor lens begins blinking) and release 2. Press & hold the Set button on Motion Sensor for an another 5 seconds (until the LED changes its blink pattern – it will now be on longer than off) 3. Press & hold the Set button on the INSTEON Responder you would like to Unlink (until its LED blinks) 4. The Motion Sensor LED will stop blinking (if not try step 3 again) 5. Test by tapping the Set button on Motion Sensor. Taps should no longer control the Unlinked device.

yep, I'm good now. Thanks, wpmjones. if UDI is listening in, might be worth labeling the IR receiver on the ISY. If not on the device itself then in the quick start guide.

yes, I found that one and many others, however it and the others I found only cover how to configure/use IR within the ISY software. I also found the one on configuring the Harmony Remote in the Harmony software. I found nothing about the hardware side of things. In fact I thought I might have to buy an IR Linc Receiver but then again there was nothing about that when I bought the ISY so that didn't seem right.

Is it the bigger of the 2 holes below the LED's on the ISY that has the receiver behind it? The emitters I have need to be glued (well, two-sided taped) to sit right on top of the receiver. [/img]

This does seem like a dumb question but how do I get IR signals physically into my new ISY99i/IR? Am not finding anything in the quick start guide, user guide, wiki or forum about it. I already have IR receivers and emitters throughout the house. Can I plug into the ISY electrically (my ISY is right next to a 4 port IR expander with a free port) or via one of my IR emitters?

Can anyone confirm/deny that numeric weatherbug data from the ISY ends up as the device value in the matching HomeSeer devices? Also, does the device string include the unit of measure, e.g. "0 mm". Newbie Q: It doesn't look like I can "try before I buy" the weatherbug module (or any, for that matter). Did I just miss where/how to do that?

Great, so the unit itself is probably fine (phew). Thanks.

More info / related question?: Diagnotics shows total of 500MB of memory (445 MB free). Is the factory installed SD card only 0.5GB or is it a sign of trouble with the SD card?

was pressing "New Program" from Program Details page and nothing was happening, except that when when I went to Program Summary page there were 4 "New Programs" that were "Not Saved". Going back to Program Detail page still did not show them. A reboot fixed the problem - well the empty unsaved new programs were gone of course but I was now able to create new programs and see them from the Program Details page. Am I looking at a bad unit, or a bad SD card? (just got the unit last week) Note: I did notice that I was getting an "error" light (well, "mem" and "error" lights together) earlier when I had rebooted my router but that went away after my router came back up (I might have rebooted the ISY too, I can't remember). Is it normal that if the router goes out, the ISY shows "err" or is it another indication that I have a bad something?