baabm

Background: I just updated from a 994 running v4.9 to EISY running v5.3.4. On the 994, I used mobilnc as my iPhone interface program and it in turn interfaced with Alexa. The way this worked (I think) was, you entered your spoken into the 994, then mobilinc scanned the spokens and made then available to Alexa when you DISCOVERED devices on Alexa, it found all the devices, scenes, programs, etc. This was very easy to use. Since EISY doesn't support Mobilinc, I found the following on the wiki: Make sure you have followed all the steps in ISY Portal Installed and Configured first. Log into ISY Portal Click on My Profile at the top right corner, choose your ISY from Preferred ISY drop down Under Select Tool, choose Connectivity | Amazon Echo Click on Add Device, Scene, Program, Variable or A/V to add a new Alexa device Choose your ISY device/scene/program/state variable Enter a Spoken (This is the name Alexa will use to recognize this device), then save. NOTE : Rooms are optional and useful only for categorization in ISY Portal So in a system with about 100 programs, and about 100 devices and about 40 scenes, and 50 variables, I'd have to (worst case) define almost 300 items individually. Tell me that I am misunderstanding how this works. Or is there a better way to do this. Thanks, Bob

@HABit - thanks for your response. I guess I didn't hit "follow" on this question since I am just now seeing your response. Anyway, I went into the router DHCP and found the timeout set to 3600 (which seems weird since the ISY was re-leasing every 30 minutes, not 60 like the router seems to be set to.) Anyway, I set it to 36000, which should give me 10 hours before the leases expire. Hopefully that helps. Regarding your 2nd suggestion, are you saying that I should assign static addresses to all my devices? Or is this something else. I have tried going into the router page "Client list", but the routers busy icon just keeps spinning and I never seem to get there. Not sure what to do when I do get there though. Thanks again, Bob

I tried to do a backup today before trying to upgrade to 4.8.0 and received the error in the title. How should I proceed? Thanks, Bob M

I noticed my system gets "non-responsive" at times (ie, I hit a button to turn on a light and nothing happens for a long while (several minutes), then the light goes on. I copied the following excerpt from last nights error log - can someone tell me 1) is this a problem? 2) If so, what causes it? and 3) How can I fix it? Thanks, Bob Wed 2020/07/15 05:09:46 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 05:39:50 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 06:09:56 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 06:40:01 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 07:10:06 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 07:30:04 PM System -50001 -7 Wed 2020/07/15 07:40:12 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 08:10:18 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 08:40:23 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 09:10:28 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 09:40:27 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 10:10:33 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 10:40:38 PM System -100 [DHCP] state=RENEW Wed 2020/07/15 11:10:42 PM System -100 [DHCP] state=RENEW Wed

I turned off the firewall (unchecked the box) as seen in the screen shot below.

Thank you for the suggestions. Although I have never turned on the firewall on my router, it did appear to be on, so I turned it off (I could not figure out how to put the ISY in a white list though). I don't feel great about leaving the router with no firewall enabled though. I have no parental controls or MAC address filtering and although I have some port forwarding, it is all for a few cameras I have, nothing there is associated with the ISY. I rebooted the router and then tried to access the ISY from Mobilinc - no joy. Then I opened the admin console and looked at the error log.... Tue 2020/06/23 12:49:38 PM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 12:49:43 PM System -100 [DHCP] state=RENEW Tue 2020/06/23 12:49:43 PM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 12:49:48 PM System -100 [DHCP] state=RENEW Tue 2020/06/23 12:49:48 PM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 12:49:53 PM System -100 [DHCP] state=RENEW SO I rebooted the ISY, opened the error log and here is what it shows: Tue 2020/06/23 12:51:08 PM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 12:51:13 PM System -100 [DHCP] state=RENEW Tue 2020/06/23 12:51:13 PM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 12:51:31 PM System -5 Start Tue 2020/06/23 12:51:34 PM System -110022 /CONF/INSTENG.OPT Tue 2020/06/23 12:51:34 PM System -110012 /CONF/INSTENG.OPT And now it appears to be working. thanks, Bob Regards, Bob

I am having trouble with my ISY. It seems to get hung up such that I cannot access it from Mobilinc Orchestrated. I am running v4.7.5. I AM able to log in via the admin console and when looking at the error log, I see the following every 5 seconds which I looked up on the wiki (WEB MODULE NO FREE SPACE), but I still don't know what it means nor how to fix it. Can someone help? I am also not sure how to write a ticket...I cannot seem to be able to use single sign-on. Thanks, Bob Tue 2020/06/23 08:09:42 AM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 08:09:47 AM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 08:09:52 AM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 08:09:57 AM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 08:10:02 AM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 08:10:07 AM System -170001 [UDSockets] Portal:41 error:6 Tue 2020/06/23 08:10:12 AM System -170001 [UDSockets] Portal:41 error:6

Just to close this out...I found where to enter a support ticket, and within a very short time, Michel responded telling me to do a factory reset on the ISY. I did this, and then was able to access the ISY from the launcher. I was able to log in using the default username/password and then was able to reload my good backup. So all is good again. Thanks, Bob M

Thank you Paul, but I am still unable to get very far with this. I found telnet on the PC and tried to "open" what I remember might be the IP address of the ISY. But I got an error saying "device not responding". So I don't know if 1) The ISY won't respond because it is hung up in a tight loop or 2) I used the wrong IP address. (The only network utility I have is on my iPhone and Apple does not allow access to MAC addresses, so the analyzer can't tell what type of device is at each IP address....so basically, I was just trying to remember what the IP address was. I also tried looking on the ISY itself to see if the MAC address was printed, but it isn't. At this point, I want to write a ticket for support but am not even sure how to do that.

I think I really screwed the pooch this time....I have been having trouble with my ISY getting hungup at certain time of the day. I couldn't figure out what was happening, so today, I used the admin console in the programs listing and searched for each and every variable one at a time, to ensure that they were being set, reset, and initialized correctly. I made a backup before making any changes, but then changed quite a few things. I left the house and noticed immediately that the program to "set away mode" didn't run when I invoked it through Alexa, nor did it run when my mobilinc geofence was crossed. I tried looking at things in mobilinc while out of the house and it wouldn't connect. When i got home, mobilinc still didn't connect, so I rebooted the ISY. It appeared to run correctly, but mobilinc still wouldn't connect. So I tried to bring up admin console on my mac. The launcher didn't find my ISY (this problem has happened frequently over the past weeks) so I went to my PC (which is the computer I used to make the changes this afternoon.) The launcher on the PC also did not find my ISY. I rebooted again, no help. I cleared the java cache on both the mac and the pc, reloaded the launcher on both and still neither of them find the ISY. I found on the WIKI that I was supposed to use terminal to do something, but I couldn't find terminal on the PC and on the MAC, the instructions weren't clear enough for me to follow them. So now I cannot access the ISY - so I can't even figure out how to reload the backup. Any help would be appreciated. Thanks, Bob

Thanks DBUSS, That worked for the Windows system, now I'll have to research how to turn it on in my MAC but at least the problem is now fixed. Thanks again. Bob M.

I just ran into this problem again for device 88834E.REC in my system. I am running 4.7.0. I tried to perform the fix described above....On my MAC, I opened a terminal window, but then it wouldn't accept a telnet command - says "telnet command not found". So then I tried to do this via a PC running windows 10 in a command prompt window, and it basically said the same thing. So can anyone help me with why does telnet not work on either of my systems. Thanks, Bob M.

Apparently Glacier911 is one of the beta testers according to this writeup.... https://lifehacker.com/how-to-enable-amazons-new-brief-mode-for-alexa-1823880787

My client version number is the same as glacier991, but I do not see a “voice responses” choice nor a “brief mode”. Could it be that I am using all Apple devices (IOS) and perhaps glacier991 is on android?

My Alexa devices are on version 601481020 and I am not seeing this behavior. In settings, I see “Sounds/Request sounds/start of request and end of request”. When I enable “end of request” sounds, and I tell Alexa to do something, she responds with a short tone, but also says OK after the tone. I am not seeing a selection to turn the OK response on or off. Perhaps you can post the version # of your alexa device. Thanks

Thanks Stu, I didn't realize that the print was so small, I enlarged it. Thanks Oberkc, The messages you see at 5:01 are after I did the reboot, so at that point everything was working again. The suggestion to log in via the IP address is a good one and I'll see if I can do that.

Can someone help me decipher the Log File and Error log to help identify the following problem. MY ISY occasionally (almost every day) hangs up and stops responding to KPL button pushes, ALEXA commands, and mobilinc control. Background: I have an ISY994 running the latest released firmware. I have variables called home (both Integer and State), that are normally set by one of 3 methods 1) if I enter or leave a mobilinc geofence, 2) if I hit one of 3 KPL switches in different parts of the house that are in a scene called HOME. 3) If I issue a voice command to ALEXA to set HOME. All 3 of these conditions run a program when the S.Home variable changes and it does a bunch of stuff. (There is also a corresponding AWAY program.) Most of the time this works very well, using all 3 of the techniques. But sometimes mostly in the afternoon, the system seems to hang up. It happens in both leaving and arriving mode: When it's NOT working - if I am home, and I tell Alexa I am leaving I can see that the HOME button on the KPL backlight doesn’t go out as it should, the functions that are supposed to occur also do not occur. If I then hit the KPL, the light goes out, but still nothing happens. The reverse also occurs, If I am away and I come home, sometimes the Geofence doesn’t set the HOME switch, telling Alexa I am home doesn’t set the HOME switch and then hitting the HOME switch turns on its backlight, but nothing happens that should happen. In all these hangup cases, I cannot access the ISY via mobilinc - it is just hung up trying to connect. If I try to start the Admin console, it just hangs up and never gets through the ISY finder, and lastly, when looking at the ISY, the only light it is the power light (no apparent error being detected by the ISY itself). Also in all cases, I must pull the power on the ISY and restart it. After that, everything seems to work OK until the next time. Thinking that the ISY was getting into some weird state, I bought a timer and had it cycle power on the ISY once a week in the middle of the night. When that didn’t help, I set it cycle the power EVERY night at 2:45am, and that didn’t help either. I have looked at the log and the error log and 1) can’t see anything in the LOG file that throws any light on the problem and 2) can’t decipher the ERROR log at all. Today the system was working well at about 1:40pm when I left the house, but sometime between then and about 4:40pm when I arrived home, the system hung up. At 5:01 I finally restarted the system and it worked after that. I am enclosing part of the error log for today, and ALL of the regular LOG for today. I have annotated where I came and went throughout the day in the log file (last column). I apologize for the size of the log file (over 500 lines long, but I didn’t know what was important and what wasn’t. To help search through it, I have put an XX: in the comment field wherever I annotated something. I am not sure how to approach troubleshooting this so any help would be appreciated. Thanks, bob M Error Log: Fri 2017/12/15 02:17:12 PM System -100 [DHCP] state=RENEW Fri 2017/12/15 02:47:14 PM System -100 [DHCP] state=RENEW Fri 2017/12/15 03:17:20 PM System -100 [DHCP] state=RENEW Fri 2017/12/15 03:47:25 PM System -100 [DHCP] state=RENEW Fri 2017/12/15 04:17:30 PM System -100 [DHCP] state=RENEW Fri 2017/12/15 04:51:05 PM System -100 [DHCP] state=RENEW Fri 2017/12/15 04:51:12 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 55 Fri 2017/12/15 04:51:21 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 55 Fri 2017/12/15 04:51:22 PM System -170001 [uDSockets] SMTP:30 error:6 Fri 2017/12/15 04:51:32 PM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 137 Fri 2017/12/15 04:51:32 PM System -170001 [uDSockets] SMTP:30 error:6 Fri 2017/12/15 04:51:38 PM System -170001 [uDSockets] SMTP:30 error:6 Fri 2017/12/15 04:51:48 PM System -170001 [uDSockets] SMTP:30 error:6 Fri 2017/12/15 05:00:41 PM System -5 Start Fri 2017/12/15 05:00:43 PM System -110022 /CONF/INSTENG.OPT Fri 2017/12/15 05:00:43 PM System -110012 /CONF/INSTENG.OPT The LOG FILE is an attachment. ISY log file 20171215.pdf

Well I am glad that I may have uncovered a problem, but I assure you, it was totally by accident. I find that as I get older, I am forgetting more and more things, so: 1) when V3 for the ISY portal was announced, with those new features, I forgot that I was using the mobilinc portal, so those changes didn’t really apply to me and 2) When I wasn’t sure why some (not all) of my scenes were being imported into Alexa, I forgot that in mobilinc, the only scenes that get imported into Alexa are the ones to which I have given a spoken. I have since had an email exchange with Wes at Mobilinc and they are still evaluating the potential impacts to Mobilinc of V3 and will start working on interfacing to it in January. I’ll sit tight awaiting an announcement from Mobilinc saying they are V3 compatible. Regards, Bob

thanks All, I knew which 8 programs I changed, so I disabled them, changed them back to the way they were and rebooted. All is well now. Even though the logic is not perfect for what I want it to do, its close enough. thanks

yes. Thanks. Now I just have to figure out how to make the changes I want. Thanks, Bob

Help please. I made some changes tonight in the aim console to a few programs, and when I hit save, I noticed that those programs icons were turning green and red in rapid succession. I tried to change the programs back and do a save, but this didn't seem to work. I then logged out of the admin console and now am unable to log in. it gets to the ISY finder page but never finds the ISY. Any help would be appreciated. Bob

Thanks Apnar, What you say seems to make sense and explains why we'd need V3 over V2. But in my frenzy to try to get this working, I forgot that I am not using the ISY portal, I am using the mobilinc portal - just another complicating factor. I sent a question off to Mobilinc to see why my ISY devices don't show up as devices in Alexa. Thanks again, Bob

Nathan, Thanks for the response. 1) I am not using V3 yet. I saw a recent post of someone saying they went thru the steps (forgetting devices, deleting V2, installing V3, discovering) and it diidn’t work for them. I will track that down before I switch over. But again, this feature is an ALEXA feature, it should have nothing to do with the version of ISY interface. And that leads to your next item. I couldn’t figure out what the 2 different symbols in the Alexa app meant. (And I’m still a little fuzzy.) looking at the Alexa app devices page, the only things that come up looking like light bulbs are my LIFX bulbs and strips. All the other devices on that page (that look like little houses) appear to be ISY scenes (although I am not 100% sure of that.) In the ISY I obviously have many devices (insteon switches and dimmers that control bulbs). And for the most I have created a scene for every single switch and some scenes that control multiple switche because somewhere on this forum, someone said its better to control things through scenes. Alexa seems to have pulled in some scenes, but not all. Everything on the Alexa app scenes page appears to be a LIFX scene or a LUTRON scene - I don’t see any ISY scenes there. And everything on the alexa app groups page are just groups I’ve created in the Alexa app. So I don’t doubt your statement, “then something isn’t set up right.” I just don’t know what is wrong or how to fix it. Thanks again.

Thanks Stu, I was trying to avoid setting up multiple accounts to accomplish this. Amazon’s documentation of the feature does not mention multiple accounts, so I assume they also expect it to work without going through that effort. BTW: Besides all the extra work of creating email addresses, creating multi[ple Amazon accounts, moving devices out of the main account and into the sub accounts, are there any other downsides to doing that? And conversely, are there any other upsides to doing it (in addition to having each rooms alexa device having that simplified interface. Thanks again.