Michel Kohanim

Hello aLf, The first issue is normal: you can only control scenes by clicking on the scene itself and then choosing on/off etc. I am not sure I understand the second issue. Would you clarify please? With kind regards, Michel

Hi killervette, Unfortunately, at the moment, it has to be a real INSTEON device. With kind regards, Michel

Hi Steven, You can use From/To. i.e. From Sunset (+/- offset) To 12:00 AM (next day) With kind regards, Michel

Hello Steven, You can read device configuration upon registering the device in ISY. In the add device dialog, you have 3 options: 1. remove existing links ... none of the device configuration is read 2. add devices found in links ... it only adds devices that are found in the device configuration 3. import existing links ... this will try to recreate all your established scenes and configuration From experience, I can tell you that it's much easier, safer, and less time consuming if you configured everything in ISY. Depending on how you have configured your devices, there might be some missing/phantom links which could cause major problems later on. With kind regards, Michel

Killervette, Currently, the only way of doing this is to assign one of your INSTEON/X10 devices as a variable: 1. In ELK, create rules that turn on/off that device in ISY 2. In ISY, create programs that based on the status of that device, a Network Resource is activated Do you already have the Network Module? With kind regards, Michel

Hello narenpublic, I do not know if you can bridge two different power grids (most probably you are going to have phase issues). You can have as many ISY's as you would like on the same network. The only caveat is that you must use the /99i/admin.jnlp so that you can choose between them otherwise (/99i) will bring up the Admin Console for the first one found on your network. With kind regards, Michel

Hello, I do apologize for the inconvenience and the time wasted. At this point, I think it would be best to setup a call with our Tech support team. This way, we can login to your system to see what's going on and perhaps reduce the time you spend on getting things to work. With kind regards, Michel

Hello Bonanza, Please see my comments below. With kind regards, Michel 1. For this to work, you have to make sure that your KPL version is above 1.60. Older KPLs did not allow for the sub buttons to control the load 2. Please make sure your KPL button is in toggle mode 1. Please make sure that your KPL is not in the non-toggle mode (it only sends off). Try the Button Toggle button at the bottom of the screen for that KPL to make sure they are in the toggle mode 2. Click on the KPL button in that scene, and make sure the on level/ramp rate for all other responders in the same scene are set properly. Please note an on level of 0 causes the device to turn off regardless of the command it receives 1. If you have 99 PRO series, please make sure that you are in automatic mode and not batch mode. In batch mode, all pending device operations are batched up 2. Otherwise, I would suspect signal/noise issues. Please try querying the device to see if it responds properly I think this is a defective switch

Hello Dennis, Please do send an email to sales@universal-devices.com and we'll figure something out. With kind regards, Michel

Dane, In addition to Brian's suggestions, it's quite possible that the device you are trying to link is already registered in ISY: 1. Go to My Lighting 2. Click on the Address Tab in the table 3. Make sure that the device you are trying to add is not already listed With kind regards, Michel

Hi fuzzersteve, I do not think the switch can go bad so quickly. I think you may have communication/noise issues. Do you know what type of load is connected to the switch that failed? Is it possible to switch the loads between the two switches? This way, if the problem moves to the good switch, then we know that the problem is load related. Otherwise, it could be the switch. With kind regards, Michel

Hello, 140000 means DNS error and it usually happens when your ISP is down or the DNS server is not accessible. With kind regards, Michel

Hi Jacques, Unfortunately, you cannot have other controllers in the same scene since sub buttons can only follow controllers. As such, you will have to revert using the button groupings. With kind regards, Michel

Hello nedsmith, Please do be kind enough to peruse the following document: http://www.universal-devices.com/mwiki/ ... Thermostat If it still does not work, you would have to make sure you have Access Points in the vicinity of your thermostats to make sure you have RF coverage. With kind regards, Michel

Hi mitch236, Yes, it does .... With kind regards, Michel

Hello all, Apologies for the inconvenience. There was a difference in the plug (2.0 mm vs. 2.1 mm) between 26 and one of the batches of 99i. If your power supply does not fit, please send an email to sales@universal-devices.com and we'll send you an adapter free of charge (using USPS). With kind regards, Michel

Hi Jeff, If you do not mind testing a build, please do send an email to tech@universal-devices.com ... it would be great to have more than one instance being tested. With kind regards, Michel

Hi kingwr, Three ways: 1. Click on the rename menu and you will see the address 2. Topology 3. http://your.isy.ip.address/rest/nodes With kind regards, Michel

Hello sk8er02, Thanks ... based on your logs, it's a guarantee that everything starts when ISY cannot contact WeatherBug and from thereon things get successively worse. I am going to add more constraints to the module infrastructure and, if you don't mind, let you try a different build. If amenable, please send me an email to tech@universal-devices.com . With kind regards, Michel

Mr. Allen, First off, when you replace the battery you MUST do a query on the low bat node to have ISY reset that status. You can use either status or control since when the low bat signal is sent, it does NOT change till you change the battery and query the low bat node. With kind regards, Michel

Hello Mr. Allen, Long time no see. All you have to look for is the name of the node associated with your Motion Sensor Low Battery and status of 100%. If you use Excel, you can simply filter everything out by name. With kind regards, Michel

Hi Robert, Currently, there are only two ways: 1. Send an X10 code from the one linked to the switch and have a program in the others to sense that signal and do an all off 2. Use network resources to do the same ... for this, you have to make sure your ISYs have static IP addresses: a. the master ISY should have network module b. in the program for the master ISY, create a resource to: http://your.isy1.ip.address/nodes/[the all off scene address]/cmd/DFOF http://your.isy2.ip.address/nodes/[the all off scene address]/cmd/DFOF c. In the resource, you want to make sure you use HTTP, GET, and add an Authorization header with the userid/pwd of each The first one is much simpler but X10 signals may get lost in the presence of all the traffic. With kind regards, Michel

Hello sk8er02, Thanks so very much for the update. Apart from Internet connection issues, do you have LAN connection issues? All the errors you posted are related to ISY not being able to either write to an outbound connection (to the Internet) or read from it. i.e. does the system still hang? With kind regards, Michel

Hi tome, Are you saying that even the LED does is not synched with the status of your sensor? With kind regards, Michel

Hello LarryC1116, First of all, apologies for the inconvenience. You should not have to do anything! We do use quality SD Cards and they should last years. The only thing I recommend is to make sure you have release 2.7.15 installed since we added CRC error detection which should help with errors communicating with the SD Card. If you are using your own SD Card, please do ensure that you use a new one and a good brand. With kind regards, Michel