Michel Kohanim

Hi johnradams, I did read your whole post ... I agree with you about the documentation and, as I had mentioned to you on our email exchange, we are working on it. The process is rather slow. MarkJames, I want to thank you as well. With kind regards, Michel

Hi Simon, I do not think you are going to have any problems. There has been 3 reported system crashes using 2.7.15 and they all have two things in common a) a Gigabit switch and b)MobiLinc. We are trying to figure out whether or not these are causes or just coincidence. With kind regards, Michel

Hi Chuck, Thanks and no, this is not one of the bad ones! What ISY firmware version are you on? Can you verify if you have this problem whether or not the load is ON for this device? i.e. what happens if you turn off the switch and then query and/or try programming it? With kind regards, Michel

Hello nickoonce, Unfortunately INSTEON APIs do not give us access to that. aLf, I have not seen any! With kind regards, Michel

Hello hart2hart, Can you tell me what errors specifically? Thanks so very much. Hi mcmcomput, Can you tell me the model/firmware version (as reported by the Admin Console) for these devices? Also, are they in any other scenes? With kind regards, Michel

Hello sperok, I do not think kingwr's suggestion is going to turn ON the lights that are already off. Sending Dim commands to devices that are already off has no impact. With kind regards, Michel

Hello agent0014, Apologies for the inconvenience. In all likelihood, your router issues a different IP address to your ISY and thus breaks its own UPnP forwarding rules. For the most robust installation, it would be best if: 1. You assign a static IP address for your ISY (or make a DHCP reservation in your router) 2. Do not use File | Enable Internet Access (actually Disable it before doing anything else) and instead create the port forwarding rule manually in your router You fill find more details in here (under Configuring Non UPnP Routers). With kind regards, Michel

Hello nikoonce, Here's the link to our developer section: http://forum.universal-devices.com/viewtopic.php?t=2321 All events published from ISY are in XML and thus your program can append them to any file/database as you wish. With kind regards, Michel

Hi Chuck, What does the Admin Console report for the version of this Switch? If v35, then rest assured the problem is the switch itself and that it must be replaced. With kind regards, Michel

Hi Illusion, Thanks so very much. Would you be kind enough to send me your log (tech@universal-devices.com). Also, do you use a Gigabit switch/router? With kind regards, Michel

Hi Illusion, Apologies for the inconvenience. This issue has been reported twice and in all cases it involves MobiLinc. We are going to aggressively try find the root cause and rectify as soon as possible. I would appreciate it if you could (if you remember) outline the steps that were taken before the crash. With kind regards, Michel

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