Michel Kohanim

Hello apostolakisl, We will look into it ... it's surely a timing issue. With kind regards, Michel

Hello IM, Thank so very much for the feedback. I will have to defer this one to the Guru himself! Hi apostolakisl, unfortunately there cannot be a tutorial since all we have is what we got from SmartHome: level for On and level for Off. And, On is a function of Off. It would be ideal if someone with a lot of time on their hands could come up with a permutation of all the on/off value pairs and their impact on the backlight. With kind regards, Michel

Thanks Illusion. With kind regards, Michel

Hello Illusion, Can you try the 3.1.7 UI and let me know if you have the same issue? http://www.universal-devices.com/99i/3.1.7 Please note that you do not have to upgrade the firmware to test the 3.1.7 UI. With kind regards, Michel

Hello j0dan, LeeG is 100% correct. This said, the internal ISY .REC file stores some of those values (such as LED brightness) in the same .REC file. As such, I still think that the problem is not necessarily LED brightness but how we handle multiple tasks trying to update the same .REC file. With kind regards, Michel

Hello LeeG, thanks so very much for the help on V2 Motion Sensors. I am not sure what to think of v2 motion sensors because this exact behavior is reported multiple times. Mine works fine but there are many others that do not and factory reset works only part of the time (so, rlebel, you are one of the lucky ones!). wuench, sincere apologies: all WSDL files are in ISY's /WEB directory. You can also find them under: http://www.universal-devices.com/developers/wsdk/[version]/ ... where, for 3.1.7, version is 3.1.7! j0dan, 1. I do not think it's the LED brightness issue but some type of resource conflict when two tasks (for instance the reader tasks and the program task, working on the same database) 2. Yes, INSTEON database records are stored in .REC files. You can restore those files but we do not have an automated way to do so except for copying the files into the SD Cards I must say that I am so very sorry for this problem and that we are hard at work to find a resolution for this. I do apologize. With kind regards, Michel

Hello Brian, I am so very sorry that somehow we lost your post. I do apologize. Can you please let me know the status and where you are with the problem? Hi Gunnersen, RL2 is not yet supported but it's high on our list. With kind regards, Michel

Hello j0dan, Unfortunately not that I know of. Of course, you could restore a backup and then restore devices but that's even more troublesome. For now, may I humbly suggest disabling those programs? We are actively trying to figure out where the bug is and fix it. thedishking, I do apologize for the inconvenience. Would you be kind enough to send your Error Log (Tools | Error Log) to support@universal-devices.com? There's a known issue where incessant DNS resolution issues may cause a system hang. With kind regards, Michel

Hi Charles, There seems to be two issues: 1. The certificate stored in Java is not the right one ... please go to Java Preferences and remove all Universal Devices certificates, clear your java cache, and then go to http://www.universal-devices.com/99i/admin.jnlp 2. Your system is using the wrong jar files and therefore it's not finding the correct resource bundles to load. I am hoping that doing the above will fix this With kind regards, Michel

Hello all, Currently known issues with 3.1.7 1. For PRO series, the batch and battery buttons do not show up for a while on the Admin Console 2. In case of too many successive DNS errors, the unit may hang With kind regards, Michel

Hi all, Currently known issues with 3.1.7: 1. For PRO series, the batch and battery buttons do not show up for a while on the Admin Console 2. In case of too many successive DNS errors, the unit may hang With kind regards, Michel

Hello all, sincere apologies for tardy reply. polexian, any further explanation to reproduce would be greatly appreciated. As far as config and admin/advanced, do you mean the Javascript interface or the Admin Console? If latter, can you please be a little more specific? j0dan, sincere apologies ... this is one of those issues that is not reproducible easily so we have to basically walk through the code and guess what could contribute to it. It seems that our guess was not correct ... back to the drawing board! rlebel, please disable Open ADR in the Electricity configuration panel. I do not think the Motion Sensor and this error are related. Once Open ADR is disabled, then we can figure out what's causing the error. mohansen, thanks for the error log. It seems that the system goes into a deadlock once there are too many DNS resolution problems. We are looking into it. With kind regards, Michel

Hello brianbhc, It all depends on the client used. Most browsers convert the user@xxx.yyyy.zzz to the proper header inside the HTTP header. If your client supports this, then the answer is yes. Otherwise, the answer is no: ISY doe not understand user@ URLs. With kind regards, Michel

Hello jpjoe, Yes, that's a correctly formatted address. The main issue seems to be that the PLM cannot communicate with the RemoteLinc. Is this regular RemoteLinc or RemoteLinc2? If the latter, then ISY does not yet support it and it will not work. If the former, would you please use Event Viewer on Device Communications level, retry, and copy/paste the output here? With kind regards, Michel

Hello cmerlino, Unfortunately ISY does not support non-toggle mode for IRLinc TX. With kind regards, Michel

Matt, I think you may want to use our 994 with integrated Zigbee. This way, ECM will publish its events to ISY. polexian, I cannot reproduce the IR issue. Can you please give me more details as to the use case? With kind regards, Michel

Hello hbsh01, My bad. It runs the If clause and if evaluated to true, then runs the Then clause. If the program is enabled and if the condition would cause it to run regardless, then the program would run and has precedence over Run at startup. Run at startup basically forces programs that a) might not have conditions to cause it to run at startup OR are not enabled to run based on their condition. With kind regards, Michel

Hello Matt, We have never tested this configuration. As I mentioned, EP1 must be in server mode (i.e. it will respond to requests and NOT push data) for this to work. io_guy, this is not anything you or your application doing that's wrong. It's our logging that has a bug: in http basic authentication, the client sends a request without userid/pwd and the server sends back the www-authenticate header. So, obviously, there will be at least one request without userid/pwd to ISY. We should log attempts of more than one and we are not doing that. This shall be fixed. With kind regards, Michel

Hi all, Thanks so very much for the feedback. Matt, you have to make sure EP1 is in server mode ... in most cases, the port is 5000. j0dan, we hope so. Tim, those are initial requests from DSC/WebLinc which come without userid/password. The code is already updated to log attempts of more than one. IM, that's a bug and it's already fixed. polexian, it might be a bug; it shall be verified and fixed immediately. I am hoping to have a minor release shortly to address these issues. With kind regards, Michel

Hello jpoje, You must use Link Management | Link a RemoteLinc. In the dialog, all you have to do is enter the address for your RemoteLinc. None of the other methods will work. Also, your RemoteLinc should be in programming mode: press and hold the Dim/Brt buttons for about 10 seconds or till the LED starts blinking. With kind regards, Michel

Hi apostolakisl/hbsh01, For those programs that have Run at Startup enabled, then yes, the Then clause is executed regardless of anything else (including enable/disable flags). With kind regards, Michel

Hello gwarthur, Did you change the HTTP port on your ISY? If not, do you use the same port for both Proliphix as well as ISY? With kind regards, Michel

Hi, Is your code subscribing to ISY? Have you tried 3.1.7? With kind regards, Michel

Hi Tim, Thanks; please do keep us posted. As far as port forwarding, you will find instructions here. If you have already done the same for SmartLinc, all you have to do is: 1. Change the port to 443 (regular httpS port) 2. Change the IP to point to ISY's IP address 3. Your remote URL would be httpS://your.remote.ip With kind regards, Michel

Hello all, Just wanted to let you know that Release 3.1.7 Beta is now available. With kind regards, Michel