johnstonf

Nope, my bad... i actually BROKE the lines reporting ok by removing 0's in my lines 2 & 4. So they are back to original, with 0's, and lines 1&3 still not reporting...

I think i answered my own Q2 (Remove 0's in the addresses... will test!)

Another big thanks from me... I have a couple of issues... Not understanding this in the customization email: Leak Status WET1:Basement Entrance: ${sys.node.25 AD EC 2.ST} WET2:Laundry: ${sys.node.25 B0 49 2.ST} WET3:Sump Room: ${sys.node.27 9F C7 2.ST} WET4:Basement Office: ${sys.node.2D D0 9B 2.ST} This is the lines in the code above: Leak Status Washing Machine: ${sys.node.2E F 25 2.ST} Hot Water Tank: ${sys.node.2E 11 9B 2.ST} Master Bath Sink: ${sys.node.2E 16 B 2.ST} Dishwasher: ${sys.node.2E 17 EB 2.ST} I'm only getting status for 2 of the 4 above (the 2nd and 4th report as "on") Q1>what does the "2" in 2.ST mean? If i change to 1, status changes to "off" instead (i couldn't see this looking at the link in above post...) Q2>why are only #2 & #4 reporting (other 2 are BLANK) (yes, i have confirmed correct addresses!) Thx

Hi Paul, Thanks for sharing that!... I'm going with a version of this for now! Fred

Yeah, I'm a bit anal on my sump pump too... I have a sump pump, with a battery backup 2nd on top. Then i have a float sensor to my monitored home alarm system. Then i have a camera on my sump pump. Then i have an INSTEON leak sensor close to the pump, on a block. Then i have a backup sump pump. Then i have a spare sump pump with no float on a quick hose fitting (Hose handy) (it is more for high water in driveway when the ice melts, but is great backup2backup) Then i have a small generator i can connect, if power out too long... Then i have NOW have some feedback from the EM system via DashBox feed. I too am VERY concerned about "another" sump pump failure (as you MIGHT be able to tell LOL) The DashBox to ISY was sort of an afterthought, but a nice "HEY!" bonus! I'm sure there'll be tons of these little lights going off in my head in the middle of the night!

OK, so that makes sense... the change in value is an "interrupt" much like all the other interrupt driven conditions... So it would, in this case be more like: -GEM sends new watts value every 8 seconds -Sump runs maybe for 1 minute -8x7=56seconds, 8x8=64seconds (thus the reason i'd sometimes get 7, sometimes 8 emails in a group) I'll try that, thanks... /Fred

This is very cool!... when my sump pump goes off, i get notified based on watts value being pushed to ISY from GEM! (Saves always sit wondering if my sump pump is active or not... quick and dirty cheap way of knowing!) What I want: When my sump pump turns on, send me ONE (max) email every hour, while it is active... What I currently get: When sump activates, i get a BURST of 8 emails, every time it runs Overview: I have my GEM dumping values into ISY variables, and it is set to do so every 8 seconds, from the GEM side, which PUSHES the values over to the ISY using REST calls. When my sump pump goes off (only a couple of weeks spring and fall normally), it is in short burst of anywhere from a few seconds to a minute, depending on water level around the house). So my program right now, sends me 8 emails in a burst, whenever the sump pump uses more than 100 watts. I'm assuming that the sump goes for a few seconds, then GEM sends its watts used and gets sent via REST to the ISY. The ISY then, every second, or so, triggers based on my program: If $s.Dash_Box_FrontOD_SUMP_03 > 100 Then Send Notification to 'ALL FREDS Email Addresses' content 'SumpPumpActivated" Wait 1 hour Questions: -Based on the above (8 seconds bursts give 8 or so emails), is it because ISY runs a program interrups every second? -How can i restructure/reprogram so i only get ONE email per HOUR while the sump pump is active? Thanks

Doesn't get much better than that ; -) Sent from my GT-N7105 using Tapatalk

Thanks AGAIN Larry... I did the factory reset and ISY restore on the IO-Linc and... as you suspected, the logic somehow reverted, and thus reversed (I THEN had to change the logic from IF OFF (DISABLED) turn fan switches OFF, to IF OFF (DISABLED) turn fan switches ON). (IO-Linc is "OFF" when Tstat is OPEN (Not calling for heat (thus window fans are ON (For "Cooling")... gets a bit complicated using the Tstat in reverse, but I still think it's better than using the Cooling mode of the Tstat... just need to think everything in REVERSE lol)) I forced the run of the QUERY, and it SURVIVED it... YAY! So I **think** I'm gold now... thanks AGAIN to Larry! Fred ===== ===== ===== ===== ===== ===== BRDR-FanOff - [iD 0059][Parent 0001] If Status 'ZZZ1-DO-NOT-USE / IO-LINCS / IO-LINC-BR-Sensor' is On Then Set 'DIMMERS+SWITCHES / SW-DR-WindowFan' Fast Off Set 'DIMMERS+SWITCHES / SW-BedRm-Fan+HTR' Fast Off Else - No Actions - (To add one, press 'Action') ===== ===== ===== ===== ===== ===== BRDR-FanOn - [iD 0058][Parent 0001] If Status 'ZZZ1-DO-NOT-USE / IO-LINCS / IO-LINC-BR-Sensor' is Off Then Set 'DIMMERS+SWITCHES / SW-DR-WindowFan' Fast On Set 'DIMMERS+SWITCHES / SW-BedRm-Fan+HTR' Fast On Else - No Actions - (To add one, press 'Action') ===== ===== ===== ===== ===== =====

Thanks Larry for the suggestion... i'll try that at some point when i get a chance, and report back...

That is correct stusviews... The batteries last for a few years (somehow), and only run the display, programming, AND the relay (which i imagine consumes MOST of the power). /f

HUH? LOL... over my head, but with with the odds of us meeting here, and living so freakin (scary) close, i may stay awake thinking about the possibilities...

Hi folks... Just to summarize, so far... There are 2 fixes, one for the "problem" of my fans turning off, the other of the equipment/signalling. The fix i am referring to is indeed band-aid, of disabling the 3am query. Worked perfectly last night, and on the bench. There is no 24v anywhere near the Tstat or IO-Link (Tstat is 2 x AA 1.5v, and relay switch on the Tstat audibly "Clicks") (but i can certainly see how applying voltage to the sensor input could damage it, if this were so) I did NOT have the "Trigger Reversed" option set, and have not made any IO-Link changes in past year. The relay, way back, was probably tested on the bench, but is NOT being used (so settings should be irrelevant, i believe) A 'manual' QUERY (Running the THEN) also gave the results of IO-Link switching it to OFF, thus turning the switches off. The programs ARE listed in a previous query. To reiterate a previous post: I ran the "then" of the query, and about a minute later, the IO-LINK status went stupid... and fans turned off. So, NOW the LED is on BRIGHT on the IO-LINK, but the state is OFF... GO FIGURE! Thanks for MOST of all your input... ) /Fred

OK, I'm done this discussion... you're not helping in the least. Larryllix solved my problem and it is all working, so DONE IS DONE. (no changes were needed to the IO-Linc itself to get this working). Thanks for your input. /f

respectfully (i'm not trying to insult you, but...) wholly crap, i wish you would learn to read! you're not getting it into your head... but, maybe you won't... i have electronics and computer background, i am capable of understanding. i am not using the relay... ok? i am not using it... only the SENSOR, THAT'S IT. Maybe re-read the whole thing... you also asked about IF the fans were coming on... THAT WAS THE WHOLE POINT! /f

That's all great... but.... I AM NOT USING THE RELAY LOL... I AM NOT USING IT!!! SO WHO GIVES A RIP? (Yes, i do know how they work, etc) Maybe you have greater wisdom on how this would affect my problem? /f

ok, how about "no reason"... what is the significance?

I'm not sure of your question... the relay isn't being used at all (as described above), so the selection and time are totally N/A (or am i missing something?). As i stated, the sensor is the only thing being monitored and used... /f Very simple programs... one for on, one for off... BRDR-FanOFF - [iD 0058][Parent 0001] If Status 'ZZZ1-DO-NOT-USE / IO-LINCS / IO-LINC-BR-Sensor' is Off Then Set 'DIMMERS+SWITCHES / SW-DR-WindowFan' Off Set 'DIMMERS+SWITCHES / SW-BedRm-Fan+HTR' Off Else - No Actions - (To add one, press 'Action') BRDR-FanON - [iD 0059][Parent 0001] If Status 'ZZZ1-DO-NOT-USE / IO-LINCS / IO-LINC-BR-Sensor' is On Then Set 'DIMMERS+SWITCHES / SW-DR-WindowFan' On Set 'DIMMERS+SWITCHES / SW-BedRm-Fan+HTR' On Else - No Actions - (To add one, press 'Action')

Well, somehow you nailed it!... i am very puzzled why, though... I ran the "then" of the query, and about a minute later, the IO-LINK status went stupid... and fans turned off. So, the LED is on BRIGHT on the IO-LINK, but the state if OFF... GO FIGURE!

Good point! I'll try it... P.S. Is the query daily really necessary?

Not using Trigger Reverse... see attached screenshot...

The attached photos show Mobilinc: -all ok, fans running at 240am -messed up at 547am Items related are first three: a-IO-LINK b-BedroomFanSwitch c-DiningRmFanSwitch

A puzzle maybe you can help me solve??? Background: Using 2 Outdoor Switches and one IO-LINK connected to a LuxPro Cooling/Heating programmable weekday/weekend Thermostat. The Tstat terminals RH/RC and "w" (heating) are wired to the IO-LINK GND/S(ensor), sending on/off signals to the ISY, which then turns on/off two window fans via 2 Insteon OutdoorSwitches (so the IO-Link is NOT directly controlling the switches). This all works GREAT on the bench. At 3am, something wonky happens... (more background...) I am using the “Heating” mode of thermostat (so don’t need to change wires in Tstat in between summer/winter, AND avoids cooling mode 5 minute protection between cycles). The Tstat is set to 18c (desired temp of bedroom for sleeping), and the ambient room temp is 26c (at 3am when incident happens). This all works on the bench fine, during the day, when testing. HOWEVER... Somehow, each morning at 3am, the IO-LINK goes out of synch with the Tstat, even though the Tstat continues to call for the fans to be on (the heat to be OFF). In this state, the room continues to heat up (no fans), so the fans never come back on automatically. . Below shows logs of when problem occurs… . Situation is that Tstat is set at 18c, room temp is well above that, at 26c, but at 3am the IO-Link goes stupid, and goes to an OFF state, so the ISY follows suit, and turns off the fans for the night, even though the Tstat still calls for cooling. I ohm’d the Stat, and it was still open (calling for cooling). On the bench, i connected a micro-switch to the sensor inputs (Gnd-S(ensor)) and bounced switch a few times to try to “fool” it, but it is rock solid, and follows suit when switch is opened/closed. Thus, even IF the Tstat bounced at 3am, the IO-LINK will follow suit. Why at same time each day? (within 5 seconds). Can the ISY somehow SET the IO-LINK state? . . . > > > > > This is Tuesday, June 27, in wee hours of morning… > > > > > This is from around 3am (just before to just after) > > > > > At this point, IO-LINK goes off, and all fans turn off for rest of the night > > > > > …even though the Tstat stays open (still calling for fans) > > > > > …but the IO-LINC turns off DIMMERS+SWITCHES / DIM#1-LivRm-WINDOW Status 3% Mon 2016/06/27 02:10:12 AM System Log Scene:ISY Status Query Mon 2016/06/27 03:00:00 AM Program Log Tstat-Main Status 25.5° Mon 2016/06/27 03:00:31 AM System Log ZZZ1-DO-NOT-USE / IO-LINCS / IO-LINC-BR-Sensor Status 0% Mon 2016/06/27 03:00:59 AM System Log ZZZ1-DO-NOT-USE / IO-LINCS / IO-LINK-BR-Relay Status 0% Mon 2016/06/27 03:01:00 AM System Log DIMMERS+SWITCHES / SW-DR-WindowFan Off 0 Mon 2016/06/27 03:01:29 AM Program Log DIMMERS+SWITCHES / SW-BedRm-Fan+HTR Off 0 Mon 2016/06/27 03:01:29 AM Program Log DIMMERS+SWITCHES / SW-DR-WindowFan Status 0% Mon 2016/06/27 03:01:29 AM System Log DIMMERS+SWITCHES / SW-BedRm-Fan+HTR Status 0% Mon 2016/06/27 03:01:29 AM System Log DIMMERS+SWITCHES / SW-BedRm-Fan+HTR Status 100% Mon 2016/06/27 03:02:00 AM System Log Tstat-Main Humidity 64% Mon 2016/06/27 03:05:25 AM System Log . . > > > > > This is Tuesday, June 28, in wee hours of morning… > > > > > This is from around 3am (just before to just after) > > > > > At this point, IO-LINK goes off, and all fans turn off for rest of the night > > > > > …even though the Tstat stays open (still calling for fans) > > > > > …but the IO-LINC turns off Scene:ISY Status Query Tue 2016/06/28 03:00:00 AM Program Log ZZZ1-DO-NOT-USE / IO-LINCS / IO-LINC-BR-Sensor Status 0% Tue 2016/06/28 03:00:58 AM System Log ZZZ1-DO-NOT-USE / IO-LINCS / IO-LINK-BR-Relay Status 0% Tue 2016/06/28 03:00:59 AM System Log Tstat-Main Humidity 48% Tue 2016/06/28 03:01:23 AM System Log DIMMERS+SWITCHES / SW-DR-WindowFan Off 0 Tue 2016/06/28 03:01:25 AM Program Log DIMMERS+SWITCHES / SW-BedRm-Fan+HTR Off 0 Tue 2016/06/28 03:01:25 AM Program Log DIMMERS+SWITCHES / SW-DR-WindowFan Status 0% Tue 2016/06/28 03:01:25 AM System Log DIMMERS+SWITCHES / SW-BedRm-Fan+HTR Status 0% Tue 2016/06/28 03:01:25 AM System Log > > > > > …i manually turned the fan on, as so hot in the room… DIMMERS+SWITCHES / SW-BedRm-Fan+HTR Status 100% Tue 2016/06/28 05:47:48 AM System Log DIMMERS+SWITCHES / SW-HUMIDIFIERPLANTS On Tue 2016/06/28 06:00:00 AM Program Log DIMMERS+SWITCHES / SW-HUMIDIFIERPLANTS Status 100% Tue 2016/06/28 06:00:01 AM System Log > > > > > END OF ABOVE SECTION

THANKS to both of you! I didn't realize I could manually set the latitude and longitude. Set it, and now it is correct, as you stated. AGAIN, THANKS! Fred

My sunset time is wrong... it was also wrong when set for Boston (now Toronto, same thing) on 4.4.6 Should be 9:12pm, says 9pm, so things starting/stopping too early. see attached screenshot...