MrBill

Did you also do Restore Device after the factory reset? If so, you either have a bad switch, bad PLM (if nothing is working for you) or Powerline noise.

Those programs will only be true very briefly at the exact time that they run, they will show false the other 23 hours 59 minutes and 59 seconds per day. To get the program to show "true" during on times write it with a "From To" If statement. I provided the exact example of that above.

You're kinda of a lone wolf. How did you complete your evaluation and arrive at the conclusion that they are selling garbage? How did you arrive at the conclusion that UDI also thinks it's products are garbage? If your premise is true, how can any user be satisfied? What specifically does "Garbage" mean in this context? You did get one thing correct!! Universal-devices will accept returns and cheerfully fully refund any user that is unsatisfied with their purchase. They also have world class support that doesn't end with warranty. Users can contact the company with support needs anytime for the life of the product (which seems to be many many years based on products prior to polisy).

AAATest.1 - [ID 01DC][Parent 0001] From Sunset To 10:00:00PM (same day) Then Set 'DN Cabana Dining Table#' On Else Set 'DN Cabana Dining Table#' Off For testing purposes you can save the program, then right click the program name in the tree and choose Run Then or Run Else. As others have indicated. if the ISY can't turn the light on or off from the device tree you must solve that problem first, then worry about programs.

Thanks, After you've written a few of these it really doesn't take alot of effort, its just knowing how to use interlocked programs. BTW, I'm not sure why you are needing this program but if you're having trouble with the indoor coil freezing up that's a maintenance issue, largely caused two ways... blocked airflow, or low freon level. Blocked airflow could be return vents that aren't blocked or dirty filters etc. Low Freon is also a possibility that most people want to dismiss as impossible, how could it get too cold if the freon's low? Keep in mind that Freon isn't carrying cold in, it's carrying heat out. When it's low it can't carry heat out fast enough, but the cooled freon is still returning from outdoors. Since it can't take the heat away fast enough the indoor coil freezes.

to add to @kzboray PG3 is the new iteration and is here to stay, and there will be a day coming that PG2 will shut down and be disconnected. Due to PG2's design it uses a lot of resources. and to reiterate, the developers that receive the money paid are not employees of UDI and are not otherwise compensated, they are just users that know how to write python programs that developed the node server.

Right click any program name, and use "Find" to see if the device is used in a program. If it's not, there might be an odd link in the devices memory... in the device tree you could try right clicking the device a choosing "restore device" to have the ISY set the devices links again.

this may still need a tweak or two but here's the logic I think should work Program CoolCycle If 'Upstairs / Master / Upstairs Thermostat status is cool Then Wait 1 hour Run Program CoolCycle_loop (then) Else (none) ----------------------------------------- Program CoolCycle_loop (Disabled) If (nothing) then Disable Program CoolCycle Repeat Every 1 hour Stop Program CoolCycle_loopStopper wait 10 seconds Set 'Upstairs / Master / Upstairs Thermostat - Main' Fan Mode On Set 'Upstairs / Master / Upstairs Thermostat - Main' Mode Off Wait 15 minutes Set 'Upstairs / Master / Upstairs Thermostat - Main' Mode Cool Set 'Upstairs / Master / Upstairs Thermostat - Main' Fan Mode Auto wait 10 seconds Run Program CoolCycle_loopStopper (then) Else - No Actions - (To add one, press 'Action') ------------ Program CoolCycle_loopStopper (Disabled) If (nothing) then Repeat every 1 minute Run Program CheckCoolCycleStatus (if) else (nothing) ---------------------------- Program CheckCoolCycleStatus (Disabled) If 'Upstairs / Master / Upstairs Thermostat status is cool then (nothing) else Stop Program CoolCycle_loop Enable Program CoolCycle Stop CoolCycle_loopStopper ----------------------- Program CoolCycle_startup (disabled) (Run at Startup) If (nothing) then Enable Program CoolCycle Disable CoolCycle_loop Disable Program CoolCycle_loopStopper Disable Program CheckCoolCycleStatus The logic is that CoolCycle watches the thermostat to go to cool. Still unsure if it needs the initial wait of 1 hour, but I think it does, however I didn't run an experiment to find out. Once it gets to the cycle loop it runs another program so that it can disable the first program. (that 1 hour wait should maybe be 45 minutes if you are wanting cycles that last 1 hour each.) Once the loop starts, It doesn't matter on the first run that the program it stops isn't running, the ISY doesn't care. So the equipment cycle occurs and at the end of the 15 minute cycle, it starts a program that checks every minute to see if we need to get out of the loop, once the mode is no longer "cool" the loop is terminated and the first program is again reenabled. All but the first program should be disabled all the time. remember that disabled program still run if another program tells them to run. The last program is optional but ensures programs are enabled/disabled correctly when the ISY starts. Let me know if you have any questions....

I've got an idea.... but I'm out of time this afternoon to think thru all the logic (it will take a couple of programs to work around, but it's do-able) I'll reply again in the morning...

"Heat/Cool State" that shows "Idle" in the screenshot is likely what you want in the IF statement. When it's Cool (or whatever the choice is) is when you want the program to run.

post a screenshot of what the thermostat looks like in the admin console and I might be able to guess....

Granted the word "Firmware" isn't there, which may be the word folks that can't find it are looking for. But the language as presented IS CORRECT as not all the releases included therein are firmware. I suppose it could be updated to say "Current Firmware and Software Release Announcements".

Someone with a 2441TH needs to chime in... I don't own one and i'm not exactly sure what node you should be using with status in the IF statement. I know that you should be using Status, and not control for this application, but I'm not sure about the choices to be used with Status.

I should add the disclaimer, that your original question about how 'Upstairs / Master / Upstairs Thermostat - Cool Ct' node works may still be applicable. I'm guessing, as I don't own a 2441TH.

Correct. "Control" would only see the ON event and not the status change. With "Status" if the status changes to false the THEN block would stop running and the (blank) ELSE block would start running. Let's pretend its a super hot day. The temp in the room rises, the air kicks on, this starts the one hour wait. The hour expires, the remaining parts of the program run.... the Then block is now over... it won't repeat it again. You need a repeat, so that it does this every hour until it's stopped by a change to the Status. If 'Upstairs / Master / Upstairs Thermostat - Cool Ct' is On Then Wait 1 hour Repeat Every 1 hour Set 'Upstairs / Master / Upstairs Thermostat - Main' Mode Off Set 'Upstairs / Master / Upstairs Thermostat - Main' Fan Mode On Wait 15 minutes Set 'Upstairs / Master / Upstairs Thermostat - Main' Mode Cool Set 'Upstairs / Master / Upstairs Thermostat - Main' Fan Mode Auto Else - No Actions - (To add one, press 'Action') I can't decide whether you need the initial wait 1 hour or if the repeat will wait one hour before the first iteration on it's own. (I don't use repeat like this anywhere and the documentation doesn't clear it up, but it's easy to test)

You might want to mention which thermostat you're using. I would assume you would want status in this case, in case the HVAC only runs 45 minutes and the thermostat becomes satisfied. As written this will not stop if the Air cuts itself off during the hour. You also probably want use Repeat in case the thermostat is never satisfied.

There is a thread where a user built a converter using a PiZero as a middleman. But I'd recommend the same as @apostolakisl your best solution is to upgrade to Polisy which will use your USB PLM. Polisy has everything the ISY994 had, plus node servers and works with any of the Insteon PLMs (but not the Insteon hub). Essentially Polisy is the newer upgraded ISY.

That's quite a display! Keep in mind when power cycling these devices that the PLM must be online first. Plug it in and wait 30 seconds before plugging in the ISY. Some people might put a label on the PLM (I saw one in an ebay picture.. haha) that says "Plug in and wait 30 seconds then plug in ISY".

This is incorrect. For 300 series z-wave boards use version 5.0.16C. 300 series boards have a blue LED next to port A and report Z-wave version 4.55.00. As @lilyoyo1 points out, Firmware isn't hard to find. even if you went to the wiki, the links there point you back to the correct place in the forum,

Since I was messing with theme settings I just tried High Contrast again, I might see if I can stick with it. I used to not like this theme, but it does seem easier to read. I think the Fuscia problem is a lot like Cilantro. Many people love Cilantro, but to some it tastes like soap. I think is more difficult for different people, and it definitely hard on the blue background of the default theme.

It's actually fuscia but this is what people call pink: I dislike it also, and can't read it at native font size, but have learned to live with it by increasing the font size to 15. Michel once said in other thread where people were complaining about this specific color that since with the move to polisy we would be moving away from the admin console, this wouldn't get changed. However it appears the admin console is here to stay, so perhaps they should rethink and possible add a high contrast them, or expose the color settings and let users pick there own. This problem effects people differently, I have great up close eyesight but on any of the theme's is difficult for me to read. Another issue with theme settings is they go back to default when you least expect it, which requires changing the theme's and then re-closing the admin console and reopening.

Depends. Are you moving the current PLM over? or do you have another PLM to use with polisy?

Which add method? Start linking or New Insteon Device? Try New Insteon Device... Fill out the address... give it a name... for device type... it's at [7.09] in the list...

Keep in mind.... That program by itself isn't notifying you of anything.. it's just setting a variable to 1 under certain conditions.

I believe the z-wave stick also needs to be properly seated at startup, I'm not sure it will be found if plugged in running..