Rocketron

Worked like a charm once the corrections made. However I do see the downside at work now. Before the fan can restart, the temp will have to drop below 25 to reset everything. As I said not a problem for me at the moment. Yes, I see where removing the variable would reduce the chances of error. I'll probably do that in a little. What I'm thinking of now is I need a variable that I would call "ascending" and another called "descending". If you took the variable for the temperature and compared it to time is it possible to create the ascending/descending variable? ie: variable x, wait time (say 10 seconds) variable y = ascending or descending temperature? Is this something the ISY has the possibility to do? I'm too weak in using variables to know if this is possible. My head is hurting, time to walk away for a little. Can someone point me to a thread which shows how to subtract variables to get a sum? I've got two variables now from the temperature separated by time. If I can do a calculation I should get either a positive or negative number. If positive I can infer that the temperature is rising, if negative it's dropping. Probably can use that information to start or stop the fan.

Ahhh the no joy in the first run. The variable isn't updating. hummmmm...... OK figured that out..... updating now. Ahh Haa! better now... Thanks ! Variable int - [ID 0059][Parent 005A] If 'ZW 125.8 Multilevel Sensor' Temperature > 24.0°C Then Repeat Every 10 seconds $State_1 = 'ZW 125.8 Multilevel Sensor' Temperature °C Else - No Actions - (To add one, press 'Action')

It appears to me that Variables are required to make this work... So this pgm creates a state variable. Not sure that is required but did it like this. You might correct me in any of this if it makes more sense to do it another way. If 'ZW 125.8 Multilevel Sensor' Responding is True Then $State_1 = 'ZW 125.8 Multilevel Sensor' Temperature °C Repeat Every 5 seconds Else - No Actions - (To add one, press 'Action') This would be the pgm (2) in the example given above. Fan waiting - [ID 005C][Parent 005A] If $State_1 > 25 Then Enable Program 'Fan on off' Disable Program 'Fan waiting' Else - No Actions - (To add one, press 'Action') Finally what starts and stops the fan pgm (1) Fan on off - [ID 005B][Parent 005A] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Ensuite fan' On Repeat While $State_1 < 48 Wait 1 second Repeat While $State_1 > 45 Wait 1 second Repeat 1 times Set 'Ensuite fan' Off Repeat While $State_1 > 25 Wait 1 second Repeat 1 times Enable Program 'Fan waiting' Else - No Actions - (To add one, press 'Action') I've gone with this method mostly because it challenges me a little (no a lot...) Repeats and waits are a totally foreign to me, and variables almost the same. I'm going to have to contemplate the waits and repeats to figure out why those are important. I suspect that since I live alone this will work in my application. If the temp doesn't fall below 25 will the fan restart? In situations where a second shower follows closely it might prove annoying. I'll run it and see what happens, of course it's slow to cool that last little bit to 25 so it'll take a while to see if it works each time I make a change.

Yes, what you've shown apostolakisl is where I was heading when thinking about the problem. Mwester, you say about the "Direction" of change in a set time period, this is where I would have liked to go but have no idea how to get there. I'm going to see what I can figure out in this direction first. I wasn't sure if I should be going into the path of using variables. I've never stepped in that direction. If someone can show I'd be better off doing that I'd certainly give it a go. I don't wish to disparage in anyway the ISY's ability to program but it is limited in someways. Of course sometimes you need to think it through to get where you are going. What is maybe causing me difficulty is my background in power engineering. Accomplishing this in an industrial setting seems so easy. Something heats up in so many seconds, something else can be programmed to react to this instantly. Thanks for the replies. Just as I was hoping it's got my brain working in a direction that is more clear. Larryllix... This is what I'm using to gather the temp data. As for the program I have, there is no use in showing that as it was just something to get me started. It's showing me how well the temp probe is picking up the data.

At first blush I thought this would be an easy install and program but once I began attempting it I've hit a roadblock. The plan was to install a temperature sensor on the hot water pipe leading to the shower. From this input it would trigger the bathroom fan to start and stop. I got the hardware installed and working then began to think about how to program this. I've not found when searching the forum anything similar. The original idea was to trigger the fan on when the temp rose to above 25`C. It seems the temperature rises to a little over 50`C once all the system is hot. Then have the fan shutoff when the temp falls under 45`C. A simple program fails as the fan starts when above 25` then shuts down right away as it's below the 45`. My solution has been to have it start at 45` and shutdown under 45`. This works like a charm but does delay the fan starting for what seems like 1.5 minutes while the piping heats up. Suggestions for improvement to get the fan running sooner? What had come to my mind was having the ISY react to a temperature increase within a time period. Say a 5` increase within 10 seconds, keep the fan running until it detected a 5` decrease without any time delay. Sounds good but I've no idea how to program something such as this. Hoping someone can see the obvious thing I don't see.

Bought one to work with the DS18B20 temperature sensors. Plan at the moment is to hook up two sensors to the pipes leading to the showers. Will trigger the bathroom fan to run and shutdown. First attempt to get it to work on my desk next to me didn't go well. No temperature other than the internal. Wired up correctly. Ok read the instructions.... Attach the temperature sensors, then include the unit to the ISY. Worked like a charm for the single sensor I have attached. I suspect adding more sensors will require excluding and including. Will update as I work toward the install.

Yes I did, had to un-link and re-link the Universal Devices service in Google home.This meant I also had to again put each device into a room before they could be controlled by Google Home. Still not seeing z-wave devices in Google Home. Might have to upgrade from 5.0.4?

I'm guessing Zwave devices will connect at a later date?