MWareman

“Hey Google, Turn on the overhead light in the kitchen and family room” “OK, turning on two lights” And indeed, the correct two lights came on.... Got to love how Google Assistant can chain commands. I tested “Turn on the kitchen and family room overhead lights” - and it got that right as well..... Standing in my family room (regular Google Home)... “Hey Google, turn off the overhead light” - and off it goes. Kitchen stays on. Move to my kitchen (an LG Smart Display)... “Hey Google, turn off the overhead light” - and off it goes. This is fantastic. I now don’t need convoluted spokens and the whole system becomes far more intuitive. Thanks again for the fast feature!

It works! Thank you so much...

There can be only one.... When you added the ISY Portal, you likely clicked past the screen that said it would disable MobiLinc Connect. As Wes said - UDI Sales can get you sorted out and switch you back (this will disable the ISY Portal). You will have to decide which to keep.

Maybe you have the ‘Reverse Trigger’ setting enabled on the iolinc? This only reverses the trigger sent when the sensor changes state, but not a query. So if you have something that queries your iolinc later the status could flip without the door being operated.

Thank you! Awesome as always...

You are correct. Thanks. Thats what I get for putting this together between other work..

When adding spokens to devices in Google home - the 'Room' is notated with '(Optional - not used)': Optional is correct. However - while this used to be not used - they are, in fact, used now. If you list rooms in a consistent way - these will be synced to the Google Home app and devices will be grouped by the room. If you have a Home device in the same room as one or more lights - saying 'Hey Google - Turn on the lights' will turn the lights in that room only on. From any Google Home - you can 'Turn on the kitchen lights' and all lights in the 'kitchen' will turn on. The only challenge I have is this... You cannot have two devices with the same spoken - even though Google at least appears to support this now (as long as the devices are in different rooms). A 'Floor lamp' can apparently exist in two rooms (say, the family room and bonus room). Saying 'Turn on the floor lamp' in the bonus room would turn only the 'floor lamp' in the bonus room if the command was heard on a Google Home that was assigned to the Bonus room. Saying 'turn on the family room floor light' will direct the command to the floor lamp in the family room even if it was heard at the home in the Bonus Room. Is it possible to test changing the unique keying to include the location as a key? So - all devices must be unique within a room - but can be duplicated in different rooms? I'd like to know if this will work now that rooms are a 1st class concept in Google Home. As someone who has Google Home Minis all over my house - this would be a huge addition... Thanks!

Here is a program that syncs a load bearing LampLink with a non-load bearing SwitchLinc dimmer and a KPL button... SCSYNC-Family-Floor - [ID 0130][Parent 0025] If 'Main / Family / Family Room Floor Lamplinc' Status is 0% Then Set 'Main / Family / Family Room Floor Switchlinc' Off Else $iSCSYNC_Temp = 'Main / Family / Family Room Floor Lamplinc' Status % Set 'Main / Kitchen / SC - FamilyFloor-KPL' On Set 'Main / Family / Family Room Floor Switchlinc' On '$iSCSYNC_Temp %' In this case - the Lamplinc is the device with the spoken assigned - as a 'Light'. Google Home then gives me full control of the device - including setting it's dim level. Every time the status of the Lamplinc changes - the 'If' executes. If the status changed to 0% - the SwitchLinc is turned off. If not - the current status of the SwitchLinc is read into a temporary variable - then that temporary variable used to set the on level of the SwitchLinc Dimmer. There is a small latency here - but it's not noticeable (since you don't really register the status of the secondary devices). Also - this needs 5.x on your ISY (the ability to read and write a device state to and from a variable is not available in 4.x). For multiple secondary devices - just repeat the last 'Set' line as necessary for all devices in a scene. Just remember you cannot set KPL buttons that way - you need to create a scene with only that button in it. Also - there is no point setting a KPL button to the state - it's only either on or off...

In most cases - I have a SwitchLinc Dimmer controlling the load in a scene (as a controller) - and a KPL Button also as a scene controller. I add the SwitchLinc Dimmer ("Kitchen-Overhead') to Google Home with a spoken (as a light). I have the following program to keep the KPL button (it's a KPL button in a scene to control the KPL button as you cannot directly control KPL buttons) in sync: SCSYNC-Kitchen-Main - [ID 006A][Parent 0036] If 'Main / Kitchen / Kitchen-Overhead' Status is Off Then Set 'Main / Kitchen / SC - Kitchen-KPL' Off Else Set 'Main / Kitchen / SC - Kitchen-KPL' On I'm working on a solution to deal with secondary devices in a scene that have dim level indicators (such as multiple SwitchLinc Dimmers in a scene) by reading the load controlling dimmers level and applying it to the others in the scene directly with a direct dim command. Not done yet... as those particular scenes have been low priority for me. This then allows me to use Google Home to full potential - and have my KPL buttons reflect the correct state.

I don’t think Insteon scenes support the ‘direct dim’ command like dimmer lights do. I never expose Insteon scenes to my Google Homes. I have the Google Home control the device that is controlling the load. Then, I have a program triggering from the ‘status’ of the device to keep the scene in sync.

Not sure about the others at this moment, but you cannot ask the status of an Insteon Scene. There is no concept of that in the protocol.

Your ‘If’ probably is testing ‘Light A’. When you turn it off, then have the ‘Wait’ - the ‘If’ will get retriggered. Your ‘Else’ is likely then set executing.

And the ability to control the lighting products!

I believe Morninglink make an Insteon lock, which would then work thru Alexa. However, they don’t support status feedback (no way to trigger n being manually locked or unlocked) and no confirmation that an open or close succeeded. You really need to go zwave for this...

I will say, while not delinking yet I did just add a few devices and assign a room (in the ISY Portal) and spoken. I synced to Google Home (this worked flawlessly since I’ve changed from sending scenes to devices) and lo and behold the new devices showed in the Google Home app as being in their correct rooms. So, somewhat confirmed....

It’s been a little bit since I did a unlink/relink - but I’m fairly sure that since I have rooms set in ISY Portal the rooms got allocated correctly in Google Home when I relinked. Was that a fluke?

No SSL cert needed (or port opening on your router/firewall) if you are using ISY Portal for your external in comms... unless you want to do SSL access on your local WiFi as well...

Depending on your program, if ‘den motion’ (the triggering condition) resets before your ‘wait’ times out, then the wait will abort and the ‘If’ will be re-evaluated - causing your variable not to be reset to zero.

The Google Home app on Android shows status for lights, but not scenes. This is the scene limitation of Insteon in action again. If you are controlling scenes with your Google Home Hub then this would likely explain why they are not showing current state. Can you confirm that you are exposing devices rather than scenes?

You can do remote connections from your phone using the stock MobiLinc app and the ISY Portal. Just configure it as a direct connection to ISY and use your Portal username and password. You’ll need to make sure the ‘Preferred’ ISY is set in your Portal account. To use this you will have to ask UDI to disable the Mobilinc Connect service on your ISY. You can also do IFTTT with the ISY Portal. It’s a bit more work though (you have to use the IFTTT ‘Webhook’ facility).

I wish I knew Python......

In my case, I had only added spoken to scenes. I regularly had to remove and reauthenticate because the connection got broken. I just started the process of switching to putting the spoken son the controlling device (so you can ask Google the current status) and implementing programs and scenes to keep the scene consistent when the device is controlled in this way. Hopefully, this change will stop my accounts from getting disassociated as well... time will tell... If this is indeed the issue, then there really should be a keepalive ping implemented in the Portal....

But it does require either an active ISY Portal subscription, or the purchase of the ‘Network Module’.

Yes, but you will likely still need to disable ‘less secure’ access, since the ISY is sending a username and password (over TLS) rather than using oAuth to authenticate. Best advise is above. Use a separate gmail account for ISY to use. It’s free!

Agreed. Sometimes a feature comes to Amazon Alexa first, sometimes to Google Home.