btreinders

@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.

Well, gun manufactures do provide a safety. Just saying, maybe the ISY should not have the ability to disarm the ELK since the ISY is not a certified alarm system.

I can turn on my Denon using the Echo and the ISY. You should be able to do that with the Onkyo too as long as it has IP control using a network resource. You should also be able to select a source. Of course that would be two voice commands to the DOT. One to turn on the receiver and one to play the song.

You can try, but without the password I am not sure how you'd do it. So, do we need to petition ELK and UDI to remove the ability to do this? I know that just because you can maybe you should not but why do they even allow it then?

I do use a disarm command from the Echo. You have to say Alexa, turn on disarm the house password ........... I am sure this isn't the most secure way of doing it since you do have to have your password stored on the Amazon Alexa smarthome settings page but I would think if your password for that site was strong you'd be ok. I also have a program that can set off the Elk by saying Alexa, turn on panic. It arms the system in stay instant and then simulates a door being opened. I guess I could add that program to an else and when someone gets the password wrong it would trigger.

Yes, I have tried discovery multiple times after a forget all but it does not help. I deleted some programs I did not use to stay below 302 with all devices and scenes added that I do use. I will stay under 302 for now unless someone finds a work around or Amazon fixes the issue.

Disabled all skills except ISY and still having issues. Seems like a hard limit at 302 items (programs, scenes and devices added together). It will discover beyond 302 if I do not forget all but once I forget all I can never get above 302 until I delete enough to get below 302 and then add again with forgetting all. How items do other people have?

Just Ecobee is shown on the smart home page with the ISY. I thought I had a few more but they are not showing. How do you see all of the enabled ones? Yes it does see some devices but not others.

ISY optimized for smart home V2

Here is one that is not discovered. And thanks!

I cannot figure out how to do that. Neither IE or Chrome let me paste images into a reply.

I cannot get Alexa to discover certain devices anymore. Programs are discovered. I even deleted them and re-created some in the portal but Alexa refuses to discover them. Any ideas? I disabled the skill and re-enabled it and rediscovered all but still nothing. Some devices that are discovered say undefined on the smart home page and others say their name.

I have no issue with Michel putting this on the wiki.

Here are the ISY programs: Heartbeat Check Var Control Server - [iD 028D][Parent 028C] If $HEARTBEAT_SERVER is 9 Then $HEARTBEAT_SERVER = 0 Else - No Actions - (To add one, press 'Action') Heartbeat Var Control Server Not Running - [iD 028E][Parent 028C] If Time is Last Run Time for 'Heartbeat Check Var Control Server' + 6 minutes And From 4:15:00AM To 3:55:00AM (next day) Then $HEARTBEAT_SERVER += 1 Else - No Actions - (To add one, press 'Action') Server Missed Two Heartbeats - [iD 028F][Parent 028C] If $HEARTBEAT_SERVER is 2 Then Send Notification to 'Brent' content 'Heartbeat Missed Server' Else - No Actions - (To add one, press 'Action') VBS Script: Set WshShell = WScript.CreateObject("WScript.Shell") 'Set http = CreateObject("MSXML2.serverXMLHTTP") 'Set http = CreateObject("MSXML2.XMLHTTP") Set http = CreateObject("Microsoft.XmlHttp") URL ="http://ISYIP:ISYPort/rest/vars/set/2/72/9" ' If auth is required, replace the userName and password values ' with the ones you use on your ISY userName = "ISY Username" password = "ISY Password" http.open "GET", url, false, userName, password http.send Set userName = Nothing Set password = Nothing Set myFSO = Nothing set WshShell = nothing set http = nothing set objXmlDoc = Nothing Eventghost just runs that script every 5 mins.