Michel Kohanim

@LFMc, CA is following through with the same unwise decision (personal opinion). Real time energy information is key for all permutations of Green. Now, something that didn't require any installation, requires CTs and professional installation in the breaker panels (CTs) or complete replacement of the breaker panels (Span.io). With kind regards, Michel

@ddimit, Thank you for submitting the ticket. With kind regards, Michel

@IT Solutions, why would have two programs anyway? Choices a) what @DennisC suggested and b) use high > temp or low < temp (this way, both are handled by the same program regardless of which one comes first. With kind regards, Michel

@robandcathy1, It's very important to a) have a good mesh with non battery operated devices and then follow these steps: - Make sure all Z-Wave devices have been added and placed in their desired physical location - Do right+click Z-Wave | Update Neighbors on all non-battery devices (i.e. devices that never go to sleep) - Do right+click Z-Wave | Update Neighbors on any devices that are still having trouble communicating with the ISY With kind regards, Michel

@IT Solutions, ISY is not procedural. ISY is event based. And, the events are handled in FIFO manner. So, if A happens before B, then the program that depends on A is evaluated before the program that depends on B. With kind regards, Michel

@PFatuova, Please make sure you don't have green/gray 1011 icons next to any of your devices. If you do, please right mouse click | Write update to device. With kind regards, Michel

@Kentinada, Unfortunately not since they are described in INSTEON protocol specs and we cannot get very detailed. A high level description is here. With kind regards, Michel

Hello all, Can we please cool it down. No Ad Hominem attacks please. @IT Solutions, as I mentioned before (and as @lilyoyosuggested) unfortunately we don't have any plans for automatic backup. If this is a hard requirement for you, then - as others suggested - you can either use Polyglot backup node server or develop your own (it's not that difficult). With kind regards, Michel

@MrBill, Init values are stored on the SD Card, backed up, and restored. With kind regards, Michel

@stephan, If you know how to access ssh, please do: curl -s https://my.pkg.isy/script/update121.sh | sudo bash If not, please submit a ticket and we'll help you. With kind regards, Michel

@IT Solutions, Variable values? Or Variables? The former is meaningless since, if you restore a backup from yesterday, those variable values mean nothing. If you are talking about variables themselves, of course they are backed up. The short answer, we have no plans of supporting automatic backup in the near future. With kind regards, Michel

@IT Solutions, would you please stop double posting in different forums? With kind regards, Michel

@IT Solutions, There's no need to auto backup daily because configurations are static. Once you are done with your configurations, back it up. With kind regards, Michel

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

@dharvey, There are no errors in the Event Viewer for that device (2F BC 96). Do you have any Adjust Scene in programs? With kind regards, Michel

@tmorse305, I replied to your ticket. With kind regards, Michel

@paulw, You can add ISY's URL to your ISY Launcher. Please click on the Add button and enter the URL without the path. (i.e. http://1.2.3.4). With kind regards, Michel

@IT Solutions, Ends. With kind regards, Michel

@IT Solutions, Not necessarily. But, they might be close to each other. With kind regards, Michel

@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