Jump to content

bmercier

Employees
  • Posts

    98
  • Joined

  • Last visited

Everything posted by bmercier

  1. Whenever there is a maintenance or a known problem, you will see a post on the forum under UD Portal. Maintenances are pinned for a while.
  2. Your ISY definitely have an issue. I know a few ISY keep connecting/disconnecting continuously. Please open a ticket so it is investigated further. FYI, when you login to portal, hover the mouse on the green dot. This will tell you the las connection time. This may be useful while you disable the notifications.
  3. Good suggestion. I will look into that feature.
  4. Click on the top left arrow
  5. Test message is the way to go. After sending a test notification, when you know who the phone belongs to, click on the name to change the name to something meaningful.
  6. UD Mobile now features 2 new notification options. Please review the notifications settings by clicking the gear icon at the top right of the "Notifications" tab. UD Communications To receive Universal Devices communications, make sure that the Group "UD Communications" has at least one phone active. System notifications On Monday April 3rd, 8 AM Pacific time, we will turn on System notifications. Whenever an ISY/Polisy/eisy connects or disconnects from Portal, you will receive a notification on all phones active in the group "System notifications". We recommend that you review your notification settings so that the relevant phones receive these notifications. Benoit
  7. Message understood. The automatic provisioning has been disabled this morning for this reason. Thanks, Benoit
  8. Maintenance is completed. Benoit
  9. Provisioning takes time. eisys were provisioned one after the other, automatically in sequence.
  10. Precisely. PG3x and IoX 5.5.9 only.
  11. Hello everyone, We will have a maintenance on Monday 03-27-2023 at 5:00 AM Pacific time which will last about 1 hour. During this period, your ISY will disconnect from portal for a few brief moments. The purpose is to rollback a feature introduced during the 03-24 maintenance. Please see this post for more details: Thanks, Benoit
  12. Here's more details. PG3 remote access will work with the help of a permanent connection to AWS IoT Core. The feature this morning included 3 things: Determine if the eisy firmware supports PG3 remote access and if it is already configured Auto-Provision the connection to AWS IoT Core Auto-Deprovision the connection to AWS IoT Core if the license expires This morning, all eisy's at 5.5.9 were auto-provisioned. This process involves a reboot on eisy, which some of you noticed. For most of you, the update went quite well. However, we noticed that a small number of eisy started to lose their connection to portal every minutes or so, and this seems to correlate with the time they were automatically-provisioned. In addition, manual deprovisioning did not help. Therefore we are planning to rollback and disable the Auto-Provisioning on Monday. Separate post to follow. If you are experiencing connectivity problem with portal, please open a ticket. We will need to see logs to find the root cause. Thanks in advance for your help.
  13. Yes, if at 5.5.9 with a valid license.
  14. This update is in preparation of PG3 remote access. One of the thing that it does, is provision access to AWS IoT Core. The reboot is a sign that provisioning went successfully. We are noticing an issue currently, several eisy's keep losing their connection and reconnecting. This is currently under investigation.
  15. I would add that the maintenance did not impact the database, the web server or the oAuth servers. The only impact was that the ISY to Portal connectivity was dropped for a few seconds, and the subscriptions as well. Benoit
  16. I'm not sure how your issue could be linked to the maintenance. Also I'm not sure how the DSC nodeserver works, if it relies on cloud resources. The answer may lie in the nodeserver log. Benoit
  17. Maintenance is now completed. EDIT: This update is in preparation of PG3 remote access. One of the thing that it does, is provision access to AWS IoT Core. The reboot is a sign that provisioning went successfully. We are noticing an issue currently, several eisy's keep losing their connection and reconnecting. This is currently under investigation. Benoit
  18. Hello everyone, We will have a maintenance this Friday 03-24-2023 at 5:00 AM Pacific time which will last about 1 hour. During this period, your ISY will disconnect for a few brief moments. The purpose is to prepare for an upcoming new feature: PG3 remote access. Benoit
  19. Should be fixed now. A server had lost it's connection to the database somehow.
  20. This is your ISY error log. Portal does not capture anything from this data. But I agree it probably should not appear in the ISY error log in the first place.
  21. What are you referring to?
  22. bmercier

    reboots required

    When it's not working, I would check if ISY is online on portal, and if so, if it responds to requests. To test this, just use ISY Web access. I don't think the issue is specific to Google home connectivity.
  23. Today's maintenance is now complete.
  24. Problem is now solved permamently. Benoit
×
×
  • Create New...