MWareman

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.

I think querying the relay should be fine. It's querying the sensor that could trigger any program looking for 'status' and cause unexpected results. Separate the sensor and relay - make sure that they are not in the same scene. Change your query to only query the relay - not the relay and sensor. Michael.

Connected Home is still beta. The skill is released. I'm sure instructions for the connected home will be published outside of the beta thread once it's no longer beta.

Thread about adding the Alexa Connected Home (beta) to your Alexa Portal, to allow ISY control (apparently its currently limited to the first 450 users).. http://forum.universal-devices.com/index.php?/topic/17861-Amazon-Echo---Connected-Home-Feature-(Beta)!

Something caused the status of the IOLinc sensor to get updated though. Perhaps before the posted log. Perhaps an event not logged. If not the 'All On Off' program, what? It's not in the log. Something did it though. Either way, putting the IOLinc sensor as a controller of a scene that the IOLinc really is a responder to will likely cause uncommanded openings at some point when you use the IOLinc as a garage door controller. (If this is indeed the case)

AFAIK - preserve simply does not remove them. ISY does not learn existing links in this situation. A scene with two devices actually contains three devices (the two and the PLM) and three links (not one). Each device in a scene has a link to and from each other device in a scene (including the PLM). If you cross-linked them and then added them individually to ISY, the ISY will not know of the pre-existing link directly between the two Switches - and will probably remove it when you save the device - effectively breaking the link between them. Some people use 'preserve' when adding ISY to another pre-existing controller and trying to use multiple controllers to control common devices. I wouldn't recommend that at all - its fraught with danger!

I'm with oberkc - if the IOLinc sensor is in the same scene (as a controller) with the relay (as a responder), then I think we've found the cause. A missed 'close' signal may trigger the relay when the 'Query All' reaches the device, and the sensor changes to the corrected state. This would also explain why you are not able to reproduce it.

Do you use the Mobilinc Portal service (called 'Mobilinc Connect')? It's purchased as a subscription within the Mobilinc app. If not, you won't lose anything by adding the ISY portal and hooking it up to Alexa. You can keep using the Mobilinc application directly to ISY just fine, but you may have faster SSL response times by reconfiguring the Mobilinc app to use the ISY Portal instead of the direct connection. If you do use 'Mobilinc Connect' with the Mobilinc app, then it will stop working when you change to the ISY Portal - since only one Portal can be active on an ISY. You'll have to reconfigure the Mobilinc app to use a new URL - and if you use IOS there are some Mobilinc IOS-only features you will lose (like push notifications). If on Android - there are no features lost by switching to ISY Portal. No other features are impacted - like XBMC integration thru the network module. That will keep on working.

It sounds like you directly cross-linked the switches. This isn't necessary when you have an ISY, and actually causes the ISY to be unaware of the situation. The correct approach is to create a scene in ISY and add both SwitchLinc dimmers as 'controllers' (not 'responders') of the scene. The ISY will then create the necessary links for everything to work as you want. That way - they will both track each others dim level, and the correct dim level will be represented in ISY. You may want to 'restore' the devices in the ISY Console first though to remove the errant direct cross-linking (if that's what you did). Michael.