Michel Kohanim

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

Hello Baypointe, The Floorplan does indeed expand the tree but you should see another dialog. Please note that we have not done anything with the Floorplan for more than 3 years now and it shall be removed in one of our future releases. As far as intermittent issues, I think it would be best to setup a call with our tech support team rather than going back and forth on the forum. Since the log shows that the status changed (system means that the device sent a response to ISY), then I suspect that the device is sending something to ISY on its own. This means that the device has been linked to ISY. So, what you need to do is to figure out to what devices is this device linked. j0dan, 3.1.8 or 3.1.9? With kind regards, Michel

robandcathy, Please upgrade to 3.1.9 as soon as you can. 3.1.6 had some bugs including a corrupted backup ... so, if you have a backup from 3.1.6, it's corrupted. The reason you see those errors is because Java has not been configured for your browser. You may want to use the application: http://www.universal-devices.com/99i/admin.jnlp With kind regards, Michel

Hi Tim, I am not sure what you are doing but something is quite amiss! The error says that you are trying to access the SSL port (443) using HTTP. What URL are you using? Have you reconfigured your network? You might want to try our website URL for the current firmware version you have in your ISY: http://www.universal-devices.com/99i/[version]/admin.jnlp If you have our official 2.8.16 release, you can simply remove the version from the URL. With kind regards, Michel

polexian, Finish does the same exact thing. In all cases, we have to take the PLM out of linking mode and we wanted this to be explicit by forcing the use of the Finish button. Moshe/rlebel, would you please let me know: 1. Which iPhone application you are using? 2. Do you have this problem locally or when on 3G? With kind regards, Michel

Hi polexian, Yes, I did! X should NOT close that dialog. Only clicking the Finish button should. If clicking the Finish button does not close that dialog, then there is a bug. This said, based on your previous problems with the Admin Console, I still think you have a conflict with previous version of Admin Console. I strongly recommend clearing your Java Cache and then going to http://www.universal-devices.com/99i/3.1.9/admin.jnlp . With kind regards, Michel

Hello ELA, I guarantee you that the problem is firewall and, in 99.99% of the cases, the filters applied by the firewall are NOT removed even if you disable the firewall. What we need to do is to put ISY's IP address (or URL) in the trusted zone/whitelist for Avast. As far as the other question, there are two types of information: 1. Configuration such as nodes, system/network config, etc. which are PULLED by the Admin Console from ISY. This will not pose any problems to the firewall 2. Status updates (things that might change frequently) which are PUSHED to the Admin Console in which case the firewall might block it since it might consider it as an attack With kind regards, Michel

Hello all, sincere apologies for tardy reply. ELA, please do contact our tech support and let us help you get unfrustrated! The problem is firewall blocking ISY from sending updates to the computer. As far as the program not running, that's a little more serious and it would really help if our tech support team can log into your system and see what's going on. Tim, are you still having issues with WOL not being sent? I did a quick test and it works fine here. As far as the errors, it does not make sense because we now log authentication errors only if the attempt is greater than 1. Who is 192.168.0.167? Is that DSCLink? io_guy, do you always send the userid/password with every request from DSCLink? With kind regards, Michel

Hi polexian, Thank you. This does not make sense unless the computer was trying to use the old version of the UI. Would you be kind enough to let me know which URL you use to access ISY? With kind regards, Michel

Hi Joe, Thanks for the update. I am a little confused, the only way to remove the PLM is through File | Remove Modem (PLM). Are we talking about the same thing? Or, did you have the HouseLinc PLM (or some other PLM) linked to ISY? As far as statuses disappearing, you mention HTML. Are we talking about our HTML page OR are we talking about the Admin Console? With kind regards, Michel

Hello LeeG, thanks so very much for the clarification! Teken, the reason you are not seeing the status of devices at work is probably because you either have corporate firewalls or a software firewall which blocks ISY from publishing events to your computer at work. Do you know what type of firewall you have? With kind regards, Michel