bmercier Posted March 21, 2023 Posted March 21, 2023 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 4 1
bmercier Posted March 24, 2023 Author Posted March 24, 2023 On 3/21/2023 at 4:47 PM, bmercier said: 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 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 1 2
bmercier Posted March 24, 2023 Author Posted March 24, 2023 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. 1 1
Recommended Posts