btreinders

@bmercier I don't see a difference in the logs with it uncommented. Should the logs look like code? I am using runthen. I tried ifttt this time and the program still did not execute.

@bmercierThanks for help! I tried this and I don't get any errors (it seems to execute fine) but the program in the ISY does not run. I was seeing the same with other code from the web that I have tried including the request module. I had also tried IFTTT before with the result. Executes but the program does not run. I have not tried the IFTTT way with this code because I was not sure what to do with the username and password. Just leave them blank? Any ideas why the rest call isn't working? Thanks!

I have tried everything I found searching the internet with https calls in node.js to make a REST call to the portal from the AWS Lambda function and nothing will activate a program. Does anyone know if this is possible? I am using the URL from the portal with my username and password. I am able to trigger a program from Chrome using the URL. I don't know much about node.js so please be gentle. Thanks!

The ISY is fine. 5.0.14 for both. It seems to be completely normal after the restore. Sorry if that wasn't clear. Polyglot not being able to login is the issue again.

Here we go again. Had to restore the ISY again after installing AVRemote. Not sure what happened but after rebooting all an entire folder of programs showed not saved and were moved to top level. I changed ISY user and password back to original after the restore and now Polyglot cannot login again. Rebooting the ISY does not help this time. Restarting Polyglot does not help. I am at a loss.

Ok, finally back in business, I had to reboot the ISY, maybe all that spamming from the old install put it in a bad state. Thanks for all the help!

It is auto discovering the ISY and the address is correct. I even typed it all in manually. Here is the log. 2018-11-4 08:51:05 - info: Settings Saved Successfully. 2018-11-4 08:51:05 - error: ISY: connection failed. Retrying... Error: Parse Error 2018-11-4 08:51:05 - error: ISY: connection failed. Retrying... Error: Parse Error 2018-11-4 08:51:05 - error: ISY: connection exceeded max re-tries. Aborting. Error: Parse Error 2018-11-4 08:51:05 - error: Get Version HTTP Error: RequestError: Error: Parse Error 2018-11-4 08:51:05 - error: ISY: Failed to get version.

Thanks! Yes, I did remove the Blue Iris node server from the ISY, from the dashboard and from the store. None of that helped. I finally just wiped the RPi and have set it up again. I installed polyglot with wget -qO - https://raw.githubusercontent.com/UniversalDevicesInc/polyglot-v2/master/scripts/install.sh | bash -e Now I cannot set the ISY password in Polyglot. I've tried with IE and Chrome and it says it saves it but really does not since I get the red bar refreshing the dashboard complaining the username and password are not set.

That just kill polyglot right? (actually it looks like polyglot just restarts itself after the kill -9) sudo systemctl stop polyglot-v2 does seem to kill it. The next time I reboot the Pi it will start again? I'd like to do a complete uninstall and then reinstall it to see if the log behaves. If I use the sudo apt-get remove command it says it is not installed. If I delete the polyglot directory it does stop it from starting at boot but once I install it again it remembers everything like username etc.... and the log is again scrolling like crazy. Thanks

Have a new issue trying to uninstall Blue Iris node server. I deleted it in the ISY, in Polyglot and uninstalled from the store. I still have this scrolling like crazy in the Polyglot log. 2018-10-30 15:19:35 - info: BlueIris(5): n005_cam5 ST set sucessfully to 0 : UOM 2 2018-10-30 15:19:36 - info: BlueIris(5): n005_cam5 GV6 set sucessfully to 0 : UOM 2 2018-10-30 15:20:17 - info: BlueIris(5): Processing command: status 2018-10-30 15:20:17 - info: BlueIris(5): Processing command: status 2018-10-30 15:20:17 - info: BlueIris(5): Processing command: status 2018-10-30 15:20:17 - info: BlueIris(5): n005_cam5 ST set sucessfully to 1 : UOM 2 2018-10-30 15:20:18 - info: BlueIris(5): n005_cam5 GV6 set sucessfully to 1 : UOM 2 2018-10-30 15:20:18 - info: BlueIris(5): n005_cam5 GV3 set sucessfully to 1 : UOM 2 2018-10-30 15:20:23 - info: BlueIris(5): Processing command: status 2018-10-30 15:20:23 - info: BlueIris(5): Processing command: status 2018-10-30 15:20:24 - info: BlueIris(5): n005_cam1 ST set sucessfully to 1 : UOM 2 2018-10-30 15:20:24 - info: BlueIris(5): n005_cam1 GV6 set sucessfully to 1 : UOM 2 2018-10-30 15:20:25 - info: BlueIris(5): Processing command: status 2018-10-30 15:20:26 - info: BlueIris(5): n005_cam1 GV3 set sucessfully to 1 : UOM 2 2018-10-30 15:20:31 - info: BlueIris(5): Processing command: status I tried uninstalling Polyglot but really have no idea how to so I tried just reinstalling Polyglot but has not helped. It's running a a Raspberry Pi III. It's scrolling so fast the log just locks up and stops scrolling and if I go to another page and back it is still scrolling.

I deleted all of the polyglot node servers and now it reboots quickly. I had AVRemote, Ecobee (which never worked), Blue Iris, Harmony, Magic Controller and Hue installed. I guess I will install them one by one and reboot in between.

Yes that allows it to boot up quickly. Here is the log file, not much in it. 0 null Fri 2018/11/02 10:20:09 AM System Start Get NodeDef ZWave 0 Fri 2018/11/02 08:20:59 AM System Log 0 null Fri 2018/11/02 11:39:38 AM System Start Front Door Kwikset Lock The user access code that associated with the most recent Alarm 0 Fri 2018/11/02 11:40:31 AM System Log Front Door Kwikset Lock Status Unlocked Fri 2018/11/02 11:40:31 AM System Log Get NodeDef ZWave 0 Fri 2018/11/02 11:42:33 AM System Log Error log Time User Code Message Fri 2018/11/02 10:20:09 AM System -5 Start Fri 2018/11/02 10:20:10 AM System -110022 /CONF/INSTENG.OPT Fri 2018/11/02 10:20:10 AM System -110012 /CONF/INSTENG.OPT Fri 2018/11/02 10:20:14 AM System -110022 /DEF/F6/I1/NLS/EN_US.TXT Fri 2018/11/02 10:20:14 AM System -110022 /CONF/UXT.BIN Fri 2018/11/02 10:20:14 AM System -110012 /CONF/UXT.BIN Fri 2018/11/02 10:20:15 AM System -110022 /CONF/ELKXPRT.XML Fri 2018/11/02 10:20:15 AM System -110022 /CONF/UZWNDKEY.TXT Fri 2018/11/02 10:20:15 AM System -110012 /CONF/UZWNDKEY.TXT Fri 2018/11/02 10:20:15 AM System -170001 [Network] Established Fri 2018/11/02 10:20:15 AM System -110022 /CONF/PORTALS.PSF Fri 2018/11/02 10:46:58 AM System -5 Start Fri 2018/11/02 10:46:59 AM System -110022 /CONF/INSTENG.OPT Fri 2018/11/02 10:46:59 AM System -110012 /CONF/INSTENG.OPT Fri 2018/11/02 10:47:04 AM System -110022 /DEF/F6/I1/NLS/EN_US.TXT Fri 2018/11/02 10:49:26 AM System -110021 /WEB/DRIVER.XML Fri 2018/11/02 10:49:51 AM System -110022 /WEB/DRIVER.XML Fri 2018/11/02 10:50:21 AM System -110022 /WEB/DRIVER.XML Fri 2018/11/02 10:50:50 AM System -170001 [UDSockets] Portal:41 error:6 Fri 2018/11/02 10:51:41 AM System -110012 /CONF/0143.CZW Fri 2018/11/02 10:51:43 AM System -110022 /WEB/DRIVER.XML Fri 2018/11/02 10:51:52 AM System -110022 /CONF/NET/38.RCT Fri 2018/11/02 10:51:52 AM System -110012 /CONF/NET/38.RCT Fri 2018/11/02 10:51:55 AM System -170001 [UDSockets] HTTP:29 error:6 Fri 2018/11/02 10:51:55 AM System -170001 [UDSockets] HTTP:36 error:6 Fri 2018/11/02 10:51:55 AM System -110022 /CONF/0151.CZW Fri 2018/11/02 10:51:55 AM System -110012 /CONF/0151.CZW Fri 2018/11/02 11:39:38 AM System -5 Start Fri 2018/11/02 11:39:58 AM System -110022 /CONF/INSTENG.OPT Fri 2018/11/02 11:39:58 AM System -110012 /CONF/INSTENG.OPT

I have been trying since 1:30 today to get the logs but I am having trouble. I rebooted from the AC and when I got home at 4:30 I still could not get the AC up. I telneted in and rebooted again and when it came back up about 20 mins later I had the programs enabled again issue. I factory reset put a different SD card in and restored from backup. I rebooted again from the AC and 1 hour later I was finally able to get the AC up but now the logs will not open. I get an error sometimes (Subscriber didn't reply to event: 1) and other times Excel opens but neither case has any data in the log. Just a header line and over 1 million rows with no data. Trying to open the error log just pops up Request Failed. I had cleared both before restarting the first time.

@Michel KohanimYeah, I hope he has some info from the log for me.

No flashing LEDs. The issue is I can't even get to the AC to see flashing red and green. The log start time is 20 minutes after I apply power so I would not think any programs would run until that point. I do have a startup program that runs once and sets a few variables but I don't see anything that would loop because of it. I do have those exact issues when it boots up and a lot of programs that were disabled are suddenly enabled. But that's not the issue here anymore. I can avoid that issue by not pulling power during the long boot up.

@larryllix I would agree but the programs don't even start executing for almost 20 minutes after reboot. The programs that were supposed to be disabled being enabled was causing the issues you quoted above. That only happens if I cycle power to the ISY while it is booting up and I am not doing that anymore. Still not sure why that happens though. It happened when I updated to 5.x as well. Thanks

No definitive culprit yet. I first re-seated the SD card and that did not help. I formatted the card and that did not help. I put a brand new one in, formatted and that did not help. I factory reset, installed 5.0.14 and that did not help. In fact since I took out the queries at startup it seems to be even taking longer. I never got into the AC and I even waited an hour one time. I put the original card back in thinking I'd be back at 5.0.13D but instead found I was still on 5.0.14. Makes sense I guess if the firmware is loaded completely in the ISY memory. I booted up on the old SD card and when I went to bed 20 minutes later I still could not get into the AC. Things were kind of working at that point though since the ELK was telling me good night when I armed it. The bedroom TV came on like it should as well and all the lights turned off after motion wasn't being detected. When I woke up I was able to get into the AC just fine and everything seems to be working. I assume if I reboot it, it'll take forever again. Below is error log since the last reboot. Of note, I booted the ISY up at 9:45 and the first entry is 10:08. Thanks in advance! Tue 2018/10/30 10:08:46 PM System -5 Start Tue 2018/10/30 10:08:47 PM System -110022 /CONF/INSTENG.OPT Tue 2018/10/30 10:08:47 PM System -110012 /CONF/INSTENG.OPT Tue 2018/10/30 10:08:52 PM System -110022 /DEF/F6/I1/NLS/EN_US.TXT Tue 2018/10/30 10:11:17 PM System -110021 /WEB/DRIVER.XML Tue 2018/10/30 10:12:17 PM System -110022 /WEB/DRIVER.XML Tue 2018/10/30 10:12:24 PM System -110021 /CONF/0146.CZW Tue 2018/10/30 10:12:47 PM System -110021 /CONF/0146.CZW Tue 2018/10/30 10:12:59 PM System -110014 /CONF/0146.CZW Tue 2018/10/30 10:13:18 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 51 Tue 2018/10/30 10:13:18 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 53 Tue 2018/10/30 10:13:18 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 55 Tue 2018/10/30 10:13:18 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 57 Tue 2018/10/30 10:13:18 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 59 Tue 2018/10/30 10:13:18 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 83 Tue 2018/10/30 10:13:19 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 63 Tue 2018/10/30 10:13:19 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 61 Tue 2018/10/30 10:13:19 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 65 Tue 2018/10/30 10:13:19 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 91 Tue 2018/10/30 10:13:19 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 69 Tue 2018/10/30 10:13:19 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 71 Tue 2018/10/30 10:13:19 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 73 Tue 2018/10/30 10:13:28 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 219 Tue 2018/10/30 10:13:30 PM System -140005 Net Module Rule: 28 Tue 2018/10/30 10:13:32 PM System -140005 Net Module Rule: 28 Tue 2018/10/30 10:14:05 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 219 Tue 2018/10/30 10:14:16 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 219 Tue 2018/10/30 10:14:40 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 219 Tue 2018/10/30 10:14:43 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 219 Tue 2018/10/30 10:14:44 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 219 Tue 2018/10/30 10:14:45 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 79 Tue 2018/10/30 10:14:46 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 204 Tue 2018/10/30 10:14:46 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 79 Tue 2018/10/30 10:14:47 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 204 Tue 2018/10/30 10:14:47 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 51 Tue 2018/10/30 10:14:48 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 53 Tue 2018/10/30 10:14:48 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 55 Tue 2018/10/30 10:14:49 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 57 Tue 2018/10/30 10:14:49 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 59 Tue 2018/10/30 10:14:50 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 83 Tue 2018/10/30 10:14:50 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 63 Tue 2018/10/30 10:14:51 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 61 Tue 2018/10/30 10:14:51 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 65 Tue 2018/10/30 10:14:52 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 91 Tue 2018/10/30 10:14:57 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 69 Tue 2018/10/30 10:14:58 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 71 Tue 2018/10/30 10:14:58 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 73 Tue 2018/10/30 10:15:06 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 51 Tue 2018/10/30 10:15:06 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 53 Tue 2018/10/30 10:15:07 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 55 Tue 2018/10/30 10:15:07 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 57 Tue 2018/10/30 10:15:08 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 59 Tue 2018/10/30 10:15:08 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 83 Tue 2018/10/30 10:15:09 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 63 Tue 2018/10/30 10:15:09 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 61 Tue 2018/10/30 10:15:10 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 65 Tue 2018/10/30 10:15:10 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 91 Tue 2018/10/30 10:15:11 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 69 Tue 2018/10/30 10:15:11 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 71 Tue 2018/10/30 10:15:12 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 73 Tue 2018/10/30 10:15:18 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 51 Tue 2018/10/30 10:15:19 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 53 Tue 2018/10/30 10:15:20 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 55 Tue 2018/10/30 10:15:20 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 57 Tue 2018/10/30 10:15:21 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 59 Tue 2018/10/30 10:15:21 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 83 Tue 2018/10/30 10:15:22 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 63 Tue 2018/10/30 10:15:22 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 61 Tue 2018/10/30 10:15:23 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 65 Tue 2018/10/30 10:15:23 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 91 Tue 2018/10/30 10:15:24 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 69 Tue 2018/10/30 10:15:24 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 71 Tue 2018/10/30 10:15:25 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 73 Tue 2018/10/30 10:15:31 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 51 Tue 2018/10/30 10:15:31 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 53 Tue 2018/10/30 10:15:32 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 55 Tue 2018/10/30 10:15:32 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 57 Tue 2018/10/30 10:15:33 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 59 Tue 2018/10/30 10:15:33 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 83 Tue 2018/10/30 10:15:34 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 63 Tue 2018/10/30 10:15:35 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 61 Tue 2018/10/30 10:15:35 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 65 Tue 2018/10/30 10:15:36 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 91 Tue 2018/10/30 10:15:36 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 69 Tue 2018/10/30 10:15:37 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 71 Tue 2018/10/30 10:15:37 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 73 Tue 2018/10/30 10:18:18 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 324 Tue 2018/10/30 10:26:16 PM System -140005 Net Module Rule: 17 Tue 2018/10/30 10:50:23 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 75 Tue 2018/10/30 10:55:49 PM System -170001 [UDSockets] HTTP:28 error:6 Tue 2018/10/30 10:55:54 PM System -170001 [UDSockets] HTTP:28 error:6 Tue 2018/10/30 11:00:02 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 51 Tue 2018/10/30 11:00:02 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 53 Tue 2018/10/30 11:00:04 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 55 Tue 2018/10/30 11:00:04 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 57 Tue 2018/10/30 11:00:05 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 59 Tue 2018/10/30 11:00:05 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 83 Tue 2018/10/30 11:00:06 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 63 Tue 2018/10/30 11:00:06 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 61 Tue 2018/10/30 11:00:07 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 65 Tue 2018/10/30 11:00:07 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 91 Tue 2018/10/30 11:00:08 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 69 Tue 2018/10/30 11:00:08 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 71 Tue 2018/10/30 11:00:09 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 73 Tue 2018/10/30 11:03:43 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 77 Tue 2018/10/30 11:06:05 PM System -5011 uuid:0 Tue 2018/10/30 11:56:06 PM System -170001 [UDSockets] HTTP:23 error:6 Tue 2018/10/30 11:56:06 PM System -170001 [UDSockets] HTTP:29 error:6 Tue 2018/10/30 11:56:14 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 72 Wed 2018/10/31 12:25:03 AM System -140005 Net Module Rule: 249 Wed 2018/10/31 12:26:00 AM System -170001 [UDSockets] HTTP:29 error:6 Wed 2018/10/31 12:26:05 AM System -170001 [UDSockets] HTTP:29 error:6 Wed 2018/10/31 12:26:10 AM System -170001 [UDSockets] HTTP:29 error:6 Wed 2018/10/31 12:55:56 AM System -170001 [UDSockets] HTTP:30 error:6 Wed 2018/10/31 12:56:01 AM System -170001 [UDSockets] HTTP:30 error:6 Wed 2018/10/31 01:55:52 AM System -170001 [UDSockets] HTTP:20 error:6 Wed 2018/10/31 01:55:52 AM System -170001 [UDSockets] HTTP:28 error:6 Wed 2018/10/31 02:25:05 AM System -140005 Net Module Rule: 249 Wed 2018/10/31 03:00:22 AM System -170001 [TCP-Conn] -6/-140002, ISY Wed 2018/10/31 03:00:22 AM System -170001 [TCP-Conn] -6/-140002, ISY Wed 2018/10/31 03:00:22 AM System -170001 [TCP-Conn] -6/-140002, ISY Wed 2018/10/31 03:00:22 AM System -170001 [TCP-Conn] -6/-140002, ISY Wed 2018/10/31 03:00:22 AM System -170001 [TCP-Conn] -6/-140002, ISY Wed 2018/10/31 03:00:22 AM System -170001 [TCP-Conn] -6/-140002, ISY Wed 2018/10/31 03:00:22 AM System -170001 [TCP-Conn] -6/-140002, ISY Wed 2018/10/31 03:00:22 AM System -170001 [TCP-Conn] -6/-140002, ISY Wed 2018/10/31 03:00:22 AM System -170001 [TCP-Conn] -6/-140002, ISY Wed 2018/10/31 03:00:22 AM System -170001 [TCP-Conn] -6/-140002, ISY Wed 2018/10/31 03:30:03 AM System -140005 Net Module Rule: 17 Wed 2018/10/31 03:30:05 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 22 Wed 2018/10/31 03:30:20 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 379

So, after I posted that I thought I'd give it one more shot. I rebooted via telnet and it came up this time, fairly quickly, still not getting a text 1 minute after boot but within maybe 5 minutes again and now all the programs are enabled again. The AC does seem to be working better than it did before when all programs when enabled. I tried to restore my backup and it is not taking. Staying at 0 percent.

Ok, I thought that was going to fix it because I found that I had a start up program that queries all 5 minutes after boot up and it also texts me 1 minute after boot. I removed the query and rebooted. It took longer than 10 seconds, maybe 5 minutes before I got the text that it had rebooted. I looked and yes the query after restart was also checked. I unchecked that and rebooted again. This time it never came back. I waited an hour. Still could not load AC. Got LIB_ERRORS-403 pop up and then "Cannot retrieve nodes from the ISY, Would you like to close the AC? " I can telnet so I did a reboot from there, same results and I don't get the text that it has rebooted either. I am not at home right now so I can't unplug it. I assume if I do unplug it, it might enable all programs again so I'll probably just format the SD card when I get home. If that does not work I have two new 16 GB cards coming. I don't think I have ever taken the original card out of it at all.

Thanks, I'll give that a try. Can I copy 1 to 1 or do I need to reload the latest firmware and restore a backup?

How long should it take the ISY to reboot? I thought in the past it only took a couple of minutes. I had an issue this past weekend where the AVRemote nodeserver was taking over 10 seconds to process commands to my Denon so I rebooted the ISY. 10-15 minutes later I still could not login. I pulled the power on the ISY and it still took forever to boot up and be able to login and once I could login I found that all the programs that were supposed to be disabled were enabled causing all sorts of issues. Lights going on and off, programs going on and off, etc... I could barely use the AC with all those programs running. I finally had to unplug the ISY and go to bed. I tried yesterday to upload the latest backup but it would not take (I assume because it was bogged down with all the programs running). I factory reset the ISY and loaded the latest backup and it is still taking 20 minutes to reboot the ISY but at least all the disabled programs were correctly disabled this time. I am on 5.0.13D. Possible SD card going bad? Thanks. Also, I had to set up my gmail again, shouldn't that be part of the backup?

And for no apparent reason Google Home is now much faster than it was with home control connected.

Mine is very fast without without home control connected and over 10 seconds as soon as I link it. I get a lot of something went wrong try again later responses as well. It's not just slow with home control responses it is slow with all responses.

If I add the UD home control to Google Home the responses take over 10 seconds. Not just home control responses either. Any thing I ask it takes much longer. If I unlink then the responses are just as fast as the Echo. Anyone else seeing this? I have not assigned rooms to any of the devices yet if that matters. I have 140 devices aren't in rooms yet is what it tells me. Thanks!

I see what you mean. Anyway, a password in the command is better than no password so if the original poster wants to implement it, it is up to him/her. I will have to think more about the consequences before I decide to remove the control or not.