bmercier

So here's what happened.
There were 2 bugs in the code of the proxy servers that were dormant. They had no effects, unless a proxy server had a hard stop... which happened last night. 
The first bug had the effect that some units were trying to connect to a no longer existing proxy server.
The second bug is more complicated to explain, but it was also caused by the hard stop. This one was causing the HTTP 500.
The hard stop was caused by AWS stopping one of our proxy instance unexpectedly. This was NOT a graceful shutdown. This is usually caused by the failure of the underlying hardware.
Both bugs have been fixed and are in production.

Problem has been resolved.
It may take a few minutes for all units to reconnect to portal.

This means that your eisy is indeed not connected to portal. For your undertanding, the connectivity from eisy to portal is initiated by eisy. 
If everything else works on eisy, then it could be a bad internet switch or port, patch cord, or perhaps the router not allowing internet access to eisy.

Contact & motion sensor events are debounced. There can't be more than 1 event within a 30 seconds period. So this is likely the reason if you are testing 2 doorbell rings within 30 seconds.
This is implemented within our Alexa skill.

I would suggest to try a different browser, or perhaps try incognito mode (If using Chrome).
I believe a browser extension is probably interfering somehow.
You could also try to press F12 and look at the browser console, then navigate to my.isy.io. You may see in the console an error message that could give you a clue.

Thanks for reporting this.
Please try again. I just forgot to push a commit.

First, please go to the Plugin store and click on "Refresh Store".
Then, you can try to restart the plugin. If it has been reinstalled in an attempt to fix it, it should be reinstalled again as the installed edition will be "Free", instead of "Standard" as it should.

Version 1.2 has no functional changes.
The main difference is that it is now using the UDI python interface's OAuth class.
If after updating there are oAuth errors, then a re-authorize should fix it.

Should be fixed now.

Have you tried to update your firmware?
In the admin console, click on upgrade packages.

It is indeed down:
https://status.ring.com/

Alexa routines should work well now for everyone.

Please wait a few more minutes. Although the maintenance is completed, not all units have reconnected to the portal. 
We currently have about 75% of the units reconnected.
I should have added that information in the notice.

My apologies, there was a bug, and it is now fixed. You should be able to by a license now.
You don't have to wait to the end of the trial. If you buy now, it will be added to the end of the existing license.

Should be working for everyone now.

This is now fixed. 
This is definitely a popup that had no functional impacts.

There was a problem with the Airthings-C licenses. This is now fixed.

No, polisy renewal price remains the same as eisy.

Notifications had some problems during the outage. The database was sometimes too slow, and this impacted subscriptions.
Do you still have problems with notifications?

The problem should be resolved now.

Please check if you still have the problem. I have reports from another user that it started working today. You may have to recreate the routine.
If not, please open a ticket and let us know:
The uuid The type of ISY "device" you are using. Is it an ISY state Variable? Insteon IOLinc? Something else? The device address What time you did the test and in what time zone (Or better, the UTC time you did the test)  

Hi Paul, 
This would require major changes. 
We are currently working on a new eisy/PG4. New features to PG3 will be limited to bug fixing and small enhancements.
For remote access to PG3, you can use UD Mobile. Click on Admin | Plugins.
 

Ed,
Could you try to unlink and relink the skill? This is likely to solve the problem.

This should be resolved now (as of 11PM Pacific time yesterday). This was caused by a misconfigured load-balancer.

Hi Geddy,
This was not a portal issue. The infrastructure was up all the time, and over 6000 units never lost their connection. There has been no changes on portal, no reboot, no lack of resources, nothing. Some units just disconnected and reconnected later.
Something happened on the internet between some customers and the portal infrastructure.