Goose66

Benoit, I don’t think you are understanding the problem. I know how to add scenes to the portal and how to control those scenes using Alexa spoken commands. The problem is the fact that the “implict targeting,” i.e., “Alexa, lights off” only works with those end points categorized as “Lights,” but most of my end points that I have (and I believe most Insteon users) are scenes. The reason for using scenes is to keep multiple switches and KPL buttons in sync. If we control devices directly all those multi-switch circuits and KPL buttons get out of sync. In order to use the implicit targeting feature, we need the Portal to show the scenes as Lights in the discovery payload to the Alexa Smart Home API instead of Scenes.

Ok, having only enabled the v3 skill last night, I quickly added a couple of devices to my bedroom and tested it to make sure it worked before posting. However, now I am looking at how I would actually use this feature, and since scenes don't work with it, it's utterly useless. The Alexa Smart Home documentation describes a "scene" as a collection of devices to turn on or off together in no specific order. And I have SOME scenes that may fall into that category. But being and Insteon user, 80+% of my scenes are to support multi-switch circuits and KPL buttons that control a single light (or set of lights). I have dozens of multi-switch circuits in the house and at least 5 KPLs. If I add devices to a Smart Home Group so that I can use the "Alexa, lights off" commands, that throws synchronization amongst my multi-switch circuits and KPL buttons (realized by Insteon Scenes) out the window. The way to fix this is to have the portal report Insteon Scenes as displayCategory of "LIGHTS" instead of "SCENES." Or better yet, add a dropdown in the portal so that I can select the displayCategory for my devices I add to the Alexa Skill. Benoit, cela peut-il être fait?

Only if you are naming your devices "Light." If you name your devices something else and put them in a Smart Home Group with the Alexa device, when you say "Alexa, turn on the lights" it will turn on every device in the group that is identified as a lighting device by the portal to the ISY Smart Home Skill.

Also, what is address 11.02.01 point to? I think the link table in the switch (2B.BF.11) may be bad. You may want to try restoring that device from the ISY.

This is reminiscent of my old house where the SwitchLincs controlling fluorescents or CFLs were constantly causing me trouble. Dumped them all in favor of LED (and legacy incandescents).

What types of motion sensors? If they are the older 2842-222 then "On Only" is a jumper setting (pin 4). It will send On on motion and continue to send On every second until motion stops. The light will be in a scene as a responder with the motion detector as a controller. When the motion detector sends an On, the light should turn on immediately without the 1 or 2 second delay introduced by the ISY's program cycle. But the motion detector never sends and Off. Your program is setup to respond to the motion detector being "switched On" and will run a timer for the desired duration after last motion and then switch the light off in the "Then" branch. Each subsequent On for the motion detector will re-run the program (and thus reset the timer). The program can also update the status of KPL keys and other switches that control the light to keep everything in sync.

Are we doing this again?

If they only lasted a year, I could go through 13 years of them before paying for one Jandy WaterColors LED pool light. Of course, those things are more like 300W equivalent as opposed to the 75W equivalent I will get from a Hue color LED light.

If I could get my stinking pool controller to handle colored lights, I could just have the ISY program color the spa blue when it's cold, yellow when it's getting close, and red when it's ready. Maybe I can just put some Hue can lights in the pool light fixtures.

Anyone used a program to flash a KPL button (1s on, 1s off) for any length of time to reflect status? I would like to flash the KPL button for my Spa after I turn it on until it is up to temperature. Could be flashing for as long as 20 minutes in the winter. Seems like a lot of Insteon traffic, though. Any thoughts or experiences would be appreciated.

My situation is similar to Larry's - the pool house is just off the garage and one level below. The closest dual-band Insteon switch is on the house side of the garage - about 32 feet away. Are you assuming that the Insteon signal is getting to your shop via powerline, then? Because mine is not working reliably via powerline, although the interference from the pool pump is something I have not thought of. I am going to flip the breakers to the pumps one night and see how the reliability fairs.

I have an outbuilding (pool house) that is on a separate electrical feed from the main house (same meter but separate branch circuit just inside the meter). Insteon in the pool house can work, but rarely does. I have Wi-fi coverage in the pool house, though, and I have a run of coax in the pool house that runs back to the main house wiring closet. Does anyone have a novel way to extend Insteon over Wi-fi or coax that doesn't involve a brand new ISY and Insteon PLM? The Coax run is currently being used for DirecTV but there may be a way to get that to work over Wi-fi. Could the coax be used with a couple of hacked range extenders to create an RF bridge over coax to the outbuilding?

I guess we'll have to wait and see when the v3 ISY Skill is available.

You can just click the "Watch this video on YouTube" link in the error message. Here is the URL: https://www.youtube.com/watch?v=UH8I8vKMJ5E Question: Are we going to have to go into the Alexa app and enable a new, specific v3 ISY Skill when it is available or is the existing "ISY Optimized for Smart Home V2" just going to start using the v3 API?

Looks like the devices need to be identified with the displayCategory attribute of LIGHT or SWITCH during discovery to be considered lighting devices by Alexa.

Is it possible this only works with Echo Plus and 2nd gen Dots? Man, that would suck!

Ok, maybe it does have something to do with the v3 API. While nothing in the incoming command payload deals with group or room, there are device classifications returned in the discovery payload that may facilitate what Alexa understands to be a “light” in the group.

The update to Alexa is supposed to let you do it without different accounts: https://youtu.be/UH8I8vKMJ5E This should not require v3 of the ISY Smart Home Skill either. It should just work, according to the video.

Nor does StuViews suggestion match the Amazon tutorials for the new Smart Home capabilities and groups. I noted this in another thread, but I don't see anything in the new API ("capabilities" or message payloads) that supports the new intelligent Group capability - I believe it is supposed to be implemented in the Alexa device and not in the ISY portal service. So I don't think it is necessary to wait on the v3 Smart Home Skill from ISY to be approved to get this functionality. According to the tutorial, you are supposed to be able to add devices and an Alexa device to a group, and then use short cuts like "Alexa, Lights On" to turn on all the lights in that group. I don't think it is necessary to rename your scene or device to "lights," just add it to the group (they add "Game Room Light" device to the "Game Room" group in the web tutorial). If there are multiple lighting devices in the group, then it should send commands to the ISY through the API to turn them all on. That said, I can't get this to work either. So don't know what the problem is. I will keep trying and let you know how it works out. EDIT: Details of my trial: I added two ISY scenes: "Living Room Lights" and "Office Lights" and rediscovered devices. These devices work by name from all of my Alexa devices. I added the Echo in the living room and the "Living Room Lights" to a group called "Living Room." If I say "Alexa, turn off the living room lights" it works, but "Alexa, turn off the lights" or "Alexa, lights off" comes back with "Sorry, I didn't find lights." Exact same setup and scenario in the office. This is exactly what they show in the tutorial, except it's called "Game Room" and they add an AV control device to the group, as well.

Excellent! Thanks for the info. EDIT: Well, crap! It looks like BRK never made a hardwired combo smoke and CO detector with the old OneLink (915 MHz wireless interlink) that works with Smoke Bridge. They made the hardwired smoke only detector with old OneLink and the battery operated smoke and CO combo detector with old OneLink, as you mentioned, but not what I need. I guess it's either just adding a relay to the 9120Bs and getting a single, uninformative alarm condition in the ISY or going with something completely different for all 6 hardwired detectors.

Yeh, I get that. I don’t intend for the existing detectors to talk to the Smoke Bridge. I would buy a hardwired OneLink detector and the existing units would talk to it via “smart interconnect.” When they alarm for smoke, the OneLink detector would alarm for smoke. When they alarm for CO, the OneLink detector would alarm for CO. Are you saying that despite the fact that the OneLink detector would alarm for CO, for example, it would not send anything to the Smoke Bridge?

I’m afraid I’m not following. The existing smoke/CO detectors are not OneLink. They are hardwired 9120Bs. I installed them last year when I bought the house to replace the 13 year old, original smokes. My question is will installing a hardwired OneLink detector, like AC10-500, and pairing it with a Smoke Linc, allow the ISY to recognize different types of alarms from the 9120Bs propagated through the “Smart Interconnect” to the AC10-500. This may be a buy it and try it scenario.

Thanks - that unit is much cheaper. I know that multiple hardwired First Alert Smoke/CO detectors can differentiate whether the alarming detector has detected smoke or CO and produce different alarms accordingly (they call it "smart interconnect"). I was hoping that someone could confirm that the one wireless device in that system would pass the different alarms (at least smoke vs. CO) to the Smoke Bridge. Actually, the SA521CN is smoke only, so that wouldn't work in my setup (or at least I would lose CO in that zone as well as possible reporting to the Smoke Bridge).

A separate but related question - if I install a single hardwired OneLink smoke detector (the new $119 one, I guess) and it is interconnected to my other hardwired First Alert Smoke/CO combo detectors, will the Smoke Bridge accurately report test/smoke/CO/low battery status from all my detectors, or just the one OneLink detector?

Thanks for the update. So in regard to nodes, do we need a way to map a node to a defined type of device then? For example, the temp_control nodes on my pool controller are a lot like thermostats and reuse some the same status values and commands (e.g., CLISPH). Since the v3 API allows you to specify distinct capabilities for devices, would there be a way to tell the Smart Home API that the temp_control node for my pool is a "thermostat" with only on, off, set setpoint, increment setpoint, decrement setpoint, and report current temp and setpoint capabilities based on its definition in the nodedef.xml file?