Scottmichaelj Posted January 24, 2016 Share Posted January 24, 2016 I have been going through trying to setup my amazon echo to the protal without any luck. After having such a bad last week I really shouldnt be messing with this but I guess I am a gluten for punishment. I setup my account on my.isy.io and entered my ISY UDID. On the ISY side I selected Manage Modules and can see the Portal tab. Under the portal tab it shows the portal offline with a red flag but registered. When on the portal website the ISY is not found. I made sure I can access the ISY from outside my network via the IP and the port, which I can but I get the security warning. In my router I have the port being forwarded to the ISY internal IP address. I have all router firewalls turned off temporarily along with my windows firewalls. I went into the network security http://isy.universal-devices.com/994i/dashboard.jnlp and set my HTTPS Client Settings to Protocol TLS 1.0 Strength ALL and Verify Checked. For HTTPS Server Settings I have protocol on TLS 1.2 Strength Low and Verify is not checked. I do not have anything in CA, Server or Client Certificates. All my network settings and ports are right and I even have port forwarding setup in my router (I also tried to delete it as well). But for whatever reason I can not get the portal to see my ISY. Anyone have any ideas? Do I need a SSL cert? EDIT I am using v4.3.26 firmware and the UI and Firmware match. Here is some of my ISY Error log: Sun 2016/01/24 02:58:13 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 02:58:43 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 02:59:13 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 02:59:43 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:00:13 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:00:43 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:01:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:01:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:02:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:02:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:03:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:03:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:04:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:04:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:05:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:05:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:06:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:06:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:07:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:07:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:08:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:08:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:09:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:09:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:10:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:10:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:11:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:11:44 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:12:14 PM System -170001 [TCP-Conn] -1/-140002, Portal-Dispatch Sun 2016/01/24 03:12:27 PM System -170001 [TCP-Conn] -1/-140002, Portal-SECR Sun 2016/01/24 03:12:27 PM System -170001 [TCP-Conn] -1/-140002, Portal-SECA Link to comment
phlojo Posted January 24, 2016 Share Posted January 24, 2016 I had a very similar problem lately. For me it started when i replaced my wifi router. The bottom line, everything worked again and the portal connection was green only AFTER I deleted all port forwarding rules and manually assigned IP address to my ISY and enabled DHCP. It then got a new IP address from the router via DHCP. I then locked that IP address for it in my LAN settings, assigned and opened the ports I needed for remote access, and Portal started working. I hope this will help Link to comment
Scottmichaelj Posted January 24, 2016 Author Share Posted January 24, 2016 I had a very similar problem lately. For me it started when i replaced my wifi router. The bottom line, everything worked again and the portal connection was green only AFTER I deleted all port forwarding rules and manually assigned IP address to my ISY and enabled DHCP. It then got a new IP address from the router via DHCP. I then locked that IP address for it in my LAN settings, assigned and opened the ports I needed for remote access, and Portal started working. I hope this will help So if I understand you right, you deleted the port forwarding and changed the ISY IP from static to DHCP? Once that was done assume your rebooted the router the powered back the ISY which obtained a dhcp ip then you added that to your reserve list and then added new port forwarding rule to it so you could use mobilinc? Is that correct? Link to comment
Scottmichaelj Posted January 25, 2016 Author Share Posted January 25, 2016 So if I understand you right, you deleted the port forwarding and changed the ISY IP from static to DHCP? Once that was done assume your rebooted the router the powered back the ISY which obtained a dhcp ip then you added that to your reserve list and then added new port forwarding rule to it so you could use mobilinc? Is that correct? Did exactly as you suggested and I stated in my post above and your absolutely correct this worked for me as well. Thanks for the help! Link to comment
Tim McDermott Posted January 25, 2016 Share Posted January 25, 2016 It may have something to do with celiac disease. Link to comment
Scottmichaelj Posted January 25, 2016 Author Share Posted January 25, 2016 It may have something to do with celiac disease. Lol what!? A digestive disease? Now I could get behind something like stupidity but not ingestion. It is interesting that people have this issue. I had everything setup correctly obviously, so just switching from static to dhcp fixed it? Why? Would changing the static IP to something different fix it to? I suspect some type of bug there. Link to comment
Tim McDermott Posted January 25, 2016 Share Posted January 25, 2016 Sorry, I couldn't resist since Huddadudda is a gluten for punishment. Link to comment
Scottmichaelj Posted January 25, 2016 Author Share Posted January 25, 2016 Sorry, I couldn't resist since Huddadudda is a gluten for punishment. Duh, went over my head! Good one! Cleaver. Link to comment
stusviews Posted January 25, 2016 Share Posted January 25, 2016 Duh, went over my head! Good one! Cleaver. I should've axed what you meant. Link to comment
phlojo Posted January 25, 2016 Share Posted January 25, 2016 This thread took a weird turn. Sent from my iPad using Tapatalk Link to comment
madcodger Posted January 25, 2016 Share Posted January 25, 2016 Soooo, back to the subject at hand... Can anyone with a static (assigned) address for their ISY confirm use of portal and Echo? Or are all DHCP? Link to comment
stusviews Posted January 25, 2016 Share Posted January 25, 2016 I'm using a static IP address for my ISY 994i Pro with the portal and 3 Echos. Link to comment
Scottmichaelj Posted January 25, 2016 Author Share Posted January 25, 2016 Soooo, back to the subject at hand... Can anyone with a static (assigned) address for their ISY confirm use of portal and Echo? Or are all DHCP? When I have time I am going to change my ISY back to the original Static IP address to test. Not sure why I had to move from Static to DHCP to make it work. I honestly did NOTHING ELSE but change from static to DHCP and it worked. Thats why I think there is some type of weird bug here. I signed up for the "Connected Home" beta with Amazon a while back and as of yesterday it disappeared from my Amazon App. I saw Michel said the Beta was closed and its now fully open to everyone and "in the queue", so I assume thats why its gone and it will be added back soon. Link to comment
Scottmichaelj Posted January 25, 2016 Author Share Posted January 25, 2016 When I have time I am going to change my ISY back to the original Static IP address to test. Not sure why I had to move from Static to DHCP to make it work. I honestly did NOTHING ELSE but change from static to DHCP and it worked. Thats why I think there is some type of weird bug here. I signed up for the "Connected Home" beta with Amazon a while back and as of yesterday it disappeared from my Amazon App. I saw Michel said the Beta was closed and its now fully open to everyone and "in the queue", so I assume thats why its gone and it will be added back soon. I changed my ISY from DHCP back to original static IP and the portal can connect to it. So as I suspect there is something that causes the portal not to see the ISY until the IP changes or refreshes. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.