bmercier

Hello everyone, Our current Google Home action will stop working on June 13th and will need to be replaced. This is due to Google which sunset Google conversation actions. Ref: https://developers.google.com/assistant/ca-sunset We are currently working on the new action "Universal Devices V2", and it should be ready on time by next week. Whenever it becomes available, you will have to unlink "Universal Devices" and relink using "Universal Devices V2". All of your "spokens" that you have configured in portal will still be there. However, whenever you unlink and relink, this will remove the devices in Google Home/Google assistant, and re-create the same devices. You will have to reassign rooms, and it will probably break your routines as well, if you are using them. Stay tuned.

Portal is up, and ISYs/Polisys/eisys are currently reconnecting.

Maintenance has started a bit late and is currently underway.

Why are you using polyglot.isy.io? Sent from my iPhone using Tapatalk

A forum post here is a good option. Often, the problem is not portal itself, and the community can help. Alternatively, a opening a ticket is another option, when you are certain that there is a problem and the community can't help. I do not actively follow forum posts, but I get notified of posts in this topic. I saw your post and investigated immediately.

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

Hello everyone, We will have a maintenance on Monday 06-05-2023 at 5:00 AM Pacific time which will last about 30 minutes. During this period, Portal will be offline. Benoit

I guess the Update button does not exists when the nodeserver is installed from the beta store. You should reinstall from the production store. There is a trial available.

In PG3, go to the Ring nodeserver (ISY Dashboard | Ring | Details), then click Update

FYI, Ring 1.1.0 is now available. New feature: Add support for shared devices. To support shared devices, you need to add a custom param "shared" with a value of "true" (without the double quotes)

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

Make sure you are using Ring from the Production store. The Non-Production store will not authenticate with the current settings.

Unfortunately no, as this is not available in the API.

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.

Portal maintenance is completed.

Please try again, this should work better now.

Hello everyone, We will have a maintenance on Tuesday 05-02-2023 at 5:00 AM Pacific time which will last about 30 minutes. During this period, your ISY may disconnect briefly from portal. The purpose is to update SSL certificates.

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.

There are many reasons why a connection may drop. If it's just once in a while, there is nothing to be concerned about. I would suggest to look at the ISY error log, there might be something happening there.

Portal maintenance is now completed.

Hello everyone, We will have a maintenance on Tuesday 04-18-2023 at 5:00 AM Pacific time which will last about 30 minutes. During this period, your ISY may disconnect briefly from portal. Benoit

It's probably the opposite. ISY rebooted, and incidently became offline. Portal does not trigger reboots (Except for one specific maintenance a few weeks ago).

Thanks for the report. I analyzed the problem and just pushed a fix. Benoit

ISY/Polisy/eisy opens a permanent socket connection to Portal. Whenever that socket connection drop, ISY will automatically attempt to reconnect. There are a number of reasons why a socket can drop: ISY Reboot Router reboot Bad Internet connectivity ISP changing your IP address Routers may also mess with connections Portal maintenance. etc. So a reconnection once in a while is not really a problem. However, if you see constant reconnections, it's a sign of a problem somewhere on ISY/Polisy/eisy, your network, or your internet connection. Portal maintenances affecting connections are rare and announced on the forum. In the future, there will also be a UD communication (push notitication) which will let you know before a maintenance. FYI, not all portal maintenances have an effect. Only maintenance on specific servers handling inbound connections would impact the ISY-to-Portal connectivity. If you see regular disconnect/reconnects, such as every hours or more frequent, I encourage you to open a ticket.

Hello everyone, There is now a delay used before sending online/offline notifications. When getting offline, there is now a delay of 60 seconds before a notification is sent. It it comes back online within that delay, no notification will be sent. When getting online, there is now a delay of 5 seconds before the notification is sent. If it goes offline within that delay, no notification is sent. In addition, the notifications now includes the alias. Let me know if you encounter any issues. Thanks for your feedback!