MarkJames

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

installing 3.5 as we speak... I was on 2.0. Like I said - it's a clunker - it'll be installing 3.5 for 45 minutes easy. Once upon a time there were no JRE's or dot net frameworks..... now it's the first thing you gotta check. Of course back then you had to check your IRQ and your DMA. I guess it's a wash. mark

Thanks, Bob, lol - good to see the author right here. Who woulda thunk it? I'm having a bit of a time getting it to be recognized in the setup screen. I keep getting an 'unable to access HSPI_ISY_insteon.hspi (or something similar - I can't cut/paste from my telnet session) in the log. I'll try updating my .net framework - perhaps it's too old. mark

Thanks - I'll try that. I was using the updater and many of the plugins said 'free to try - x$ to buy' but that one didn't have that notation attached. Thanks again, mark

I didn't see a try-before-you buy with it. All I saw was a 'pay now' button. $60 is a lot to buy something sight-unseen. mark

I was just about to buy the ISY plugin for homeseer. I noticed there's a coupon code box. Does anyone know any coupon codes for this? Thanks in advance, mark

I'm not sure Michel meant that all your devices have to be in the same 'state' as your scene in order to write. If that were the case I'd never be able to write to any of my switches as they're all members of multiples scenes. They'd never be in sync with one another as far as all the different scenes were concerned. If this is, indeed, the case I'd like to know as it would be a significant change to my understanding. mark

Sorry.. this is the quote I was referring to from a different post in which Michel mentioned that you could delay writes. In retrospect it doesn't seem to answer your problem. mark

My bad - I assumed the hometroller was some kind of flash-based device that ran only homeseer. Does that work well? I've considered it but rejected the idea thinking that noise and such would make it clunky Are you using stargate relay outs to direct your PA announcements or are you targetting them some other way/not at all? Stargate is truly a stable workhorse. It's hard to make it crash without dumping tons of data into the serial ports. Is this just to integrate everything? Schedules still have to be written in winevm, I would think. I've wanted to use communicating thermostats but my home is a mix of hotwater baseboard heat, electric radiant, and electric baseboard. The electric baseboard requires 220V thermostats. There was once a co mmunicating stat made by ouelette - x10 based - but it's no longer available and you couldn't query it. If I can't do all of it it seems pointless to do part of it. You must have built your home around your HA. Sounds like you've got serial communication wire running all over - that's hard to retrofit, though possible if you're determined enough.

I think oberkc hit it. There are a couple of green icons in 2.7.12 and the previous few releases. One has like a 101 on it - the other says writing. The 101 means that there is a pending write - the writing one - well - is writing. I don't have pro but from what I understand there's a batch write feature. I thought this was mostly intended for RF devices but the impression I got was that it can be used for any. Have you tried rightclicking the device with the green arrow and hit 'write updates'? Or using the batch mode button? I'm with oberkc on this - I don't think that the state of any scene/device matters to it as far as ISY writing to it. If it is it's a behavior I've never seen myself.

Are you using the pc based version or the controller based? If it's the pc based do you find it stable? mark

Just curious if anyone is using voice prompting at all with their ISY. I come from JDS Stargate so I've become dependent on voice outputs and phone commands. I really miss those. Being informed through a speaker that 'the garage door is open' is far superior, imho, to having a light flash or some other indicator. To accomplish this with ISY I've been using it parallel to PowerHome 2. The PowerHome software supports TTS (text to speech). I have an old PC that I've installed Powerhome on with a second PLM to integrate it into my home system. I haven't added any of my insteon devices to the second PLM - it's just there as an interface between the insteon powerline messaging and the PC. When something turns on - like the garage door I have a program like this If Status 'Garage Door Sensor' is not Off Then Send X10 'E3/On (3)' Set Scene 'Garage Door Open Alert LED' On Else Set Scene 'Garage Door Open Alert LED' Off The Powerhome software sees the E3 On via the PLM and that triggers a TTS event that speaks the words 'Garage Door Open' through an amplifier connected to speakers in the house. It checks the time of day first, of course, so it doesn't go yelling stuff in the middle of the night. This works - sort of. Powerhome is a bit prone to crashing so I have to restart it every couple of days. It would be great to have an interface of some sort that would allow TTS based on Insteon messages/status. Is anyone aware of such a creature? mark

I just read through all the posts in this forum and I think congrats are in order. There doesn't appear to be many problems reported with 2.7.12 Time for the Elk module!

you can't 'write anything'? As in make changes to the link records and change the scene memberships?

That's true - the PLM is a controller for every button, group, load, and scene in the system. There's a long-winded explanation for how controller/responder records works here

Good point! I've been lucky - never had an update go bad! Keepin' my fingers crossed!

ahh... thank you. So as long as I find ISY just fine through my regular browser session to the ISY ip there's no reason for me to use the launcher. Excellent. I'll keep that link info around in case I need it one day, though. mark

Is there a difference between launching the admin console from http://www.universal-devices.com/99i/2.7.12/admin.jnlp vs just pointing my browser straight to the ISY? Why would you use one over the other? mark

I updated from 2.7.11 to 2.7.12 and can no longer play the violin. Curse you, ISY

I only forward port 80. I use port 800 externally and internally use port 80. My ISY is on port 192.168.0.170 - so my forward looks like this TCP forward external port - 800 internal port - 80 destination IP - 192.168.0.170 My WAN IP (given to me by my ISP and visible in the status section of your router or even easier - just go to whatismyip.com) is, say, 169.154.20.13 - so when I'm away I log on to http://169.154.20.13:800 The reason I use 800 instead of 80 is that some ISP's scan their IP range for web servers and will give you grief if they find one. If you don't care about this you can just forward your port 80 and skip the :800 part as http will take you to port 80 by default. mark

You'll have to follow the bug reports and firmware updates page to see if anything impacts on you. I currently use 2.7.11 - the newest version - and have noticed no problems. I don't use an IRLinc, EzIO, or communicating stats but have every other insteon creature there is. I think 2.7.7 is the last 'official' release - the others are alphas. The nice thing with ISY is it's not like other hardware/software. The engineers and programmers are right on top of it. If there's a bug or problem it's fixed - usually within days. Enjoy!

My apologies - I did misunderstand. I thought your load was turning on/off from a button that you didn't want controlling it. I'm afraid I don't have a clue why ISY doesn't match statuses with you and will shut up now and wait for michel and the gang to help you out. The only thing that I could imagine is that the Offs and the very low %age ons are getting confused. regards, mark

You're trying to turn it OFF with an ON command - you can't do that with a KPL local button. If you want to turn it off you'll have to do it with an off command or set the dim level to like 1% which, for all intents and purposes, is off. Just be careful because if you then use it's status for programs it's status is NOT off - you'll have to watch for dim levels instead. Dimmed to 1% looks off but is considered on. As for your button 3 controlling the load when you don't think it should, have you tried checking the links to see if all is right? Go to Tools -> diagnostics -> show device links then hit start. Select the KPL that's causing trouble and let it run it's course. When it's done hit the compare button and it will compare what's in the KPL vs what ISY thinks should be there. This is a hugely handy feature. I'll betcha dollars to donuts that you have some links from your pre-isy time. mark

6 button and 8 button KPL-s work the same way - only the naming changes. In an 8 button KPL the buttons are number 1,2,3,4,5,6,7,8 In a 6 button KPL the buttons are number 1,3,4,5,6 - the 2 is merged with the 1 to become an ON and the 7,8 merge to become the OFF. Either way the load is button 1 or 1/2 or A or A/B whatever you want to call it - and is the only place the load can connect. You can switch a KPL-6 to be an 8 and back again by air gapping it 10 seconds then holding A and H while pressing in for 2 seconds to make it an 8 or pressing AB and GH for 2 seconds to make it a 6. Of course you have to change the face plate as well as the button configuration is physically different. I've been wishing for a long time that they'd make a KPL with a user-definable load button but that doesn't seem to be a high priority for many people. Some users have even used KPL-8s upside down in order to make the load the H button. mark