LeeG Posted June 6, 2012 Share Posted June 6, 2012 Some folks do upgrade remotely but UDI recommends doing the upgrade locally. Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 6, 2012 Share Posted June 6, 2012 Thanks Quote Link to comment Share on other sites More sharing options...
Xathros Posted June 6, 2012 Share Posted June 6, 2012 Another question: Do I have to do the upgrade while on the same local network or remotely thru the internet would also work? It's safer to do locally however, I have done this remote a number of times without issue. If you feel that you have a solid connection from the remote location to the ISY then you should be alright. If you have problems making the backup due to the remote connection, that would be a good indication that you are likely to have similar issues during the upgrade. In that case I'd say wait until you can work locally. -Xathros Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 10, 2012 Share Posted June 10, 2012 I upgraded 2 days ago and since then my ISY is constantly locking up. I had to reboot probably 30 times already in those 2 days. Quote Link to comment Share on other sites More sharing options...
Xathros Posted June 11, 2012 Share Posted June 11, 2012 Can you check your error log and see whats showing up there since the upgrade. -Xathros Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted June 11, 2012 Author Share Posted June 11, 2012 Hello hbsh01, In addition to Error Log (as Xathros suggested), please go to http://your.isy.ip.address/rest/config and send the result to support@universal-devices.com . Also, do programs continue to work when the unit is locked up? With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 11, 2012 Share Posted June 11, 2012 Xathros, Michel, It's now locked up again & I can't log in remotely. I will have to wait till I get home & reboot it again. I am not sure about the programs in general if it worked while being locked up since I was constantly rebooting it. That much I do know that I did not receive email notifications while being locked up. Also if that helps, most of the times when being locked up the MEM LED was on steady, sometimes only the power LED was on steady while locked up, while at least once the MEM & ERR were blinking. Thank you. Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 11, 2012 Share Posted June 11, 2012 By the way, yesterday I added an IO Linc to the ISY, and since then Conductor for Android keeps on crashing every time i try to open it. I tried to uninstall & reinstall with no results. A couple of times this also caused the ISY to lock up. (The ISY started to lock up though even before that). Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted June 11, 2012 Author Share Posted June 11, 2012 hbsh01, Two comments: 1. We have had at least 3 reports of conductor causing a crash on 3.2.6 ... we are investigating but it's difficult since Brad is no longer maintaining conductor 2. If you have Mem/Err blinking, it's quite possible that after the upgrade, your ISY got a new IP address which is now in conflict with some other device on your network. This is only the case if your ISY is not setup with static IP address And, finally, what's your router's make/model number? With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 11, 2012 Share Posted June 11, 2012 Michel, 1. It's interesting since it worked fine after the upgrade (When the ISY wasn't locked up) until I added an IO Linc & then did a re-download in Conductor. 2. I did not assign a static IP using the ISY setting but I did assign a static IP thru the router settings, so I highly doubt it got a new IP address. Unless the MAC address changes with a firmware upgrade? I will double check in the router when I get home though. My router is an ActionTech MI424-WR. It's the router given by Verizon to it's FIOS customers. Thank you. Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted June 11, 2012 Author Share Posted June 11, 2012 Hi hbsh01, Thank you. Can you tell me whether or not you have any programs based on the status of this IOLinc? With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
Xathros Posted June 11, 2012 Share Posted June 11, 2012 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. Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 11, 2012 Share Posted June 11, 2012 I have one program to send me email notifications of status changes in the sensor. Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 11, 2012 Share Posted June 11, 2012 Xathros, The lockups started on Friday after I upgraded the firmware while I added the IO Linc on Sunday. I uninstalled conductor last night & it still locked up today. Thanks. Quote Link to comment Share on other sites More sharing options...
Xathros Posted June 11, 2012 Share Posted June 11, 2012 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 Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 11, 2012 Share Posted June 11, 2012 Xathros, The ISY is being assigned a static IP by the router. The router is the only DHCP server on the network. Thanks. Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 12, 2012 Share Posted June 12, 2012 Here is the error log. By the way I realized now that I actually upgraded on Wednesday not on Friday which will be reflected in the log. Time User Code Message Wed 2012/06/06 06:22:20 PM System -5 Start Wed 2012/06/06 06:22:30 PM System -170001 [Network] Established Wed 2012/06/06 06:22:40 PM System -60006 n/a Wed 2012/06/06 06:22:50 PM System -50001 -14 Wed 2012/06/06 06:22:50 PM System -50001 -14 Wed 2012/06/06 06:22:50 PM System -50001 -14 Wed 2012/06/06 06:22:51 PM System -50001 -14 Wed 2012/06/06 06:22:51 PM System -50001 -14 Wed 2012/06/06 06:22:51 PM System -50001 -14 Wed 2012/06/06 06:22:51 PM System -50001 -14 Wed 2012/06/06 06:22:51 PM System -50001 -14 Wed 2012/06/06 06:22:51 PM System -50001 -14 Wed 2012/06/06 06:25:50 PM System -50001 -14 Wed 2012/06/06 06:25:50 PM System -50001 -14 Wed 2012/06/06 06:33:21 PM System -50001 -14 Wed 2012/06/06 06:33:41 PM System -50001 -14 Wed 2012/06/06 06:33:52 PM System -50001 -14 Wed 2012/06/06 06:34:12 PM System -50001 -14 Wed 2012/06/06 06:37:23 PM System -50001 -14 Wed 2012/06/06 06:42:35 PM System -50001 -14 Wed 2012/06/06 08:50:37 PM System -5 Start Wed 2012/06/06 08:50:42 PM System -170001 [Network] Established Wed 2012/06/06 08:50:52 PM System -60006 n/a Thu 2012/06/07 08:50:43 AM System -100 [DHCP] state=RENEW Thu 2012/06/07 10:58:47 PM System -5 Start Thu 2012/06/07 10:58:50 PM System -170001 [Network] Established Thu 2012/06/07 10:59:00 PM System -60006 n/a Fri 2012/06/08 10:58:58 AM System -100 [DHCP] state=RENEW Fri 2012/06/08 04:17:26 PM System -5 Start Fri 2012/06/08 04:17:29 PM System -170001 [Network] Established Fri 2012/06/08 04:17:40 PM System -60006 n/a Sat 2012/06/09 04:17:39 AM System -100 [DHCP] state=RENEW Sat 2012/06/09 04:17:49 PM System -100 [DHCP] state=RENEW Sun 2012/06/10 03:30:03 AM System -5012 27 Sun 2012/06/10 03:53:44 AM System -5012 28 Sun 2012/06/10 03:55:24 AM System -5012 29 Sun 2012/06/10 02:35:43 PM System -5 Start Sun 2012/06/10 02:35:46 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:35:52 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:35:52 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:52 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:52 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:52 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:52 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:53 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:53 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:53 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:53 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:53 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:53 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:35:57 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:02 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:07 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:12 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:17 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:22 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:27 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:32 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:37 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:42 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:43 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:36:43 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:36:47 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:52 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:36:57 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:36:57 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:36:57 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:02 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:07 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:12 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:17 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:22 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:27 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:32 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:37 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:42 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:47 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:52 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:37:57 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:02 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:07 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:12 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:17 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:22 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:27 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:32 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:37 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:42 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:47 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:52 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:38:52 PM System -50010 smtp.gmail.com Sun 2012/06/10 02:38:52 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:38:57 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:02 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:07 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:12 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:17 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:22 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:27 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:32 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:37 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:42 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:47 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:52 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:39:57 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:02 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:07 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:12 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:17 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:22 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:27 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:32 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:37 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:42 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:47 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:40:52 PM System -100 [DHCP] state=NOT STARTED Sun 2012/06/10 02:41:54 PM System -5 Start Sun 2012/06/10 02:41:58 PM System -170001 [Network] Established Sun 2012/06/10 02:42:08 PM System -60006 n/a Sun 2012/06/10 02:44:06 PM System -5006 uuid:27 Sun 2012/06/10 02:57:51 PM System -5 Start Sun 2012/06/10 02:57:57 PM System -170001 [Network] Established Sun 2012/06/10 03:04:22 PM System -170001 [uDSockets] RSub:32 error:6 Sun 2012/06/10 03:04:33 PM System -5012 27 Sun 2012/06/10 03:10:54 PM System -5 Start Sun 2012/06/10 03:10:57 PM System -170001 [Network] Established Sun 2012/06/10 03:45:04 PM System -10011 n/a Sun 2012/06/10 03:45:07 PM System -170001 [Auth] 192.168.1.13:39099->99, Num=3 Sun 2012/06/10 03:45:07 PM System -10011 n/a Sun 2012/06/10 03:45:09 PM System -170001 [Auth] 192.168.1.13:51594->99, Num=4 Sun 2012/06/10 03:45:13 PM System -170001 [Auth] 192.168.1.13:59906->99, Num=5 Sun 2012/06/10 03:45:13 PM System -10011 n/a Sun 2012/06/10 03:45:15 PM System -170001 [Auth] 192.168.1.13:51602->99, Num=6 Sun 2012/06/10 03:45:15 PM System -10108 Check log Sun 2012/06/10 03:45:16 PM System -170001 [Auth] 192.168.1.13:50708->99, Num=7 Sun 2012/06/10 03:45:16 PM System -10108 Check log Sun 2012/06/10 03:45:16 PM System -10011 n/a Sun 2012/06/10 03:45:18 PM System -170001 [Auth] 192.168.1.13:53646->99, Num=8 Sun 2012/06/10 03:45:18 PM System -10108 Check log Sun 2012/06/10 03:45:24 PM System -170001 [Auth] 192.168.1.13:54564->99, Num=9 Sun 2012/06/10 03:45:24 PM System -10108 Check log Sun 2012/06/10 03:45:24 PM System -10011 n/a Sun 2012/06/10 03:45:26 PM System -170001 [Auth] 192.168.1.13:37075->99, Num=10 Sun 2012/06/10 03:45:26 PM System -10108 Check log Sun 2012/06/10 04:15:59 PM System -5 Start Sun 2012/06/10 04:16:02 PM System -170001 [Network] Established Sun 2012/06/10 04:40:13 PM System -170001 [uDSockets] RSub:32 error:6 Sun 2012/06/10 04:40:22 PM System -170001 [uDSockets] RSub:32 error:6 Mon 2012/06/11 08:20:12 PM System -5 Start Mon 2012/06/11 08:20:15 PM System -170001 [Network] Established Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted June 12, 2012 Author Share Posted June 12, 2012 Thank you. I responded to your email. There are a few things that stick out: 1. ISY cannot get an IP address from your router ... this has to be resolved 2. 192.168.1.13 trying to hack into ISY (does not use the correct credentials) Apart from that, we need to isolate as many variables as possible. Does the IOLinc relay control anything? With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 12, 2012 Share Posted June 12, 2012 Hi Michel I got your email. 1. I double checked my router settings. The ISY is being assigned a static IP address by the router so nothing changed on the router's part. 2. 192.168.1.13 is my Android phone's IP address when connected to WIFI at home using Conducter. The credentials setup in conductor are the same as always. The IO Linc does not control anything. I use the sensor part of it to connect to my smoke detector in the house. I added it on Sunday after the problems began. I stoped using Conductor since last night & still it was locked today. Thanks. Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 12, 2012 Share Posted June 12, 2012 One other bit of info which might be relevant: Right after I upgraded the firmware, the SMTP settings which I used for the last couple of years from Optimum Online stopped working. So I changed the settings to use Gmail's server. After testing the gmail settings a couple of times I got an "OPEN SOCKET etc." error message & that's when the ISY locked up for the first time. Quote Link to comment Share on other sites More sharing options...
Xathros Posted June 12, 2012 Share Posted June 12, 2012 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 Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 12, 2012 Share Posted June 12, 2012 Xathros, I upgraded from firmware version 2.7.15. According to the instructions on this forum I wasn't required & did not install a new certificate. Could this still possibly be the problem with Conductor? Quote Link to comment Share on other sites More sharing options...
Xathros Posted June 12, 2012 Share Posted June 12, 2012 Xathros, I upgraded from firmware version 2.7.15. According to the instructions on this forum I wasn't required & did not install a new certificate. Could this still possibly be the problem with Conductor? 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 Quote Link to comment Share on other sites More sharing options...
ISYhbsh01 Posted June 12, 2012 Share Posted June 12, 2012 I uninstalled Conductor already & will switch to Mobilinc but it hasn't solved the ISY locking up problem. This morning my ISY was locked up again even though conductor was already uninstalled. Quote Link to comment Share on other sites More sharing options...
Xathros Posted June 12, 2012 Share Posted June 12, 2012 I uninstalled Conductor already & will switch to Mobilinc but it hasn't solved the ISY locking up problem. This morning my ISY was locked up again even though conductor was already uninstalled. 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 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.