bmercier

Try 1.2.9.x or 0.0.x.x 1.0.0.0 would make it dimmable, but on a scale of 0-255, which is probably incorrect.

Context: When you expose an ISY scene/program/variable as an Alexa scene, you can control them through Alexa by voice, but they are not visible in the Alexa app anywhere. Normally, you can change the Alexa category to expose them as a regular Alexa device instead. However, if for some reason you have deleted your mapping, and the scene stayed in Alexa, then there is no easy way to remove it. But here's the trick: You can add the scene to an Alexa group, then delete it from there. Here's how: Open the Alexa App. Select Devices, then click +, then Add Group, then Create a room or device group, give it a name. When adding devices to the group, scroll all the way down and add these extra Scenes to the Group and save. Now go back to Devices, and under Groups, click the group you created. When looking at the group, under SCENES, you should see the scene you added. Click on your scene, then you can click the trash can. This works at the time of this writing. Please note that Amazon updates their App frequently, so the instructions may be slightly different over time. Credits for this trick goes to @lgilsenberg Original post by @lgilsenberg here: https://forum.universal-devices.com/topic/42569-can-no-longer-delete-old-scenes-within-alexa/?do=findComment&comment=377233

Plugins needs to be updated. I believe most if not all have been updated by now.

I'm not exactly sure why, but it may have to do with the browser local storage. Try to clear the browser cache, or try using a different browser, or incognito mode.

I know nothing about Yolink, but based on the log, I believed it probably uses mqtt to connect to devices. If so, the plugin needs to be updated by the author. I recommend you post on the plugin's forum. The author needs to change this: https://eclipse.dev/paho/files/paho.mqtt.python/html/migrations.html#versioned-the-user-callbacks

Reinstall all plugins.

The plugin is trying to load module collections, but it can't find it. Try to reinstall this plugin (or all of them using System | reinstall all). If the module properly requires the module, it will get installed and will start to work. If it does not, then please try to contact the author using the plugin specific forum.

Please login to PG3 and try this: System | Reinstall all plugins

That's very strange that all of them don't start. Can you check the plugin logs? Does anything show at all when starting?

Hello everyone, This is the support thread for PG3x v3.2.27.

Hello everyone, There has been a few releases not publicly announced - here's the details: Release notes for: 3.2.27 Change timestamp format to YYYY-MM-DD HH:mm:ss.SSS (Same as python interface). Release notes for: 3.2.26 Enhanced reliability of the plugin's status node connected state. Release notes for: 3.2.25 Fix for UD Mobile remote connections. Some messages were too big and would not reach UD Mobile, causing a "spinning wheel". This fix is in PG3 only. An update to UD Mobile will be coming as well. Release notes for: 3.2.24 When reinstalling a plugin, don't delete the existing plugin files. Add support for plugins to override the polling values. Plugin license check tolerant of connectivity failures. Release notes for: 3.2.23 Added feature to allow system to automate a reinstall all plugins automatically, which will be used for emergency updates by UDX

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.

If you can reproduce the problem, look at the PG3 log. Look for this right after a node is created: "Group command sent..." or "Group command not sent..." An error code might give a clue. Or, PG3 may see a success where it is no. Either way, that would be useful to know to troubleshoot further.

No, unfortunately not possible.

FYI, a fix has been made:

If anyone still had problems with routines, please give it another try. A bug was found and fixed earlier today. Accounts with no preferred ISY would not receive events. The Alexa skill can work with no preferred ISY if the account only has one ISY. However, events would not be sent in that case. Now they are sent in that case as well.

My apologies if me or another team member let you down. Unfortunately I can't find any recent tickets from you related to this, so I'm not sure in what context I or someone else "has gone silent". This is definitely not how we do things at UDI. I must say that I worked extremely hard lately to identify and fix related Alexa routine issues in the back end. At this time, it should be stable for everyone. If it is not for you, I encourage you to open a ticket and mention your uuid. I will be happy to investigate further and ensure that it works for you as well.

No, polisy renewal price remains the same as eisy.

Are you able to see the sensor in the Alexa app, and have it change state? If you can, and you are on 5.8.3, please open a ticket and mention your uuid & which spoken you are testing with, I will check the logs.

Check your IoX version. Most likely you need to upgrade to the latest version, 5.8.3.

Notifications had some problems during the outage. The database was sometimes too slow, and this impacted subscriptions. Do you still have problems with notifications?

For anyone who is still having issues with Alexa routines, please check your IoX version. If it is not current, please make sure to upgrade to 5.8.3. There is a bug with subscriptions that can make it unstable and thus have an impact with Alexa routines. To upgrade, use Upgrade packages in the admin console.

The isy skill is very old, and this is not a smart home skill. That's a "custom skill". There's no chance that this interferes with isy optimized V3.

Go to the web site, My account | My tickets