bpwwer

I've seen a couple of threads about the Kwikset deadbolts on Cocoontech forums, but it seems that most people are using some type of HA software to control them. I just bought a Kwikset zwave deadbolt but was sent one with the wrong finish so I'm waiting for the right one. I already have HomeSeer so that's probably what I'll use, at least at first.

Well I'm still not seeing any variable events. I have a variable set up to increment as part of repeat program so it increments every 2 minutes. I see the program events, but nothing for the variable. I also set a variable via the REST interface and see no events generated. The screen shot clearly shows that the variable changed at 6:41:27 but the event viewer shows nothing variable related anywhere around that time. My own program that subscribes to the ISY is showing the same thing as the admin console event viewer. Everything else variable related seems to work fine so what am I missing?

Thanks Brad and Chris, I'll spend some more time playing with it. My initial check was not showing any variable related messages. However, most of the changes were being made from the admin console screen. I did set up a program to increment a variable and I did see the program messages but no variable change message (could be I'm filtering those out though). Also, I was looking for updates in the udiws20.ws and didn't realize there was a new udiws30.ws Doh!

Some of these variable related questions might be more appropriate in the Developers forum but since we're talking about them Will changes to variables eventually send messages? Right now I'm not seeing any messages from the ISY when variables are created, removed, or when the value changes. Also, will variables be accessible though the WSDL interface or just REST?

Steve, Did you restart the HomeSeer or the plug-in after the swap? If not, I'd recommend at least doing a re-sync of the plug-in from the plug-in's status page. Restarting HomeSeer would be better to make sure it syncs properly with the ISY. Also, what version of the plug-in and what version of the ISY firmware? If at some point in this your ISY got upgraded to the latest firmware but you're still using an older version of the plug-in, you'll need to update the plug-in to the latest release candidate available on the HomeSeer Forums. http://board.homeseer.com/forumdisplay.php?f=919

I think you need to put the "/setoutps.cgi?0000W11=TTL1+ON" up in the Path text box. It needs to be sent as part of the URL instead of as the HTTP body.

If you are seeing a pause of 5 seconds between when the ISY starts to query the ECM-1240 and when it gets a response from the ECM-1240, that seems excessive. I'm able to query my ECM-1240 every 2 seconds without a problem. I don't have any MS and my ECM-1240 is hardwired to the EP-1 but even so the EP-1 should respond almost instantly when it's queried for data. Michel, Is it possible that the ISY is blocked while a TCP connection is trying to be established and that the serial buffer for the PCM connection overflows, losing any messages that were sent at that time?

Same result here. I had to do the update twice to get it take. The first attempt showed no errors or failures. I suggest performing the upgrade a couple more times (without re-downloading the file) and see if that works.

The ISY plug-in in HomeSeer doesn't create separate devices for the weatherbug values. It currently just creates 1 device for the module. The device string contains the current temperature value and unit so mine currently has "60.8 F" in the device string. The individual weatherbug values are accessible to HomeSeer scripts and can be used in conditions/triggers. There is also a plug-in status page that shows all the individual values, you can see an example of that on my web page for the plug-in http://www.bobsplace.com/ISYInsteon/ You're the second person to ask about individual HomeSeer devices for the weatherbug data. So it will very likely end up as a feature of a future version.

Hi nickoonce, I have a sample Visual Studio C# application that subscribes to events and just displays them in a window. If you'd like the source send me an email or PM. bob@universal-devices.com

but seriously, what does "code freeze" mean? Typically, it means that the source code is locked and developers are not allowed to make unapproved changes to it. This is used to prevent minor changes going in and generating new bugs right before a release. Only fixes to critical bugs would normally be allowed during this time. Those would have to be well understood so that risk to other parts of the code are known. Basically, now that it's been tested for a couple of weeks, don't break it right before release

I do have a couple of controlincs so I can try to reproduce this, but I'm not very optimistic. What I can do is create a special build of the plug-in for you with just the controlinc triggers instrumented to display some detailed log entries. I can either instrument all controlinc button press events, or if you want to send me a specific insteon address, I could just instrument events from that device only. What version of the plug-in are you currently using? Send me a email at isyinsteon at bobsplace.com and I'll let you know when I ave a special build for you.

upstatemike, About the only thing I can suggest is to turn up the logging on the plug-in. It will generate a lot of log information and being intermittent, it will be hard to track down the problem in the log, but you will be able to see what the plug-in is getting from the ISY. When button 2 causes HomeSeer to do the speak action, I assume it also isn't causing the same result on the linked devices as button 1, correct? If so then that probably means something is wrong in the plug-in. Can you get it to happen in a reasonable amount of time if you repeatedly press the 2 On button? What are buttons 1 and 2 linked to? Is it a small enough set of devices that you could post the details? What trigger are you using in the plug-in?

Mark, I wasn't really recommending a virtual machine for HomeSeer. Mostly I just wanted to give another example of what works well from the processing/memory requirement standpoint. No worries. When we first got boards with Atom processors, we used them a bit for large compilations and they were really slow compared to our regular development machines. However, it was pretty amazing that there was no fan and no heat sink on the processor. You could touch the processor without getting burned! Don't try that with you Celeron system

I suspect that memory is probably the bottle neck. But unless you have some laying around, it may not be worth the effort to try and upgrade it. I'm probably a bit biased since I work for Intel and currently work on software for Atom based platforms so I figure I should disclose that up front. I have something that's similar to the Revo, a 1.6GH Atom based system, but with 2GB of ram. I use this system to run MainLobby and it works fine. I don't have any performance issues with it. I suspect HomeSeer would run fine on it too. I replaced a Pentium 4 based machine and don't notice any real difference performance wise (given the limited interactive use it gets). The primary reason for the Atom based system was to reduce the power being used since the system is always on. I have HomeSeer running on a virtual machine (hosted on a Mac mini). I give the virtual machine 1GB of ram and it's fine. I also use the virtual machine for a lot of other things. Both machines are running Windows XP.

You're welcome! Any questions or other problems, just let me know.

Hi Mark, Thanks for the detailed report! Based on that error I'm going to guess that you have an ISY firmware version newer than 2.7.6. And that you have the official plug-in release from the HomeSeer updater. If those are both true then that's the problem. The 1.0.1.0 official version of the plug-in only support ISY firmware up to 2.7.6. Please go to the HomeSeer forum and download the beta version 1.0.1.12. That version should work with all ISY firmware version 2.7.0 and later, including 2.7.12. I don't believe you'll have any problem because o the missing services. If you can connect to the ISY via a web browser or the admin console from that machine, it should be fine. There's no problem running both at the same time. I have run Brad77's MediaCenter plug, my HomeSeer plug-in, my Mainlobby ISY plug-in, and the admin console all that the same time.

It does require .NET 3.0 or later. With the older .NET versions it does fail in a non-obvious way.

Hi Mark, Beta versions (which also have the same 30 day trial period) are posted to the HomeSeer website. I just finished posting the latest a couple of minutes ago. If you're using any of the recent ISY firmware versions, you'll be better off with the beta. The latest beta version is what's being targeted for the next official version. http://board.homeseer.com/forumdisplay.php?f=919 Most of the support happens via the forum above, but you can also email me directly at isyinsteon at bobsplace dot com.

This is a pretty good reference: www.elkproducts.com/pdf/ELK-Insteon-ISY99i.pdf There might have been some issues with some of the recent alpha versions of the firmware but I just followed the instructions using 2.7.11alpha without any problems. I believe all versions of the firmware between 2.7.0 and 2.7.6 should work fine too.

Hi Jackie, I saw this post before the email. The current release version of the HomeSeer ISYInsteon plug-in does not work with the 2.7.8 firmware. Some of the interface API changes cause some failures in the initial communications between the plug-in and the ISY. There is a beta version of the plug-in posted on the HomeSeer forum that does work with the 2.7.8 firmware. See http://board.homeseer.com/showthread.php?t=138709

Hi Xathros, The X10/A10 module doesn't add anything to the linking menu. After you select "New INSTEON Device", You'll find X10/A10 devices listed in the device type drop-down menu if it is installed. I believe you enter the X10 house/unit code in the address field. Once added, it should show up in the tree.

It looks like you have the basic format of the request correct, but the device address format is wrong. You need to use the ISY's address format. Best way to get that is to use the REST /rest/nodes first and look at how the device addresses are returned. I think you probably want it to look like: http://192.168.50.100/rest/nodes/12 4B 5A 1/cmd/DFON For the browser URL, you might have to change the spaces to '%20'.

Have you tried a different cable between the PLM and the ISY? If that doesn't work, take a look at the connector on the ISY and make sure none of the springy wires in there are stuck down do they don't make a good connection.

There should not be any issues with having the console open indefinitely. The ISY is designed to have clients that maintain a constant connection to it. Home automation software plug-ins need this capability so that they can keep device state synchronized between the automation system and the ISY. If you do see any adverse effects that seem to be caused by having the console open for extended periods of time, let us know because it would be considered a bug.