Michel Kohanim Posted October 16, 2016 Share Posted October 16, 2016 Hi steve9f, Can you please let me know your ISY's firmware version? With kind regards, Michel Link to comment
LoftyNotions Posted October 18, 2016 Share Posted October 18, 2016 Hi Michel, I'm not steve9f, but I just had the same thing happen. A reboot seems to have taken care of the issue. My firmware is currently at v4.4.6. Larry Link to comment
steve9f Posted October 19, 2016 Share Posted October 19, 2016 I lost connectivity from the portal again. Same symptoms - portal shows ISY offline but ISY shows it's connected to the portal. A reboot of the ISY resolved the issue. I'm running v4.5.1 firmware. Thanks - Steve Link to comment
starmanj Posted October 19, 2016 Share Posted October 19, 2016 One of my ISYs is online to the portal, the other is offline. Why? ISY Portal tab says registered and offline. Refreshing does nothing? How do I get the offline portal to go online? Starmanj Link to comment
stusviews Posted October 19, 2016 Share Posted October 19, 2016 The usual procedure is the reboot the ISY. Link to comment
starmanj Posted October 19, 2016 Share Posted October 19, 2016 I had to downgrade from 5.0.6 back to 5.0.2 so might have lost some Portal settings? I note there are network setting requirements for TLS etc. but nowhere does it explain where those settings are (Wiki, etc just say make sure it's set but now HOW). How exactly do you modify network settings? It's not under configuration-->system that I can see. Reboot does nothing to change offline status. Link to comment
Michel Kohanim Posted October 19, 2016 Share Posted October 19, 2016 Hi starmanj, Http://isy.universal-devices.com/5.0.6/dashboard.jnlp With kind regards, Michel Link to comment
stusviews Posted October 19, 2016 Share Posted October 19, 2016 Hi starmanj, Http://isy.universal-devices.com/5.0.6/dashboard.jnlp With kind regards, Michel 404 - Not Found Link to comment
rccoleman Posted October 19, 2016 Share Posted October 19, 2016 It looks like it should be http://isy.universal-devices.com/994i/4.5.1/dashboard.jnlp. Note the "994i" that was missing. Rob Link to comment
MustangChris04 Posted October 20, 2016 Share Posted October 20, 2016 I'm having the same issues. Portal doesn't work and shows offline from my.isy.io. Will an occasional reboot need to occur as more servers are added or is this just a one-off event? Link to comment
starmanj Posted October 20, 2016 Share Posted October 20, 2016 I'm confused...where on the dashboard can you change TLS settings? And does it matter that one of my ISY's are offline, if the second is online? That is, can Alexa still communicate with both ISYs? Anyway I wish there were some debugging steps to why I have an offline ISY... Link to comment
Michel Kohanim Posted October 20, 2016 Share Posted October 20, 2016 Hello all, This is the link for security configuration for the dashboard: http://wiki.universal-devices.com/index.php?title=Main_Page#Network_Security The best place to start is error log. In 99.9% of the cases, the issue is either DNS (not finding my.isy.io) or router configuration not letting ISY get out to the Internet. If you wish, you can send your error log to support@universal-devices.com and we can take a look. With kind regards, Michel Link to comment
Javic Posted October 26, 2016 Share Posted October 26, 2016 My ISY is currently working fine, but I wanted to provide a bit more information and a suggestion to Michel, I've recently experienced a few brief power outages, and I've noticed once power is restored, the Portal isn't connecting for me, although the ISY is up and reachable on the local network. A reboot does resolve the problem though, This thread helped me figure out the problem, Thanks guys! From the logs it looks like its probably the DNS issue mentioned earlier in the thread. I think perhaps, in my particular case, it could be because the ISY boots up faster than my router, hence when it attempts to resolve these addresses it fails because it can't reach the Internet yet. The logs seem to indicate it retries a few times but then stops after a period (approx 1:45). Do you think it would be possible to add a periodic retry every 5 or 15 minutes after the initial cycle fails? This might ensure any other network gear has had ample time to boot up and allow traffic to pass again, and could prevent us from having to manually reboot the device when a new DNS query attempt could be made automatically. It might help enhance the recovery and I would think could be fairly easy to implement. Even adding a manual "retry DNS query" option in the Admin Console would help too. Although its quick, a full reboot is not ideal if there are less intrusive ways the problem could be resolved. Here's the relevant section from my error log Tue 2016/10/25 09:33:19 PM System -5 Start ####Power Failure Tue 2016/10/25 09:33:20 PM System -110022 /CONF/INSTENG.OPT Tue 2016/10/25 09:33:20 PM System -110012 /CONF/INSTENG.OPT Tue 2016/10/25 09:33:23 PM System -170001 [Network] Established Tue 2016/10/25 09:33:23 PM System -60001 pool.ntp.org Tue 2016/10/25 09:33:23 PM System -140000 my.isy.io Tue 2016/10/25 09:33:23 PM System -60001 pool.ntp.org Tue 2016/10/25 09:33:25 PM System -60001 pool.ntp.org Tue 2016/10/25 09:33:30 PM System -60001 pool.ntp.org Tue 2016/10/25 09:33:35 PM System -60001 pool.ntp.org Tue 2016/10/25 09:33:40 PM System -140000 my.isy.io Tue 2016/10/25 09:33:40 PM System -60001 pool.ntp.org Tue 2016/10/25 09:33:40 PM System -60006 Stopping retries/next cycle Tue 2016/10/25 09:34:10 PM System -140000 my.isy.io Tue 2016/10/25 09:34:45 PM System -140000 my.isy.io Tue 2016/10/25 11:23:03 PM System -5 Start ####When I rebooted to resolve the issue Thanks for the consideration and keep up the great work! Link to comment
Michel Kohanim Posted October 26, 2016 Share Posted October 26, 2016 Hi javic, Thanks so very much for the details. Please note that ISY will retry incessantly ... so, the question is whether or not the router provided the correct DNS server once ISY booted up. If not, you might want to consider a static address configuration BUT note that if you ever change your router, you might have to factory reset your ISY and restore from your backup. With kind regards, Michel Link to comment
starmanj Posted October 27, 2016 Share Posted October 27, 2016 I was able to check TLS settings but that is not the problem. No idea why my ISY will not go online with the portal. Here are last parts of my error log: Thu 2016/10/27 10:24:30 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:25:09 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:25:39 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:26:09 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:26:39 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:27:10 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:27:40 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:28:15 AM System -140000 my.isy.io Thu 2016/10/27 10:28:54 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:29:33 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:30:03 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:30:38 AM System -140000 my.isy.io Thu 2016/10/27 10:31:09 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:31:40 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:32:10 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:32:44 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:33:19 AM System -140000 my.isy.io Thu 2016/10/27 10:33:53 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:34:26 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:35:01 AM System -140000 my.isy.io Thu 2016/10/27 10:35:31 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch I can login to my.isy.io fine from my web browser; can't tell if the ISY can't login? Starmanj Link to comment
rccoleman Posted October 27, 2016 Share Posted October 27, 2016 My ISY was successfully connected to the portal last night, but dropped off just before 2AM PDT. The ISY thinks that it's registered, but the portal says that it's offline. Rebooting the ISY doesn't help. Edit: Weird. It's back up after rebooting my pfSense router. It looks like my cable modem freaked out around 1:30AM and rebooted, causing it to reacquire the WAN address. After that, everything seemed fine from my perspective (I could ping external sites and access my.isy.io), but the ISY was offline as far as the portal was concerned. I'll have to dig into it a bit to see if pfSense was dropping the ISY packets for some reason, but it was weird that the ISY thought that it was still registered with the portal (green flag). Rob Link to comment
starmanj Posted October 27, 2016 Share Posted October 27, 2016 Fixed it...I had a bad Comcast DNS assigned in the ISY config. Online now! Link to comment
Javic Posted October 27, 2016 Share Posted October 27, 2016 Hi javic, Thanks so very much for the details. Please note that ISY will retry incessantly ... so, the question is whether or not the router provided the correct DNS server once ISY booted up. If not, you might want to consider a static address configuration BUT note that if you ever change your router, you might have to factory reset your ISY and restore from your backup. With kind regards, Michel Thanks for the response! I actually do have static addresses assigned, with Google's Public DNS server of 8.8.8.8 set for DNS. If the ISY continues to try to resolve the hosts, are successes listed in the regular log? Based on my logs above, there was an almost 2 hour period where it wasn't retrying or failing, yet it still showed as Offline in the ISY Portal, so I'd like to try to see what address it did ultimately resolve to if it wasn't the correct one. Link to comment
MWareman Posted October 27, 2016 Share Posted October 27, 2016 Edit: Weird. It's back up after rebooting my pfSense router. It looks like my cable modem freaked out around 1:30AM and rebooted, causing it to reacquire the WAN address. After that, everything seemed fine from my perspective (I could ping external sites and access my.isy.io), but the ISY was offline as far as the portal was concerned. I'll have to dig into it a bit to see if pfSense was dropping the ISY packets for some reason, but it was weird that the ISY thought that it was still registered with the portal (green flag). Rob I've had pfSense hold on to old state records when the external IP changes. Very frustrating. I've been away from it for a while and just recently switched back. Hopefully that little bug is squashed in the newest builds... If it happens again, try flushing the state table to see if that helps.... Link to comment
rafarataneneces Posted October 27, 2016 Author Share Posted October 27, 2016 Hi javic, Thanks so very much for the details. Please note that ISY will retry incessantly ... so, the question is whether or not the router provided the correct DNS server once ISY booted up. If not, you might want to consider a static address configuration BUT note that if you ever change your router, you might have to factory reset your ISY and restore from your backup. With kind regards, Michel Dear Michel With SO MANY people having problems with ISY Portal, have you thought that the solution is not that the ISY Portal will 'retry incessantly'? It's 100% obvious that rebooting solves the issue, so have you thought of officially name this a bug and work with us towards a solution? Do you know if V4 has this problem or is it only V5? Link to comment
Michel Kohanim Posted October 28, 2016 Share Posted October 28, 2016 rafarataneneces, No. With kind regards, Michel Link to comment
rccoleman Posted October 28, 2016 Share Posted October 28, 2016 I've had pfSense hold on to old state records when the external IP changes. Very frustrating. I've been away from it for a while and just recently switched back. Hopefully that little bug is squashed in the newest builds... If it happens again, try flushing the state table to see if that helps.... My ISY dropped offline from portal again yesterday, shortly after I left for work. It's unfortunate that it's become flaky, given that it's been working for many months. I get a bunch of stuff like this in the ISY error log: Wed 2016/10/26 09:08:24 AM System -140005 ISY Wed 2016/10/26 09:50:15 AM System -100 [DHCP] state=RENEW Wed 2016/10/26 10:50:19 AM System -100 [DHCP] state=RENEW Wed 2016/10/26 11:50:26 AM System -100 [DHCP] state=RENEW Wed 2016/10/26 12:50:30 PM System -100 [DHCP] state=RENEW Wed 2016/10/26 01:50:36 PM System -100 [DHCP] state=RENEW Wed 2016/10/26 02:50:42 PM System -100 [DHCP] state=RENEW Wed 2016/10/26 03:50:47 PM System -100 [DHCP] state=RENEW Wed 2016/10/26 04:50:51 PM System -100 [DHCP] state=RENEW Wed 2016/10/26 05:50:55 PM System -100 [DHCP] state=RENEW Wed 2016/10/26 06:51:01 PM System -100 [DHCP] state=RENEW Wed 2016/10/26 07:51:05 PM System -100 [DHCP] state=RENEW Wed 2016/10/26 08:51:10 PM System -100 [DHCP] state=RENEW Wed 2016/10/26 09:51:18 PM System -100 [DHCP] state=RENEW Wed 2016/10/26 10:34:13 PM System -170001 [UDSockets] RSub:28 error:6 Wed 2016/10/26 10:34:18 PM System -170001 [UDSockets] RSub:28 error:6 Wed 2016/10/26 10:34:23 PM System -170001 [UDSockets] RSub:28 error:6 Wed 2016/10/26 10:34:28 PM System -170001 [UDSockets] RSub:28 error:6 Wed 2016/10/26 10:34:33 PM System -170001 [UDSockets] RSub:28 error:6 Wed 2016/10/26 10:34:36 PM System -5012 91 Wed 2016/10/26 11:36:22 PM System -100 [DHCP] state=RENEW Thu 2016/10/27 12:24:52 AM System -140000 my.isy.io Thu 2016/10/27 12:25:27 AM System -140000 my.isy.io Thu 2016/10/27 12:26:02 AM System -140000 my.isy.io Thu 2016/10/27 12:26:37 AM System -140000 my.isy.io Thu 2016/10/27 12:27:11 AM System -140000 my.isy.io Thu 2016/10/27 12:27:46 AM System -140000 my.isy.io Thu 2016/10/27 12:28:21 AM System -140000 my.isy.io Thu 2016/10/27 12:28:55 AM System -140000 my.isy.io Thu 2016/10/27 12:29:30 AM System -140000 my.isy.io Thu 2016/10/27 12:30:05 AM System -140000 my.isy.io Thu 2016/10/27 12:30:40 AM System -170001 [Network-DNS][Task=22] Failed DNS 11/rc=6 Thu 2016/10/27 12:30:40 AM System -140000 my.isy.io Thu 2016/10/27 12:31:15 AM System -170001 [Network-DNS][Task=22] Failed DNS 12/rc=6 Thu 2016/10/27 12:31:15 AM System -140000 my.isy.io Thu 2016/10/27 12:31:50 AM System -170001 [Network-DNS][Task=22] Failed DNS 13/rc=6 Thu 2016/10/27 12:31:50 AM System -140000 my.isy.io Thu 2016/10/27 12:32:26 AM System -170001 [Network-DNS][Task=22] Failed DNS 14/rc=6 Thu 2016/10/27 12:32:26 AM System -140000 my.isy.io Thu 2016/10/27 12:33:01 AM System -170001 [Network-DNS][Task=22] Failed DNS 15/rc=6 Thu 2016/10/27 12:33:01 AM System -140000 my.isy.io Thu 2016/10/27 12:33:36 AM System -170001 [Network-DNS][Task=22] Failed DNS 16/rc=6 Thu 2016/10/27 12:33:36 AM System -140000 my.isy.io Thu 2016/10/27 12:34:11 AM System -170001 [Network-DNS][Task=22] Failed DNS 17/rc=6 Thu 2016/10/27 12:34:11 AM System -140000 my.isy.io Thu 2016/10/27 12:34:46 AM System -170001 [Network-DNS][Task=22] Failed DNS 18/rc=6 Thu 2016/10/27 12:34:46 AM System -140000 my.isy.io Thu 2016/10/27 12:35:21 AM System -170001 [Network-DNS][Task=22] Failed DNS 19/rc=6 Whatever is failing, it doesn't seem to recover and I have to reboot my pfSense router to get the ISY back online. At the same time, I can obviously access the ISY and the portal, and my network access to the outside world is fine. I was using DHCP with an address registration and DNS address of my router, so I switched the ISY to a static address and DNS of 8.8.8.8. I hope that that improves the reliability, but it would be good to know what's actually going on. This morning, this was the end of the error log with the ISY offline at the portal. The "Start" was where the ISY rebooted after I gave it a static address: Thu 2016/10/27 12:59:16 AM System -170001 [Network-DNS][Task=22] Failed DNS 60/rc=6 Thu 2016/10/27 12:59:16 AM System -140000 my.isy.io Thu 2016/10/27 12:59:51 AM System -170001 [Network-DNS][Task=22] Failed DNS 61/rc=6 Thu 2016/10/27 12:59:51 AM System -140000 my.isy.io Thu 2016/10/27 01:00:26 AM System -170001 [Network-DNS][Task=22] Failed DNS 62/rc=6 Thu 2016/10/27 01:00:26 AM System -140000 my.isy.io Thu 2016/10/27 01:01:01 AM System -170001 [Network-DNS][Task=22] Failed DNS 63/rc=6 Thu 2016/10/27 01:01:01 AM System -140000 my.isy.io Thu 2016/10/27 01:30:25 AM System -140000 my.isy.io Thu 2016/10/27 01:31:00 AM System -140000 my.isy.io Thu 2016/10/27 01:31:35 AM System -140000 my.isy.io Thu 2016/10/27 01:32:10 AM System -140000 my.isy.io Thu 2016/10/27 01:32:46 AM System -140000 my.isy.io Thu 2016/10/27 01:33:21 AM System -140000 my.isy.io Thu 2016/10/27 01:33:56 AM System -140000 my.isy.io Thu 2016/10/27 02:21:30 AM System -100 [DHCP] state=RENEW Thu 2016/10/27 03:21:34 AM System -100 [DHCP] state=RENEW Thu 2016/10/27 04:21:38 AM System -100 [DHCP] state=RENEW Thu 2016/10/27 06:37:29 AM System -170001 UDQ: Queue(s) Full, message ignored Thu 2016/10/27 06:37:29 AM System -170001 UDQ: Queue(s) Full, message ignored Thu 2016/10/27 05:21:42 AM System -100 [DHCP] state=RENEW Thu 2016/10/27 06:21:42 AM System -100 [DHCP] state=RENEW Thu 2016/10/27 07:21:51 AM System -100 [DHCP] state=RENEW Thu 2016/10/27 07:41:13 AM System -10011 n/a Thu 2016/10/27 07:42:15 AM System -5 Start Thu 2016/10/27 07:42:17 AM System -110022 /CONF/INSTENG.OPT Thu 2016/10/27 07:42:17 AM System -110012 /CONF/INSTENG.OPT Thu 2016/10/27 07:42:18 AM System -110022 /DEF/F3/I1/NLS/EN_US.TXT hu 2016/10/27 07:42:24 AM System -7123 ID 0077 :err=0, tag='status', num=44, nest=4, o Link to comment
Michel Kohanim Posted October 28, 2016 Share Posted October 28, 2016 Hi rccoleman, I am so very sorry to hear. I think the issue is with DNS servers and probably the vestiges of the hack last week. In some cases, rebooting the router will help (clears the DNS cache) but I am afraid there's really no good solution at the moment except waiting for things to settle down. The last entries in your log are from yesterday. Do you still have the issue today? With kind regards, Michel Link to comment
rccoleman Posted October 28, 2016 Share Posted October 28, 2016 It was working this morning and it looks like it's still online now. If it happens again, I'll try some more surgical clearing of state information on the router. Link to comment
Michel Kohanim Posted October 28, 2016 Share Posted October 28, 2016 Hi rccoleman, Thanks so very much. Please do keep us posted. With kind regards, Michel Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.