Michel Kohanim

Hello Mack, I think you installed the module before upgrading to 3.1.4. Please do be kind enough to send your UUID (Help|About) to support@universal-devices.com and we'll reactivate it for you again. With kind regards, Michel

Hi Illusion, This is a different one and I am not sure how different it is but the sub category is different. With kind regards, Michel

Hello jdheltne, IRLinc buttons can be used as controllers in scenes (just like regular switches) so, in essence, you do not need to use the IRLinc to send information to ISY but, rather, you are going to use each button as controllers in scenes. What you have to do is to use Link Management | Add Button to IRLinc Receiver and then follow the instructions on the screen to add the buttons on your harmony remote. For each button learned by IRLinc you will see one node in the device tree in the Admin Console. With kind regards, Michel

Hello Jason, It's an either/or situation: which one do you want to use IRLinc (uses NEC codes) or the IR sensor in 99i (uses RC5 codes)? In case of the former, then your instructions are correct. If you want to use the IR on 99i, then you should follow instructions here: http://www.universal-devices.com/mwiki/ ... FIR_Series With kind regards, Michel

Hello junkycosmos, Thanks so very much! This is a bug that only happens when the previous event and the schedule event coincide. With kind regards, Michel

Hello Tom, It seems that your router is connected to another router. Please let me know the topology of your network. With kind regards, Michel

Hello sanders2222, Please send your station ID to support@universal-devices.com and we'll look into it. With kind regards, Michel

Hi sanders2222, This is quite odd ... do you also have any problems sending emails from ISY? How about synchronizing with NTP server? Do you have a static IP address? With kind regards, Michel

Hello kingwr, thanks so very for all your help and support. Enable Internet Access tries to configure a UPnP enabled router with port forwarding rules for ISY. In most cases, this is not a very reliable method since the router will lose it if rebooted. ingeborgdot, if you have a lot of problems configuring remote access, please do not hesitate to contact us and we'll walk you through it. With kind regards, Michel

Hi junkycosmos, Apologies for tardy reply. Would you be kind enough to try the following: Change: PROGRAM " EZRain2b Drive" If From 6:00:05AM ... To: PROGRAM " EZRain2b Drive" If From 6:00:15AM ... And, please include Alert.Default Body and Alert.Program Name in the body of your template. Once you get a notification, please post back. With kind regards, Michel

Hello Jasson, The new name should be reflected in programs and, regardless of the name, the only time you would get not-specified is if the device itself is NO LONGER registered in the system (i.e. you do not see it in the Admin Console's device tree). With kind regards, Michel

Hello thefunconsultant, 1. What URL do you use to access your ISY? Also, are your wired/wireless networks on two different subnets? (or, you can send me an IP address of a computer on the wired network and an IP address from the computer on the wireless network) 2. I think this problem is due to the fact that your switches have their memory wiped out. A simple test: change the on level on the Admin Console, then go to the switch and do an air-gap (take the set button out and then nudge it back in). If this works, then the problem is that the power outage has erased the memory on your switches as well With kind regards, Michel

Hello all, IMPORTANT note when upgrading from 3.1.3 and below: If you are using WeatherBug Module's Rain Today in your programs, please note that the precision has changed from 1/10 to 1/100 and thus your programs might not run properly. With kind regards, Michel

Hello All, IMPORTANT note on 3.1.4: If you are using WeatherBug Module's Rain Today in your programs, please note that the precision has changed from 1/10 to 1/100 and thus your programs might not run properly. With kind regards, Michel

Hi Tim, Thanks so very much and YES INDEED: my oversight for not including a warning. With kind regards, Michel

Hello ketchup318, Please go to https://www.universal-devices.com/ssl/insteon and reinstall a self signed certificate for your ISY. The old certificate no longer works with the new firmware. With kind regards, Michel

Hello junkycosmos, The problem is: Body: ${alert.event} at ${alert.date} ${alert.time24} You see, alert.event is the event that caused the program to run. What you want instead (to be consistent with the version without variables) is program.name. With kind regards, Michel

Hello, That's quite odd ... the programs use device address and NOT the name to present the name. So, are you certain that the not specified device is actually the one you are renaming? Also, please note that programs should reflect the new name. With kind regards, Michel

Hello wrj0, I think you installed the module before upgrading to 3.1.4. Please do be kind enough to send your uuid to support@universal-devices.com and we'll reactivate it again for you. Hi Brian, that usually happens if ISY cannot communicate with a client (in this case Admin Console). In some cases, after clearing Java cache, the computer may be too busy starting to run the new code and thus ISY will not get the acks as quickly as it would want. This will cause ISY to expire the subscriptions and thus those errors and lack of device state on the UI. With kind regards, Michel

Hello junkycosmos, -5011 means that a client (such as Admin Console) which has subscribed to ISY is not longer accessible. So, if you have a mobile device such as iPhone or Droid which might go to sleep mode, then you will see these errors because they do not unsubscribe. With kind regards, Michel

Hi Lee, Thanks so very much! Verified as bug and already fixed for the next release. With kind regards, Michel

Hi johnnyt, What firmware version were you using. The scene UI does NOT allow a sensor node to be added as a responder. With kind regards, Michel

Hi Illusion, Thanks so very much. Verified as bug and unfortunately it has to wait till 3.1.5. With kind regards, Michel

Hello all, Release 3.1.4 (Beta) is now available: viewtopic.php?f=25&t=6547 With kind regards, Michel

Hello all, Release 3.1.4 (Beta) is now available: viewtopic.php?f=25&t=6547 With kind regards, Michel