mink

I trying to add an Ecolink Z-Wave Plus Rare Earth Magnets Door & Window Sensor, White & Brown (DWZWAVE2.5-ECO). The ISY 994i IR/Pro 5.2.0 with the new 500 Zwave is a SECONDARY Controller A Honeywell/Ademco TUXWIFI Zwave 6280i zwave Keypad is the PRIMARY controller wjith a Honeywell Zwave Thermostat. The only way this seemed to work was to remove the ISY from the TUXWIFI's network, learn. Then add the Sensor to the TUXWIFI (actually, the sensor could be already added to the TUXWIFI). Then add the ISY back as a SECONDARY controller, LEARN and then synchronize the nodes. Rather scary, but the previously added Thermostat nodes all came back. Unfortunately it seemed the sensor status would not update and then a "cannot communicate with device error". This showed the green 0101 but, but now just RED exclamation points. I tried adding the Ecolink Window sensor directly to the ISY when it was not associated with the TUXWIFI , but that did not work either. any ideas anyone? Thanks ZW 009 Notify Sensor Error 0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 Mon 2020/09/07 01:04:44 AM System Log ZW 009 Notify Sensor Mon 2020/09/07 01:04:44 AM System -2 Sync Full ZWave All Mon 2020/09/07 01:06:37 AM System Log Get NodeDef ZWave ZW001_1 Mon 2020/09/07 01:07:42 AM System Log Get NodeDef ZWave ZW001_111 Mon 2020/09/07 01:07:42 AM System Log

@bpwwer Thank you kindly. Yes, been thinking of this also, once the Admin Console bugs get sorted out, and I'm up to 5.2 firmware. Stopped the fan and shut the windows last night due to smoke. I wish I could access zone status of the Ademco/Honeywell TUXWIFI. Even though it is the primary Zwave controller (ISY is secondary), it did not get anything out of it. Do you know if there is a Polyglot node for it, or how would I check to see, not having that yet installed. Likely things will change with the 500Z-wave board and 5.2. <G> Marking time until then mainly now. I've been looking into rigging a 4 or 5 inch wide Merv 10+ furnace filter outside one of the windows, in a plenum to use during bad nights. our furnace uses the 20 x 25 x 6" size anyway. In fact, our under porch, dining room window would take two of these stacked vertically. But, WAF would not be there<G>. Another window is available for that, on the side out of view, but that one is roof rat time.:( ---> Which weather station are you using? I've thought of that route too for the temp data, and just why not. Used to have one but the anemometer cups and van are busted, and it isn't connectable. ---> Temp sensor recommendations? cheers

In case anyone interested this mostly works. Perhaps this post should be elsewhere. I apologize if this should have been split up and if this has been beaten to death in prior posts (tried looking, however). This is a continuation of an earlier post.detailing integrating a Honeywell Thermostat/Alarm system into the ISY. Our coastal climate has fairly cool nights, even on very hot days, allowing for night cooling for the last 2 decades. Up until recently we would just run the fan most off the night, wasting electricity and actually over chilling the house. On days we slept in, the fan might start blowing hotter morning air in. We live in a canyon and solar panels shade the hotter portions of the roof (really helped, actually) so with double paned windows, a cold house coasts most of the day, even on when it is fairly hot. Normally by the time it begins to get uncomfortable, the cool coastal air has made it over the mountains. Once the Honeywell Zwave system got learned into the ISY994i , the Honeywell Thermostat became available see the earlier post, and a better way is now possible. I used variables for this, but am not very good at ISY programming, so this likely could have been done better with using the programs as the variables, but it was a long time since I've touched anything in ISY land.<G> I'm also fighting the ISY994i IR/Pro as it won't let me delete or rename any of the existing devices. Open ticket on that with ISY. Hope that upgrading the Z-wave board to 500 (on the way), and firmware from 5.1.0 RC2 to 5.2 will help. Notes The whole house fan is a fairly powerful two speed, pull chain type, in the central hallway of a 2,500 sq ft house that is in the attic space access hatch, on a counter weighted piano hinge. A 8-KPL secondary ON button is part of a standard 3-way for manual control. It is not a good idea to run this fan without a window open, especially if ever the furnace got turned on, or during cooking, so an open window check gets run. (Eventualy) Closing the monitored window will shutoff the fan in both FAN auto and ON modes. Need a wireless window sensor. For testing, an old IOLinc dry contact is sitting on my desk. Variables have INIT values so on power fail recovery the fan is shutdown. This might be a case for sticking with variables, but likely possible with program as variable approach too. I just felt more comfortable with variables, but one should move to the best practices. Eventually, once the above issues sorted might try to setup graceful power fail recovery. Need an outdoor temperature sensor to monitor night temp. Right now the we make the choice to run with a KPL button that indicates FAN auto status. With outdoor temperature, the program could calculate the HouseTempGoal. Eventually I will likely either buy a Polysis or run Polyglot on one of the RPi4s 4G currently running. (Might even get a third RPI4 to segregate function and have more redundancy, especially with native boot from SSD now. They already run off USB/SSD with the SDcards just being boot loaders.) With eventually getting weather data, may also factor in predicted low and high, which is part of the manual setting of the night target temp now. Having outdoor air temp local CURRENT, temperature, though is better. Hotter places will need to adjust the iThStat.HouseTemp.Fire value. It is a good idea to have an upper limit for auto house fans, no 'fanning the flames'. The CZU fire isn't all that far away right now, and I'm considering a temporary furnace filter in on of the windows, but so far, our nights have seen the smoke reduce enough. In the morning, after closing all the windows, air filters clean up the air well. In 20+ years we've not needed AC. Solar panels helped by shading the sun facing roof/attic, as did an attic ventilator fan (used to be controlled by the ISY for season on/off, may add back)! --> Any recommendations for indoor window sensor and outdoor thermometer (under porch is actually quite protected), probably Z-wave? Aotec, Zooz and inovelli seem popular but some scary reviews are out there so hard to know. --- Core control program, events like closing a window, time change trigger evaluation: NightCoolFanOn-Control - [ID 000E][Parent 0014] If ( $sWindow.Open is 1 And $sThStat.HouseTemp > $sHouseTemp.Goal And $sThStat.HouseTemp < $iThStat.HouseTemp.FIRE And $sNightCoolTime.Yes is 1 And $sFAN.House.Mode.Auto >= 1 ) Then Set 'Scenes.Button / EntryKpd / EntryKpdLtOn.H.FanRelay.Contr' Fast On Wait 4 seconds Set 'LTinside.Scenes / House.FanRelay.Contr' Fast On Wait 4 seconds Set 'LTinside.Scenes / House.FanRelay.Contr' Fast On Else Set 'Scenes.Button / EntryKpd / EntryKpdLtOn.H.FanRelay.Contr' Fast Off Wait 4 seconds Set 'LTinside.Scenes / House.FanRelay.Contr' Fast Off Wait 4 seconds Set 'LTinside.Scenes / House.FanRelay.Contr' Fast Off --- Polling the Honeywell YTH8320 ZW1007/U Z-Wave Thermostat. I tried 15 minutes but for some nights, 10 was better. If 10 min is too often, 15 min is ok. GetThStatData - [ID 000C][Parent 0014] If From 12:00:00AM For 24 hours Then Repeat Every 10 minutes $iThStat.HouseTemp.Prior = $sThStat.HouseTemp Set 'ZW 002 Thermostat' Query Wait 2 minutes $sThStat.HouseTemp = 'ZW 002 Thermostat' Temperature °F $sThStat.HeatSetPt = 'ZW 002 Thermostat' Heat Setpoint °F $sThStat.Mode = 'ZW 002 Thermostat' Mode $sThStat.FanMode = 'ZW 002 Thermostat' Fan Mode $sThStat.FanModeOveride = 'ZW 002 Thermostat' Fan Mode Override $sThStat.FanState = 'ZW 002 Thermostat' Fan State $sThStat.HeatCoolState = 'ZW 002 Thermostat' Heat/Cool State $sThStat.Responding = 'ZW 002 Thermostat' Responding Else - No Actions - (To add one, press 'Action') --- NightCoolSetFanMode - [ID 0012][Parent 0014][Run At Startup] If 'EntryKpd.G' is switched On Or 'EntryKpd.G' is switched Fast On Then $sFAN.House.Mode.Auto = 1 Run Program 'NightCoolFanOn-Control' (Then Path) Else $sFAN.House.Mode.Auto = 0 Run Program 'NightCoolFanOn-Control' (Else Path) --- This could get the outdoor temperature initially, ie only cool if outdoor temp lower than indoor temp by a certain delta. With a fanlinc, https://www.amazon.com/Insteon-2475F-FanLinc-Dual-Band-Controller/dp/B00715SU4A increasing the speed for a smaller delta might be good. I've thought of putting a fanlinc in a J-box, wired to the Hot wire and leaving the House fan in HIGH. Not sure if that migh burn out the motor though. Frankly. On hot days, cycling on/off on high was fine, and on less hot days, there would be shorter cycles. We actually turn Auto off in the morning, and turn on at night when it gets cool as we open the windows for now. This routine then really just stops the fan in the morning. Another way, until outside temp data is available would be to track rising house temperature, The there is a prior house temp variable for this, that stores that previous value from the thermostat. In the morning, we don't want the fan blowing hot air into the house, but we usually don't have that type of climate being close to the coast. NightCoolTimeSet - [ID 0003][Parent 0014][Run At Startup] If From Sunrise + 10 minutes To Sunset + 20 minutes (same day) Then $sNightCoolTime.Yes = 0 Else $sNightCoolTime.Yes = 1 Sets State variables to indicate call for night cooling --- WindowIsOpen - [ID 000B][Parent 0014][Run At Startup] If 'House.Devices / 17.77.11-Sensor' is not switched Off And 'House.Devices / 17.77.11-Sensor' is switched On Then $sWindow.Open = 1 Else $sWindow.Open = 0 Wait 5 seconds Set 'LTinside.Scenes / HouseFan.Relay.On' Fast Off --- I don't think being used for this version, but might be useful in future. I think the button 'IF' is incorrect, need to look at it more. NightCoolFanManual-Trigger - [ID 0002][Parent 0014] If 'EntryKpd.H' is switched Off And $sFAN.House.Mode.Auto >= 1 Then $sFAN.House.Mode.ManualOn = 1 Else $sFAN.House.Mode.ManualOn = 0 --- Yes, well, no kidding, shutdown everything, we might be on fire. Hmm, the are variables set last to avoid trigger the fan control program, likely best to just stop it first? NightCoolFanFire-Action - [ID 0009][Parent 0014][Run At Startup] If $sThStat.HouseTemp > $iThStat.HouseTemp.FIRE Then Set 'House.Devices / YardLightTransformerRelay' Fast Off Wait 3 seconds Set 'Scenes.Button / EntryKpd / EntryKpdLtOn.H.FanRelay.Contr' Fast Off Wait 3 seconds Set 'House.Devices / YardLightTransformerRelay' Fast Off $sFAN.House.Mode.ManualOn = 0 $sFAN.House.Mode.Auto = 0 $sNightCoolTime.Yes = 0 Else - No Actions - (To add one, press 'Action') Here is the Scene for the House.Fan.Realy [sorry, I can't rename the device right now, it used to control a mag transformer for the yard lights. Also the GrowLtHtrPadRelay is for testing at night when wife is sleeping - no seedling starts needed right now] Here is the Scene definitions for the Entry area 8KPL with [Button G] FAN for Auto [Button H] ON for Manual control Finally the standard 3 way Scene: I wonder if this is really needed, but things seem to be working so well. Here is the State.variable table. I'm sure there is room for much improvement, but this is a starting point. cheers and stay safe.

About the RainMachines While this is an old thread, in case someone lands here. I recently found a setting checkbox for increasing watering during heatwaves, doh! In addition to (from the manual) This can be changed to allow more watering on hot days, so go through all the settings for the zones carefully, after updating the firmware.

I've had a RainMachine HD-12 that might have been during their kickstarter (if they had one, yeah that long ago). Recommend, highly with everyone else. The HD display is very useful with high WAF. Check with your water company; ours offers $125 rebate for connected, smart water saving controllers on their list. Thinking of getting a new on, since the rebate is available, the company is offering early adopters a nice discount, and mine is ancient now (would keep as a back up). The new versions offer backup of settings, reporting from multiple weather sites. I use NOAA mainly, but every now and then, NOAA goes off line for a few days and the RM runs off the forcast, rather than the daily 4/day updates. They have been great about reconnecting to NOAA, so this has been quite rare. Make sure to check over the full manual and enable increased watering during heatwaves! People answer the phones at their tech support. The NOAA/RainMachine setup offers very granular data using your address. Useful in areas like ours with microclimates. (I've no financial relation with the co, just like it, as do my plants). So, for those using Polyglot to access the RainMachine, what kind of data can you get off it? BTW, I have 4 EZFLORAs kicking around, two are solid, 2 I need to test to ensure full function. Actually, I would test them all before sending along. Any offers? Cheers

ISY Control of Whole House fan, polling Zwave Thermostat with safety checks and Manual / Auto switching In case anyone interested this mostly works. Perhaps this post should be elsewhere [I posted an edited version in Questions & Answers - will let Mod decide if this post should remain for continuity or be deleted] . I apologize if this should have been split up and if this has been beaten to death in prior posts (looked, however). This was a continuation of the earlier post. I used variables, but am not very good at ISY programming, so this likely could have been done better with using the programs as the variables, but it was a long time since I've touched anything in ISY land.<G> I'm also fighting the ISY994i IR/Pro as it won't let me delete or rename any of the existing devices. Open ticket on that. Hope that upgrading the Z-wave board to 500 (on the way), and firmware from 5.1 RC2 to 5.2 will help. Notes The whole house fan is a fairly powerful two speed, pull chain type, in the central hallway of a 2,500 sq ft house that is in the attic space access hatch, on a counter weighted piano hinge. A 8-KPL secondary ON button is part of a standard 3-way for manual control. It is not a good idea to run this fan without a window open, especially if ever the furnace got turned on, or during cooking, so an open window check gets run. (Eventualy) Closing the monitored window will shutoff the fan in both FAN auto and ON modes. Need a wireless window sensor. For testing, an old IOLinc dry contact is sitting on my desk. Variables have INIT values so on power fail recovery the fan is shutdown. This might be a case for sticking with variables, but likely possible with program as variable approach too. I just felt more comfortable with variables, but one should move to the best practices. Eventually, once the above issues sorted might try to setup graceful power fail recovery. Need an outdoor temperature sensor to monitor night temp. Right now the we make the choice to run with a KPL button that indicates FAN auto status. With outdoor temperature, the program could calculate the HouseTempGoal. Eventually I will likely either buy a Polysis or run Polyglot on one of the RPi4s 4G currently running. (Might even get a third RPI4 to segregate function and have more redundancy, especially with native boot from SSD now. They already run off USB/SSD with the SDcards just being boot loaders.) With eventually getting weather data, may also factor in predicted low and high, which is part of the manual setting of the night target temp now. Having outdoor air temp local CURRENT, temperature, though is better. Hotter places will need to adjust the iThStat.HouseTemp.Fire value. It is a good idea to have an upper limit for auto house fans, no 'fanning the flames'. The CZU fire isn't all that far away right now, and I'm considering a temporary furnace filter in on of the windows, but so far, our nights have seen the smoke reduce enough. In the morning, after closing all the windows, air filters clean up the air well. In 20+ years we've not needed AC. Solar panels helped by shading the sun facing roof/attic, as did an attic ventilator fan (used to be controlled by the ISY for season on/off, may add back)! --> Any recommendations for indoor window sensor and outdoor thermometer (under porch is actually quite protected), probably Z-wave? Aotec, Zooz and inovelli seem popular but some scary reviews are out there so hard to know. --- Core control program, events like closing a window, time change trigger evaluation: NightCoolFanOn-Control - [ID 000E][Parent 0014] If ( $sWindow.Open is 1 And $sThStat.HouseTemp > $sHouseTemp.Goal And $sThStat.HouseTemp < $iThStat.HouseTemp.FIRE And $sNightCoolTime.Yes is 1 And $sFAN.House.Mode.Auto >= 1 ) Then Set 'Scenes.Button / EntryKpd / EntryKpdLtOn.H.FanRelay.Contr' Fast On Wait 4 seconds Set 'LTinside.Scenes / House.FanRelay.Contr' Fast On Wait 4 seconds Set 'LTinside.Scenes / House.FanRelay.Contr' Fast On Else Set 'Scenes.Button / EntryKpd / EntryKpdLtOn.H.FanRelay.Contr' Fast Off Wait 4 seconds Set 'LTinside.Scenes / House.FanRelay.Contr' Fast Off Wait 4 seconds Set 'LTinside.Scenes / House.FanRelay.Contr' Fast Off --- Polling the Honeywell YTH8320 ZW1007/U Z-Wave Thermostat. I tried 15 minutes but for some nights, 10 was better. I 10 is too often, 15 is ok. GetThStatData - [ID 000C][Parent 0014] If From 12:00:00AM For 24 hours Then Repeat Every 10 minutes $iThStat.HouseTemp.Prior = $sThStat.HouseTemp Set 'ZW 002 Thermostat' Query Wait 2 minutes $sThStat.HouseTemp = 'ZW 002 Thermostat' Temperature °F $sThStat.HeatSetPt = 'ZW 002 Thermostat' Heat Setpoint °F $sThStat.Mode = 'ZW 002 Thermostat' Mode $sThStat.FanMode = 'ZW 002 Thermostat' Fan Mode $sThStat.FanModeOveride = 'ZW 002 Thermostat' Fan Mode Override $sThStat.FanState = 'ZW 002 Thermostat' Fan State $sThStat.HeatCoolState = 'ZW 002 Thermostat' Heat/Cool State $sThStat.Responding = 'ZW 002 Thermostat' Responding Else - No Actions - (To add one, press 'Action') --- NightCoolSetFanMode - [ID 0012][Parent 0014][Run At Startup] If 'EntryKpd.G' is switched On Or 'EntryKpd.G' is switched Fast On Then $sFAN.House.Mode.Auto = 1 Run Program 'NightCoolFanOn-Control' (Then Path) Else $sFAN.House.Mode.Auto = 0 Run Program 'NightCoolFanOn-Control' (Else Path) --- This could get the outdoor temperature initially, ie only cool if outdoor temp lower than indoor temp by a certain delta. With a fanlinc, https://www.amazon.com/Insteon-2475F-FanLinc-Dual-Band-Controller/dp/B00715SU4A increasing the speed for a smaller delta might be good. I've thought of putting a fanlinc in a J-box, wired to the Hot wire and leaving the House fan in HIGH. Not sure if that migh burn out the motor though. Frankly. On hot days, cycling on/off on high was fine, and on less hot days, there would be shorter cycles. NightCoolTimeSet - [ID 0003][Parent 0014][Run At Startup] If From Sunrise + 10 minutes To Sunset + 20 minutes (same day) Then $sNightCoolTime.Yes = 0 Else $sNightCoolTime.Yes = 1 Sets variables iDaylight and sDaylight to '1' if between Sunrise and Sunset, '0' otherwise --- WindowIsOpen - [ID 000B][Parent 0014][Run At Startup] If 'House.Devices / 17.77.11-Sensor' is not switched Off And 'House.Devices / 17.77.11-Sensor' is switched On Then $sWindow.Open = 1 Else $sWindow.Open = 0 Wait 5 seconds Set 'LTinside.Scenes / HouseFan.Relay.On' Fast Off --- I don't think being used for this version, but might be useful in future. I think the button 'IF' is incorrect, need to look at it more. NightCoolFanManual-Trigger - [ID 0002][Parent 0014] If 'EntryKpd.H' is switched Off And $sFAN.House.Mode.Auto >= 1 Then $sFAN.House.Mode.ManualOn = 1 Else $sFAN.House.Mode.ManualOn = 0 --- Yes, well, no kidding, shutdown everything, we might be on fire. Hmm, the are variables set last to avoid trigger the fan control program, likely best to just stop it first? NightCoolFanFire-Action - [ID 0009][Parent 0014][Run At Startup] If $sThStat.HouseTemp > $iThStat.HouseTemp.FIRE Then Set 'House.Devices / YardLightTransformerRelay' Fast Off Wait 3 seconds Set 'Scenes.Button / EntryKpd / EntryKpdLtOn.H.FanRelay.Contr' Fast Off Wait 3 seconds Set 'House.Devices / YardLightTransformerRelay' Fast Off $sFAN.House.Mode.ManualOn = 0 $sFAN.House.Mode.Auto = 0 $sNightCoolTime.Yes = 0 Else - No Actions - (To add one, press 'Action') Here is the Scene for the House.Fan.Realy [sorry, I can't rename the device right now, it used to control a mag transformer for the yard lights. Also the GrowLtHtrPadRelay is for testing at night when wife is sleeping - no seedling starts needed right now] Here is the Scene definitions for the Entry area 8KPL with [Button G] FAN for Auto [Button H] ON for Manual control Finally the standard 3 way Scene: I wonder if this is really needed, but things seem to be working so well. Here is the State.variable table. I'm sure there is room for much improvement, but this is a starting point. cheers and stay safe.

@lilyoyo1 Thank you kindly, it appears I'm not using them anyway, but yes, no wish to do anything outside of the ISY! So, much progress to report: The Isy994i is now a secondary controller to the TUXWIFI Z-Wave AlarmKeypad network with access to house temperatures. Interestingly the Thermostat appears as both a controller and a responder. This is what I had to do: First I followed this from the "Automation Cookbook" and other instructions (The TUXWIFI Primary Controller was already in Z-Wave add mode, listening): Several tries resulted in seeming hangs, so I exited back. However the Z-Wave Menu changed to having a Learn Mode: The Z-Wave | Learn Mode menu item had to be clicked, which caused enrollment activity and several nodes appeared (yea). This is all with the 300 Z-Wave board and an External antenna. So now to figure out how to use these to control the whole house fan by house temp. I also need to monitor a window so that the fan is not turned on without an open window. I had hoped to access Alarm system contact status (but doubted it would be available). I found an I/O linc in the Insteon parts box so can run a pair into the alarm box and connect it in parallel to a window dry contact magnetic reed sensor. It works on my desk, just to hook it up now. Looks like a program is needed for this, as too much for a scene. Cheers and thanks.

CraigB Thanks Soo much for the quick reply! My first post got deleted, so here we go again. Believe am running current UI using latest method to ensure that, Great, do have to re-enable the Networking module as it got disabled with the upgrade. Thanks, "DUSK" program looks great. How do you handle ISY power failures and resets for the program setting $Away_state? We get power outages now lasting many hours such that even my UPS on the data closet dies. We don't like to run the gas generator while we sleep. I tried that. Nothing happens with clicking it. Perhaps the KPL needs to be deleted and re-added or it is in the wrong mode so it can't have Buttons Grouping. The setup is very old. Before I muck it up and find out nothing changes, I'll see if I have a spare KPL to add fresh. This might have been 6 button that I redid to an 8, so maybe that is the problem. I wanted the top pair of button to be one MASTER ON/OFF and the remaining 7 be individual scenes that toggle ON/OFF. Perhaps that is impossible. Our 1960s house is flex aluminum so adding circuits for separate controls was not possible - many KPLs and inLineLincs. They have a pull down with a slew of different versions to pick which confused me. I should likely shoot a question to support about that. Since my OP, what I have is the ISY994i IR/PRO with the 300 ZWave Board added and an external antenna. All my Zwave are several years old, so upgrading the board to the 500 (which may not even be available) may not make sense even since it seems the ISY994i is approaching EOL anyway. Great, sounds like the way to go. I've been confused about which should be primary vs secondary and this seems to make the most sense. Ideally, I'd like to get Alarm zone status into the ISY from the VISTA20p Alarm panel, but doubt that will be possible. It has the 9.12 PROM chip with TC2.0 and internet so we get status updates with a nice UI. In a perfect world the ISY would check for open windows, low outdoor temp, high indoor temp and turn on the whole house fan, provided the fire detectors have not tripped <G>. (So perhaps a ISY detector as well - more likely shut off if house temperature above 105 as that just doesn't happen here normally?) Somehow I don't think that is possible without adding either a Zwave or Insteon window sensor just for the ISY as a proxy for having opened up the windows for whole house fan. Unfortunately, the fan is controlled now by a two speed pull chain. It would have to be left in one speed for the ISY unless the pull chain switch it subbed out - not really something I wish to do. The current setup leaves a nice manual backup in case of hardware failure. Again thank you kindly Cheeers

Hi there, hope you all are well. Mostly successful upgrade from 4.7.3 to 5.1.0 RC2. I know that this was not recommended, having an older Zwave (board added to 994IR Pro in 12/2013) but 5.0.16C would not see the Zwave ext antenna or board. I'm using the newer UI and that was a specific fix for this release. The motive for digging back in to the ISY is getting an attic fan, whole house fan, Honeywell YTH8320 ZW1007/U Z-Wave Thermostat and HoneyWell Ademco TuxwifiW Z-Wave 6280i Graphic alarm keypad all integrated. Now the 6280 controls the thermostat via ZWave based on Alarm status. I'd like the ISY to get temp data from the thermostat as well as outside temps as we use the fans for night cooling without an air conditioner. With the loss of the climate module I don't see any sunrise/sunset or weather data fields anymore. The heat waves have made this a pressing issue. Fortunately, irrigation has been handled by a RainMachine HD12 for the last 6 years, so the deprecation of weather/climate did not affect that. After much reading on this forum it seems a good solution will be running Polyglot on one of the RPi4s with a weather node and this Polyglot Cloud Intro - YouTube seems like a good place to start. The Polisy seems quite nice, but redundant with a two running RPi4s, especially one already running off a 1TB SSD (its a music server, the other is a pihole). Respectfully, some questions: - Through trial and error, it seems the ISY994i IR/Pro needs the Non OADR firmware, is this correct? I got an error "update failed written size invalid" with the OADR firmware, but the regular completed fine. Oddly, the reverse happened with 5.0.16C. The external Zwave antenna is recognized and the board seems to show as a Zwave device. The OADR 5.0.16C firmware listed the bootloader as 0.00! - When registering the ISY994i on the new UDI product portal, what is the version for this box since it was assembled over time with the addition of the ZWave board (21100 circa 12/13)? It's not clear from my ordering receipts. - Perhaps the RainMachine Node can pull/push weather data, making a second weather node redundant? - Do I need to purchase a subscription Polyglot? Is there a better way for weather data? - Anyone know how to get the Honeywell keypad and thermostat to be seen by the ISY994i? I believe the Honeywell alarm keypad (6280i) is the Primary ZWave controller for the thermostat. Besides the ISY, these are the only ZWaves. Perhaps the ZWave board is bad but with the ISY994i approaching EOL is replacing it really viable? I think so far, but once things are working there may be more. They are all withing 5 feet of each other, separated by one or two sheetrock walls. The ISY sits in a data closet, hardwired into the main network switch, the alarm pad on the other side of the wall and the thermostat a coat closet away. Internet is gigabit copper with gigabit fiber WAN. - I try to answer my own questions and indeed got through most of the update issues for 4.7.3 -> 5.0.16C -> 5.1.0 but having kicked around with ISY since the 99, It's hard to know what procedures have become deprecated, especially with such a major release as 5x. Is this still a good reference for V5: The ISY994 Home Automation Cookbook pdf ? My Keypad lincs don't have the group screens like it shows, but perhaps they need to be deleted and re added. Fortunately, the network isn't really all that large at this point. - And now a really dumb question, could someone point to the current way to turn something on and off based on sunrise, sunset times by scenes and programs? If I should split this up with tickets. please advise me so. Thanks in advance. Be safe out there, wear a mask, the life you save might be someone you love (retired Family MD/MBOC consultant)!

First Alert is selling through Lowes two Zwave smoke detectors: (Lowes calls Zwave IRIS) ZSMOKE for smoke and ZCOMBO (smoke+CO) detectors. Anyone using these with the ISY994i? My research indicates these are fully zwave compliant and should work. I have a Honeywell Tuxwifi Keypad as a Primary Zwave linked to a Honeywell zwave thermostat and my Vista20p Panel. The Tuxwifi adjusts the thermostat based on the alarm state. I have the Zwave module for the Isy994i with and external antenna but have yet to try and integrate them. I assume too that adding several of these would improve the zwave mesh. Concerning the TUXwifi and the ISY994i playing nicley, any recommendations, gotchas etc about which should be the primary controller and which should be the secondary? The ISY has far more scenes available, so does than mean it should be the primary since the The Tuxwifi only has 8? Or can I leave the Tuxwifi controlling the thermostat mostly, and do some additional setting from the ISY? I have the TUXwifi set up so I can use it to control the alarm panel and thermostat via my Android phone both from inside my house, and from away. The TUXwifi has a great display and can show and send camera shots, but I haven't messed with that yet. I do like the TUXwifi adjusting the house temp based on alarm state since that would work even if the ISY dropped offline. I need to replace some stand alone smoke detectors that have aged out. Adding some ZSMOKEs and/or ZCOMBOS detectors would allow me to replace the old detectors and integrate all my smoke detection into the home control. I'm still using the Honeywell Total Connect service for text status reports, but could drop that once I've integrated everything into the ISY. The ZSMOKE and ZCOMBO are quite reasonable in price, especially since no insteon bridge would be needed and they are much cheaper than the Onelink units which would need the bridge. Thanks for any help. If no one comments I may just give one a go figuring the UDI folks will get them working shortly anyway.

This is an exciting thread and I look forward to the enhanced sophistication of irrigation in the ISY/EZFlora system. We have just completed a major landscaping project in our backyard. 7 of our zones are newly planted and need daily watering to establish while 3 of our front zones are established and need less frequent watering. Will there be a way to incorporate this type of zone specific parameters in the new version or will it be best to have a different set of programs in different folders to handle newly planted zones? Thanks to all for the work on this! cheers

Upon reflection, it seems to me that as long as the programstatements in the loop do not involve conditions requiring interaction from devices, but rather work with variables and programs which also are mainly internal to the ISY, the latencies and load from even a fair number of such programs should be low. After all the ISY is a 200mHz processor. In the above example the only device interaction will be when the loop count completes and a valve and perhaps a kpl light gets turned on or off, every 10-30 minutes. Am I understanding things right? thus if one codes to use minimal device status or queries, but use variables and program status for logic, and mainly use the powerline to generate actual control commands there should not be much traffic on the powerline. TIA

thanks guys, the short program does show how powerful the state variable implementation can be! Now on to coding the rest of it! cheers

oberkc yes, separate buttons would be nice, but I'm likely to end up with over 9 irrigation zones, spread over two 7 button kpl which also have to control some lights. I would like to give a button to each zone that would provide manual coontrol and be on if zone is running (but not use flash for that). Also it would be less confusing to my wife to have a flash as a status indicator for the button assigned as a master controller, rather than simply on. I was not planning on every few seconds, but more like once every 10, and only for an exception state. thanks

kingwr, Thanks for thinking through the issues, but fear not, the actual design WAIT will NOT be one SECOND, but MINUTE. I did say that in the post. I watched it run, and it incremented pretty accurately for the 20 second test period several times as I reset the counter. My intent is to eventually control an irrigation valve by setting a variable on a web page, so the units will be minutes and a minute or two extra will not be a crime. Since the repeats would likely be between 5 and 30 at most, a few seconds lag per loop would not be important. I'd be interest in seeing a way that minimizes load and lag and put this up to help move the thread forward. I also suspect at a minute interval, the overhead should not be excessive as only one valve will be running at a time. If you think a minute interval is still too much, than 2 or even 5 minute intervals would likely be enough granularity of control, but seems to me a minute should be fine. After all, since state variables are intended to trigger programs, should not using them that way be better than have a larger number of programs checking state via if statements and integer variables? I would love to see what Michael say about this approach, since many people have wanted variable control of wait or repeat loops. This seems to work fairly well, with the warning to keep the interval above a point to avoid lag and overhead, until he gets Wait/Repeat Variable ability programmed in. It also would be easily converted to the WAIT/VARIABLE construct when that became available. Thanks for your answer and exploring these issues carefully is why I posted and a great feature of the forum! cheers