bmercier

Message understood. The automatic provisioning has been disabled this morning for this reason. Thanks, Benoit

Maintenance is completed. Benoit

Provisioning takes time. eisys were provisioned one after the other, automatically in sequence.

Precisely. PG3x and IoX 5.5.9 only.

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

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.

Yes, if at 5.5.9 with a valid license.

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.

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

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

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

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

Should be fixed now. A server had lost it's connection to the database somehow.

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.

What are you referring to?

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.

Today's maintenance is now complete.

Problem is now solved permamently. Benoit

Problem is now solved.

There is currently a known problem with the update: UD Mobile does not get device statuses. We are working on it.

Step one of the update is completed.

On Thursday and Friday, January 19th & 20th, we will proceed with a Portal update. This is a fairly major technology update which will cover the node.js version, but also major updates to node.js modules. The migration will be done in 2 steps and should be totally transparent with no down time. This is only a technology update; there are no new features. The first step will be done on 01/19 from 5am PST to 7am PST, and the second step will be done on 01/20, from 5am PST to 7am PST. Benoit

I believe you have another device with the spoken you chose. Try to enter the spoken in the search box to find which device has this spoken.

The refresh button on the right only refreshes the UI with the content from the server. It's only useful if the UI is opened from several devices at the same time. If the intent is to sync the devices with Alexa, the best way is to ask "Alexa, discover my devices". The sync is always from portal to Amazon. Not the opposite. Thanks Benoit

Portal does not support websockets. You can however get a subscription using a web service. You have to make a POST /services (using preferred ISY) or POST /<isyKey>/services This should get you started: const customHeader = { SOAPACTION : '"urn:udi-com:service:X_Insteon_Lighting_Service:1#Subscribe"' } const body = new Buffer.from('<s:Envelope><s:Body><u:Subscribe xmlns:u="urn:udi-com:service:X_Insteon_Lighting_Service:1"><reportURL></reportURL><duration>infinite</duration></u:Subscribe></s:Body></s:Envelope>') Benoit