oberkc

Yes, I went ahead and ran the power cycle. It is now on 5.7.0_5. My programs and needs are nowhere as complicated and numerous as many here, so it was not much more than 10 minutes of work to manually re-enable the appropriate programs and all appears to be working again (except the known problem with displayed sunrise and sunset times). On an unrelated topic, while I was on a roll, I finally upgraded to polyglot 3X without any apparent issue. Update: I guess something happened last night and even the displayed sunrise and sunset times are back to being correct.

My system sunrise/sunset times are off one hour (early), but programs based upon sunrise/sunset are scheduled one hour later (correct time). Based upon my system, I see no reason to think that this is nothing more than a UI issue.

Not yet. Just "rebooted" (from the admin console). I may do this soon.

When my programs became disabled (and sunrise/sunset times wrong) over the DST change, I ran upgrade packages. I started on _4 and am still on _4 after the upgrade. It is very possible I am doing something wrong, but I did not observe any unexpected problems.

Same here. I am assuming this is fixed in most recent update 5.7.0-5. Unfortunately, I was on -4.

I use hue and twinkly. Integration with hue seems rock solid to me. Twinkly works reliably, but options are limited to OFF and ON (no color or brightness options). i use a couple of other brands, but without ISY integration. For those, I power through insteon or zwave so that I can at least turn them on and off) having confirmed that the various settings persist when power is disrupted, and changing settings via the little included remote. One such brand is ecosmart fro home depot and another is from batteries plus (brand I cannot remember).

To the advise by dbwarner5, I add that having Alexa turn the program ON will run the THEN path of the program, and OFF will run the ELSE path.

It is near certainly doable, but the wiring method would depend on the original, whether there is currently a neutral at the switch box. If not, you will need to adjust the wires at the fixture box.

Just upgraded to 5.7.0. Upon quick and early inspection, I don't see any programs that were marked disabled that were not supposed to be. On the other hand, like the others, I have an error message in the launcher "Not Found" but this was happening before the upgrade. Also I see two instances of "My Lighting": one with the 192.168.... address and one with the polisy.local address. Selecting either one seems to work. Neither the error message nor the dual instances of the IoX seem to be a functional problem, as near as I can tell. Now...off to upgrade to PGX

I don't suppose that the name in the program list has a little green arrow? Is it possible that you made changes to the program but did not save them? I agree, this program should work, and not turn on the lights outside the stated time range.

I think you have a logic (boolean hierarchy) problem in your program. Try (same approach for both programs): If ( ‘Hallways / Hall-Up Sensor / Hall-Up.1 Motion’ is switched On Or ‘Hallways / Hall Entry Sensor / Entry.1 Motion’ is switched On ) and From Sunrise To Sunset (same day) Then Set ‘Hallways / Hall Lights Day’ on Wait 35 seconds Set ‘Hallways / Hall Lights Day’ off Else -No Actions

Upon further review, I think your point is correct. “Control on” would not trigger the program from the reciept of an OFF command.

I also recall a time when a setting (trigger reverse?) on the iolinc could result in the overnight query triggering a garage door.

I suspect the problem is that when the motion sensor turns off, it triggers your program and runs the ELSE path. Unfortunately, it likely does so while the program is in the WAIT state, interrupting the program, and the 30 minutes never gets to pass. Make sure your motion sensor is configured only to send ON commands.

Are there any unusual LED indications on the front of the polisy?

I have both running. I don't remember any special tricks.

As far as I know, there are no colour changing bulbs that work "natively" with the ISY. Having said this, one could control hue bulbs with the ISY using the network module. Doing so required a bit more effort, but was not too bad once you get through the learning curve. Unfortunately, I am not sure one can add the network module anymore if the ISY is no longer supported.

I suspect the problem with adding fanlinc as a fan-category is that this approach does not keep other devices that are in scenes with the fanlinc (keypadlincs, for example) synced up. I would wager that this is the problem mrbill is trying to solve with programs.

Ever since upgrading to IoX5.6.0 and PG3 3.1.20, I get a regular occurrence that the PG3 becomes disconnected from the ISY. Power cycling temporarily solves the problem, but it returns the next day. I have initiated a ticket with UDI.

JTsao, did you ever find a solution? I recently upgraded to 5.6.0 (and PG3 version 3.1.20) and PG3 was disconnected from the ISY...PG3 could not find the ISY. I individually rebooted (software reboot) IoX and PG3, with no benefit. I power cycled the whole unit (Polisy, in my case) and this fixed it, only to have the problem return a couple of days later. I don't know if this is going to be a recurring theme or not.

If you are interested in node servers to integrate addition device types into your system, upgrading to the EISY is probably worthwhile. I am also a bit of a fan of upgrading on your own schedule, rather than waiting for a failure of the old ISY and suddenly having an "emergency" situation. On the other hand, the polyglot/node servers and ISY (or is it IoX?) is a bit more complicated and finicky from my experience. If you fear that the ISY has gotten beyond your abilities or interest, the EISY will not make things any easier.

Last I checked, the ISY IP address could be identified via admin console: Help>About. Also, since you mentioned the launcher, the current version of the launcher shows the IP address. I do not recall which launcher works with your ISY software version, however.

No, most certainly.

I don't recall with great confidence, but I can tell you I got them at Lowe's and they were likely the GE brand that they used to carry.

In retrospect, my migration (to polisy, not easy) went mostly well, though it was a bit of work. The only problem I continue to have is that z-wave motion and door sensor no longer work in my system. I had to replace them with Insteon.