Michel Kohanim

Hello jmael, This is a behavior that we have never seen before and thus it's quite difficult to diagnose remotely. My recommendations: 1. Go to Spotlight and type Java Preferences 2. In the Security tab, remove all certificates 3. In the Network tab, click on View Cache Files and remove each and every one If all fails, please do be kind enough to call our support so that we can log into your computer and see what's going on. With kind regards, Michel

Hello kyeck, For MAC, in most cases a reboot is necessary to clear Java cache files. Alternatively, you can click on View Cache Files and remove them one at a time. Furthermore, you have to make sure that you are going to the correct URL, in this case, http://www.universal-devices.com/99i/3.1.9/admin.jnlp (or directly to your ISY's IP address). With kind regards, Michel

Hello Gerard, Unfortunately we do not support this product and have no plans thus far. With kind regards, Michel

Hi j0dan, Thank you. As far as logs, you can see all network errors/warnings in the error log. As far as logging everything that happens, it's a delicate balance between performance and logging. We have kept logging event to the most essential events (in the logs and NOT error log). In any case, I think we may have found the issue. Moshe, polexian is correct. Please make sure that if you have setup a static IP address, that it can access the Internet. With kind regards, Michel

Hi raydoc, If you are still having problems please contact our tech support team so that we can find the source of these issues as they are not normal. With kind regards, Michel

Hello ergodic, Thanks so very much for the suggestions. I am hoping that 3.1.10 would help alleviate the subscription issues but I have my doubts ... do you have Avast? sanders2222, if you use the Admin Console or the Dashboard, closing it will log you off. If you are going to the HTML/Javascript page, then you are not actually logging in to ISY. You are just communicating with ISY and sending your credentials with each request. That's why when you are remote, we strongly recommend using HTTPS. With kind regards, Michel

Hello easytim, Welcome! Unfortunately ISY does not work with any of the U (for USB) versions. You need 2413S + a power supply. With kind regards, Michel

Hello jpjoe, Has the RemoteLinc already been registered in ISY? I do not think the problem is the PLM but the signal NOT reaching the PLM. The best test would be to plug an Access Point right into outlet where the PLM is plugged into and then try registering your RL very close to the Access Point. If this works, then the problem is that the signals are not getting to/from RL. With kind regards, Michel

j0dan, Ok, now we need a little more specifics ... what do you mean by "accessed often"? How is it accessed? Accessed to query? Accessed through programs? Accessed physically? Is it the same exact bug where you lose the where the .REC become empty? What do you mean by "BETTER LOGGING" ... what was missing and what did you expect? Next release hopefully by the end of the week. With kind regards, Michel

Hello mb323, That's quite odd. The only thing I can think of is that Java is using old certificates. Would it be possible to copy/paste the output in Java Console? If not, please try removing all the certificates in Java Preferences | Security and retry. Please do make sure that you ACCEPT when you are asked whether or not you want to trust Bouncy Castle and Universal Devices. With kind regards, Michel

Hello handyman300, We are looking into subscription issue. The SSDP issue is related to MAC's firewall blocking UDP traffic. Perhaps we'll disable SSDP (UPnP) on MAC. Above and beyond the initial dialog, that error is completely benign. Hello CopyRon, can you explain what you mean by fail? Does it mean that they do not report their status? BrianH, you are 100% correct. Those errors can be ignored completely. With kind regards, Michel

Hi matapan, It's quite possible that your new security settings are blocking traffic to port 80. With kind regards, Michel

Hi Bondo, Possible but I cannot guarantee. We need to release a few bug fixes immediately which we cannot put on hold. We'll do our best. With kind regards, Michel

Hi Tim, Thanks so very much for the update. Please do keep us posted with Motion Sensors! With kind regards, Michel

Hi matapan, localhost is how "your computer" refers to itself. So, you cannot use localhost as the host to which network resources are directed since localhost for ISY is ISY itself. What you need to do is to provide the IP address for your computer as the host parameter. With kind regards, Michel

Hello all, handyman300, is it always the same devices that have the communication errors? If so, then we will have to figure out what's causing the communication errors. bocarob, please note that only one firmware version of 2411T works with ISY ... if you have their latest firmware, please do be kind enough to contact SmartHome and request that they send you one with firmware that works with ISY. If you have any problems, please do be kind enough to contact us (support@universal-devices.com) and we'll get that taken care of for you. BrianH, it seems that for some reason the initial subscription is not successful. We'll take a closer look and see what's going on. j0dan, we are working on it. With kind regards, Michel

Hello mb323, If you cannot use https locally either, then the problem is that you need to reinstall an SSL Certificate (Help | Request/Manage SSL Certificates). With kind regards, Michel

raydoc, Please do ensure that you have either our official 2.8.16 OR 3.1.9 installed. With kind regards, Michel

Baypointe, If you originally chose the 3rd option to register your device in ISY, then ISY maintains all those links that were inside your switch and every time you restore, ISY will restore them. The best thing to do is to remove your switch from ISY, do a factory reset on it, and then add it back to ISY using the first option (remove existing links). rlebel, The warnings (file open) are completely normal. If there are no reports of the activity in the log, then the problem is between devices and ISY is not a party to this behavior. In short, all device activity is logged in the log. As far as MobiLinc, there's a known issue with 3.1.9 and synch with MobiLinc. This has already been fixed and shall be included in 3.1.10. If you cannot control your devices via 3.1.9/MobiLinc, then we will need to make sure Wes is made aware so that we can diagnose and fix the problems. With kind regards, Michel

Hello j0dan, I am almost certain the problem is related to scene adjustments OR a defective SD Card. Did we try sending you a new SD Card to try? Unfortunately I do not think we would have enough time to do both (find the bug and allow for individual link records to be restored) within the same release as it would dramatically increase regression testing time. Please do let me know if disabling those programs helped at all. If not, then I would have to suspect a corrupt or defective SD Card (but that would not make sense since the problem is always the same devices which are in those programs). I am hoping to have a better understanding of our next release date by upcoming weekend. Sincere apologies for all these problems ... I know how frustrating this has been. With kind regards, Michel

Hello kaisersoze, Sincere apologies. Please do be kind enough to send your UUID (and your name by which you purchased the module) to sales@universal-devices.com and we'll reactivate it for you. With kind regards, Michel

Hi Tim, Make sure ISY has two DIFFERENT ports used for HTTP and HTTPS. The rest is done at the router. With kind regards, Michel

Moshe and skisteep, The problem has been identified and we are trying to fix it as we speak: MobiLinc is using UPnP to find ISY on the network and we have reduced the limit on UPnP packets. As such, in some cases, MobiLinc will not be able to find ISY. In the meantime, you can set ISY's local IP address in MobiLinc. j0dan, I am so very sorry to hear. I am quite unsure what to think of the garage door opening ... that's quite serious. There's just one more path that we are going to review and hopefully this will fix the issue. With kind regards, Michel

Hello gwarthur, ISY comes equipped with HTTPS (under Configuration | System | Network) the default port of which is 443. If you wish, you can change this port to anything between 2000 and 65535. Devices that support HTTPS must have SSL stack inside. If your device does not support HTTPS, then you cannot use it securely. With kind regards, Michel

Hi Tim, You cannot change the regular port (80) to (443) which is used for HTTPS. What you need to do is factory reset and then restore your backup. With kind regards, Michel