Michel Kohanim

Hello DigitalGuard, It all depends on what you are trying to accomplish. If you want simple control, then using a Global Caché TCP to IR (or Serial) would work very well. There are many examples here: http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Network_Resources With kind regards, Michel

Hi Jim, I am so very sorry to hear. HAM just fixed an issue with Rain Today values. Questions: 1. Is it raining right now? If so, do you get the correct value in Rain Today? 2. If #1 is true and when rain stops, do you get 0 for Rain Today (the next day)? With kind regards, Michel

Hi Ed, You can create self signed certificates in the dashboard: http://wiki.universal-devices.com/index.php?title=Main_Page#Network_Security With kind regards, Michel

Hi scubaguyjohn, I am so very sorry for the dearth of information. You can see a full list of possible properties by going to http://your-isy-ip-address/rest/configand extract the elements. With kind regards, Michel

Hi guedesluz, Ok, please do keep us posted. With kind regards, Michel

Hi Don, What you can do is: 1. Download http://isy.universal-devices.com/local-admin/4.2.15-ISY.zip 2. Extract it into a directory on your computer 3. Double click admin.jnlp in that directory This way, Admin Console will only look for local files on your computer. With kind regards, Michel

Hi Big Toro, Most stations do not report light. What firmware version are you on? If not 4.2.18, then I strongly suggest upgrading so that we have the same point of reference. With kind regards, Michel

Hi guedesluz, Please try reseating your SD Card. With kind regards, Michel

Hi Teken, Yes, of course ISY can handle negative values for energy monitoring. As far as getting triggers for devices that are not even plugged in, the best thing to do is to check your log and see whether or not the values change for that period. With kind regards, Michel

Hi camron, I am so very sorry to hear. The error code (-6) means that ISY could not communicate what that port: http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages#SMTP_Errors My suggestions: 1. If you have setup ISY with a static IP address, please do make sure your gateway and DNS are correct. In short, does ISY have access to the Internet or not? 2. If you have setup access filters on your router (such as parental controls), please do make sure that ISY is not included in the list 3. Try the default till you get everything working (as it uses the most simple SMTP communications possible) then move to your own SMTP settings In all likelihood ISY does not have access to the Internet and thus all the issues. You might want to go to Configuration tab | Clock and click on Synchronize Now. If that also fails, then ISY definitely does not have access to the Internet and something is blocking it. With kind regards, Michel

richardl007, All are benign. With kind regards, Michel

Hi richardl007, This means: -110014 SD DRIVE CONFIG READ FAILED You will find all our error codes listed here: http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages What it basically means is that ISY has a problem reading the configuration file for your INSTEON device with address of "12 EF AE". Two things may contribute to this issue: 1. Corrupted SD Card 2. Corrupted file The first question is: what is this device? If still in your ISY, you may want to remove it, and then add it back. The second question is: do you have more of these errors with other files? If so, then I suspect you have a corrupted SD card With kind regards, Michel

Hi LeeG, Thanks so very much for the feedback and it makes sense. Reason 9 = Cannot determine device link table address So perhaps we are dealing with an older PLM that does not support I2CS? Thanks again LeeG. With kind regards, Michel

Hi Kentinada, Please go to Configuration | Email&Notifications tab. There's a list of recipients at the bottom and 5 is the name on one of the entries. With kind regards, Michel

Hello 416to305, Just a few pointers: From what I see in your posts, I am very much concerned that the issue is not even with ISY/PLM/IOLinc. The reason is that the communication issue is related to the Sensor and not the Relay. ISY does not send any commands to the Sensor node of IOLinc because you really cannot do anything with it (it's read only). So, not only I urge you to contact our tech support but also check your Tools | Log and look for entries for your IOLinc-Sensor node. This will give us clues as to what else maybe trying to control the IOLinc. From over 8 years of experience I can assure you that factory resetting ISY will never solve any issues especially when communications related. Not only that, factory reset will prevent us from figuring out what the root causes are and, in case something starts working (intermittently), it's bound to fail again. And, thus a waste of your time. Factory resetting the PLM is sometimes useful but mostly when the issue is related to a full database on the PLM. I have never seen factory resetting the PLM fix communication issues. So - and to save you time and frustration - I do recommend not factory resetting ISY/PLM without a good reason (see above). With kind regards,

Lee, please contact our tech support. There's a problem with the setup and all the factory reset, moving around, changing things will only exacerbate finding the root cause. With kind regards, Michel

Hello 416to305, Please note that for battery operated devices, they have to be in awake mode otherwise ISY cannot program them. As you can see: TX/ACK but no SRX or ERX: TX - ISY sends a command to PLM ACK - PLM Acks the command SRX - The device Acks the command from the PLM So, please do make sure your battery operated devices are awake before you do anything to them. Also, our tech support is available to help you with all these issues. Please do not hesitate to contact us (links below). With kind regards, Michel

Hi eyost, You do not need to make any VPN connections to ISY. All you need to do is: 1. Make sure you install a certificate (it can be self signed) 2. Always use HTTPS when you access ISY remotely and don't ever open the http port to the outside world 3. Change your password every 6 months With kind regards, Michel

Hello JoeA, Thanks so very much for the details. Yes, you can definitely reboot ISY using our WSDK. This said, please let us go through your logs and fix this issue. It has to be fixed anyway. Thanks again and with kind regards, Michel

Hi telljcl, I am so very sorry to hear. Can you please let me know what's your firmware version? With kind regards, Michel

Hi sparkmedia, Thanks so very much! With kind regards, Michel

Hi LeeG, thanks so very much as always. Hi telljcl, Let me try to clarify: 1. The sequence of execution of each program is based on the order of the programs as you have them listed 2. The issue arises when the program you are calling has interruptible constructs (such as Wait or Repeat) or that it depends on some condition that has not yet been met at the time of the call. Or, it's calling network resources, email notification, updating variables (which may cause other programs that depend on the variable to run), etc. which go in a queue and are processed independently So, if all your programs simply turn on/off a device (WITH a condition that's always true), then the sequence of execution will be the same as you have listed them in your programs. Now, going back to LeeG's comments, and what I have outlined above, it would not be a good practice to depend on the sequence simply because there are too many variables that may contribute to the sequence to be broken. So, of course you can do if $A=5 the set $B=2 ... If A is a state variable, then B is set to 2 as soon as A is changed to 5. Now if B is also a state variable then any programs that depend on B will start getting evaluated and may run. If you need help with your programs, please don't hesitate to contact our tech support (links below). With kind regards, Michel

Hi Joe, Apologies. That's really odd. Would you please take a look at your logs and see if the time actually changed (fell back) on Sunday? With kind regards, Michel

Hi Techman, What's your ISY's firmware. This might be an old bug. With kind regards, Michel

Hi alexmanning, I suspect they disabled SSL due to the POODLE vulnerability. If you have an ISY994, then please upgrade to 4.2.18 and retry: http://forum.universal-devices.com/topic/14420-release-4218-rc8-is-now-avaialble/ If you have a 99, I am afraid you will need to upgrade to a 994. With kind regards, Michel