KMan

Thanks for the suggestions. Will look in to CasaTunes, although it sounds too pricey. The only Apple hardware I own is a 2nd(?) gen iPod, and not really looking to upgrade that device. I did find an open source media server (Subsonic) which looks like it will do a lot of what I want, looking in to it right now. It is more focused on music than Kodi or Plex. As far as amplification, I haven't really decided yet ... looking at purchasing a small amp/splitter. Our house already has whole house audio via an old 1970's intercomm system ... we're not audiophiles, so it sounds ok to us lol. Probably could continue to use that wiring as is, but will likely re-wire it.

I want to set up an ISY controlled music server, which 90% of the time would be playing an iTunes playlist. If anyone has suggestions or setups already doing this, I'd love to hear them. Here are the requirements: Tier 1 requirements: - Play an iTunes playlist - Playlist dynamically updated when changed in another PC Tier 2 requirements: - Play radio stations - Start/Stop/Pause via ISY (this is Tier 2 only because I think I can just use Insteon controlled power to the amp if needed) Tier 3 requirements: - Control iTunes playlist (i.e. select other lists) Constraints: - I already have speakers throughout the house, just need a source. So not going to use Sonos or something similar. - Not a fan of Apple products, so not likely to use them (other than iTunes) I have an always on PC and an always on RPi that could be used. Would also consider an always on Android tablet. Some things I've looked at, but none seem easy to integrate iTunes playlists ... - Plex - Kodi - iTunes (doesn't seem to have an open API for remote control). I suppose I could just have it always on, and control the output power. Anyone have any suggestions or guidance? Thanks, Kyle

Ah ... missed that in the first post. Makes sense that he needs the variable then.

If the variable isn't needed for other programs, there are a few ways to do this without the variable. Which either makes it more or less complex ... but it is always good to know multiple ways of solving these problems.... Here is one way, using the motion sensor commands to directly control the program: Laundry Motion - [ID 0009][Parent 0001] If Control 'Motion Sensor-Sensor' is switch On Or Control 'Motion Sensor-Sensor' is not switched Off Then Set 'Basement / Laundry Light' On Else Wait 1 minute Set 'Basement / Laundry Light' Off With the above If construct, the "Then" clause will run when the sensor sends the On command, and the "Else" clause will run when the sensor sends the Off command. The "is not" is used to specify to run the Else clause when the statement is true. Here is another way, and is the way I use, as it results in slightly faster response. Whether the faster response is noticeable or not I don't know, but I set this up right after I had set up an open/close sensor which responds slowly (I'm not sure if the slow response is due to the sensor itself, the ISY or the target device). 1) Change the motion sensor to only send On commands (assuming the one you are using can do this). 2) Link the motion sensor directly with the target device (Basement / Laundry Light). That is, make the motion sensor a controller for the light, and the light a responder to the sensor. Mine are linked via a scene, but I honestly don't remember if a scene is required or not. Doing these 2 steps removes the ISY from the "turn on" command. The sensor directly turns on the lights. Then you only need the program to turn the lights off, which could look like this: Laundry Motion - [ID 0009][Parent 0001] If Control 'Motion Sensor-Sensor' is switched On Then Wait 1 minute Set 'Basement / Laundry Light' Off Else - No Actions This program essentially just starts a timer when the sensor sends the On command, and will turn off the light after 1 minute without seeing another On command. Note that to get the exact same behavior as the your program, you'd need to make the wait time 1 minute + the Off time of your sensor. This timer starts with the On, while yours starts with the Off. -Kyle

If you blink ... UDI slips in another feature. Now if Amazon would just be as responsive ...

Teken, I *think* intermediate certificates are needed if you want to use IFTTT without the ISY portal. I don't think they are needed to do things locally (neither ifttt nor ISY portal can be run locally). The native ifttt email trigger can trigger on receipt of any email, or on a hashtag in a subject line. Note that these emails are sent to an ifttt email address. There is another channel specifically for gmail that is more flexible and integrates into a gmail address. If you are running an SMTP server locally, I suspect there are ways to hook in to it and/or run scripts to generate rest requests to the ISY. It would be more complex, and may require some programming, but also is not dependent on the cloud (ifttt). -K

HAD is available via the portal ... see Benoit's post here.

Email to ISY can be done indirectly through IFTTT, using the email channel and maker channel. The email channel will receive an email, and the maker channel can generate a rest call to ISY. You will either need to have the appliance send an email to IFTTT, or have the email forwarded to IFTTT. I think any rest call to ISY is going to require credentials. If using IFTTT, going through the ISY portal gives some measure of security, as you can create an ISY Portal user that is non-admin. Here is a good post by MWareman describing how to use the maker channel and the ISY portal.

Did you review this thread: http://forum.universal-devices.com/topic/17567-purchased-portal-module-but-unable-to-connect/?p=158620 Sounds like Skywizzard was having a similar error, though he reported it in the portal, not from echo.

Did you get an email with a link that you clicked on?

DId you go to Configuration->Portals? I think that's where the approval is done.

In the portal, there is a "My Profile" link in the upper right hand corner, which will let you link your amazon account.

From: http://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface#Nodes You need to use "nodes" and put a "cmd" in there: /rest/nodes/45761/cmd/DON

Good info on the credentials, I wasn't aware of that feature. I'll probably purchase portal just for the speed of connection. Mobilinc is painfully slow for me when used remotely. Shhh ... don't tell UDI, but this is probably the real reason I'll purchase the portal. I've "donated' more money to other companies that have done a lot less for me.

It's never been clear to me how much of ISY business is from "integrators", who build systems for others to use. That's where the ease of the portal pays off, but I'm not sure if that is a real business case for UDI. Someone elsewhere also mentioned the portal being more secure than port forwarding, with the claim that you don't need to have your ISY credentials out there ... but I assume the portal also requires credentials, so I don't understand this point.

I believe the portal also solves the problem of your WAN IP address changing. The communications through the portal is not dependent on your WAN IP address. Although both port forwarding and changing IP address can be addressed in other ways, they are not very easy for most people.

I had the same problem on 2 switchlincs (all that I've tried so far) ... but they both started working after I told them to brighten to 100 (didn't try anything else before 100). Working means that "Turn on" now works for both of them.

What are you trying to do? My understanding is that your program will only run twice a day: The "Then" clause runs at 9pm and the "Else" clause runs at 9 am. So it is not processor intensive, but it probably isn't doing what you want.

Just want to say thanks to everyone who has contributed to this effort. Got my Echo and ISY integrated over the weekend ... just the basics right now, but am looking forward to extending the functionality. Wife was pretty tickled when she was able to turn lights on/off through the echo. I followed the instructions posted by jackal in post 867 ... had a few bumps along the way, mostly with resurrecting my RPi (and my lack of Linux experience).

If you run at the cmd line with the > logs part included, and the logs file isn't created .... that is a pretty good indication that there is a problem with creating that file. Try taking everying out after the ">", except for the last "&". That will do the same thing, just without creating the log file.

I think you are on the right track .. I just had a very similar issue, which was due to the logs directory not existing. Are you doing this at the command line or in rc.local?

Thanks for posting that. What is the need for the network module in this setup? What does the ISY need to talk to for this to work? I haven't had time to read the 40 pages in this thread yet ... not sure if I'll have time before the UDI skill is approved/published. This thread (and the pending UDI skill) prompted me to pull the trigger on an echo over the weekend. So far, entirely underwhelmed with it, but integrating it with the ISY would be off the charts in WAF.

lol ... I thought that's what I provided ... I just chose 2 minutes for the timeout. I *think* the programs I provided will restart the sequence if the next keystroke isn't pressed within 2 minutes. I was thinking that the "Run Program 'Master Light Timeout' (Then Path)" statements would re-start the 2 minute timeout each time a keystroke was pressed. But honestly I don't know if it works like that.

Thought I did provide a 2 minute timeout on the sequence.

Ah ... cross posted with oberkc ... he is probably right ... might be easier done with a variable .... State 1: If Control 'Master Light.C' is switched Off And $i.PanicExitState is 1 Then Run Program 'Master Light Timeout' (Then Path) $i.PanicExitState = 2 Else - No Actions - (To add one, press 'Action') State 2: If Control 'Master Light.C' is switched On And $i.PanicExitState is 2 Then Run Program 'Master Light Timeout' (Then Path) $i.PanicExitState = 3 Else - No Actions - (To add one, press 'Action') State 3: If Control 'Master Light.C' is switched Off And $i.PanicExitState is 3 Then Stop Program 'Master Light Timeout' Run Program 'Panic Exit' (Then Path) $i.PanicExitState = 1 Else - No Actions - (To add one, press 'Action') Master Light Timeout: (always disabled) If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 2 Minutes $i.PanicExitState = 1 Else - No Actions - (To add one, press 'Action')