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

Every node and designated variables from ISY appear as HA entities. I started out using HA because I didn't like any of the mobile apps available a couple years ago (UD mobile has changed that landscape since) I started using HA just so I could use it as a front end to the ISY... Since then I've added on the HA side integrations that ISY doesn't yet support (zigbee for example). Phone app tho I use HA for both.

For the ISY994 there should be no port number, for polisy it should be :8080. It's exactly what shows up in ISY Finder window without the /desc on the right end.

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

the 2242 hub supports X10, the 2245 Hub does not. (The PLMs also support X10). The Insteon Integration can not provide X10 support for the 2245 because the hardware does not support it. That's a different issue than the one I was reffering to above. (the one above was the very old one-- perhaps a year now, where the integration couldn't start because HA was timing out too soon.) HA can link two ISY's, I had it set up at one point, but don't at this moment. The May HA release (last Wednesday's) just made IoP auto discovery possible. From the detailed release notes:

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)

It's github's second most active project.

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.

As mentioned they push out a major update on the First Wednesday of every month, then about 6-9 minor releases follow in the same month (April had 7), as I recall March was 9. Most of the time you can load the .0 release and not feel pain, but twice I've been caught in first Wednesday of the month bugs (one involved the ISY integration and it also affected @asbril), so I just wait a week to 10 days after the first Wednesday. Another piece of advice is always check the release note for "breaking changes"... not a single month goes by that I don't see someone ask somewhere...."the HA update broke my ____ I can't figure it out" followed by screenshots and logs... then a reply... "did you read the release notes? that's in breaking changes" or "that's covered in the release notes, it moved from switch. to light. you'll need to manually update automatons" and so on....

Yes they are. I found one on Amazon relatively quickly for my son's house after the Insteon shutdown, but the same "kit" with Pi, basic case, memory card, power supply and other doo-dad's you don't actually need was twice the price I paid for the same 18 months earlier. They are largely out of stock. If it's purpose is for Home Assistant and he doesn't mind waiting til mid-july, check out Home Assistant Yellow. https://www.crowdsupply.com/nabu-casa/home-assistant-yellow the complete first item on the list doesn't ship until end of year, but if you instead buy the Kit and either the 2gb or 4gb Raspberry Pi compute board, you should receive both components in the first half of July. (I'd recommend the 4gb, Home Assistant and all the add-on's become addictive). O ordered to upgrade my HA installation and to support the HA project, the custom board has a zigbee (to be upgradded to Matter) controller built in.

Your quickest solution is to run Home Assistant, it will talk to a hub. I've done this at my son's house, it was pretty easy, but the caveat is I already run HA in my own house and knew how that controller works. If you can find a Pi4, either 2 or 4gb (they are in short supply at the moment) that's the hardware I would recommend, that said there are many other ways to run Home Assistant.... (make sure 'Supervisor" is part of the install tho... that makes keeping the system updated much easier.) https://www.home-assistant.io/getting-started/ For Alexa connectivity you will also need the 6.50/month or $65.00 Nabu Casa subscription, to make Home assistant talk to Alexa in the cloud. It also offers remote connectivity tho, if you or someone else will be helping her maintain Home Assistant.

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,

I've never had problems with Alexa trying to sell me shit. I do frequently make sure "skills" haven't been added without me realizing it. The most annoying thing to us is we play music on the "everywhere group" almost all day everyday and have the volume adjusted perfectly for the music source. The volume for her voice tho is too low to understand unless 1) the music isn't on 2) you're actually near a speaker 3) you're ready to listen. That should work out fine, because for what we user her for 1) Music 2) turning devices on or off 3) kitchen timers and kitchen conversions we don't really need to "listen" to her. BUT.. she has an a habit of saying "By they way, did you know blah blah blah" and i really don't want her to do that. Never ready to listen, don't care if she think I might not know how to use something, etc etc.... What makes Alexa's inexpensive tho is the fact the power to voice process is the cloud, thousands of alexa's can share the same processor power.

I read the HA release notes last night. HA puts out a major update the first Wednesday of every month, and about 6-9 minor releases follow during the month. I've learned not to load the first release of the month, I always wait until about .4 or .5 in a week to 10 days after the first Wednesday. I've been running HA for a couple years now, and twice have gotten caught up in nasty first release of the month bugs, as a result I adopted the "wait-a-week" strategy. mostly what's in the minor releases during the month are fixes to the major release on the first Wednesday. Also always be sure to read the release notes, the HA project is fast moving and you need to watch for new integrations that work for you, and play close attention to the list of breaking changes.

My son adopted Home Assistant with his V2 hub and loves it. His automatons now exceed anything he had the old way... for example, the fireplace now turns on with lights in that room, but only if it's cold outside, before it was just alexa, turn on the fire. It's quite interesting as I've helped him through this, his approach to automations and how he wants it to work is entirely different than the way I do things/like things. Neither of us are wrong, just different. My wife and I like button pushes or switch taps over talking to Alexa, in his house they definitely prefer Alexa only for day to day control. I love having a geofence and the house automatically shutting off etc when we leave, geofences for some reason don't interest him, he just wants to say "Alexa, we're leaving" on the way out. To him it seems the concept of Home Automation begins with the word "alexa".

The only issue that I have with MyQ (and I use it too) is that it has a cloud component. which as we know: Are subject to the internet to your residence not going offline second that the company paying for the server doesn't go away, go into bankruptcy, or just decide to pull the plug. I'm back to wanting as few cloud dependencies as possible after the Insteon debacle which didn't affect me but reminded me that cloud servers not controlled by me are problematic.