Xathros

GreyFox- You could delete all of the devices from the admin console then add them back selecting "Remove Existing Links". You still have to rebuild everything from scratch but this "should" clear all the old links. If I was doing this, I would factory reset all of the devices before adding them back to be sure that there are no garbage links left. When we moved into our new home last fall, I went through this process with all of the gear I pulled from the old home. As I installed each device, I did a factory reset then added it to the ISY (which I factory reset first). This way everything was like new with no phantom links or X10 stuff to worry about. -Xathros

LeeG- I didn't realize that the Toggleinc Relay had moved to I2CS already. Thanks for that tidbit. -Xathros

Your firmware and User Interface versions don't match. Try clearing your java cache then access the admin console at http://your.ISYs.IP.address/admin Once there, you may want to update to the latest firmware (3.2.6) but I don't believe any of the Toggleinc devices require it yet. -Xathros

Alf- Its not necessarily right or wrong but more a matter of preference as to how you set your static address but doing both at the same time I see as wrong. If you are reserving the address at the router by MAC, then set the ISY for DHCP and let it retrieve the address from the router. If you prefer to hard code the static address in the ISY, then use an address that is OUTSIDE of the routers DHCP pool and eliminate the reservation from the router. I have my ISY, Cameras, printers and desktop workstations all hard coded. it eliminates much of the DHCP traffic when the power is restored and all of my network tries to come online at once. Mobile devices, game consoles, set top boxes etc all DHCP and occasionally will need a restart after power is restored to get them back online. I chalk this up to DHCP failure due to either too much DHCP traffic or the devices timing out waiting for DHCP before the router/modem is ready though I haven't spent the time to prove this theory. In this configuration, I have never been unable to reach the ISY, cams or desktops unless the power is out or the cable is down. Here is my thinking: Static coded at the device - if this device need to be accessed from the network/remotley and will never leave this network or join other networks. This reduces the DHCP traffic at startup and ensures proper addressing. Addressused for these devices are below my DHCP pool. DHCP Addressing - for devices the move between networks and don't need to be accessed remotely or can easily be found by other methods (UPnP, Bonjour etc.) The main idea here is to keep the device in a DHCP mode to aid in joining foreign networks. Static DHCP - For devices that need to be accessed remotely while on my network but will frequently join foreign networks (my Laptop). This way I know where it is at home and it still auto configures elsewhere. This is the only case where I have a reservation set in my router. The address assigned is the last address in the DHCP pool. I have seen many consumer grade routers choke on DHCP traffic. This is why many of my clients have a startup cheat sheet at the modem router for startup procedure that looks like: 1)Power modem, wait till ready. 2) Power router, wait 15 seconds. 3) Start computer(s). All of that said, at the office with commercial grade routers and smart switches I have very few devices hard coded and most everything uses DHCP assignments reserved at the routers. Too much to manage any other way. -Xathros

Alf- My guess is this is due to variable boot times at the modem/router. How is your static address for the ISY assigned ? At the router or hard coded in the ISY's admin console ? If in the admin console, is the address used outside of the router's DHCP pool ? -Xathros

I'm running Java 1.6.0.31 here without issues as well. Does the upgrade fail at the same point each time of at different points along the way ? If always at the same point, I would suspect a bad download. What is the status of the front panel LEDs at the point of failure ? -Xathros

snownh2o2- What version of Java are you running? There has been some trouble with Java 7 reported. -Xathros

Wouldn't it be nice if Smarthome could give us the option on all load controlling devices to: A) Default to Off on AC Restored Default to On on AC Restored C) Return to previous State on AC Restored Hey, a fella can dream right ? -Xathros

Excellent! Glad I could be of some assistance at least. This was a tough case but it sounds like its fixed. Thanks for the update. -Xathros

Do you have Kaspersky or Avast Antivirus ? If so, disable and test. Please let us know what turns up during your support call. I am really curious to know whats going on here. -Xathros

Lets try a "File / Restore PLM" and see if we can get your statuses working. -Xathros

I have done this, just this week. And yes, it does work. I have 3 Toggleinc Relays around my kitchen and dinning room. If I fade down any of the 3, a program is invoked to turn off 2 scenes. All of the 3 switches exist one or the other of those 2 scenes. When fading down the light will just turn off while I'm still holding the paddle down. I suspect if the device was a dimmer, the light would start do dim then turn off a second later when the program executes. -Xathros

I believe the blinking ERR led indicates a problem with the file system. Yet another indication of an SD card issue. If you believe the backup after the upgrade was successful, then that is the one to use. If not, then I would attempt to make another now. If you are unable to due to lockups, then you can use the older one but I think you would want to flash the new/formatted card with the version of the firmware that was in use at the time of that backup, restore that backup, then upgrade to 3.2.6 after that. Of course your TriggerLinc will not be there and your notification program for the Triggerlinc won't be there since they were added since the upgrade. I would follow the Wiki procedure as there was something specific to the card being formatted by the ISY. I suspect it wants to be FAT16 not NTFS or HFS+ etc. and there may even be more to it than that. I have read that older ISY hardware has a 512Mb card size limit. I'm not sure at what point they started supporting the larger cards or how we can tell if yours does or not. Hopefully Michel can chime in on that. Lets hope you have/can get a good backup and that a reformat is all thats needed. -Xathros EDIT: Also, if you are using the Network Resources Module and have stuff in the webserver, you need to copy that out first as it is not in the backups and will be lost on the reformat. EDIT #2: Lets start simple. Power down the ISY, then remove and re-seat the SD card first. Test.

I don't really think the initial DHCP process is whats locking it up but possibly at IP lease renew. Really just trying to eliminate things to narrow down the problem. Also I see -50010 errors in your log related to smtp.gmail.com. I believe this is a DNS lookup failure. I was having some issues with my ISY not resolving both SMTP and NTP servers a month or so ago. I resolved it by statically setting 8.8.8.8 and 4.2.2.2 as my DNS for the ISY. I suspicion is that the ISY is not waiting long enough for a response from the DNS servers and my ISP's servers in conjunction with my router were not responding fast enough resulting in a timeout. (Thats all just my "feeling" as I haven't been able to prove any of it yet) In any case, setting the DNS as stated above solved the problem for me. I am concerned that the MEM led is on steady when it's locked up. This may be a clue since as far as I can tell that LED should only be lit during SD card access and not be in a steady on state ever. It's possible you have a corrupted or failing SD card. I'd like Michel's thoughts on this as well. In any event, here is the Wiki data on reformatting or replacing the SD card: http://www.universal-devices.com/mwiki/ ... an_SD_Card If you are up for it, I would try the reformat first. MAKE SURE you have a good backup of the ISY before you begin. -Xathros

I really think you will be happy with MobiLinc. I love it. Lets eliminate DHCP issues. Can you assign a static address inside the ISY that is outside of your routers DHCP address range? This will simplify the startup a bit and will eliminate DHCP errors from the log. You will need to edit your port forwards (if you have any for the ISY) to match the new address. What was the state of the LEDs after it locked up this time ? How old is this ISY ? -Xathros

I'm not entirely sure, however, if your login credentials haven't changes and conductor is failing to log in, there is a strong possibility that the certificate that conductor has is mismatched with that of the ISY. It wouldn't hurt to clear that on the android and let it re-accept what the ISY has. EDIT: I was just reading a bit over on the Conductor for Android forum and see that there is another person having the same problem after adding a FanLinc to their ISY. I wonder if there is some I2CS issue with conductor that shows up like an authentication error. Anyway, the recomendation there was to switch to Mobilinc for android. I love Mobilinc on my iPhone and Wes (the developer of Mobilinc) is as responsive and helpful as the UDI crew so support is not a concern. -Xathros

hbsh01- I suspect your android phone has an old certificate for the ISY and needs to accept a new one after the upgrade. I don't know how to delete the existing cert on android but if you can find that and remove the old cert then allow it to accept a new one that may resolve your failure to authenticate from conductor. I too had issues with my web host's SMTP with the ISY and switched to gmail's SMTP. I've had no issues with notifications since. -Xathros

It sounds like those have been eliminated then. Hopefully there will be something useful in the logs. EDIT: Another thing to consider, Is it possible you have another device on your network that is statically configured for the address that your router has issued the ISY ? Or, another device offering DHCP services on the same subnet ? To test, you could temproarily disconnect the ISY then try to ping that IP from a computer and see if you get a reply. If so, you have an IP conflict at that address. -Xathros

I wonder if the combo of the new IOLinc and Conductor is whats causing the lockup. Can you either remove the IOLinc or disable Conductor for a little while to see if the lockups stop ? -Xathros EDIT: I see Michel is on the case here. I'll step back and watch unless something jumps out at me.

Can you check your error log and see whats showing up there since the upgrade. -Xathros

You can certainly configure things such that you could do all of the control from one place. You would still be able to control the second ISY or Smartlink independently if you wanted as well. -Xathros

I'm sorry to hear that. I still wonder if there is a way to trick the transfer switch into thinking that utility power has been restored or to tap into the control circuitry at that point to tell the generator to do a normal shutdown. Please do let us know if you find a workable solution. -Xathros

Excellent. Please let us know how it works out for you. I have some long term plans for doing something similar at my place. -Xathros

There is another configuration that I had considered and rejected. Run the 24V over the existing 2 wire to the Venstar. Add EZIO or IOLinc at the furnace/zone valve/pump whatever for the contact closure and use the ISY to Monitor the tstat and control the zone. Only reason I rejected this is in the event of a comm failure a zone could be left on or fail to turn on. A periodic query could fix that issue as lons as comm failurs are rare in your setup. I preferred to have the tstat do the control directly. -Xathros

Jeff- I don't believe there are any stack issues with this. I have something similar on my ISY and haven't had any problems. As for copy paste, right click the program name in the tree on the left, select Copy to Clipboard. HTH -Xathros