bmercier

You will not see the port in the router, that is not something that would show. You need to connect to your Elk M1 using ElkRP2, you should see the port there. The default is 2601. As for the host, I would first look in ElkRP2. Is it configured with a static IP, or dynamic IP? If dynamic, then look in your router, it should show the IP address. If static, then it has to be in the same network as your eisy (and ideally your computer as well). Either way, are you able to ping it? If not, that has to be resolved first.

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.

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.

Please open a ticket, I will investigate the license issue. Please include your uuid & a link to this thread.

This was probably the Portal's Occupancy Node server. On my.isy.io, Select Tool | Occupancy Node Server | Configure, you can configure or remove the configuration. Slot 1 has no particular meaning. When you configure Occupancy, this will use the first slot available. That's probably what you had there.

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

There seems to be an outage with Ring itself. The infrastructure is up and we keep receiving webhooks from other sources than Ring. But It seems like we stopped receiving webhook events from Ring about 3 hours ago. Also, the errors in your PG3 log seems to confirm that the Ring API also do not respond. So something's wrong at Ring.

The best approach woud be to use an Alexa A/V device. In Portal, Select Tool | Connectivity | Amazon Echo, click on Add, A/V Give your receiver a name, and on the Volume tab, you can assign the Volume Up and Volume Down to programs. This will allow you to says something: "Alexa, turn up the volume on <spoken>"

Maintenance is now completed. Units now reconnects to portal a lot faster. Thanks for your patience! Benoit

Hello everyone, We will have a portal maintenace Monday July 29th at 5am PST, for a duration of approximately 1 hour. During this maintenance, there will be dowtime. During July 22nd's maintenance, we notices that it took quite a bit of time for all the units to reconnect following the maintenance. The purpose of this maintenance is to optimize this. Benoit

No, this was indeed a problem in Portal infrastructure. The way devices are queried and Routines gets triggered are 2 different things. When you go to the Alexa app and look at a devices, the status comes this way: Amazon makes a request to portal, and Portal makes a request to your controller. For this to work, you just need the skill to be linked, and your controller to be online on portal. Now in the case of routines, this requires a permanent "subscription" to your controller. Just like when you open the admin console, this creates a subscription and from now on, all devices changes are sent in real-time to the admin console, which updates. The bug was with the subscriptions.

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

Alexa routines should work well now for everyone.

Alexa routines should be working well as of now. There was a bug in the recent code that would break Alexa routines. Relinking the skill was a good work-around, but should no longer be necessary.