bmercier

I looked at the logs, and it looks like your problem is now resolved. If not, please open a ticket and it will be a pleasure to help you. Benoit

When adding/updating/deleting Alexa spokens from Portal or UD Mobile, changes are now immediately reflected in Alexa. It's no longer required to ask "Alexa, discover my devices" to send updates to Alexa. This change makes the maintenance of spokens easier and less error prone. This works as long as the skill is linked. You can still add or update spokens while the skill is not linked, however a device discovery will be required to send updates (it's done automatically after linking). If you delete spokens while the skill is not linked, then the corresponding Alexa device also has to manually removed from the Alexa app, just like before. A device discovery only add/updates the Alexa devices. It won't remove the spokens removed from portal or UD Mobile.

I have made a few more tests. Some that work: HDMI1 HDMI2 DVR ANTENNA Many don't though. When you hear <device> doesn't support that, it's a sign that the input was understood, but your A/V device did not have that input defined. If you hear any other error message or a beep, Alexa does not understand the input you spoke.

Wow, that's a neat trick. Never though of that, but it makes sense. Thanks for sharing!

Please try different and easier input names. Because the the input select names are custom, Alexa has to really understand very well the name so that it can be an exact match to what you entered.

I reproduced this problem on eisy. If you are familiar with ssh, here's how to resolve the problem. The instructions below are used to complete the installation of node-sonos-http-api, which is used by the ST-Sonos plugin. From a command prompt, ssh to your eisy: ssh admin@eisy.local Default password is admin Confirm that node-sonos-http-api is now working: curl http://localhost:5005/ You should be getting a connection error. Go to the folder where plugins are installed: cd /var/polyglot/pg3/ns Check the list of plugins installed: ls -l You need to know in what slot the plugin is installed. You can check in the PG3 Dashboard. Go to the plugin folder: cd <uuid>_<slot> The easiest is to copy paste the folder name you obtained from ls -l in step 3 Go to the node-sonos-http-api folder: cd node-sonos-http-api Install node-sonos-http-api pre-reqs: sudo npm install Start node-sonos-http-api: npm start Restart the plugin from the PG3 dashboard. It should now be working. When rebooting eisy, it appears that node-sonos-http-api is also restarted. You can use these instructions until a permanent fix is made to the plugin. UPDATE: Node server has been fixed, uninstall and reinstall the plugin. You may have to restart PG3 if you are reinstalling before the update is refreshed from the store.

This means PG3x service is not started. Can you access isy through admin console?

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

Please open a ticket, mention your uuid, and attach the error log.

Hello everyone, This is the support thread for PG3x v3.2.17. Happy Holidays!

Hello everyone, Here's the latest PG3x release. Release notes for: 3.2.17 - 12/19/2023 Allow to remove a node server even if the store entry no longer exists. When auto-logout, add a message in the UI. Add a rate limit on MQTT inbound messages from plugins & UI. Fix addnode for cases where the ISY request fails with an http error. When viewing a plugin, hide the readme and changelog if they are null. When new version is available, have the update button appear. Previously a restart of the node server was required. Make PG3 logLevel persistant Fix setController on first startup. Previously, setController will fail if addnode is not finished. Fix store edit UI (We could get a JS error due to accessing an incorrect field). Minor bug fixes and logging enhancements

You may want to try a reboot. Portal infrastructure is up, and looking at the numbers, most units are up. There is no mass outage as was seen earlier today.

It should be automatic. The unit retries to connect every minutes or so. You must have another problem going on as we have pretty much the same number of units connected as before. So perhaps in your case you should try a reboot. If this does not come up, please open a ticket, reference this thread, let me know your uuid, and attach your error log.

Hi Chris, The UD Portal forum is a good place for such a post. Internet access option in admin console no longer exists on new polisy & eisy.

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.

We are getting many reports of portal being offline. At this time, it looks like it's up and most isy/polisy/eisy are online and working. We are currently investigating this and will post an update here when we have more information.

Please update the plugin to version 1.1.7, that should fix it.

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

Please open a ticket referencing this thread. Make sure to mention your uuid and the node address that is “matched properly in my.isy.io” but that won’t appear in google home when syncing. I will investigate further.

Those settings only control the discovery of devices. Once they are discovered by Alexa, the devices will continue to work as long as the spoken still exists and the ISY is still in the account.

Did you login with the same portal user and password? If so you should see them there. The "Showing 51 to 1 of 1 entries" seems to indicate a UI problem. I suspect there may be special characters that may be messing the display. Are you able to reproduce the problem? Please open a ticket, attach the screen shot, and please let me know the uuid. Will also need to know what browser you are using as it may be browser-dependant. If you know how to reproduce it, please let me know how.

It could have been that it was not approved in the admin console, then you approved it before trying it again? Or perhaps it was just not online, but then, the message would have been different.

My recommendation would be Alexa. I developed both the Alexa skill and Google Home action, and I can tell you the integration is slighty more advanced with Alexa. We also have significantly more customers using Alexa than GH.

I'm not sure what are the capabilities of this node. I guess it's used to arm and disarm. Does it accept commands like DON/DOF? if so, with the right hint, it could be exposed as a light. @KHouse, You could try hint 1.2.9.0 as a test. After changing a hint, you need to add or remove/re-add the node to the spokens, then have Alexa discover your devices. The main problem I see though is that if you expose this node directly like this, then turning on/off will allow to arm and disarm. If you only want to arm by voice, and prevent disarm, then I would take this approach: Create a program, in the then statement, have it arm your elk. Leave the else empty. Expose the program as a light. Add the program to the spokens, have Alexa discover your devices. "Turn on" will run then, "turn off" will run else... which means it won't do nothing. @Jimbo.Automates, the hint for an alarm panel should be 1.1.1.x, as defined in hints.yaml. But that will not make it work with Alexa. The skill does not currently have support for an alarm panel. But that could be a future enhancement.