Michel Kohanim

Hi robandcathy, Would you please try turning the load off on those devices and retry? I suspect that there is some type of noise not letting ISY communicate with those devices OR it might be that the devices are defective. I am sure our forum community is a much better source of help for your programs since we are basically not setup for it and our resources are limited. In any case, you are welcome to send a request to support@universal-devices.com and perhaps Rand or Darrell can help you on the side. With kind regards, Michel

Hi all, Apologies for a collective post: 1. robandcathy, you can add IRLinc TX in 2.7.11 ... they are just basically buttons that you add to your scenes 2. If you actually have SignaLincs (not AccessPoints) then that could explain the problems you are having communicating with your devices and that's why you keep getting the green icons 3. RLIKWARTZ, I am hoping to have 2.7.11 release before the end of the week and it will have solved the problem with RF devices With kind regards, Michel

Hi Mark, Unfortunately not yet. With kind regards, Michel

Hi sneumann, We look at the value in EventInfo.EventState element and use it as a "multiplier". So, you will have to first have the base price set in Configuration/Electricity tab. With kind regards, Michel

Hi upstatemike, This is a known issue in 2.7.8 and above. 2.7.11 should fix it. With kind regards, Michel

mearnhardt, As far as not seeing the other modules/configuration parameters, you will have to make sure to use either one of the following URLs (/99i would not work): http://isy http://your.isy.ip.address http://www.universal-devices.com/99i/2.7.7 As far as enabling Internet Access, please note that UPnP is not very reliable. If you could enable Internet Access before but can't anymore, may I humbly suggest try rebooting your router? With kind regards, Michel

Hi molepacker, This is a known issue with 2.7.6 and below. If you have not yet, please upgrade to 2.7.7 (extremely stable) or 2.7.10 (stable and feature rich). With kind regards, Michel

Hello Mr. Earnhardt, Please note that File | Enable Internet Access tries to configure UPnP enabled routers. It seems that you do not have an UPnP enabled router and thus the issue. Actually, it's much safer and more robust if the port forwarding rules are created manually in your router. This way, the settings persists even if the router is rebooted. The procedure is usually very simple: http://www.universal-devices.com/mwiki/ ... o_Your_ISY With kind regards, Michel

Hi stevehoyt, Just the fact that scene test fails (especially with all those access points) is enough for me to certain that the source of all the problems are the SWLs. Yes, you will have the correct status in the log. And, I really do not think you will need any access points as long as a) you use your LLs to bridge the phases correctly and you are certain they are not going to be unplugged. With kind regards, Michel

Hi Mark, Thanks so very much for the clarification. I totally agree ... there are NO problems whatsoever in supporting other CA certified certificates (except spending time and resources). All we have to do is to extract the p, q, mod, and exp out of the certificate. This is on our list and shall eventually be done. I just cannot commit to a date. With kind regards, Michel

Hi Mark, I am not sure what you are referring to since that's precisely what our utility does: it generates self signed certificates in X501 format and then submits it to ISY. Haven't you already tried this? With kind regards, Michel

Hi mitch236, ISY uses whatever is your external/ISP's IP address. If you have Dynamic DNS or a forwarding IP address which points to your existing router, then you should be OK. With kind regards, Michel

Hi David, Unfortunately not because we do not have access to the internal IRLinc database. We have been investigation what we could do to support this without making more trouble. Alas, and as you might have guessed, we've not been successful as of yet. With kind regards, Michel

Hi Steve, Thanks so very much for the update and your kind words about my wisdom! Based on what I see, I can almost assure you that once you replace the SWLs and remove some of the excess access points, all your problems are going to go away. I have contacted SmartHome and I am sure they will help you out. In the meantime, you might want to try the Scene Test. And, yes, ISY should have all the statuses reflected in the log. With kind regards, Michel

Hi Jeff, Would you be kind enough to send an email with this information to tech@universal-devices.com . I will see what we can do to support them. No, it's not as easy as formatting ... everything in the certificate is binary. With kind regards, Michel

Hi Jason, The problem is that the status of the motion sensor does NOT change till the internal timer turns is off. What you might want to try is Control instead of status. Control means every time ISY hears an On or and Off (regardless of the status of the motion sensor) then the program is re-evaluated. And, for testing purposes, it's always best to have a folder and separate this program in two: one for On and one for Off. This way you can actually see the status of the programs as they are being re-evaluated. With kind regards, Michel

Hi Steve, Thanks so very much for the update. First, I would like to know a little more about your sunset scene: 1. Do devices actually respond to your sunset commands? 2. Are you actually turning on/off a scene? 3. Is the status in ISY on when it should be off or the other way around? As far as query all, yes, indeed it does query every device for it status. Please note that there was a bug in the log which returned 0 for certain devices (when doing a query). And, unfortunately - and please forgive me - I really do not think adding more access points is going to solve the issue. Personally, I think adding more access points is going to cause more problems than fix anything. And, finally, I do not think anything would recompense for the issues relating to SWL 35. All this said, if you wish, send and email to tech@universal-devices.com and I'll see if I can help you get your SWLs replaced before spending more money on Access Points. With kind regards, Michel

Hi AnthemAVM, Currently, there's no way for this to work with ISY. Incidentally, this is a requirement we already track but with a low priority. Have you considered using free Dynamic DNS services? With kind regards, Michel

Hi kingwr, Yes, indeed this is an issue with the unit. It seems like you have file system/SD card error. I already have an email from you to which I am going to respond shortly with instructions for RMA. Sincere apologies for the inconvenience. With kind regards, Michel

Hi Jeff, The format is ISY specific. It uses X501 certificates but decomposed into p, q, exp, mod, with their lengths. We are planning to support CA certified formats in the future but have assigned it a very low priority since most people are not willing to pay between $14.00 to $400.00 per year for a certificate. With kind regards, Michel

Hi zyll, Apologies for a tardy reply ... I have already responded to your tech support ticket. Please note that incomplete means that ISY could not restore ALL devices. It does not mean that it completely failed. For instance, if you have any RF devices, you must put them into programming mode before you try a PLM restore. In releases 2.7.10 and above, ISY changes the icons for the nodes that it could not restore to 0101 (in green). In the meantime, it would be best to open the Event Viewer to level 3 ... this way, you will know exactly which devices are not restored. With kind regards, Michel

Hi delston, Apologies for the lack of clear documentation on this. The first thing is to note that you can only install the SSL certificate if and only if you are local to your ISY. Secondly, please note that installing 2.7.10 caused ISY to reload the default certificate. In which case, you will have to reinstall the new certificate. mgreene, Which URL did you use to install the certificate? With kind regards, Michel

Hi heatvent, Ah ... apologies for not understanding your question correctly. You are very much correct on both accounts: 1. This is INSTEON limitation 2. The scene commands do NOT have any attributes for the responders. They simply tell the devices to turn on/off/dim/brighten a scene. The responders MUST already be pre-programmed with on level/ramp rate for that scene Sorry ... With kind regards, Michel

Hi Chris, I am glad that it worked alas I am not satisfied for two reasons: 1. I want to track down the breakdown in our ticketing system. As such, if you do not mind, please do be kind enough to forward the ticket creation confirmation (if you received any) to support@universal-devices.com. I would sincerely appreciate it 2. The fact that it took you multiple times to restore your ISY is bothering me. As such, I would like to know what firewall software you have Now, going forward: 1. Please note that since you have a new PLM, you MUST do File | Restore Modem (PLM) otherwise none of your scenes will work nor would you get any status updates from any of your devices 2. I strongly recommend upgrading to 2.7.7 (after we determine the cause of intermittent restores) As far as Internet Access, in all likelihood your router is not UPnP enabled. It's generally a better idea to do manual port forwarding the instructions for which you find here: http://www.universal-devices.com/mwiki/ ... o_Your_ISY With kind regards, Michel

Hi heatvent, You can dim scenes (ISY scenes) from any ISY client. What you cannot do is to send Dim-to-level since INSTEON does not support this feature on scenes. So, what I would do would be: 1. Click on the Scene in the Admin Console 2. Adjust the desired on level / ramp rate for both of your devices 3. Click on each one of the devices in that scene, and then click on Copy Attributes button This way, all your controllers, including ISY, will have the same on level/ramp rate behavior and you can use any one of them to have the same exact behavior. When you want to dim, please dim the ISY scene instead of any of your devices. With kind regards, Michel