Michel Kohanim

FYI from Amazon : "8:48 PM PDT We have identified issues in AWS Lambda's capacity subsystem related to the increased API error rates and latencies in the US-EAST-1 Region and continue to work toward resolution." With kind regards, Michel

Hi all, Definitely AWS Lambda related. Unfortunately, there's no ETA. We'll keep you posted. With kind regards, Michel

Hello everyone, We are investigating but it does seem to be AWS in the east. We'll keep you posted. With kind regards, Michel

Hi Techman, Thanks so very much for the update. I very much doubt this had anything to do with Norton. With kind regards, Michel

Hi Techman, That would be highly unlikely unless you had no status updates in the Admin Console from other devices. Just to be clear, even though you see a mismatch in link records, right mouse click | Write updates to device does absolutely NOTHING. Correct? With kind regards, Michel

Hi Techman, Is there a green/gray icon right next to it? With kind regards, Michel

Thanks for the feedback everyone. With kind regards, Michel

Hi Athlon2k2, The error logs are with regards to the ISY trying to communicate with devices in which this PLM does not have a link. Did you actually do a File | Restore Devices? And, if so, did you see a series of link creations in the PLM FIRST before all the traffic you attached? With kind regards, Michel

Hi ggdowski, Already responded to your ticket. With kind regards, Michel

Hi Dr Pepper, Which ISY firmware? With kind regards, Michel

Hi Jimbo, I also got your ticket and forwarded to Chris. With kind regards, Michel

Hi Drew, Unfortunately not. But, if those devices are no longer in the system, it's best to do right mouse click | Disable. With kind regards, Michel

Hi geekdad, NOOO. That link is for the Amazon Skill ... i.e. Alexa ask izzy to ... With kind regards, Michel

MikeD, Correct! Thank you. With kind regards, Michel

Hi DarkCanuck, My pleasure and I am so sorry you have to go through this. With kind regards, Michel

Hi DarkCanuck, Unfortunately so. But do Z-Wave / Tools / Synchronize / All rather than deleting nodes. This will Synchronize ISY with your dongle. With kind regards, Michel

Hi jasont, Thanks so so very much for your input. With kind regards, Michel

Hi DarkCanuck, When you upgrade the firmware on the Z-Wave dongle, Unfortunately you lose all the data which you cannot restore unless you have backed up the dongle. The question are: Why would you upgrade the firmware? Had you ever done Z-Wave / Tools / Backup any time before upgrading the Z-Wave firmware? With kind regards, Michel

Hi geekdad, Have you tried: what is? http://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration#Supported_Commands With kind regards, Michel

Hi keribi, 512 is no longer supported by any sane browser. So, please use at least 1024. With kind regards, Michel

Hi keribi, What are your settings for Key Length, TLS (1.0, 1.1, 1.2), and Strength for HTTPS Server? With kind regards, Michel

Hi chrkov, Unfortunately quite out of our hands. With kind regards, Michel

Hi keribi, You can install a new self signed cert through the dashboard: http://wiki.universal-devices.com/index.php?title=Main_Page#Network_Security You will need to do that for HTTPS Server. With kind regards, Michel

Hi fastbird, 1. Please install the latest UI on your desktop: http://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Icon_on_Your_Desktop 2. Double click on the icon 3. In ISY Finder, click on the Add button 4. Enter the remote URL for your remote ISY With kind regards, Michel

Thanks Gary. Benoit reviewed the specs and it seems that everything is local (no cloud) which his fantastic. This said, they have their own protocol on top of Bonjour (for discovery) so the level of effort would be just a little less than developing Z-Wave or Zigbee protocol stacks. In addition, it's still quite fuzzy as to where ISY fits in. We are still investigating. With kind regards, Michel