
johnstonf
Members-
Posts
369 -
Joined
-
Last visited
Everything posted by johnstonf
-
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?
-
-
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...
-
Amigo presents the only option that is also good for me. i am not an IOS user (not an Apple hater... have macbooks, mac mini, appletv, but need Android for techy reasons, and removable battery, built in stylus, large screen, microSD, some apps, etc etc). I have NO interest in Mobilinc, as i don't like their licensing, their crappy Android attempt, tons of users complaining, but no action from Mobilinc, etc). I find the web and isyhelper just fine for my needs, but, DO need a separate admin and user separation (so users don't disable, run then / else portions, change variables, etc etc.). It's got to be low level protection in the isy os itself). I hope UD can come up with something... that is a big disappointment (compared to how i love the isy platform... it is great). I don't want to have to buy and install software for all my kids, parents, guests, friends etc to be able to run my HA, but i do want to give them access (limited), to control anything while they are on my LAN/HAN (and no WAN access). Right now, everytime someone comes and leaves, I have to remember to reset the password.... TOTAL PAIN! Quick browser access works great right now, except for ALL the MANY problems with TOO MANY rights... PLEASE PLEASE PLEASE UDI, CAN YOU HEAR ME / US?
-
I am new to ISY... one thing i can't figure out... When I have guests into our home, I like to give them browser access to my HA system. As i don't like to give them full ADMIN access, I'd like a "non-admin" type of account, so they can't get into they ISY and make changes (not that they would, but i feel uncomfortable giving that level of access). Is there a way to create a 2nd "non-admin" level account to give to non-admin folks onto my ISY? Thanks!
-
Hi All, This post is quite long-in-the-tooth (and good)... I am new to all of this. Can anyone point me to the latest and greatest to learn ISY programming, but using the new variables, event programming, etc, starting with event concepts etc, using variables. I'm scared of learning concepts here, that may no longer apply using variables, etc Thanks!