-
Posts
1001 -
Joined
-
Last visited
Everything posted by andyf0
-
Aside from the conversion about powering up / down the camera vs leaving it on all time ........... Under my Foscam cameras (Insteon?) under Settings, I have a section called PTZ. Under PTZ there is a startup option. Click to bring up the startup options and select "Disable StartUp". I haven't tried it but it sounds like it may do what you want.
-
That's good to know. Thx.
-
A drawback is that a scene command will not retry. If you try to send a command to a single device via a scene and the command fails to reach the device, there is no retry. Talking directly to the device will attempt retries if the initial attempt fails.
-
Until the battery status changes from the 30% you observe the program will not trigger, so you'll have to wait until it goes below 30% (or above).
-
Leave the "if" blank. I generally put a "Wait 2 mins" before sending the notification to allow the ISY time to complete it's boot up and query devices.
-
I have had an EZflora for over 3 years now and it's still working fine. If using it with an ISY, you use the ISY to do all the smarts and simply turn each zone on & off. You can only have one zone on at a time. It has a 30 minute timeout for each zone in case it misses the ISY command to turn the zone off, although turning on a different zone will automatically turn the previous zone off. It will handle 8 zones or 7 zones and a pump on/off control. Remember, only folks with bad things to say will post on forums to say bad things.
-
My "goodnight" program takes a little while to run also. It calls about 4 programs, one of which calls a couple more. But it doesn't bother me since I'm already in bed and pulling the covers up when I push the button. I think it's changing the settings on 2 Z-Wave thermostats that takes most of the time since I adjust mode, cool & heat set points on both. Lot's of Insteon and Z-Wave traffic going on which obviously has to get queued up.
-
You can combine all your door sensors into a program using 'OR' for each sensor to trigger the program. If any of them open send a custom message using a substitution variable ${sys.node.#.name} to identify which device caused the trigger. You can do the same for a low battery message. So 2 programs.
-
You know there will be a 6 hour delay after each run of the program. The repeat every 6 hours means there will be a 6 hour wait after each run of the program. I used to get very confused by this.
-
I was wondering what that program was that you were running at the end. So you're calling itself. I think I used that technique myself in a couple of programs where a repeat was not suitable. I really don't think the variable would glitch other than if there was another program referencing/changing it somewhere. Otherwise I don't see why it shouldn't work as you want.
-
The program will only run once when the state variable changes to "1" and then stop. It doesn't run just because the variable has a value of one. You really need a "repeat" statement in the "then" section". When you set the variable to "1" from "0" then it will repeat the "then" with the frequency/duration you specify in the "repeat". When you set it to "0" it will interrupt the repeat loop and run the "else" once and turn it all off. If $PoolHeating is 1 Then repeat {every x minutes/10 times etc..} Set 'Pool Equipment / SupplyValve' Off Set 'Pool Equipment / ReturnValve' Off Set 'Pool Equipment / Polaris' Off Wait 1 minute Set 'Pool Equipment / FilterPump' On Set 'Pool Equipment / PoolHeater' On Wait 2 hours Set 'Pool Equipment / FilterPump' Off Set 'Pool Equipment / PoolHeater' Off Wait 4 hours Run Program 'HeatPool' (Then Path) Else Set 'Pool Equipment / FilterPump' Off Set 'Pool Equipment / PoolHeater' Off ***notification
-
Maybe if you put the "st" in caps? "ST".
-
You can, in a program, send an Email. You can configure your SMTP Email provider in the Configuration tab. You can send an Email to your cell providers EMAIL to SMS bridge to send yourself a text message, again, setup in the Configuration tab.
-
I've been testing my new Estimote beacons that arrived with the hope of replacing the geofencing feature of MobiLinc. They come with some demo programs, so I fired one up to full power, balanced it above my garage door and backed out of the garage and drove away. I have broadcasting set to 1 sec. I got about 200' away before it recognized I was gone. When I returned it didn't recognize my arrival until I hit the driveway. So it may work quite well, but I must admit I have gotten used to the garage door being completely open by the time I hit the driveway. Now I'll have to wait while the garage door opens. The other two are definitely going to be needed, probably at full power also, around my 2 story 2800 sq ft house. I was walking around the house and one or other was dropping out from time to time at low power. There are certain habits that form (like going to get the mail) when you know that the geofence won't trigger because you have to be so far away for that to happen. Now the beacons will probably lose me when I get the mail. Although the motion sensors in the house do give me a 15 minute timeout before the house shuts down, just can't get into a long conversation with a neighbor at the mailbox.
-
According to Amazon's description it's a Zigbee device so no, this is not Z-Wave compatible.
-
If you make your message > 160 chars then T-Mobile will automatically convert the message from SMS to MMS and you will receive the From: correctly. Unfortunately there is not a separate MMS vs SMS mail address to send a message to with T-Mobile. ATT does have separate mail addresses for SMS & MMS. One of the reasons I switched back to ATT a while ago. Unfortunately it usually means padding your message with junk to get the character count up. Also note, MMS can take a little longer to go through than SMS.
-
I think Stu got confused with what you want to do. Yes, you can create a custom notification message with the current temperature embedded in the message. I forget the actual variable name but if you search the Wiki you can find the system variables that you can use in your message. Or .. someone that already does this might chime in.
-
I occasionally get a MultiSensor node with the same ZW number as a light switch. I just delete it and re-sync the nodes. No bad side effects.
-
Your repeat loop is interrupted because you changed the state of **003 Living Room Pots. Since this device is now part of the "if" statement it causes the repeat to be interrupted and the "if" re-evaluated.
-
Be aware that MMS messages are not necessarily immediate. I've had a few notifications delayed by an hour on AT&T. Most come through right away though. SMS messages seem to be more reliable but you get that stupid random number in the From: field.
-
For T-Mobile you have to pad the message to >160 chars to force it to go to it's MMS server rather than SMS server.
-
Presumably the light is attached to a module or SwitchLinc. Add the module or the switch as another controller to the scene, not as a responder.
-
Of course, if we were able to test for a program that is currently running (then or else?) ......... (and trigger on the state change?) . Oh! and include that state in a WAIT command, like WAIT until Program 1 is idle. Just a feature request .......
-
I use MobiLinc geofencing and it is reasonably accurate. More accurate for leaving the area than arriving. If the phone is sleeping I can arrive in the driveway before it triggers. I use 4 motion sensors with 15 minute timeouts to detect motion in the house. If all sensors timeout it is assumed no one is home. This sends a text to my iPhone and shuts down the house and thermostat 5 minutes later. Of course, this only happens if the iPhone is away from home. Before the geofencing feature the house would shutdown if I took a nap.
-
I am using an iMac with the same versions of the OS & Safari. The only times the window loses it's size seems to be: A reboot of ISY A reboot of the OS An update to Java An update to ISY and the Admin Console (maybe). Java cache is cleared (I wish UDI would save the settings elsewhere). An occasional unexplained event. But most of the time my Admin Console window size sticks. However I haven't accessed the ISY from outside my home network in a very long time. Something is stuck in the Java cache. Try rebooting the OS, when I do this the Admin Console opens up full screen and all folders expanded. Set the size you want and try again.