Michel Kohanim

Hello nickoonce, As far as logging interval, in V2 thermostats, the dongle sends change of state and ISY logs if and only if the status has changed. ISY does not log WB data simply because the data points are way too high. You can certainly write a program which subscribes to ISY and you will receive ALL the events including those of WB. JSDK (Java SDK) and WSDK (Web Services SDK) both provide you with sample applications that can receive ISY events. With kind regards, Michel

Hi Eric, Failed writing high watermark means that ISY could not write the record in the motion sensor's database. This is due to communications errors. You should not see any traffic when you click the set button unless the motion sensor has already been registered in ISY. With kind regards, Michel

Hi mitch236, Repeat only repeats all the statements immediately following it (not before it). With kind regards, Michel

Hi mitch236, For SWLs, as far as I remember, 40 was the starting version which supported the LED brightness. What are the firmware version of those that work? With kind regards, Michel

Hi Bernhard, Please do ensure that you have 2.7.15 installed. You will find developer links here: http://forum.universal-devices.com/view ... 7334#17334 You would want to download the latest JSDK. With kind regards, Michel

Hello Bernhard, that makes sense. What you really need is to use either JSDK or WSDK to subscribe to ISY events. This way, when the programs change, you will be notified of the change and then you can reload them to get the correct id for the program. What programming environment do you use in your server? With kind regards, Michel

Hi gadgetfreak, I am not going to feign expertise in X10 but I can offer my experiences (and some theory): - X10 Phase couplers do not let INSTEON traffic through - X10 boosters do cause interference with INSTEON in some cases. The only way to know is if you unplug/test/plug back in/test again I do not think you have missed anything in bridging the phases using the Access Points. With kind regards, Michel

Hi someguy, I have not seen those so they must be pretty new. If they support the beep function, then you should be able to use it in program. With kind regards, Michel

Hi Bernhard, The main question is: what's your ultimate goal? As far as being notified of changes to IDs, our WSDK/JSDK both provide events which let you know that something changed. You will have to subscribe to ISY to get those events. With kind regards, Michel

Hi gadgetfreak, Thanks so very much for the detailed report. I do understand your concerns ... so let's try and figure out what's causing all the noise. If at all possible, the first thing I would want to do is to swap the locations of one of the non-responsive KPLs with one that works properly. If this causes the problem to remain isolated to the bedroom, then we know the problem is noise/signal strength/neutral wire. If the problem stays with the non-responding KPL, then we know that the KPL is defective. As far as old X10 devices, I have seen (only in some scenarios) that X10 repeaters may cause INSTEON signal issues. As such, you may want to disconnect, check, connect, check again to see their impact. Now, as far as isolating noise/signal strength issue: 1. Make sure that the neutral wire is securely connected ... this is very important 2. Make sure that your Access Points are actually bridging the phases 3. Unplug the load from the problematic KPLs and see if they start responding. If they do, then we know there's something wrong with the load With kind regards, Michel

Hello Bernhard, Unfortunately you cannot add an X10 device to an INSTEON scene. You still need to use programs to control your X10 devices. With kind regards, Michel

Hi richardl007, For some SWLs, 0 is full brightness (unfortunately). Would you please try 1 and report back. With kind regards, Michel

Hello gadgetfreak, At this point I must confess that I think you have signal strength problems. i.e. the signal is not getting from the PLM to your bedroom KPLs and nor do the signals from your KPL are getting back to the PLM (and thus the blinking). Do you happen to have any SWL version 35s in your system? If so, this could explain the behavior somewhat. I do recommend using INSTEON native functions (putting the KPL buttons in a scene) as much as possible. With kind regards, Michel

Hi Illusion, Thanks so very much for the update. We are well aware of the automatic update issue and thus the recommendation to use https. That's another one of those MAC specific networking issues which is not the same as Windows/Linux. With kind regards, Michel

Hi someguy, SWL versions 40 and above (those with the beep feature) and dual band LampLincs and some newer version of KPLs are currently the only devices that support the beep command. All it does is a beep the duration for which is adjustable. Some may not honor the duration though and we have yet to figure out the exact values for those. So, in short, it will be a trial and error routine to figure out the beep duration. With kind regards, Michel

Hi Eric, The second message is OK; it simply means that ISY got duplicate messages from the motion sensor and ignored one of them. On the ones that you cannot link, may I humbly recommend doing a factory reset on it and retry. If it fails again, I must assume a defective (or low battery) motion sensor. With kind regards, Michel

Hi Eric, That's correct. Is it possible that your Motion Sensor is not near an Access Point? Also, please do ensure that Link Management | Advanced Options is set to Automatic. You may want to try the Event Viewer on Level 3 to make sure that you get a response back from your MS (i.e INST-SRX for each INST-ACK). If not, then surely your Motion Sensor is either not near an Access Point or the battery is low. With kind regards, Michel

Hi Eric, No ... you cannot link them as you would other INSTEON devices. What you need to do is to use Add New INSTEON Device and then choose the Motion Sensor from the list. With kind regards, Michel

Hi Jeff, Thank you. Would it be possible to connect your ISY directly to your router and let me know if that helps the issue. If it does (i.e. if everything works for a week or two without a problem), then I would like to send you a replacement unit to try. In the meantime, we would try everything we can to reproduce this issue (alas, not successful thus far) so that we ascertain where the problem comes from. With kind regards, Michel

Hello Jeff, Apologies for the inconvenience. 60001 means that ISY couldn't resolve the DNS entry for the NTP time server. Although I think these are related but I think the 60001 is the symptom of ISY not being able to get to the Internet. Looking at the code, the only reasons setting NTP time would happens so often are limited to: 1. NTP synch interval is set to a low interval (9 seconds in your case) 2. The IP address for your ISY changes every so often OR ISY is not able to renew its DHCP address So, I have the following questions: 1. What's the NTP synch interval in your system? 2. Do you use DHCP for your ISY, and if so, what is the lease time? 3. Is your ISY connected to a switch (is it a GigaBit switch) or directly to the router? When you have this error, do other programs work (those that are not network related)? With kind regards, Michel

Hello sfhutchi, Unfortunately INSTEON spec does not allow you to use the local ramp rate for the scene ramp rate. i.e. devices participating in a scene respond with the scene ram rate. If you want to use the local ramp rate, you must address the device specifically and not within a scene. With kind regards, Michel

Hi gadgetfreak, If noise, then the process is a little arduous. Basically, you must turn off suspicious devices (plasma tvs, battery chargers, CFLs, etc.) one at a time to see which one is causing the noise. And, once found, you will have to put that device on a FilterLinc. With kind regards, Michel

Hi Bernhard, Long time no see!!! Ok, the first thing I recommend is to checkout either of: TouchSwitch: http://forum.universal-devices.com/viewforum.php?f=49 ISY AJAX: http://forum.universal-devices.com/viewforum.php?f=55 In short, what you need to do is to use Javascript, retrieve all the nodes (by going through /rest/nodes), and then let the Javascript interact with ISY and the user with Javascript. With kind regards, Michel

Hi jwagner010, that's quite strange and thanks for reporting it. Would you please keep an eye on it and let me know if it happens again? gkouri, please try https://your.isy.ip.address as the URL and retry. justin.cool, yes, you do have the correct thermostats (firmware version>=91 is V2). With kind regards, Michel

Hi gadgetfreak, Thanks for the answers ... they will make the troubleshooting much easier. First of all, 11 seems way too low of a record count for the number of devices/scenes you have. So, the first thing I suggest is to do a File | Restore Modem (PLM). After you are done with this, check the record count again and make sure it's more than 11. For your installation, assuming 6 button KPLs, and 9 other devices, you should have at least 25 records in your PLM. Now, based on the scene test results, I do think that you have some signal issues as well. The first thing I recommend is to plug in one of the ApplianceLincs which fails right into the same strip as the PLM. If this solves the problem, then we would have to figure out if the problem is signal strength or noise. To test signal strength, if you have any Access Points, plug it right on top of the PLM and retest. If that does not help, then the issue is noise. With kind regards, Michel