bmercier

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.

Most if not all systems are now back online.
This seems to have been caused by a regional internet outage somewhere. Some customers reported the error log, which allowed to determine it was indeed a connectivity issue.
On the portal side, no servers have been restarted, and no issues could be seen other than systems having disconnected and reconnected.
In addition, looking at the numbers, over 6,000 units stayed online. 

Login to portal using the same portal credentials. Click on My Profile (top-right), and change the preferred ISY to your eisy.

Are you perhaps running a VPN?
Can you check if you can login directly to Ring?

Hi Jim,
Found the problem. This is not specific to Ring. There will be a fix in PG3x 3.2.2. Look for a release later today.
Thanks for reporting this.
Benoit

One of the server lost it's connection to the database and was restarted.

Try this URL in a browser:
https://<your eisy>:3000/frontend/cloudlink
Make sure that <your eisy> is the same IP or hostname that you are using to access PG3
This URL should give you an error.
Then try again the Authenticate button
Not sure why the Update button would pop info about the node though.
Benoit

Use Select tool | Connectivity | Device Hint Editor
Choose your device and change the hint to 1.0.0.0.
This will make it recognized as a dimmable device.

Please try again, this should work better now.

This is happening because the device type is not recognized. If you try to use /rest/nodes/<your device address>, the type is probably 0.0.0.0. This is typical of early nodeservers.
To fix this, use Select Tool | Connectivity | Device Hint Editor.
I'm not sure what this device can do, but if it can be set to a value of 0 to 100, I would suggest to try 4.17.x.x, which is the equivalent of a dimmable ZWave dimmer. If this is only fully on/off, you can also use 2.x.x.x, which is the equivalent of an insteon non-dimmable switch.
 
 
 
 

Should be fixed now. A server had lost it's connection to the database somehow.

This is your ISY error log. Portal does not capture anything from this data.
But I agree it probably should not appear in the ISY error log in the first place.

Another thigh to try: 
go to Alexa.amazon.com. There is a place with a button to forget all devices. This might help.

Problem is now solved permamently.
Benoit

It's up now. ISYs are reconnecting.