MarkJames

I've never set my 2420's to time out other than the default time. I recently tried to change the default time on 2 of them from the options dialog. I set one for 5 minutes and one for 8 minutes. However they both remain at the default time. When I go back to the options menu I put them in linking mode, ISY goes out to query them, and it returns with the appropriate values (5min and 8min) but even so they send an off command after the default 1min. I can't seem to make them last longer than 1min. Any idea what to check with this? mark

I'll try and hide my disappointment - but it'll be tough!

Well spank my *** and call me Sally - that worked. $30 later I've now got a couple of shiny new toys to play with. Much thanks mark

is that combined total of devices + scenes? I just checked this with a new switchlinc dimmer - same error - so it's not the 2420s or anything to do with them. I have roughly 100 -110 devices not including access points (, remotelincs (3) and 2420s (5 with 2 more pending) - about 70 scenes. I think the problem is my PLM Link table count. I just checked it and it's over 800 - I gave up waiting for the final count I'm not sure why it popped up so high... it was down in the 300's till I added homeseer to my system. I'm running it on a dedicated machine with the ultram1g plugin, the isy plugin, and the weatherbug plugin. Homeseer should not have created PLM entries, though, should it? mark

OK.. I'm stumped. I have 5 2420m's already so I'm no stranger to them. I'm trying to add 2 new ones but can't get either one to add into ISY. I keep getting errors. First things first... I'm on 2.7.12 I notice that when adding a 2420m ISY does not prompt you to put the device into linking mode. I assume it has to be so I put it in by holding the button 5 seconds till it starts slow flashing. To be on the safe side I've tried adding it without putting into linking mode but then I get the 'failed to write high water mark' error instead. So... I put it in linking mode, bring up the add insteon device dialog, put in a name, add the address (there are no 0's or O's - it's 13.EF.36), and select 2420m from the dropdown box. ISY goes out to add it but fails with node not added - failed restoring device. I've factory reset the 2420's, though they're new. I've backed up my system and reinstalled 2.7.12 in case something got corrupt I've removed all the access points in my house except for the one right beside me and the 2420 I've deleted my java cache I've confirmed that it's 2.7.12 from the help->about box Now I"m not sure that this is only related to the motion sensors. Yesterday I was trying to add in a couple of old KPL's in a seldom used area. They wouldn't add - same error - node not added - failed restoring device. I chalked this up to these KPL's possibly being faulty as they were in my 'spare parts' drawer. mark

Ahh... OK... I thought it was some strange GUI thingy for ISY. Sort of a graphical layout tool for your switches and such. I tried to use it for that but obviously that didn't work out so much. Thanks! Mark

Well, Bob, I bought a new atom based PC to run homeseer and the ISY plugin. The one I bought has 4gb of RAM and a 500gb hard drive - all for under $400. Pretty good value for the money, really. Has an HDMI output that I'll never use and came with a cordless keyboard/mouse besides. Slick little box! Amazing that it has no fan in it. I can't even hear the drive running - I could actually put this in my bedroom to watch movies across the network and not mind it at all. Even has built in wifi and gb lan! Now to get it up and integrated! Mark

I tried to find an answer to this but using search with the word 'Floor Plan' brought up everything that had to do with plan or floor. Too many results to wade through. Anyways... what's the deal on the 'floor plan' function? Is anyone using this? What is it's intended purpose? Mark

I see, oberkc, that you're a glass-half-full kinda guy! Good point, though! Mark

Oh.. ok... I only have a few in my installation and none are part of scenes that require them to turn off when the scene turns on. I just assumed. It's a shame that the KPL buttons can't be made to match up using scenes - it leaves KPL buttons 'out of sync' with the devices they control. I guess the only way to do it is make the KPL Leds part of a scene and then turn that scene off programmatically. Thanks, Rand, mark

ooooooh.... that's making a pretty broad statement. Turning a scene on can turn many devices off but afaik not KPL buttons not switchlinc relays not some older devices that could dim down but not off trying to turn things off with scene 'on's has cost me a lot of hair. Hair which I can ill afford to lose, I might add. mark

Just so you know - when you do a restore PLM it will remove the links you currently have to the old PLM in every single device in your installation and replace it with a link to the new PLM - again, in every single device. Just a heads up because all your RF devices will need to be relinked to the PLM as well. If you run pro you can keep those to the end and do them separately otherwise they'll likely time out before the restore gets to them. Devices that don't write should have the little green 101 left beside them so you know - you can then put them in linking mode and write them too. If you have a lot of devices it can take quite a while. If you have some weak communication areas it will also take quite a while. mark

He is correct. I'm assuming charter is his ISP. If he's on a connection where his IP changes then he will not be able to access his machine from remote without knowing what it changed to. The easiest way around this is using dynamic IP. There are many of them out there - like dynip.com. You install a small software app on your PC and when your IP changes it informs their company. You would access your machine using the URL you get from them like say MyISY.dynip.com MyISY.dynip.com (the myisy part is something you make up yourself) will resolve to the IP of the PC and the software agent on the PC keeps that IP up to date. Google dynamic IP and you'lll soon see what it's all about.

Sorry if this is 'going against the grain' but I can't say I agree with any of the posts that I've seen claiming that older KPL's cannot control their load from a sub button. I have KPL's going back to the very first version and I've always used button H to turn off the load on button A. The only difference is that I cannot use a scene controller - not iSY - not Houselinc, not Powerhome - to make it happen. I must manually link it. If you press/hold H till the load flashes and then press hold A till the load flashes the H will, indeed, control both the button A LED and the load attached to A. It will turn if off, on, or dim/bright as well as follow fast off and fast on. In my case H is always a non-toggle OFF. I have this set up on at least 12 KPL's in my home. If I'm misunderstanding then my apologies.

I had this happen to me when I moved my PLM. Don't know if that helps but moving the PLM or adding some electronics can mess up the communication pretty badly. A PLM dying is a possibility too. I had a lot of trouble with one KPL that had the little reset button get stuck from time to time, too. It would get wedged between the decorative faceplate and the G/H buttons so when you pressed them it would go in a little and not come back out. mark

Cool - post back your results. Michel hasn't answered back yet about toggling non-toggle KPL buttons. Jeez, Michel, it's been like 6 minutes - you on coffee or something? If it's not a problem then his idea of setting your buttons to non-toggle is much better than using programs. Programs work well - but not if ISY isn't running or your PLM fails or what-have-you. Buttons always work. mark

Oh, this would be perfect, how do you do it? When I try to write a program to set the KPL LED the only options I get are to set the backlighting for the whole KPL. There are no options for turning an individual light on or off. Are you able to do that? It's a bit 'different'. Make the LED a responder in a scene and then turn the scene on/off Mark

Will this be OK if the KPL is used as an indicator of door status too, Michel? If you turn OFF the LED on a non-toggle ON or turn ON the LED on a non-toggle OFF what happens? mark

I would have to say to your first question - no - you need a program - otherwise the KPL will send an on to the sensor to close the door and an off to the sensor to open the door. If you want the KPL to only send an on and not an off - ie directly control ONLY a close but not the other - then I don't think you can do it. If you try to make your switch non-toggle you'll get all messed up when you turn the LED on or offto use it as an indicator. You could try that but I don't think it will work. As for the problem of the door not closing and the KPL led being out of sync the most common method I've seen for accomplishing that is do a wait from the time that the close door signal is sent - 20 seconds or whatever. Query the sensor after the wait and see if it's closed. If it's not then turn your KPL LED back on. It's not a good idea to try closing it again, though, as it probably means it's blocked. Hope that help, Mark

I hadn't considered that. I've set my home up as a domain and all the workstations log in for file and resource sharing. This is primarily to keep control of my kids and so I can sleep at night knowing noone is gonna fdisk my drives while I'm away. It also prevents the issue of malware installing itself as noone has admin privileges but me - so if something is gonna get installed I gotta be the one to install it. As a concession, though, I run vmware on one of my workstations so my kid can play all he likes. There are no shared folders with the real world on this setup so he has full admin privileges and I don't much care what he does. Mostly he plays with Greenfoot - a Java kind of interpreter language for kids game development (I think) It would be a non-issue, though, to run a second VM on that machine for homeseer as it has 7gb of RAM in it.... Then again, for $200 I could stick it in a closet, RDP to it for programming, and otherwise forget about it. I'll have to give this some thought. The only issue I can see is hooking the VM machine isn't near the PA system so I couldn't run the audio through the house. It's also a long way from the Stargate so I couldn't control that either. Anyways... sorry for thinking 'out loud', and thanks for the input. Mark PS.. sorry for the 'crappy Atom' comment... didn't realize you worked for Intel If it's any consolation all my computers are Asus mobos with Intel processors.

Well it's quickly becoming apparent that my old celeron based clunker with a whopping 256mb of ram is just not gonna do it for homeseer. It works - but just. As I just dropped the better part of 4grand on a new DVR, cameras, wireless sensors, some more smarthome goodies and a bunch of other stuff the wife doesn't know about I'd say that a new PC of any consequence is out of the question. Bob... you would probably know the answer to this. I'm looking at the Acer Revo - a sort of netbook with a crappy atom processor in it - but it's like $200 and it has a gb of RAM. Would this be enough of a computer for homeseer with your plugin? mark

Always a handy thing to have in a large X-10 installation.

You know your code! It's chugging away doing it's thing. Thanks for the help. mark

That will be it, then. I'm on 2.7.12 I'll go get the beta. Thanks for your help! Mark

Well - I seem to be having some trouble with the homeseer plugin. I got it installed and config runs but I can't add my devices. Here's the log 3/5/2010 9:42:05 PM - Info - Initializing Plug-in: Insteon on COM port 3 3/5/2010 9:42:06 PM - Insteon - PLM contacted on COM3 with an Insteon address of xx.xx.xx and firmware version 85 3/5/2010 9:42:06 PM - Info - Finished initializing plug-in Insteon 3/5/2010 9:42:06 PM - Info - Initializing Plug-in: ISY Insteon 3/5/2010 9:42:06 PM - ISY Insteon - Creating isy class instance: [192.168.xxx.xxx] 3/5/2010 9:42:06 PM - ISY Insteon - COMM: Parse description URL (http://192.168.xxx.xxx/desc) 3/5/2010 9:42:07 PM - ISY Insteon - COMM: Attempt to authenticate ISY access. 3/5/2010 9:42:07 PM - ISY Insteon - COMM: Authenticating with ISY 3/5/2010 9:42:07 PM - ISY Insteon - COMM: Subscription thread started 3/5/2010 9:42:08 PM - ISY Insteon - COMM: Authenticate returned 200 3/5/2010 9:42:09 PM - Database Item - Saving Device Global Insteon All Devices 3/5/2010 9:42:10 PM - ISY Insteon - COMM: service client created 3/5/2010 9:42:10 PM - ISY Insteon - COMM: Set ClientCredentials. 3/5/2010 9:42:10 PM - ISY Insteon - COMM: Busy Check - delay only. 3/5/2010 9:42:18 PM - ISY Insteon - COMM: ISY configuration query attemp 1 failed. 3/5/2010 9:42:18 PM - ISY Insteon - COMM: ISY configuration query attemp 2 failed. 3/5/2010 9:42:19 PM - ISY Insteon - COMM: ISY configuration query attemp 3 failed. 3/5/2010 9:42:19 PM - ISY Insteon - COMM: ISY configuration query attemp 4 failed. 3/5/2010 9:42:19 PM - ISY Insteon - COMM: ISY configuration query attemp 5 failed. 3/5/2010 9:42:19 PM - ISY Insteon - COMM: ISY configuration query attemp 6 failed. 3/5/2010 9:42:20 PM - ISY Insteon - COMM: ISY configuration query attemp 7 failed. 3/5/2010 9:42:20 PM - ISY Insteon - COMM: ISY configuration query attemp 8 failed. 3/5/2010 9:42:20 PM - ISY Insteon - COMM: ISY configuration query attemp 9 failed. 3/5/2010 9:42:20 PM - ISY Insteon - COMM: ISY configuration query attemp 10 failed. 3/5/2010 9:42:21 PM - ISY Insteon - COMM: ISY configuration query failed. 3/5/2010 9:42:21 PM - Info - Finished initializing plug-in ISY Insteon 3/5/2010 9:42:21 PM - Info - Finished initializing X10 interface 3/5/2010 9:42:21 PM - Info - Finished initializing infrared interface 3/5/2010 9:42:26 PM - Info - Local IP address (subnet) is: 192.168.xxx.xxx(255.255.255.0) 3/5/2010 9:42:26 PM - Info - UPNP Discovery started 3/5/2010 9:42:26 PM - Info - Web Server started on port 80 3/5/2010 9:42:27 PM - Info - Web Server authorized local login successful from: 127.0.0.1 User: default 3/5/2010 9:42:27 PM - Info - Creating ASP.NET application host... 3/5/2010 9:42:37 PM - Info - ASP.NET application host created then when I just hit the save button I get 3/5/2010 9:54:04 PM - ISY Insteon - MAIN: Entered GenPage for Status 3/5/2010 9:54:04 PM - ISY Insteon - COMM: GetNodes: No matching nodes of type TYPE_CLIMATE found. 3/5/2010 9:54:04 PM - ISY Insteon - COMM: GetNodes: No matching nodes of type TYPE_WEATHER_MOD found. 3/5/2010 9:54:04 PM - ISY Insteon - COMM: GetNodes: No matching nodes of type TYPE_ENERGY_MOD found. 3/5/2010 9:54:04 PM - ISY Insteon - MAIN: Leaving GenPage for Status 3/5/2010 9:54:08 PM - ISY Insteon - MAIN: Enter Status PagePut 3/5/2010 9:54:09 PM - ISY Insteon - COMM: Subscription thread started 3/5/2010 9:54:09 PM - ISY Insteon - COMM: Calling GetNodesConfig ... 3/5/2010 9:54:09 PM - ISY Insteon - COMM: Subscribe: Caught abort: Thread was being aborted. 3/5/2010 9:54:09 PM - ISY Insteon - COMM: Busy Check - delay only. I've updated to dot net 3.5 and the newest version of the Java runtimes. I've confirmed that I can get to admin console from that machine and connect properly. I do have a number of services disabled on that machine. As I mentioned it's not a very powerful box so I've disabled a lot of services that I normally wouldn't use - network DDE, net tcp port sharing, routing and remote access, and a few others. I'm wondering if that might be the problem. The other potential issue I should point out is that I'm testing Brad77's mediacenter plugin. I'm not sure if the connection from the mce plugin could in some way interfere with the operation of the homeseer connection. I know my Elk rules won't run with my ISY till I disconnect from the Elk. I've tried shutting down MCE while testing the homeseer plugin but, as Scotty would say 'It dinna do a bi agood' mark Edit: [40 minutes later] I thought about it a bit and decided that perhaps I shouldn't have insteon enabled in homeseer if I have the isyinsteon plugin there as well. I thought having 2 PLMs in the system (yeah... I'm strange, I actually have 3) may confuse things. I disabled it and restarted homeseer but it didn't make any difference. I did notice a message that didn't appear in the log - it said 'comm manager found a non-ISY UPnP device' when I hit save on the insteonISY config page. here's the log from an attempt to use the port as 192.168.xxx.xxx:443 (I thought it may need to be https) and with my regular IP again. 3/5/2010 10:31:05 PM - ISY Insteon - MAIN: Entered GenPage for Configuration 3/5/2010 10:31:05 PM - ISY Insteon - MAIN: Leaving GenPage for Configuration 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: Enter PagePut 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: old_loc = 0, location = 0 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: old_loc2 = 0, location2 = 0 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: Leaving PagePut 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: Entered GenPage for Configuration 3/5/2010 10:31:12 PM - ISY Insteon - MAIN: Leaving GenPage for Configuration 3/5/2010 10:31:19 PM - ISY Insteon - MAIN: Enter PagePut 3/5/2010 10:31:19 PM - ISY Insteon - MAIN: PagePut: Calling start_isy() 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Subscribe: Caught abort: Thread was being aborted. 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Subscription thread started 3/5/2010 10:31:20 PM - ISY Insteon - COMM: isy instance reset to initial values. 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Calling GetDescURL(192.168.xxx.xxx:443) 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Parse description URL (http://192.168.xxx.xxx:443/desc) 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Attempting to auto-discover ISY 3/5/2010 10:31:20 PM - ISY Insteon - COMM: Starting auto-discovery 3/5/2010 10:31:25 PM - ISY Insteon - COMM: Found a NON-ISY UPNP device. 3/5/2010 10:31:29 PM - ISY Insteon - COMM: Found a NON-ISY UPNP device. 3/5/2010 10:31:29 PM - ISY Insteon - COMM: Found an ISY: http://192.168.xxx.xxx/desc 3/5/2010 10:31:29 PM - ISY Insteon - COMM: Found URL http://192.168.xxx.xxx/desc 3/5/2010 10:31:29 PM - ISY Insteon - COMM: Parse description URL 3/5/2010 10:31:30 PM - ISY Insteon - COMM: Attempt to authenticate ISY access. 3/5/2010 10:31:30 PM - ISY Insteon - COMM: Authenticating with ISY 3/5/2010 10:31:30 PM - ISY Insteon - COMM: Authenticate returned 200 3/5/2010 10:31:30 PM - ISY Insteon - COMM: service client created 3/5/2010 10:31:30 PM - ISY Insteon - COMM: Set ClientCredentials. 3/5/2010 10:31:30 PM - ISY Insteon - COMM: Busy Check - delay only. 3/5/2010 10:31:31 PM - ISY Insteon - COMM: ISY configuration query attemp 1 failed. 3/5/2010 10:31:32 PM - ISY Insteon - COMM: ISY configuration query attemp 2 failed. 3/5/2010 10:31:32 PM - ISY Insteon - COMM: ISY configuration query attemp 3 failed. 3/5/2010 10:31:32 PM - ISY Insteon - COMM: ISY configuration query attemp 4 failed. 3/5/2010 10:31:32 PM - ISY Insteon - COMM: ISY configuration query attemp 5 failed. 3/5/2010 10:31:33 PM - ISY Insteon - COMM: ISY configuration query attemp 6 failed. 3/5/2010 10:31:33 PM - ISY Insteon - COMM: ISY configuration query attemp 7 failed. 3/5/2010 10:31:33 PM - ISY Insteon - COMM: ISY configuration query attemp 8 failed. 3/5/2010 10:31:33 PM - ISY Insteon - COMM: ISY configuration query attemp 9 failed. 3/5/2010 10:31:34 PM - ISY Insteon - COMM: ISY configuration query attemp 10 failed. 3/5/2010 10:31:34 PM - ISY Insteon - COMM: ISY configuration query failed. 3/5/2010 10:31:34 PM - ISY Insteon - MAIN: old_loc = 0, location = 0 3/5/2010 10:31:34 PM - ISY Insteon - MAIN: old_loc2 = 0, location2 = 0 3/5/2010 10:31:34 PM - ISY Insteon - MAIN: Leaving PagePut 3/5/2010 10:31:34 PM - ISY Insteon - MAIN: Entered GenPage for Configuration 3/5/2010 10:31:34 PM - ISY Insteon - MAIN: Leaving GenPage for Configuration 3/5/2010 10:35:05 PM - ISY Insteon - MAIN: Enter PagePut 3/5/2010 10:35:05 PM - ISY Insteon - MAIN: PagePut: Calling start_isy() 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Subscribe: Caught abort: Thread was being aborted. 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Subscription thread started 3/5/2010 10:35:06 PM - ISY Insteon - COMM: isy instance reset to initial values. 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Calling GetDescURL(192.168.xxx.xxx) 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Parse description URL (http://192.168.xxx.xxx/desc) 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Attempt to authenticate ISY access. 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Authenticating with ISY 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Authenticate returned 200 3/5/2010 10:35:06 PM - ISY Insteon - COMM: service client created 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Set ClientCredentials. 3/5/2010 10:35:06 PM - ISY Insteon - COMM: Busy Check - delay only. 3/5/2010 10:35:07 PM - ISY Insteon - COMM: ISY configuration query attemp 1 failed. 3/5/2010 10:35:08 PM - ISY Insteon - COMM: ISY configuration query attemp 2 failed. 3/5/2010 10:35:08 PM - ISY Insteon - COMM: ISY configuration query attemp 3 failed. 3/5/2010 10:35:08 PM - ISY Insteon - COMM: ISY configuration query attemp 4 failed. 3/5/2010 10:35:09 PM - ISY Insteon - COMM: ISY configuration query attemp 5 failed. 3/5/2010 10:35:09 PM - ISY Insteon - COMM: ISY configuration query attemp 6 failed. 3/5/2010 10:35:09 PM - ISY Insteon - COMM: ISY configuration query attemp 7 failed. 3/5/2010 10:35:09 PM - ISY Insteon - COMM: ISY configuration query attemp 8 failed. 3/5/2010 10:35:10 PM - ISY Insteon - COMM: ISY configuration query attemp 9 failed. 3/5/2010 10:35:10 PM - ISY Insteon - COMM: ISY configuration query attemp 10 failed. 3/5/2010 10:35:10 PM - ISY Insteon - COMM: ISY configuration query failed. 3/5/2010 10:35:10 PM - ISY Insteon - MAIN: old_loc = 0, location = 0 3/5/2010 10:35:10 PM - ISY Insteon - MAIN: old_loc2 = 0, location2 = 0 3/5/2010 10:35:10 PM - ISY Insteon - MAIN: Leaving PagePut 3/5/2010 10:35:10 PM - ISY Insteon - MAIN: Entered GenPage for Configuration 3/5/2010 10:35:10 PM - ISY Insteon - MAIN: Leaving GenPage for Configuration mark