3-26-16 Portal Issue?

[hmatos]

My ISY is working - I log in to the console and look at portal configuration and it says its online and registered.  When I go to the portal, it says my ISY is offline.  The Amazon Echo of course is not responding to any devices connected to my ISY.

 

Thanks,

 

hmr

[philtor]

Same here.

[tmorse305]

Ditto

[Thanatar]

Same here.

[bgav]

Had the same issue. Power cycled ISY, cable modem & router. Issue resolved.

[Deane Johnson]

Same here.  Power cycled and seems to be back working normally.

[paulbates]

Same. The message says "Offline since Saturday March 26th, at 4:01 am"

 

Reboot fixed it. The AC showed registered and online, pressing refresh changes nothing.

Edited March 26, 2016 by paulbates

[rlrjupiter]

Exact same problem.   Portal said it wasn't connected to house ISY, yet ISY said it was connected to portal.  Power reset on ISY resolved the issue.

[Teken]

Yesterday I received several emails indicating the 994 Series Controller was down and not accessible on the network infrastructure. Using the various network tools in the system confirmed the controller was not listed on the router or visible.

 

Performed a remote hard reboot from across town and she came back up. I detailed this same issue in the 4.4.6 RC3 thread and sent in my error logs to Mitchel the same night when I got home.

 

Not sure if this is related to my incident at all but wanted to put that out there. Upon logging into the ISY Portal it says it was online since Saturday March 26, 9:02:23 AM.

 

So its apparent to me the cloud service was down the whole night up to now?

[paulbates]

I'm guessing since 4am.. i got an expected email notification after midnight and wasn't looking for any since then  Here are some other investigative tidbits:

• Last error log entry, portal: 
  • 2016/03/16 00:34:36 System -140005 ISY
• Last few error log entries, ISY
  • Fri 2016/03/25 06:54:00 PM System -5012 390
    Fri 2016/03/25 06:55:06 PM System -5012 391
  • Rebooted here ~9:51am 3/26

    Sat 2016/03/26 09:52:18 AM System -170001 [uDSockets] RSub:24 error:6
    Sat 2016/03/26 09:52:30 AM System -5 Start
    Sat 2016/03/26 09:52:33 AM System -110022 /CONF/SEP/PRICE.LBL
    Sat 2016/03/26 09:52:41 AM System -110022 /DEF/F3/I1/NLS/EN_US.TXT
    Sat 2016/03/26 09:52:49 AM System -170001 [Network] Established
    Sat 2016/03/26 09:52:49 AM System -60006 n/a
    Sat 2016/03/26 09:56:25 AM System -140005 Net Module Rule: 18
• ​​​ISY Programs, network module and email alerts have been working as expected including the time the portal was down
• Eventlog looks normal throughout the night

Looks like some things going on portal wise.

 

Paul

[MWareman]

In my.isy.io - my ISY shows:

 

My ISY is still 4.4.5.

 

However, when I send REST commands via the ISY Portal - the ISY receives them...  ??

In the admin console - the portal shows 'Online' and 'Registered'. 

 

The entire portal UI thinks my ISY is offline though... even though REST commands via the Portal are still working.

 

Not sure what this all means - but it seems to be a false indication on the portal itself...

Edited March 26, 2016 by MWareman

[paulbates]

In my.isy.io - my ISY shows:

Capture.PNG

 

My ISY is still 4.4.5.

 

However, when I send REST commands via the ISY Portal - the ISY receives them...  ??

In the admin console - the portal shows 'Online' and 'Registered'. 

 

Not sure what this all means - but it seems to be a false indication on the portal itself...

 

That lines up with mine Michael, my 4:01am et would be your 3:01am ct

Paul

[MWareman]

A reboot caused the Portal to report online again...

 

I would guess some back-end process got kicked on the Portal - but none of our ISYs knew they had to re-register. 

[jerlands]

Exact same problem here.  offline since 0301am and reboot got it back.  Echo reported devices as offline in my case.

 

 

Jon...

[Michel Kohanim]

Hello everyone,

 

Sincere apologies for all the interruptions. The proxy was indeed going off and on with max memory usage. Although stabilized, we continue monitoring.

 

Again sincere apologies.

 

With kind regards,

Michel