mvgossman

Since I can't use the Admin Console, I can't go into the reset options to determine what I did, but basically it was a last ditch effort to get things to work again via deleting all of the ISY994's data prior to restoring from my last backup. Yes, cleared cache all three boxes and downloaded a fresh copy of start.jnlp. Current version of Java on the Mac. When opened, I have to go into the Mac Privacy and Security settings to allow it to be opened, and still nothing. I've done this a few times, and always worked before, the console appears instantly in both LAN and Cloud options. And like I said, the very strange additional thing is that the login using the Cloud access method doesn't work, as if the password is incorrect, but it just isn't. Is there a way to do a factory reset on the ISY994 and start over? But, I'm willing to get an Eisy anyway, I understand it has some speed, usability, features, memory, and more that make it time to upgrade anyway, do you agree with that?

I had a power surge/failure destroy my serial modem so I replaced it. I know my ISY994i is alive and kicking since I can access it via the ISY Portal's ISY Web Access, operate lights and so on. I have long used the Admin Console on my Mac, but when I use it now (see photo) it doesn't pull the LAN based access to it automatically. I added the Admin Console URL manually on the IoX Launcher, audit shows up as Cloud access, but when the "Authenticate My Lighting" dialog box comes up, my login credentials don't work. I tried the default admin-admin and no go. Certainly didn't change the password, but at any rate I know it's operating inside that black box because it works through the Web Access. I updated Java, cleared all the cache boxes, restarted everything (cable modem, router, serial modem, and the ISY994), and it won't budge. During all this troubleshooting of the failure after the thunderstorm, I misguidedly reset the ISY994's data and thought I might have to restore from a backup, perhaps that is related. This might be an opportunity and excuse to finally start from scratch with an eisy (WITH SUPPORT!), including redoing my entire network of lighting products, but anyway, any thoughts on what's going on?

Thank you, "Geddy", I've been fat dumb and happy for a long time with the system I have. I wasn't aware of the new PLMs, that was a crisis for the unlucky people whose systems were hanging by that crucial device as I recall. I guess I'll go whole hog with the eisy and get a USB PLM. I've got too much invested in Insteon switches to bail on it, nothing I've found has the functionality I want. I'm finding Insteon switches and other things to be pretty easy still on eBay, thankfully.

Thank you, I'm afraid Nodeserver is greek to me, will look into that. Mobillinc does seem rather dated. What is the app on the iPhone called that allows access to the full range of features?

My ISY994 works perfectly, no complaints. The only reason to upgrade to the eisy for me would be for irresistible features, and I suppose better stability and room for growth in the future. Naturally, I'm worried about encountering a major problem and wishing I hadn't undergone the major surgery. SO! 1. Is the interface for programming scenes, devices, etc. still done through the iOx Launcher Admin panel via Java? A nice new feature would be a more robust Admin panel. 2. Is the MobilLinc Pro app still usable? 3. And while I'm at it, is there a way to interface to a different PLM? I've been fortunate, my two PLMSs (two homes) are going strong, but my luck could run out. 4. Any other great features to be gained?

I agree... I was joking about the cost because it's so reasonable.

Thanks! I didn't find anything specific in a search with respect to the VTEXT for Verizon being down, but now that I know it's truly down, and possibly no workaround, I just installed Pushover, and it is great. I suspect I'll find this useful in other situations. I just realized that you can set the Mail app to put up on alert notification whenever an email is received by a certain email address. One could have a special email address only used by the ISY. I'll have to think about this before I put forth that massive cost of $4.99 for lifetime Pushover use. Still, Pushover also integrates with multiple devices very nicely, although I can't get the notification to work yet on the Mac, I've got a support question to Pushover in for that.

I use Gmail to send text messages from the ISY994 to my Verizon cell phone. Not long go, it stopped working, and found out about the Advanced Security issue at Google that required you to set up a unique password to allow an external app (like the ISY's email capability) to use Gmail as the email client, and it started working again. Within the past week, I stopped receiving texts again. I researched it, and supposedly Verizon has stopped passing through to Verizon's "2125551212@vtext.com" email to text feature. It also doesn't work with an email client on a regular computer to send a text to the vtext email address when using Gmail, but when using an alternative email address service (in my case, my office's domain name that uses Microsoft, I receive a text just fine. Is there a workaround to salvage the Gmail method? If not, what's the SMTP configuration for an alternative email address? I only have one other email, a Yahoo address, and I've tried everything and it won't work.

I've had some glitches with my T1800 Venstar thermostat which I use via the ISY994 and Mobilinc. It's not pleasant when I'm heading to the cabin 6 hours away and it's 50 degrees in there. So I'm considering replacing it with something else, anyone had a positive experience with one? There are a couple Honeywell ones. There's the Nest which I figured I wouldn't want in the cabin setting since I'm there irregularly and have no need for it to learn my temperature habits, but it does have a manual mode I just learned. There are many others. Mitch

I figured out the problem after searching for others who have had this issue and drilling down to the specific issue of the motion variable appearing as a light. I have the Alexa ISY Skill V2. I just updated to V3 and it works perfectly Thank you very much for the help, now I have to figure out what else I've been missing out on. Here's the thread that clued me in, even though going to V3 didn't seem to help this chap.

Tmorse305: That's a good clue that the description differs radically from yours. I flushed everything on the ISY itself, the ISY Portal, and Alexa app and started from scratch. Pic 1 is the entry on the Variables page for my ISY Console UI. It appears on the ISY Portal as Pic 2. It appears on the Alexa app as Pic 3. Note that the description is nothing like yours, it's the same name on all three, yet yours says ISY State Variable Address. I sense that I'm missing a step. I read something about "exposing" the variable, is there this step or some other step I'm missing? I don't know if it matters, but I am running UI and Firmware 4.7.3. I see there's a 4.7.5, but doesn't appear widely adopted yet. One thing I have not done is cycle the ISY. Mitch

I may have found an important clue to what's going wrong, last paragraph But first, I definitely did remember to do "discover devices" before and it showed up in the devices list on Alexa app as it should. Most definitely it was a variable defined as a Motion sensor, and as a "state variable" on the ISY Console. To start from scratch, I deleted the device from ISY Portal, and did a "discover devices" fully expecting nothing to happen since it doesn't tell you that it notes that devices have been deleted, and checked Alexa app to verify that the device was gone, and it was. I re-added it it, see pic 1. I went to the online Alexa.amazon.com and the Alexa app and verified that it re-appeared as a motion sensor variable, and it did, see pic 2 and 3. But when going to create a routine, and selecting "when this happens", then "Smart Home" where the doggone thing should appear, it just doesn't, see pic 4. I even removed it from the ISY and re-installed it, and nothing appears in the Smart Home Alexa list on the app when making a routine. See pic 5 and pic 6 though for a clue that something's wrong. This is what you get when on the Alexa app you go to "All Devices" (pic 5) and select the motion sensor, and when you touch the GEAR ICON upper right you get pic 6. I see that the descriptions says "Motion (variable)" no doubt because that's what I named it on the ISY Console, but the "Type" is "Other"on the Alexa app. Should that say "Motion Sensor" as type since that's what's selected on the ISY page (Pic 1)?? If so, why doesn't it?

I did confirm that it is designated as a Motion Sensor on the ISY Portal. Can you show a shot of you "When this happens", which button you select (I assume it would appear under "Smart Home", and what it looks like there? See screenshot on computer of the ISY Portal definition and its definition on the ISY console.

Incidentally, the whole range of my Insteon Devices is there which is handy. I don't know why my August lock is there magically, but I like it. I just programmed a routine to turn on a local radio station when the door is unlocked.

I'm stuck again. I finally got the Variable to appear as a motion sensor device (#1). Clicking this produces this screen (#2). I proceed to the Routine definition (#3).Add new (#4). On the "when this happens" page (#5) I don't see anything about a motion sensor or variable or anything else under any of those categories. What am I doing wrong? If I click Smart Home, I get seen #6, nothing there either.