Michel Kohanim

Hello sk8er02, At this point, I would like to send you a replacement to try. It's good news that everything else works except the network functions so hopefully it's a hardware issue. If you have purchased your unit less than 12 months ago and from SH, you can call them directly for a replacement. Otherwise, please send you serial number and date of purchase to sales@universal-devices.com with subject RMA. With kind regards, Michel

Hello fasttimes, Yes, just click the green batch icon at the top (one to the last) and all your updates will be written out. With kind regards, Michel

Hello mrp, Thanks so very much for the detailed analysis; it was quite helpful. I can reproduce this problem intermittently and it has to do with the fact that we are getting two responses back from the EZIO ... I just received an email from SHN outlining the new firmware for EZxxx devices which - I am very much hoping - is going to solve most (if not all) of our compatibility issues. I am going to send all our EZxxx devices back to SHN for the firmware to be updated (apparently, the first one to be updated is EZRain). Once we have the updated firmware, we'll delve deep into all the incompatibility issues. Unfortunately - and without the updated SHN firmware - there's no easy fix that we can provide as it will be a temporary/patch work. I do understand your frustration and we'll do our best to get it out as quickly as possible. With kind regards, Michel

Hello mrp, Thanks so very much for the detailed description. First of all, the event viewer/INSTEON traffic are meant for users (or tech support team) who understand what the traffic really means. With this said, the Process Response failed message is absolutely normal simply because your EZIO is responding with the same response twice (i.e. they are duplicates ... look at the SRX right before the failure). In short, the second response is considered duplicate, fails processing, and is ignored. Now, with this said, I am quite surprised that you have gotten your EZIO to even send status updates (without query) to ISY. So, may I summarize your post with the following: ISY is not reporting the correct status of the EZIO inputs when queried? With kind regards, Michel

Hello sk8er02, The errors you are seeing are related to ISY not having access to the Internet ... I do not think these errors would cause ISY to lockup. You mentioned that when this happens, your programs do not run either, correct? If you know the IP address of your router, can you try telnet to your ISY? It's very important to see whether or not ISY is even responding. With kind regards, Michel

Hello theedudenator, Unfortunately I believe that you need a replacement PLM (your PLM is defective). With kind regards, Michel

Hello treighmy, That usually happens with a defective PLM (or a loose cable). Please do keep an eye out for disappearing programs or unresponsive devices. If it happens again, I strongly recommend getting a replacement PLM. Final note: you do not need to restore devices. With kind regards, Michel

Hi Terry, That's really odd! If you are certain that originally you got a 10.0.x.x address, then would you be kind enough to: 1. Go to your Kitchen computer 2. Click on the Run menu, and then type cmd 3. Once in the DOS prompt, please type ipconfig ... let me know what is the IP address for your computer With kind regards, Michel

Hi Terry, Thanks for the update. If indeed you got a 10.0.x.x address originally and now you are getting a 192.x.x.x, it means that you have two DHCP servers on your network. Do you have an Airport/Express router installed anywhere? To upgrade, simply go to http://www.universa-devices.com/99i, login to the Admin Console, and then choose File | Manually Upgrade My Lighting. With kind regards, Michel

Hello sk8er02, I do apologize for the inconvenience. Quick questions: 1. Are you on 2.7.14 or 2.7.15? If .14, please upgrade to .15 just so that we have the same point of reference 2. Do you have an ELK system to which ISY communicates with? 3. Do you have access to a serial port? If possible, and when it happens, we would like to login through the hyperterminal and see what's going on With kind regards, Michel

Hello theedudenator, Please go to Tools | Diagnostics | PLM Status/Info and ensure that it indicates that your PLM is connected. If not, then the problem (in all likelihood) is the PLM itself. With kind regards, Michel

Hi Tim, Orchestrator is a 99i with a Zigbee SEP module and thus can natively communicate with SmartMeters. As far as PG&E, none of their Smart Meters have the Zigbee module enabled yet. Orchestrator is available through HDS and directly from us. But, it's functionality will be equal to 99i if it cannot communicate with the meter. You might want to contact your PG&E rep to see if your meter has the Zigbee SEP module enabled. If so, I would be delighted to send you one. With kind regards, Michel

Hi Terry, I just want to make sure that the exchange of emails solved the problem. Specifically, you do not need to enable Internet Access to upgrade the firmware. With kind regards, Michel

Hello IM, Would you be kind enough to let me know how the second button press sends the device to 100%? Is it fast on? Normally, if fast on is not sent, ISY infers that the device should go to the on level as it's programmed. With kind regards, Michel

Hi Mitch, You just have to make sure ISY is in the white/allowed list. With kind regards, Michel

Hi bellias, This usually happens when the PLM sends two ACKs instead of one. It's usually benign and happens most often with RF devices. With kind regards, Michel

Hi jerlands, Yes, this feature was added in 2.7.8 and above which basically ensures that either all device writes are written to the device OR you will get an 0101 green icon so that you can retry writing to the device (ISY retries every time you make a change). The other feature is Batch mode in the PRO series. In short, you can do all your configuration in batch, and then click the Batch button and have ISY write all the configuration changes to the devices. With kind regards, Michel

Hello ryarber, So would I!!! I am not sure if they are competing with Zigbee SEP ... in California, more than 5 million smart meters have been installed that provide energy utilization amongst other things. We actually do have a product, called Orchestrator, that natively communicates with Smart Meters! With kind regards, Michel

Hi Terry, Apologies for a tardy reply ... we are off on Saturdays. We'll try to get to the bottom of this over the weekend. You are correct: Mem/Error means that your ISY is not connected to the network. The most important test would be to look at the LEDs on the Network Jack on ISY. One of them should be steady green and the other one should blink intermittently. If your ISY is connected through a switch to your router, then you might want to try and connect it directly to the router and observe whether or not there are any changes. Please do keep us posted and we'll find a solution. With kind regards, Michel

Hi Wes, Thanks so very much for your help. Indeed appreciated. Mitch, one more thing about your computer/Admin Console: would you please let me know what firewall software you have? Thanks and with kind regards, Michel

Hi Wes, Thanks so very much for looking into this and I think you are right on. As far as -5012, perhaps you can use IsSubscribed service to make sure you are still subscribed before unsubscribing. I think that would alleviate some or most of the issues. Thanks again and with kind regards, Michel

Hi Rich, What you have is correct with one exception: you have to use From 7AM to 8PM otherwise your program will stop in the middle at about 7:10. With kind regards, Michel

Hi mitch236, Thanks so very much for the update. Again, although benign, but this is not a good use of logs. I am going to send Wes a link to this post and together we are going to figure out what's causing the error. Your suspicions are correct: while ISY is sending the events, MobiLinc is closing the connection. With kind regards, Michel

Hi Tim, Thank you so very much for the confirmation. I have logged this as a bug and we shall have it fixed in our next release. With kind regards, Michel

io_guy, I love putty ... it's a life saver especially when dealing with SSH. With kind regards, Michel