bmercier

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.

There's nothing to do with the file. This was just a way to test that there's no networking issue preventing access to the certificate. If that was the case, that could have been a reason for the error message you are getting. At this point, I'm not sure why you are getting this error.

In addition, I would try this; Check if this link works from your computer (The same device you are using for https://tesla.com/_ak/my.isy.io): https://my.isy.io/.well-known/appspecific/com.tesla.3p.public-key.pem This is supposed to download a public key. One of the potential causes for the error you are having is that it can't download this public key.

@larryllix This seems to be an Amazon bug indeed. A smart home skill can't decide on what words to speak. It can return error codes, which triggers Alexa to speak pre-determined error messages. So if it's saying nonsense, then it's either an Amazon bug or an Alexa configuration issue. An example that comes to mind is if it was configured for an incorrect language, then it would not understand you and say some gibberish in another language. You probably have a different issue that this as she seems to respond in english, but I have no clue what the problem may be.

Portal now supports an easier method to sign-in using a Google account. If your portal email address is a gmail account, you can use Google sign-in for a faster login. If a portal account does not exist for the google email address, a new account will automatically be created. If you currently use a non-gmail address to login to portal and would like to use a google email instead, then proceed this way: Login to my.isy.io and click on users Add a user profile with the same email address as your google account That's it. You can now use Google Sign-in, to login to your portal account. There's no need to validate your email address, you can ignore the verification email. Optionnally, you can remove your previous use profile. If so, and if you are using Google Home or Alexa, you will have to relink the skill with with the new user profile. Your spoken configuration will be preserved, all you need is to relink.

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

Just wanted to confirm that the maintenance is completed.

Hello everyone, We will have a portal maintenace tomorrow Friday October 25th at 5am PST, for a duration of approximately 30 minutes. During this maintenance, units will disconnects and reconnect briefly. The purpose of this maintenance is to fix an issue where some units may sometimes become non-responsive when accessed from portal. Benoit

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.