Jimbo.Automates

I haven't changed my programming since the original post. I would try triggering the scene manually the same way the programs do. I can try to review the programs and see if I have any other suggestions. Sent from my Nexus 7 using Tapatalk

Hi Mike, sorry I am not very good at debugging the logs, but I would first try triggering the IoLinc manually to see if that works, the trigger it thru the ISY.

The program stops running when the sensor turns back to on. Move the lines in the then part to a separate program and run that program instead. Sent from my Nexus 7 using Tapatalk

Oh nice! I use the E from SDG&E! Guess I need to start looking at what this all means Sent from my Nexus 7 using Tapatalk

As Lee mentioned, you have the old 99i, but also you are using the UI that is newer. You need to install the UI that matches your firmware version. That could be why you have issues with adjusting the slider. Sent from my Nexus 7 using Tapatalk

Lee, if the ISY waited a little longer before querying the next node wouldn't that help reduce the chance of this issue? Sent from my Nexus 7 using Tapatalk

There is a good write up on push notifications: http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification and a little on using Tasker: http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification:Tasker

I use pushover notifications sent to an android tablet that is almost always plugged in, which speaks the notification in Tasker. Sent from my Nexus 7 using Tapatalk

Yes, as Lee mentioned, he was pretty sure you needed to remove it from the folder.

Thanks for the info Paul. I have a few of the insteon brand plates and really liked how solid they mounted, but the are so expensive. Those lutrons look good and much cheaper. Sent from my Nexus 7 using Tapatalk

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