starmanj

I just setup geofencing using node server->occupancy 1.0. Configured node server successfully, and Locative iOS app successfully changes occupancy status in ISY when I use "send test-request" under Settings part of Locative. However, the Locative geofence simply won't change the ISY occupancy status when I set fence to minimum (less than a block from my house), and I walk more than a block away... Is the Locative server still functioning? Or is the fence boundary much larger than the Locative map shows? AND...portal teases an Iphone app for UDI mobile, what is the status of this? Starmanj

FIXED. FYI see my resolution post above. It's not the Portal, it's needing to "forget" and discover devices more frequently than I have been, to avoid Portal confusion.

Any chance we can see these capabilities enabled in the Portal? https://developer.amazon.com/blogs/alexa/post/bda9d70c-2f0d-454d-9939-2eb82868cf35/announcing-contact-and-motion-sensor-apis-and-integration-into-alexa-routines-adding-new-home-automation-features-for-customers-and-new-opportunities-for-smart-home-developers

I've been having major issues getting Portal to be reliable; Alexa and Google Home report the ISY Portal is down, far more than is being reported here. Benoit helped but we were both stumped. Solution: I have NOT been routinely "forgetting" all devices as I make Portal changes. Apparently enough bad cache/data was accumulated where the Portal was getting confused what to do. I do have multiple ISYs as well. Once I "forgot" all devices and rediscovered on both ISYs everything works perfectly now. My Alexa and Google commands for devices and programs are completely reliable again (was failing about 70% of the time before). This is an FYI in case somebody has this problem and searches for a solution. Starmanj

Must be isolated to me for some reason. I'll open a ticket next time Benoit. It's random, and Google home always confirms it can't connect to UDI server...

It seems in the last few weeks, the portal is down as much as it's up...I have Alexa's side by side with Google Homes in about 16 different rooms across two homes. Alexa will simply say it can't find a group or device names whatever I said. Only the google Home will actually say the ISY portal is down. And it happens a LOT. Are there reliability issues ongoing with the Portal that we are not aware of???

Very much appreciated, thank you Benoit.

An echo is linked to one specific Amazon account. During account linking, you link to a specific Amazon account to the Portal, right? So your workaround is to assign an Echo to a specific Amazon account which is then linked to a Portal sub-account, right? I'm just trying to understand what you are suggesting as a workaround to using two ISYs without having to keep specifying my "preferred ISY" every time I use a different ISY. So, I'd love to know if anybody finds the Portal useful for more than one ISY. If you don't support the feature "support an echo to be aware of devices on 2 different ISYs and just send the right command to the right ISY" then I for one am wasting my money using the Portal, because it's simply a pain to keep switching "preferred ISY" to make it work. I think this is quite fundamental, and am puzzled why the Portal even bothers with multiple ISYs at all.

Does any of your echo need to be aware of devices on 2 different ISYs? -- Still confused. I have 4 echos in one home, 10 in another. One amazon account for all of them. I want to turn on lights using 4 echos in one ISY in one home. Turn on lights using 10 echos in the other ISY in the other home. So all my echos need to be aware of all my devices depending on which home I am standing in..."Alexa turn on Florida Kitchen Lights" vs "Alexa turn on Colorado Kitchen Lights". See? I can't assign my 4 echos to only one ISY, unless I am missing something...do you mean create two amazon accounts, one for each home? I don't want several Amazon accounts to satisfy Portal issues... And why can't the portal support an echo to be aware of devices on 2 different ISYs and just send the right command to the right ISY? If yes, that's not supported. If no, you can link your echos to a different ISY Portal user profile. You could have a user profile for ISY A, and a user profile for ISY B. You could, if you wish, have 15 different sub-accounts with each their ISY Portal user profile and their own set of spokens. --How do I link an individual echo to a specific ISY portal profile? I only have one amazon account. I know about sub-accounts but as I understand it, they each have to have their own amazon account? Which is not how normal users would ever want it in my opinion... The restriction is that an echo can only see one ISY. --Why is this restriction there? And what is "an echo"? Do you mean "an amazon account which is assigned to specific echos"? Benoit

Trying to understand this-- you mean a spoken command to an Alexa sends the command to the Portal API, right? And the Portal then sends the command to an ISY? Then why can't the Portal send that command to both ISYs? Or does Alexa send the command directly to an individual ISY? Not sure what you mean by a single Echo to two ISYs...I have 15 Echos between two different homes. I have a single Amazon Echo account. Pretty normal except for lots of echos.

I used to be able to use commands across two ISYs without having to manually switch ISYs in the portal. It no longer works...on V2 nor V3. Is there a way to do this? I have all unique voice commands between the two ISYs, why do I have to switch ISYs in the portal? Takes away the utility of having the portal to me. spearse

And...SOLVED! Thank you Paul Bates. Indeed, for some reason Java had disabled "keep temporary internet files"! I checked it, re-rean admin.jnlp, and voila, the administrative console shortcut appeared on my desktop! Thanks everyone, mission accomplished!

I have the admin.jnlp. Maybe I've got this all wrong...when you click on admin.jnlp, is the java app supposed to then download another java app from the ISY? Because it takes about 5 seconds every single time to download that applet. Why does it have to download the applet every time? Am I supposed to click on admin.jnlp to bring up the admin console, or is there supposed to be available the java app that admin.jnlp has ALREADY downloaded previously? I would attach a screenshot but I can't figure out how to upload an image on this BBS. I've done it before but this "my media" thing only lets you post images uploaded previously by some inscrutable mechanism...or from an URL...or something...

Hi Michel- No-- the subject is where is the applet? I have the admin.jnlp, but that is downloaded every single time; per the wiki: "ISY994i Series: Click on admin console link... this should put an icon on your desktop once you click on the downloaded admin.jnlp file" This does not happen. I don't see an icon for the admin console anywhere on my computer; I looked on the desktop, username folder, both major temp files...it's the case of the missing admin console applet.

? You have an ISY folder in the start section? Not sure what you mean? When I click on windows start button there are no ISY entries.

I have tried many many times...clicking on admin.jnlp starts a download from I assume my ISY994i, and the "finder" automatically opens up. I have no idea where the downloaded console app is going. It is not going to my desktop as the guide says.

To get to the admin console, I click on "admin.jnlp". It starts downloading the applet from my ISY which is slow...Where is the applet downloaded? Shouldn't I be able to click on the applet it downloads instead of the admin.jnlp? Can't find it anywhere... starmanj

Fixed it...I had a bad Comcast DNS assigned in the ISY config. Online now!

I was able to check TLS settings but that is not the problem. No idea why my ISY will not go online with the portal. Here are last parts of my error log: Thu 2016/10/27 10:24:30 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:25:09 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:25:39 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:26:09 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:26:39 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:27:10 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:27:40 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:28:15 AM System -140000 my.isy.io Thu 2016/10/27 10:28:54 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:29:33 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:30:03 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:30:38 AM System -140000 my.isy.io Thu 2016/10/27 10:31:09 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:31:40 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:32:10 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:32:44 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:33:19 AM System -140000 my.isy.io Thu 2016/10/27 10:33:53 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:34:26 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch Thu 2016/10/27 10:35:01 AM System -140000 my.isy.io Thu 2016/10/27 10:35:31 AM System -170001 [TCP-Conn] -3/-140002, Portal-Dispatch I can login to my.isy.io fine from my web browser; can't tell if the ISY can't login? Starmanj

I'm confused...where on the dashboard can you change TLS settings? And does it matter that one of my ISY's are offline, if the second is online? That is, can Alexa still communicate with both ISYs? Anyway I wish there were some debugging steps to why I have an offline ISY...

I had to downgrade from 5.0.6 back to 5.0.2 so might have lost some Portal settings? I note there are network setting requirements for TLS etc. but nowhere does it explain where those settings are (Wiki, etc just say make sure it's set but now HOW). How exactly do you modify network settings? It's not under configuration-->system that I can see. Reboot does nothing to change offline status.

One of my ISYs is online to the portal, the other is offline. Why? ISY Portal tab says registered and offline. Refreshing does nothing? How do I get the offline portal to go online? Starmanj

So I tried following WIKI instructions...didn't work. did you mean to put in "Peter" in the body to post? Anyway my hue hub responds with [ { "error": { "type": 1, "address": "/", "description": "unauthorized user" } } ]

Fixed! Michel explained you must be on 5.0.4 or revert back to 4.5.2 to get networking module back. Done.

I hope I don't have to purchase the networking module a SECOND time?? I am on firmware 5.02 both system and UI agree. My admin.jnlp is current, java cache cleared.