MrBill

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..

It's running but not as expected for the suite of programs that you're trying to replicate. Honestly I scrolled thru that article when you linked it in another thread a few days ago... it's good, and it's advanced. You should start with beginner stuff tho.... You've moved straight to the Diamond slopes without going to Ski School. Start with some more basic programs and learn how the ISY Programming language works.. then build on that until you reach this advanced state that you're trying to replicate and not having luck with because you don't understand what it's doing, or for that matter what it means when a program "runs".

It's Variable. Note that you need to have a line in the IF block selected. Variable if a line in the THEN or ELSE block is selected will be differnt. The program ran indeed, but if this is your Then block: it didn't actually do anything.

I've been watching for another "button"... I do like hidden buttons... even more than I like voice control....?

I use Alexa primarily for voice commands too. My counter came with the fact that you were grouping in Alexa, which I suppose if the group only pertains to a voice command is fine. If Alexa's not home then perhaps the group doesn't matter either. I have a complicated method using helper programs that lets me set specific dim levels via alexa and also keeps Scenes/KPL buttons in sync. But Alexa only knows of lights to set, I have a group called Living Room Lamps that in fact is just a helper program in the ISY that gives dimmer values to each of the 3 lamps as if they had been called out individually. Some utilities now offer off peak discounts. That is a case where automation could come into play... but why would having an automation platform be better than the time delay feature on the door of the dishwasher.... A human still needs to decide that it's full enough to need a cycle, they still need to add soap. We haven't reach the point yet that dishwashers are smart enough to know how full they are, and be able to determine how many additional dishes might be coming at the next meal and determine if it's economic to run a cycle at X capacity. Further unlike Rosie from the Jetson's, Alexa won't put the dishes away.... Garage door-wise mine do have a cloud dependency (MyQ) for control. Pre-dating that tho there are other door sensors that are now-redundant but not bad to have, as I can at least be told if/when cloud control failed. I have Zigbee shades with no cloud dependency... but they are also directly connected to HA. Stay tuned tho, local zigbee will be coming to Polisy. In fact I just passed a suggestion for expediting that to the powers that be.... we'll see if it works out. Pi's are hard to come by these days. Check out the Home Assistant Yellow crowd sourced project. It will be a couple months until they are shipped. I ordered Yellow for the built in zigbee (eventually matter) component, and because it's eliminates the Micro SD card by including an NVMe SSD . I already have HA running on a 4gb pi4 (with zigbee via ConBee2 and an add-on), for the upgrade I ordered the "Yellow Kit" and the compute module separately to get the 4GB option. I had the thought yesterday while typing another reply to you, that you would probably enjoy adding HA to your arsenal, it works great alongside ISY/Polisy, the HA Universal Devices Integration works fantastically well.

Add all the lines in order. Then add the Or and And parenthesis from the top down. It is difficult to work with multiple levels of parenthesis in your example, which is one reason i mentioned there is more than one way to skin the cat.