superioreo Posted January 6, 2019 Posted January 6, 2019 Hi - I have 4 of these 14287 and they work great. I have my Ecobee hooked up through NodeLink to tell me the temperature in each room and the ISY will trigger the fans based on temperature ranges I have set in programs. All is good... unless I want to manually trigger the fans. Since I have them hooked up based on the temperature, I need an override if I manually trigger the fan on, say, when it's "too cold" for the fan to go on, but I have burned something in the kitchen and I want to get the fan moving -- or it feels like I want the fan on even if my temp settings seemed like a good idea. With Insteon, I could tell when the switch was triggered and start a countdown until the "machine" takes over again. With these fans (or perhaps with Z-Wave altogether?) I have not figured this out. Can someone tell me if there is a simple way to make this happen I have overlooked, or whether there is a workaround someone has found for the fans or Z-Wave as a whole? Since I moved a year ago, 95% of my equipment are now Z-Wave whereas I used to have an Insteon house. Thanks much!
lilyoyo1 Posted January 6, 2019 Posted January 6, 2019 Does the fan provide status? If so you could write a program that runs when the isy sees it triggered
asbril Posted January 6, 2019 Posted January 6, 2019 3 hours ago, lilyoyo1 said: Does the fan provide status? If so you could write a program that runs when the isy sees it triggered I have the older version (not Zwave Plus) and even that one provides status, and yes you can include it in a program as IF or THEN/ELSE.
jc986 Posted January 6, 2019 Posted January 6, 2019 I've done almost something very similar in with my fans. Here's what I've done. Put all the programs which automatically control the fan on / off / speed into a uniquely named folder for the room. Create a state variable to be associated with the "manual" state of the fan speed switch and add it to the IF conditions in the folder you just created such that "if state variable = 0' the programs in the folder are enabled. Now, create a "manual on" program whose condition is the "control" of the switch being "switched on" rather than the status and the "then" statement sets the previously mentioned state variable to '1'. I then have a "manual off" program which triggers on the "control" of the switch being "switched off" and sets the state variable to "0" once again. This allows local control of the switch to override the automatic programming based upon temperature. Cheers
oberkc Posted January 6, 2019 Posted January 6, 2019 22 minutes ago, jc986 said: Now, create a "manual on" program whose condition is the "control" of the switch being "switched on" rather than the status and the "then" statement sets the previously mentioned state variable to '1'. This (or similar) is the approach I would take as well. Unfortunately, I have a couple of z-wave switches that don't trigger a "control" condition. Yes, they show accurate status, but it appears that the ISY cannot distinguish the difference between direct control or other causes of status change. Whether (or not) the 14287 Jasco switch is one that would trigger a "control" condition I do not know, but it would be easy enough to find out with a simple experimental program.
superioreo Posted January 6, 2019 Author Posted January 6, 2019 So I just tried this program below to see if it would trigger the manual state variable when I switched the fan on and it did not. Is this the right program to test this? Thanks in advance! If 'FamilyRmFan' is switched On Then $FamilyRmFanManual = 1 Else $FamilyRmFanManual = 0
oberkc Posted January 6, 2019 Posted January 6, 2019 Looks like a good test program, yes. Your results are same as mine. Also, check status of last run time for that program. If it shows that the program ran, let us know. I assume that your log will show NO run time for this one. I remain uncertain if upgrading to the newer z-wave board will solve this problem, but others may know with more certainty.
superioreo Posted January 6, 2019 Author Posted January 6, 2019 Correct, no run time. Hey thanks for testing on your end too oberkc. Is there a workaround or some way to accomplish this with these switches or Z-Wave in general? Appreciate any help. THx
oberkc Posted January 6, 2019 Posted January 6, 2019 This method works really well with inteon switches. Unfortunately, it seems that there are more variables with zwave. Whether this is due to the large number of zwave vendors or something else...who knows for sure. I can think of nothing other than to try to verify in a place such as here that a specific zwave switch triggers the "control" condition. Or use insteon. I am pretty confident that none of my zwave switches do this, but I will double check later.
jc986 Posted January 6, 2019 Posted January 6, 2019 That's interesting. I have both the old Leviton and the new GE / Jasco 14287 switches using this exact method. I am running V5 on my ISY which, I believe, is a prerequisite for this to work. I will say that I never did see the "Else" trigger in response to a "control switched off" event which is why I created the "manual off" program. Manual On If 'Room / Fan Switch' is switched on Then $RoomFan = 1 Manual Off If 'Room / fan Switch' is switched off Then Stop Program 'Return to Autocontrol' // Wait timer which will return the fan to automated control $RoomFan = 0 As I say, I use this with both the old Leviton Z-Wave and the new GE / Jasco Z-Wave+ switches (14287 - not the older non-plus models).
superioreo Posted January 6, 2019 Author Posted January 6, 2019 Thanks for the response. I am running V5 and have ZWave up to date at 4.55 with the GE/Jasco 14287. I'll tweak some things and try again later.
oberkc Posted January 6, 2019 Posted January 6, 2019 I must rescind my response earlier. In fact, it appears my z-wave devices trigger "control" conditions. Perhaps I was remembering from v4 software. Perhaps I never checked it after update to v5. I must be getting too old for this. I am on v5.0.13D. Zwave says 4.55
oberkc Posted January 6, 2019 Posted January 6, 2019 superioreo, I also re-looked at your original test program. I was premature in declaring your program correct. ON should trigger it, but OFF would not. Try it again, if you don't mind, but add a second line: If 'FamilyRmFan' is switched On and 'FamilyRmFan' is not switched Off <<<<< add this line Then $FamilyRmFanManual = 1 Else $FamilyRmFanManual = 0
superioreo Posted January 7, 2019 Author Posted January 7, 2019 Thanks oberkc. I tried it again with the modification above and also tried it with the line 'FamilyRmFan' is switched Off just for "completeness" and nothing has yet triggered the THEN and changed the variable from 0. I wish I could figure out what I'm doing wrong. Does ZWave not pass status over multiple hops? Eric
oberkc Posted January 7, 2019 Posted January 7, 2019 Am unsure of the hop thing, but I understand that zwave devices relay commands, perhaps by a pre-defined path. Is this zwave device otherwise communicating properly? Is correct status showing?
superioreo Posted January 7, 2019 Author Posted January 7, 2019 It shows correctly when I turn it on at the switch. When I use a program to set it at, say 45%, it registers 100%.
larryllix Posted January 7, 2019 Posted January 7, 2019 @superioreo BTW: Did you know you can combine your two programs into one by using this logic trick in ISY? This makes vocal control easier also. If 'Room / Fan Switch' is switched on AND 'Room / fan Switch' is Not switched off Then $RoomFan = 1 Else Stop Program 'Return to Autocontrol' // Wait timer which will return the fan to automated control $RoomFan = 0
Recommended Posts
Archived
This topic is now archived and is closed to further replies.