Michel Kohanim

Hi RLIKWARTZ, Currently no ... we decided to leave it in for now. With kind regards, Michel

Hi intellihome, All you have to do is: 1. Remove your KPLs from ISY ... you don't have to touch any scenes since ISY removes them for you 2. Factory reset your KPL 3. Add them back in Do not touch your programs since they work based on INSTEON address. As such, when you add your KPLs back, they should start working again. With kind regards, Michel

Hi all, Thanks so very much for your patience. If you would like to try 2.7.11 ALPHA, please do be kind enough to register at http://eepurl.com/ha4Z . For a list of fixes in 2.7.11, please checkout this post: http://forum.universal-devices.com/viewtopic.php?t=930 And, finally, general operations instructions: Instructions for 2.7.8/9 can be found here: http://forum.universal-devices.com/view ... hp?p=27368 With kind regards, Michel

Hello again, Thanks so very much for your kind words! I am so very glad everything works. Certificates are quite important for remote access so all your research is time well spent! With kind regards, Michel

Hi andrewm, You do need 2.7.8 and above to use all the features of the new V2 thermostat. May I humbly suggest not spending too much time on 2.7.6 and the issues with the V2 thermostats? We should have 2.7.11 out shortly. With kind regards, Michel

rLav, EZIO6I issue is now fixed in 2.7.11. Nick, Battery powered REST services are now included in 2.7.11: /rest/batteryPoweredWrites -- Returns status [0|1]", /rest/batteryPoweredWrites/on -- Writes all pending changes to battery powered devices when batch is off. /rest/batteryPoweredWrites/off -- Does not write changes to battery powered devices when batch is off. geekdoc, Apologies for not seeing your post till now. The main issue is that a sub button cannot turn OFF a load on a KPL. We do not know why this is the case. With kind regards, Michel

Hi mitch236, In addition to brad's suggestion, you will have to note that this program is only run if the light level actually changes. So, for instance, if the light level was 5 and still remains 5, this program is not re-evaluated unless the time changes and comes within the range. With kind regards, Michel

Hi, The problem is the format of the certificate in 2.7.10. While you have not installed 2.7.11, please try the following: 1. Telnet to your ISY: http://www.universal-devices.com/mwiki/ ... o_Your_ISY 2. Login 3. issue: RF /CONF/UD.DCF This will install the default certificate. With kind regards, Michel

Hello spage, This is mostly due to a router that is not UPnP enabled. In all cases, though, it's much more reliable to do create manual port forwarding in your router. This will persist router reboots whereas UPnP loses the rules: http://www.universal-devices.com/mwiki/ ... o_Your_ISY Please take a look Configuring Non-UPnP Router section. With kind regards, Michel

Hi, We will investigate this issue and put a fix as soon as possible. With kind regards, Michel

Hi Jim, Thanks for the update. I must say that I am not satisfied with this workaround! We need to get to the bottom of this issue. Few questions: 1. What is the firmware version and the ID of your PLM (Tools | Diagnostics | PLM Status/Info) 2. Please go to Tools | Diagnostics | Show ISY Links Table and then choose the problematic KPL, and then click Start. Please let me know how many link records you find with the PLM ID (you found in 1) for this KPL With kind regards, Michel

Hi Mike R., In your local network, please try going to httpS://your.local.isy.ip.address ... if this does not work either, then there lies the problem. With kind regards, Michel

NJ_Mark, If everything worked fine in 2.7.10 then I must suspect something changing the local load on your KPL without going through ISY. Is this a possibility? With kind regards, Michel

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