Jimbo.Automates

If that switch doesn't have real good communication to the ISY this can happen. Put the MS in linking mode and run a couple queries with the event viewer running at level 3. Copy and paste to the forum and one of the experts can help.

The relay should only be on for the short time, but I need to check my setup to verify.

Kush, you are welcome. Lee, that explains the issue for NC, but mine are NO, so not sure what caused this for me?

I have experienced the exact same 3am query all problem with IoLinc sensor status, because of this I changed my notifications to run a query again before sending the notice. I suspect they were caused by communication problems but haven't been able to confirm. Sent from my Nexus 7 using Tapatalk

Yes, then enter your desired text in the pushbullet plugin filter configuration. Sent from my Nexus 7 using Tapatalk

Yes, I was not able to get that to work completely either, I thought it was me.. I wish I could use pushbullet, but for this reason, and because pushover has high priority I have stayed with it for my notifications. But it is on my list to look at autoremote, just waiting for variable support in the network module since I'll redo everything when that is working. Oh, and there is a new Tasker pushbullet plugin I need to check out as well. Sent from my Nexus 7 using Tapatalk

Sorry, life gets in the way of reading forums sometimes :-/ Yes that should work. I don't remember, but I don't think pushover Android app is free. I tried to use pushbullet, but Tasker doesn't have access to what is in the message, but you probably could use it to make a specific sound when one is received. Sent from my Nexus 7 using Tapatalk

Email to pushover and Tasker can act on it, I have a tablet that uses text to speech to read some pushover notifications. I use network module to talk to pushover api, but you could use emails. Sent from my Nexus 7 using Tapatalk

Use if control instead of status like Xathros mentioned in post #4

Like Stu said, the if runs only when it is switched On, so nothing stops the program from running. I think if you add an if is not switched off, it will restart the program when an off is received and evaluate to false.

The write device updates only works when the device wakes up. I use a state variable to track the status of all my open/close sensors just for this reason. Each time the status changes a program sets the state variable, along with the init to value. Sent from my Nexus 7 using Tapatalk

Thanks, it's on my list of things to try, but haven't had time.

Have you tried the RESTask for Tasker? Just curious if it helps with that issue.

Or if the scene has a controller, like a KPL button, then check the status of that controller. So if you manually turn off the scene or another scene turns off the KPL it still works. Sent from my Nexus 7 using Tapatalk

Thanks, and yes, always best to set the init values for important variables like that. Sent from my Nexus 7 using Tapatalk

Hey oberkc, I have never used programs for status, does the ISY retain the last status after a reboot? Sent from my Nexus 7 using Tapatalk

There is an writeup by MWareman on the wiki for using the rest interface directly, but that should help get you going. If not, let us know what part of the setup you have issues with. Sent from my Nexus 7 using Tapatalk

Make the Tasker profile run a program to set a variable to true as the entry task, and false as the exit task, then use that variable in your door notification trigger. Sent from my Nexus 7 using Tapatalk

If you only want the then/else to run at 9pm then one way is to move everything except the time is 9pm to a separate program that is disabled, and run that program at 9pm. Sent from my Nexus 7 using Tapatalk

You can use the http port 80 to test, and since this is all internal to your network do you really need https? Sent from my Nexus 7 using Tapatalk

When you say the scene goes off then on, what is changing the scene? A program, manually at the switch, toggling the scene in the Admin Console or from mobilinc or? Sent from my Nexus 7 using Tapatalk

Thanks Xathros, that was the one I was looking for.

Someone posted about having a program to set user codes on schlage's in the last few weeks but I don't remember the specifics. For now I just have the codes always there and have notifications sent when they are used.

Here is my program. The s.MS.FRO.Dark is 1 when I want the light to come on, Also, the door sensor is a open/close sensor with the jumper removed (2 scene mode) so it only turns the scene on, not off, and I have a separate timer program to turn the light off. The only issue with this that I have found is if it's light and I do turn the light on, the sensors will turn the light off. I'm trying to perfect the programs, but not quite there yet... AL FRO Enable Auto On - [ID 0008][Parent 0017] If $s.MS.FRO.Dark is not 0 Then In Scene 'Z-Motion / FamilyRoomOutsideMS-Senso' Set 'Outside / BackYard / FamilyRoomDoorOutside' 100% (On Level) In Scene 'DoorsAndGates / FamilyRoomDoor-Opened' Set 'Outside / BackYard / FamilyRoomDoorOutside' 100% (On Level) Else In Scene 'Z-Motion / FamilyRoomOutsideMS-Senso' Set 'Outside / BackYard / FamilyRoomDoorOutside' 0% (On Level) In Scene 'DoorsAndGates / FamilyRoomDoor-Opened' Set 'Outside / BackYard / FamilyRoomDoorOutside' 0% (On Level)

In the adjust scene, select the sensor in the top selection, not the scene itself. I can post a pic when I'm at my computer. Sent from my Nexus 7 using Tapatalk