bpwwer

Hi deg01004, Basically, what you're doing is correct. However, you're going to need to supply the authentication information too. What I've done looks like this: GET /rest/nodes/ HTTP/1.1 Authorization: Basic xxxxxxxxxxxxxxxx The GET line is terminated by a \r\n (carriage return, line feed) and the Authorization line is terminated by \r\n\r\n The xxxxxxxxxxxxxxx is the ISY username and password base64 encoded. admin:admin => YWRtaW46YWRtaW4= There are a number of on-line base64 converters like: http://www.motobit.com/util/base64-decoder-encoder.asp I don't use the HOST header, it's optional.

I'm glad the MLISY plug-in is working well. It is in need of an update though. It's pretty easy to find something to do the base 64 encoding. This site showed up on a google search and seems to work: http://www.motobit.com/util/base64-decoder-encoder.asp However, it's up to you if want to trust entering your isy password in a on-line form. Linux systems typically have a command 'base64' that can do this. I'm sure there are similar programs for pretty much any OS.

Can the crestron controller send strings to an IP address? If so then you should be able to use the REST interface. I wrote a simple little program so that I could use the REST interface from the Linux command line. It creates a string based on command line arguments that looks like this: GET /rest/nodes/x x x x/cmd/DON HTTP/1.1\r\nAuthorization: Basic YWRtaW46YWRtaW4=\r\n\r\n The authorization string above is admin:admin base64 encoded. The "x x x x" is the device address. My program just opens a network connection to the ISY and sends that string. So if you can format a string like that with the crestron, it should work.

You know what would be cool? A way to temporarily disable RF signals on the access points while doing power line device programming. Even better if this could be done progmatically. Or better yet, a way to disable any device from transmitting. Send out a broadcast message that says unless you're in program mode, don't transmit. Then a another message when done that says OK to resume transmitting.

This is just an idea, I don't have any X10 motion sensors or any X10 RF devices anymore so hopefully someone else can correct anything I'm wrong about. 1) Use a V572A or W800 to move the X10 signals to the power line. 2) Create 2 programs on the ISY for each motion sensor. The first sets the second one on and then off after a delay. if X10 G1 status ON then set program motion-1 to true wait 60 set program motion-1 to false I don't think the second program has to have any code in it at all, it is just acting like a true/false variable. Then in HomeSeer, hide the first program (filter it out in the config page) and use the second (motion-1) for your motion status. You can then use HomeSeer events to trigger on motion-1 going true or false to send whatever notifications you want. It might be possible to do this with one program per motion sensor, but I'll leave that to the ISY programming experts [/code]

The PLC should still have any links in it's link database. HomeSeer should still be able to control the devices. The rest of your devices should be clear of any links. Everything should be ready for you to start setting up everything with the ISY. Now all you need is some time

Rich, The HomeSeer PLC plug-in has to have created at least one link in the PLC for each device so that it can get status change messages. It may have created a corresponding link in each device. Using the ISY, under the tools menu, there's a way to read the device link tables. Pick a device, read the table and look for links to the PLC's address. If you find any then you know. You'll have to add the device to the ISY first, and when you do this, select the option to leave existing links. This isn't the recommended selection, but by using it, you won't break your existing setup. However, this is fine for some initial testing and experimentation with the ISY. I don't think there's any good way to migrate from one system to the other. The cleanest method is to reset all the devices to factory defaults, start adding them to the ISY and then re-create any scenes using the ISY. I'm assuming you're also going to switch to my HomeSeer plug-in, in which case you fire that up next, let it import everything and then start re-creating HomeSeer events as needed. There are a few people that have done this migration. Don't know how many regularly hang out here, but take a look here http://board.homeseer.com/forumdisplay.php?f=91 there are a few posts on the subject.

Great idea! I like to see "...and more!" I think some examples/demos of actual uses would be good. Things like garage door control, irrigation, motion sensors. I know there's a lot of information on these topics in the forum, but interactive sessions where the details can be more easily explained, I think would be helpful.

So I'm seeing something similar. I do have the Brultech module so I have an electricity tab, but nothing for Open Auto DR or Flex Your Power. When I check for available modules, I see the Open Auto DR module listed as available for $49. I didn't try to purchase it since I don't think I can do anything with it. From what I can tell it only works with certain rate schedules and mine isn't one of them.

Hi MIchel, Looks like both Tim's and mine are day(s) apart so what we're seeing probably isn't an issue. Thanks for the explanations. Michel, I have these 2 errors (among others) in my log too. So I am a bit concerned that they may be caused by my plug-in. Is there any way to see what client IP address is at fault? I regularly have 3 to 4 clients connect to the ISY (1 or 2 admin consoles, MainLobby Plug-in, and HomeSeer Plug-in). I also have up to 8 computers on my network and a couple other IP enabled devices. Trying to track down what may be trying to log in with bad credentials.

Michel, I have these 2 errors (among others) in my log too. So I am a bit concerned that they may be caused by my plug-in. Is there any way to see what client IP address is at fault? I regularly have 3 to 4 clients connect to the ISY (1 or 2 admin consoles, MainLobby Plug-in, and HomeSeer Plug-in). I also have up to 8 computers on my network and a couple other IP enabled devices. Trying to track down what may be trying to log in with bad credentials.

There are a copy of examples in the GUI Enhancements sections. http://forum.universal-devices.com/viewtopic.php?t=2275 is a replacement home page http://forum.universal-devices.com/viewtopic.php?t=2295 has an example of using the data from weatherbug to create real-time charts.

Michel, Thanks for that explanation. I didn't realize that's how the ISY prioritized tasks. While I like the idea that plug-ins get a higher priority, is this something that could be made user configurable in a future version? For people that want the ISY to be the primary controller it might make sense if the priority could be switched to make programs more responsive.

It appears to be hanging on the web services GetNodesConfig call. I have the plug-in in a loop that keeps re-trying if that command fails. I currently don't have it reporting the error, but I'll work with Michael and get him a version that does if it turns out to not be a hardware issue.

Joe, I posted a link to my web page that uses javascript and the weatherbug info to generate charts. Some of the ideas should be applicable to what you want to do too http://forum.universal-devices.com/viewtopic.php?t=2295

I think you can boot linux on a Mac using boot camp. I've seen references to people doing that but I've never tried it. Another idea is to use VMWare or Parallels on the mac to run linux distributions. I've been using Parallels on my Mac Mini to run Windows XP and it works really well. The only issue I have is lack of memory. The current Mini only has 2Gb of ram so it tends to swap a lot. That's how I've been doing all my development lately. The virtual WinXP machine is usually running Visual Studio, HomeSeer, and MainLobby concurrently. You'd have to check, but there might even be support for 64bit OSes in the virtual machines.

As a data point, on my Fedora 8 machine, I get this error when trying to change timezones: Exception in thread "AWT-EventQueue-3" java.lang.ClassCastException: java.lang.Double cannot be cast to java.lang.Integer I have Sun's Java package installed.

intellihome, If you have questions about how the HomeSeer plug-in for the ISY works feel free to post them here or in the HomeSeer forum section dedicated to the plug-in. http://board.homeseer.com/forumdisplay.php?f=919 I think there's a thread or two over there about how people are using the combination that you might be interested in.

Ahh, That makes sense. Thanks for clarifying.

I'm seeing the same thing. ISY-26, PLM v52. I upgraded from 2.6.12 directly. All three of the motion sensor devices show up with blank status and if I try to query any one of them, I get nothing. No messages in the log (set at level 2). I tried changing the advanced options to "Device Reported" and did a query of My Lighting and again, no entries in the log for the motion sensor. I'm also seeing the same behavior for the EZRain zones. All my other devices are queried just fine.

If it's failing, it's not displaying any error messages. The upgrade seemed to go flawlessly, just like every other upgrade I've done. After the upgrade, everything was working fine except the motion sensor and the the version number. I too first thought the upgrade didn't actually happen or that I had the wrong version. At least until I noticed the motion sensor wasn't working. That's why I tried so many times. edit: Just saw that 2.6.10 was released so I'll give that a try later. Thanks for such a quick response (to the posts and the release!)

I just updated to 2.6.9 and had to downgrade back to 2.6.8. After upgrading the Help->About box still said 2.6.8. I performed the upgrade 4 times and downloaded the version 3 times. All 4 attempts were successful. So I think the version number didn't get updated. This is for the ISY-26 After upgrading, my motion sensor shows up as an unknown device like reported elsewhere. This is why I'm pretty sure that I really did have 2.6.9 even though it reported itself as 2.6.8. After going back to 2.6.8 the motion sensor is correctly identified.

Ah, that maybe explains what I'm seeing. I was going to ask about this. I just got a motion sensor a few days ago and it shows up via the web services as 16.0.0.0 and the Smarthome docs say it should be 16.1.0.0 (I think) so I was wondering if the ISY was just reporting it wrong or if the docs were wrong.

Yeah, Ctrl-C

You can grab a copy from my website, http://www.bobshome.net/isy/isylogger.zip It's pretty simple, unzip the program, open a command prompt, execute the program with your ISY's ipaddress, username, and password as arguments. Not fancy auto detecting of the ISY.