sandryseibert

It's not the first but the fifth time I had to disable a lamp device in Alexa app to stop her hunches to try to turn off a lamp in my house and then suddenly she (or something else) turn that lamp on instead. When I search the Logs, I can only see the Insteon device location followed by a simple "Error" and the log type Log is followed by another log type -2. When checking the isy.io eventlog, I found the following: 32 A2 72 1 ERR 0.000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002023/10/06 00:48:50 System 5 32 A2 72 1 2023/10/06 00:48:50 System -2 I've opened a support ticket and they told me Alexa sent the command correctly, but they told me Alexa sent the command correctly but "something" when wrong and Alexa canceled the action. When I look into Alexa app for hunches, I can see that indeed it is not asking me if she did it correctly or not, but a Cancelled status. In cases like this, Amazon is telling me that the fault was due to the device (this case IO portal). Does anyone experienced this issue?

Thanks for the response @MrBill.. I opened a ticket and Michael fast answered and fixed my backup. He found a huge Windows directory which was probably part of my efforts in the past to have a dashboard on ISY. I think I create a topic here many years ago talking about the process and I left it running even after move to Grafana/InfluxDB, so I think I was guilty. I couldn't login using the port 22 or 126.. I don't have telnet, but should open using Putty anyway.. Well, the only think I can say for now is thank you and special thanks to Michael for supporting me. I'm definitely decided to move to eisy as soon as I have change to travel to US again because here in Brazil we don't have ways to bring this device through standard carriers. Cheers Sandry Seibert

Hello community, I can't believe I tried to upgrade something that was working for so long just to connect an app, but I did that and the result was tragic. After update following the instructions with care I noticed the Zwave devices were not working. The Zwave 300 series which I have here used to report the firmware 4.55 and some version of the bootloader, however the bootloader start to show 0.00. I then tried to remove and add back my Schlage Lock and it almost worked showing the lock status but not the buttons to Lock and Unlock. So I had the brilliant idea to reset the Zwave dongle and redo the Zwave network, so I removed some devices and did the factory reset. After factory reset I noticed the Dongle were no longer responsive and I tried to restore the 4.9 backup which gaves me the Socket timeout error after show the error "Upgrade Failed: Failed uploading file (reported written size is invalid)". Doing the basis, research and try on my own to resolve the issue I found people stating it's probably an SD error, so I swapped to a new one and tried to restore, but keeps showing the error and what's most strange is that it's not happening on the same file. I mean, when you start the restore procedure you can see which file is being copied and it randomly stops in different stages, sometimes when copying a XML, sometimes other files... I already checked my firewall is off, my network isn't dropping any package even tried to direct connect to the ISY without using my LAN. Is there any way to extract the backup content directly to the SD card? I also noticed I can't use Putty to connect to the ISY, the port 126 is unresponsive. Thanks for some help