Michel Kohanim

@IT Solutions, You can query devices in the same program BUT the total wait within the repeat can NOT be longer than the repeat duration. So, if you want to wait 2 minute between each, you would have Then Repeat every 6 minutes and 10 seconds Query lock-1 Wait 2 minutes Query lock-2 Wait 2 minutes Query lock-3 Wait 2 minutes Or, you can have 3 programs. It's totally up to you. I would choose 3, because it makes debugging easier (the name of the program points to the name of the door lock). There are no limits to the number of conditions and actions. So, you can put 100s of things inside one program. With kind regard, Michel

@IT Solutions, ISY does not work like that ( you can not use a result of an action in the program UNLESS it changes the state of something in the condition). i.e. there's no such a thing as "check lock" ... So, you need either 1 (or 3) programs the sole purpose of which is to query the locks. If any of the queries fail, then Not Responding event is generated for that lock. In which case, the program above is run and increments the number of failures. If the number of failures reaches 3 or more (or whatever you want), then the notification program sends the email. With kind regards, Michel

@IT Solutions, I don't think you need a Wait. The Repeat includes the wait. i.e. repeat every minute. With regard to sensing failures, you would need a State variable for each. --> State variable $doorLock1NumFailures If Control 'door lock 1' is not Responding Then $doorLock1NumFailures += 1 Else $doorLock1NumFailures = 0 //notification program If $doorLock1NumFailures >= 3 Then Notify <whomever/> <some-content/> With kind regards, Michel

@IT Solutions, Thank you for the links. IMHO, it's best to replace them. Since you cannot get any events from these locks to fine tune the query, then you will need something like the following regardless. The reason is, you would not know when the door is locked/unlocked if they do it manually/physically. If From 12:00:00 AM To 12:00:00 AM (next day) Then Repeat every <you choose the duration> Query the lock Please note the following: ISY retries all commands and puts a lock on Z-Wave communications. So, when this program is run, and if there are communication issues, then no other Z-Wave device can be controlled. Events from other Z-Wave devices are sill captured and put on the queue, but the queue depth is going to increase since the program is retrying. In short, it's just a bad idea all around. With kind regards, Michel

@IT Solutions, Please try a factory reset, exclude, and include. I have yet to see a door lock that does not report status. With kind regards, Michel

@IT Solutions, I agree with @lilyoyo1, all locks do report their status unless there's something wrong with them. Did you try factory resetting first? With kind regards, Michel

@IT Solutions, I don't recommend doing a query. It will cause all sorts of other traffic issues. What I suggest is to get a couple of range extender and then update neighbors. Need to get to the root cause. With kind regards, Michel

@Blackbird, Signal/noise. INSTEON: Troubleshooting Communications Errors - Universal Devices, Inc. Wiki (universal-devices.com) With kind regards, Michel

@Ajax, I responded to your ticket. With kind regards, Michel

@asbril, I totally agree with you. We should have a search function + date. Also, when PG3 is out (very soon hopefully), we'll have newsletters with new node servers. With kind regards, Michel

@IT Solutions, Line of sight, with no obstruction, it should be 100ft. That's how we got certified. With kind regards, Michel

@jmpnjimbob, are you installing UD Mobile from the Play Store, if so, it does not yet support Geo Fence. With kind regards, Michel

@IT Solutions, Some suggestions, please put ISY Vertically. Put range extenders in strategic locations AND right mouse click | Z-Wave | Update Neighbors. With kind regards, Michel

@ISY Newbie, Do you get events from any other devices? If so, and if you have linked them properly (you don't see any 1011 icons), it's probably signal (RF) related. With kind regards, Miichel

@ISYhbsh01, Thank you and I agree. But, there are just so many ISYs out there, some have been running for over a decade, that it would be impossible for us to contact all the customers. And, if we just do that, the cost of having to explain to those whose notifications stopped is not tenable. With kind regards, Michel

@Bizywk, I suspect your programs are inside a folder with a condition that is not true. With kind regards, Michel

@btreinders, Weren't you working with @Chris Jahn on this? With kind regards, Michel

@wdhille, I already responded to your ticket. For your reference: If you open the Event Viewer and change the Level to 3, then ISY logs the source address/port and the local ISY Port. This is specifically there so that you can see whether or not anyone is hacking you. In your case, no one is. It’s your phone/mobile app talking to ISY. With kind regards, Michel

@seattlestexan, "Not Implemented" is a sign that your UI is not correct. Also, forum is not tech support. If you do need tech support, please either submit a ticket with relevant information or send an email to support@universal-devices.com. Please do NOT post a reference to the forum. We do not have the resources to read 5 pages of back and forth. Thank you. With kind regards, Michel

@crotius, Please use https://isy.universal-devices.com/994i/5.3.1/admin.jnlp ... this will ask you to upgrade. With kind regards, Michel

Hi @dalter2, Thank you for the vote of confidence. I didn't say we would not support the PLM. I said, we won't have the bandwidth to support their newer devices in a timely manner. If they have APIs available, then it'll be a little easier. With kind regards, Michel

From UD perspective, we have not been given any information on their new products (including the PLM). So, at the moment, our working assumption is that none of their new products will work with ISY/Polisy. And, given all that's on our plate with our existing contracts, I am not so sure we will have the bandwidth to support new INSTEON products in a timely manner. But, then again, perhaps that's SmartHome's goal to begin with. And, it's entirely up to them to decide ... With kind regards, Michel

@GaryK4, Thank you. Usually 403 errors are due to missing files. So, if you have replaced the SD Card, and you mentioned that you uploaded insteon_5.3.0.zip, then everything should work. With kind regards, Michel

Hi @GaryK4, Did you upgrade ISY firmware from ISY Portal? With kind regards, Michel

@larryllix, Partly but all the testing is done via Admin Console so that we can make sure all features are working. @cosyn, yes and very impressive! Only if we could build vaccines like computers ... With kind regards, Michel