bsobel

I believe 'restore device' is your 1B Bill

The 'no go' symbol means that the program is disabled (when you edit the program there is a checkbox that says enabled, or you can right click on it to enable it) If your father had this disabled before it may have been intentional, but you'd have to ask him why. The programs sounds fine, the symbol does not mean there is an error just that is was manually (or automatically from another program) disabled from running. Best, Bill

How do you have these wired? Is this a three way circuit? The voltage at the switch should be the same regardless of the dim level so I'm wondering if you them wired correctly. Sent from my iPad using Tapatalk HD

You need to go into safari settings and allow the java app for udi to run outside the sandbox. This is new in Mavericks. Sent from my iPad using Tapatalk HD

After a brief power outage in Mexico the other day I've been looking to do the same thing. I'm leaning towards the web control board or a relay driving a pin on a raspberry pi (I use raspberry pi's already for Philips Hue, Sonos, and bluetooth phone detection tied to the ISY). Please post what you come up with (I'll do the same if I solve it), I'm sure we aren't the only ones who want this.

Lee is the query guaranteed to return before the next statement or is a wait needed? I'm hoping its the former but was never clear on this specific construct.

FYI the new appliance links (shipping 11/22) appear to support being a controller from the manual on/off buttons they are adding. Just a thought if local control is critical you might want to swap out this unit for one of them http://www.smarthome.com/2635-222/INSTE ... ule/p.aspx

IMHO The dual band switches are good for one use case, when you have multiple of them in a box and they are on different phases. Gives another path for the signal. The access points have a much less obstructed ability to relay the signals in my experience. Bill

"but both AND and OR produce the same results" Sigh. Bill

As written with the ands I don't see how it could ever execute

Ok, this is where the ISY language syntax doesn't make sense to (some of us). The second line 'and control is NOT' doesn't do what I think you expect it to do. Its normally used when you actually want to check for that event (e.g. fast off) but want the else clause to fire. As written I don't think the statement can every fire. I also don't think you need the 'is not switched' part of each test. If you remove that you should be fine.

Try restoring the device. Mine seemed to lose its' PLM link before and restoring it fixed it. Bill

I never noticed that. Is the port/format documented somewhere? Might as well write a listener for my rasperrypi's since they monitor pretty much everything else now too.

Well to be fair they are supposed to act like access points, but given where they are typically installed they are very range limited. The keypad communication isn't that strange. You have three devices, the keypad, the second keypad, and the PLM. The two keypads can see each other (possibly via RF) but one can't see the PLM (or the PLM can't see it). WIth noise and signal suckers you tend to wind up with groups of close by devices working just fine (once programmed) but difficulty with devices far away (like I'm guessing the PLM) not seeing them. As to Write Changes and Restore, write changes just tells the unit to try and write and queued up information to the device. Restore tells the system to queue up and fully reprogram the device. You shouldn't have to use that very often.

I could swear when I replaced my last one with a dualband I got the option to use replace device. Are you running the latest software?

If you can't write to the device you have a noise or signal suck issue you need to resolve. You won't be able to do any changes to the device until you resolve that. It doesn't sound like you have any access points, I can't urge you enough to get some. The dual band switches (IMHO) are really useful where you have a group of switches on different circuits in the same gang box. WIthin that box wireless gives them a great way of further linking the network. They do not (again IMHO) have the range in many situations to act as a reliable access point replacement. I probably have 10 or so of them installed here in San Diego, I think I have something like 22 in Mexico (old wiring and 3 foot stone walls make for fun installs) Restore device rewrites all the settings to the device that ISY tracks (the link table, state of the buttons [toggle or fixed on/off], etc.

For a run that long I'd suggest running one circuit from the old house to the new house and basically just putting an access point on it. Use that to 'couple' to the circuits in the new house. You could try two externally mounted access points (I do this at one of my places where there are 2 separate outbuildings from the main house, it works well but I've not tried that kinda of distance). I wish Smarthome would release a accesspoint with a wired (coax or cat5) option to physically link separate electrical systems...

"This second "on" tap didn't work on any other dimmer than the one controlling the actual load. The other ones just sat there." Are all of the dimmers controllers for the scene? This should just work, I'm not why you had to glue it together with a program to monitor them.

I realize this is an old post, but why do you need both iAqualink and the Autelis? I could recreate all the functionality with just the Autelis but already had the iAqualink and the app is ok so saw no reason to rip it out since it coexists fine...

The IF part of your command get re-evaluated during the WAIT command, and on the second eval it's false so the wait cancels and nothing else runs past that. If you want to use the logic as is, have your then run a second program that does the light on/wait/off (with no conditions on the IF). The use of the second program ensures their is nothing to re-evaluate to cause the wait to not complete.

FYI I've asked (in the programming improvements area in the past) for the ability to write a program like this based on a scene and have the ISY internally 'break it out' into the list of individual devices (so that if you update the scene membership the program would automatically update). E.g. is control 'All Light Switch Scene' is on and internally the ISY would generate a list much like what you wrote above. We shall see if it is considered...

You definitely misunderstood its fully supported and not a linux thing. I'm doing it with my Raspberry Pi now for my Hue integration. You can see status changes, variable changes, etc. With the 4.x alpha you can get control events as well.

Those two lines are email headers, they should not occur in the body. Did you somehow get an extra CRLF into the Subject line? That would cause this. Can you post the raw message you received, headers and all?

If you want to keep the programs you can export them before the factory reset and import them later (same with network resources and I think variables)

Michael, I went through the same discovery process with this issue. I wound up writing an smtp proxy on my raspberry pi that connects to the pushoverapi directly if the email is sent to the Pushover email alias. This way I could simply use the ISY email configuration (and substitutions) instead of coding a bunch of network resources. In UDI's defense they literally ran out of firmware space on the 99s so couldn't get the required cipher suites on the box. This seemed to be the final nail in the issue, not their willingness to put the feature in. Cheers, Bill