TJF1960

Oh, you also need a 5v power supply to power the ISY, but then you probably already have one but thought I would mention it just in case. Z-Wave is in Alpha stages right now, soon to be Beta stage. Once it is available you can order the module from UDI.

I am pretty darn sure the hub is not compatible with the ISY. The hub is an HA controller with a PLM built in. The ISY is an HA controller as well but requires a PLM such as 2413S.

Ah, I didn't realize you could pull status of other devices and have them displayed, I knew you could with variables. I haven't played much with notifications. Thats great info, Thanks.

What you can do as a work around until the feature you want is available is create a simple program which monitors the status of the device and switches an integer variable to 1 when it is on and 0 when off. Then have the text/email send you the variable value so you will know whether was on or off when notified. If Status RoomFan1 is on Then set $iRoomFan1 = 1 Else Set $iRommFan1 = 0

Only if that device is what triggered the notify program. In that case: In Custom Notification select Alert. You can select Node Name or Node Address which will supply the name or address of the device which ran the notification email. If the notify program was triggered by an If Status of device then select Action to report the status of the device. If it was triggered by If Control device then select Control.

They are pretty big, I don't know the exact size but they will not fit in a regular junction box.

Another thing you can do is have the kpl or switchlinc beep after a successful fast on or off.

I am not sure what a network delivered x10signal is, but you should be able to use a network resource on one ISY to change a variable on the other. The one sending will need the network module, if both will send each other messages then both will need the network resource module.

Well, I may just be really tired, but as his program is written I too would expect the program to be true if either switch was fast on, and false if either switch was fast off. If it were me I think I would be looking to see if there are any comm. issues, maybe the ISY is not receiving the fast on/off commands from those switches.

Yes. ISY programs are event driven. If from 5:30 pm for 2 hours then else

If you are checking the fan before the 30 minute wait when the program would shut it off, and it is off, what does the ISY show for a status of the fan?

He told me it (local ip address/es) are stored in the cloud, so it wouldn't work if the cloud or internet were down. I was going to test to make sure but just haven't had the time yet. But I will tell you that if it does originate from the cloud, its pretty darn quick. The time from when motion or water detection occurs to when the ISY variable is switch is maybe 1 second, no more and maybe less. I was really surprised at the quickness of response. I will check when I get a minute and post back.

Another possible solution for the op would be the wireless tag sensor. I just picked one up to play with. http://www.wirelesstag.net/ They just increased the range of the sensors which detect motion and temp. They claim you can throw the sensor in the door of the fridge or freezer. I have the tag manager sending status updates to variables in the ISY, surprisingly fast response.

Ah, I was not aware the programs would run in sequence during catch up schedules! And sorry for my short question, it was based on the assumption that the op's catch up schedules was checked. Thanks, Tim

Xathros, if the ISY is rebooted for whatever reason wont the two programs run and possibly set the tstat incorrectly?

I am unsure, and curious, what you mean here. 3rd parties? Are you talking unauthorized individuals? If so, put a switch in a desktop enclosure and hide it somewhere. He is tracking the pet / baby sitters movements thru his house, If they are opening doors and going into rooms they are not supposed to be in.

This may be a reach but as I understand it with the x10 module you can create a virtual x10 device. I don't know if the device will show up in Mobilinc or not. Maybe someone more familiar with the x10 module can chime in.

I am not even so sure about that. For 3 or 4 days this last week my Evapotranspiration was reporting as 0.019"per day and typically its around 0.16 with the weather we have been having for the last 2 weeks. The stations I am using is KBAB (Beale AFB), which is listed on the NWS site.

Exactly. When the red exclamation point first turns on is the only time that program will evaluate true. When the red excalmation point disappears that is the only time that program will eval. false. Except of course for forced runs.

Sorry I am late getting back to the party, and I apologize for missing the fact that belias was trying to force run the program. If the red exclamation point is showing and he forces that program to run "if", it should evaluate as true. If the device is responding properly and a force run "if" is done the program will run false. By itself the program will only run true or false once - with each status change from responding to not responding only. But not by a query after the status has changed. belias, there must be something odd going on if you are forcing the program if and it is evaluating false when the red ! is visable, but I don't know what. edit: boy I am really late, I didn't see the last 2 post until now.

That is correct, it will only evaluate true when the device goes from responding to not responding. In other words the program will only evaluate true once. Once the device starts responding then stops again the program will evaluate true again, once.

Momentary just has to do with the relay and shouldn't have anything to do with the sensor status. Is it possible the sensor isn't being held low fully? Check the event viewer on level 3 and block the beam and see if there are multiple occurrences in the viewer. Also the wait placed where it is in the first program is not do anything. In settings is the sensor trigger reversed?

Seems to me if the beam is broken the iolinc will send an "on" (or off, however it is wired) just once. When the beam is restored the iolinc sends off. Once the beam is broken and stays broken the program should not retrigger until the beam is restored. It might be best to post the program in question.

Thanks Lee, Once again you saved the day!

So it sounds like if I have 2 programs both of which are doing math functions and are sharing 1 integer variable as a place holder the data may get corrupt if they both run at the same time, esp. if one starts before the other but the other finishes first. So I will need a placeholder for each program. Thanks Lee, Tim