MWareman

Update, just saw this: http://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Portal.2FAmazon_Echo.2FIFTTT The wording of the 'Please Note' for prior purchases of the module seems to imply that you don't get the actual Network Module with a Portal subscription. You do, however, get the functionality of the network module for the duration of your portal subscription. That's why you have the tabs of the network module, but you won't see the module in your 'Installed Modules' list. And if your portal subscription expires, the functionality will disable as well.

That Networking tab is the network module. It wouldn't be there otherwise. Click 'Add' to define your first network resource. Also, take a look at the Wiki. Tons of examples to pour thru. Also, the web server tab wouldn't exist without the networking module being enabled.

I think the confusion also comes in because when you add multiple Switchlincs into a scene - with all being a controller and one of them connected to a load, you can dim and brighten the scene from any of the controller switches. To then say scenes cannot be dimmed thru the protocol simply dosnt equate with the ability to dim a scene from any member switch. A way needs to be found to implement scene dimming thru the rest interface and, by extension, Alexa. If a scene has 3 devices in it (A,B and C) with the on level for A and B being 100% and the on level for C being 50% - what is so hard about a scene on 50% command (thru rest or Alexa) resulting in scene members being set to 50% of the normal on level for the scene - so A and B end up at 50% and C ends up at 25%? That would allow the WAF to be preserved... Just my $0.02.

With either Mobilinc Connect or ISY Portal, the modes are identical. There is no difference. You can locally and directly connect to ISY with both via HTTP, and if you install a local SSL certificate you can connect locally with a secure HTTPS connection. Even if you have enabled the ISY Portal. Not sure where the misinformation is coming from that claims otherwise. However with both the Portal and Connect you must create two profiles in Mobilinc if you wish to use both (local and Portal/connect) each with their own connection settings - and manually switch between them based on your location.

Thanks Benoit (and Michel)! It's customer service like this that keeps me coming back for more...

Benoit, I understand (and encourage!) Security first - but there are ways of providing a 'Remember Username' check box on a logon form, then encrypting the username using a symmetric key (with timestamp and nonce) in a cookie to persist it in the browser. When the cookie is received in the future, you (and nobody else) can decrypt it, obtain the timestamp to determine if it has expired (only allow the next 30 days, for instance) and use the value to pre-populate the username. There is no loss of strength as a result of this. After a successful logon, you resend the username encrypted cookie with a new timestamp and nonce - providing another 30 days of remembering the username. I actually suspect it would be more secure than having Chrome remember it - and its use would be optional. Michael.

That's really a question for Wes. I've never had IOS specific features so I don't know. As an Android user myself, nothing was lost (because Mobilinc on Android also dosn't support the Mobilinc Connect specific features that Mobilinc on IOS supports). What I do know is that for push notifications to work at all, and intermediate server is required. That's what the Connect Portal does - acts as an intermediate. So yes, I believe you would lose in-app push notifications. However, Pushover is coming to the ISY Portal soon-ish (we are told) - so you could add the Pushover client to your i-device and get notifications that way as a replacement.

My Alexa just died. Totally dark and not responding.... I guess I'm contacting Amazon in the morning.... But yes, I did the in-app voice training and it dosnt have an issue understanding me (with my mixed British-midwest accent). It dosnt have an issue with understanding my 11 year old Daughter either with no training... so I'm not sure what to make of that.

Trying to figure out if 'very soon' is < 'imminent'.... Or the other way around...[emoji14] (Can you tell were an impatient lot!)

'Standards based' - I cannot believe the FUD coming out of their PR dept.... Download the .jnlp, run it. Doesn't use the browser plug-in feature at all. Carry on..... My opinion - good riddance. 99% of all vulnerabilities and performance issues are due to poorly implemented plugins.

ISY also shows up in the 'Connected Home' page of the Amazon app - but only if you clicked the activation link Michel posted in the instructions while previously being logged into your Amazon account. If its not showing, you haven't clicked the correct link yet to activate it (and Amazon haven't taken the 'beta' lock off yet) I'm sure this will be going away at some point - it (is/was) the way Amazon control access to beta resources. If you're looking in the 'Skill' area - your in the wrong part of the app.

I've been doing this for the last year - it continues to work well for me.

So in that regard, ISY wins! ISY wins again due to being able to run programs from Connected Home...

This works just fine... Michael.

Woot! Does that mean ISY will show up in the Alexa app even for those that haven't clicked the activation link? If so - that even better and should drive sales of ISY. You should put out a press release and yell it from the rooftops! Congratulations! An amazing milestone.

That's kinda bad! Sounds like you have an 'else' clause somewhere with a relay 'on' command in it that's running on the reboot. I doubt this would happen otherwise.

You could always create programs on ISY1 to trigger ISY2 scenes via network resources and effectively control ISY2 without having to connect directly to it.

You don't need to do that. All 'Enable internet access' does is map a port forward if your router supports upnp. If it doesn't, you will get an error message. Those without the portal will usually manually configure a port forward (since upnp is generally not considered secure for firewalls). Those with the Portal will likely use the portal for remote access, making it unnecessary to port forward at all.

Did you group the lights in Alexa's settings? If so, that would explain the group activation.

I don't use the IOLinc to control my door (due to Insteon insecurity), but the manual seems to suggest that 'Momentary C' is the correct one for garage doors... http://cache-m2.smarthome.com/manuals/2450.pdf That way, an 'ON' will only ever open the door and never close it, and an 'OFF' will only ever close the door and never open it. The sensor status drives which command will be ignored, and which will be processed. That has the added benefit of the relay status just naturally following the state of the sensor (after the door completes its operation), and means you shouldn't need programs to reset the state of the relay at all... Like I said - don't use one this way - just going by what the manual says.

The log shows the sensor was queried as well. I wouldn't have the relay in a scene - there does not seem to be a purpose to this. Just set the relay to momentary and use a program to turn it 'on' to activate the door. Hide the relay device from Mobilinc so its status dosnt get in your way. Have the sensor be the controller of a scene that lights (or unlight) a KPL.

Awesome! Won't get chance today, but I'll play with this over the weekend!

The Admin approval request is in the Java Admin Console - not the ISY Portal Console. What version does it show in 'Help' 'About'?

True enough - but the step that says 'Click this link' after 'Login to alexa.amazon.com' is Amazons way of adding a beta channel to Alexa that is not in production yet. The Wiki really should say that this is still beta IMO - certainly the forum thread does, in capital letters!

Nope. Different things.