
bmercier
Employees-
Posts
168 -
Joined
-
Last visited
Everything posted by bmercier
-
TinyMCE window appearing when accessing the Portal.
bmercier replied to garybixler's topic in UD Portal
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.
-
Support thread for: PG3x v3.2.22 (April 16th, 2024)
bmercier replied to bmercier's topic in Polyglot v3 (PG3x)
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
-
Please open a ticket, and attach the PG3 log. Will investigate.
-
That should work. The important thing is when reinstallling, you are presented with all the purchases, including the free license. The install has to be done using the purchased one. Sent from my iPhone using Tapatalk
-
Then events are sent to Amazon. If you can see the status changes in the Alexa app, then it can only be a problem at amazon. Sent from my iPhone using Tapatalk
-
This thing works by maintaining a permanent subscription to each units. If the subscriptions does not come up, that would show this symptom. So as a test, please try to use AC or UDM over a remote connection. This will test that subscriptions are working.
-
I checked the logs, and events seems to be working well. So it's likely an issue at Amazon.
-
PM me your uuid. Will check the logs later tonight. Sent from my iPhone using Tapatalk
-
Does UDM or AC work remotely? Is this a 994? Sent from my iPhone using Tapatalk
-
Try to recreate your routine. Test if you can login with the Admin console through portal, or using UDM remotely (not locally).
-
Portal is not involved with sending emails. Alexa routines should be working. Try to recreate the routine.
-
For some users, if it's still not working, it's likely a problem with the security settings. This means you are on a 994 with an encryption setting set to low or medium. That is no longer supported. It has to be on high or auto, which is the default. To change it back to high, you need to use the former ISY Dashboard.
-
Please try one more time. As of now, this should be working for the vast majority of users.