Michel Kohanim

Hello pitbull5.0, I am so very sorry to hear. This problem is mostly caused by a firewall software on your computer not allowing ISY to publish events to the Admin Console. If you have a firewall software, please do make sure ISY is in the trusted zone/whitelist/exclusion list and then: 1. Reboot ISY 2. Retry launching the Admin Console If you are still having problems, please do not hesitate to contact our support team (links below). With kind regards, Michel

Hi WhiteSax, Indeed very clever and I do apologize for plagiarizing your idea: based on your input, we just added BEEP action to scenes in 3.3.1. On the bright side, you can get rid of your network resources! Thanks again and with kind regards, Michel

Hi jmed999, This means that the Admin Console could NOT connect to your ISY. This happens in the following cases: 1. ISY is no longer on line or perhaps the IP address has changed 2. Your firewall is blocking the Admin Console from making an outbound connection With kind regards, Michel

Hi RichT99, Almost ready and should be there in our next release (3.3.1) either today or early next week. With kind regards, Michel

Hello P805, Is this with the default ISY interface? With kind regards, Michel

Hello zeenon, I am so very sorry to hear. Please do the following: 1. Telnet to ISY (http://www.universal-devices.com/mwiki/ ... o_Your_ISY) 2. Login using your credentials 3. At the prompt, type: RF /CONF/XXXXX.REC where XXXXX is the file that ISY is complaining about 4. Do the above for all files for which you have problems All this said, I am a little worried that may have a corrupted file system and/or SD Card. So, before you reboot, take a good backup and make sure you keep it somewhere safe. With kind regards, Michel

Hello timdenike, I am so very sorry to hear. If you don't mind, would you be kind enough to activate Java Console (Java | Advanced | Show Console) + Enable Lifecycle debugging/trace and then try again. If there's an exception, please do send it to support@universal-devices.com. With kind regards, Michel

Hi daxiang28, Do you get a completely blank message? With kind regards, Michel

Hello hspindel, You will have to activate the scene to which both of these devices belong for both to respond. In programs, scroll down and choose Beep. With kind regards, Michel

LeeG, As always, you are so perceptive and, I - well - I guess I am blind! You are so right: those FF devices are X10 devices in which case they should not even have any .REC files associated with them. There was a bug in older releases where these would show up but they should not appear in 3.2.6. Thanks again LeeG! With kind regards, Michel

Hello jmed99, What mode are you using. I suspect that you may want to use the latch mode but I cannot be sure (it depends on your garage door). With kind regards, Michel

Hello clyp, These are configuration files for INSTEON devices. The fact that ISY cannot open them means that basically ISY would not know how to respond and/or communicate with them properly. Nor would you be able to modify them in a scene. Can you tell me: 1. Which firmware version do you have? 2. Have you had any power outage? 3. Have you restored a backup from a 3.1.6 release? For faster response, it would be best to send your response to support@universal-devices.com. With kind regards, Michel

Hello osurh18, The first thing I suggest is to go to http://whatismyip.com and make sure your IP address has not changed. Also, did you manually configure your router for remote access or did you use File | Enable Internet Access. If the latter, then you will need to redo it. With kind regards, Michel

Hi LeeG, thanks so very much for all your help and precise instructions. Hi Braq, as LeeG mentioned, the main issue is that the device is not responding to Link Begin. All I2CS devices require this method to link. The reason you can no longer talk to other devices is because the PLM is in Linking mode and will not get out of this mode for about 4 minutes or till ISY hears a Link Response. Quick questions: 1. Do you have any Baby Monitors around? 2. Do you have any thermostats around? With kind regards, Michel

Hello mikeyngo, Numbers 1-3 are correct. Apart from that, I think it would be best if you contacted Autelis directly to see what they need. Unfortunately I do not know much about Somfy products but I am certain Autelis can help you figure out exactly what you need. With kind regards, Michel

Hello mikeyngo, No problem at all ... these things tend to be confusing. What you need is Network Resources Module (Help | Purchase Modules on the Admin Console). Once you have that, then your ISY can communicate with Autelis (as per their instructions). Once integrated, then you can use ISY programs to do anything you wish including having one of your INSTEON devices control the shades and/or use the web interface to control your shades. With kind regards, Michel

Hello swbrains, IES used to work with ISY but I am not sure of the status now. Have you contacted Howard at IES? Above and beyond IES, I am not aware of any other touch panels. With kind regards, Michel

Hello bipto, Thanks so very much. For that button in the Admin Console, if you keep on clicking it, does the status change in the Admin Console (only for that node) from on to off and vice versa? With kind regards, Michel

Hello bipto, It seems that your buttons are being activated as non-toggle (you can only send ON and not OFF). I am very sorry to have to ask this question: are you certain you were following the instructions for toggle mode. With kind regards, Michel

Hello RussD, THANKS so very much! With kind regards, Michel

Hi mikeyngo, The link BrianH sent you works with RF Somfy systems/ISY. Also, Autelis has a solution: viewtopic.php?f=78&t=8816 With kind regards, Michel

Hello flemingmike, Pro and non-Pro version use the the same exact code base and thus I really do not think the problem is related to the upgrade. What happens if you unplug the PLM and then plug it back in? With kind regards, Michel

Hello jmed999, Apologies for tardy reply. Ignored messages are completely benign and acceptable (ISY is just letting you know that the device sent the same message twice which is always the case for RF/dual band devices). And, I would not worry about the Ack error. What I would worry about is that you have only one hop left between messages. This indicates that the signals keep hopping between devices and never reach their destination. The main questions are: 1. How many phases do you have? 2. Are you certain that the phases are bridged properly? 3. How big is your venue and how many devices in total do you have on each phase? With kind regards, Michel

jmed99, I meant that those errors you see in the event viewer might actually mean: got two ACKs for the same device. Are these RF/dual band devices? With kind regards, Michel

Hi brausse, Verified as a bug and it's already fixed. The problem happens with ST of 0 and 255 only. With kind regards, Michel