Goose66

I want to make a point in this thread for future readers: While it would likely just burn out your millivolt valve, hooking the 5 volt output of the I/O Linc through the relay to the valve COULD work. However this would be VERY DANGEROUS because in these systems the fact that the pilot light heats the thermocouple to produce the electricity to open the valve is a safety feature. If you were to supply external power to open the valve when the pilot was not lit, that could release gas into the house and asphyxiate the occupants.

The two wires that went from the fireplace to the switch now go from the fireplace to the NO (normally open) and common terminals on the I/O Linc. This gives you ISY control of the fireplace.

My fireplace is controlled by a millivolt gas valve. The small flame (pilot) heats a thermocouple that produces the voltage required to operate the valve. No external power is required. I had a standard decora wall switch that simply connected to two small gauge wires to control the fireplace. I ran a 4 conductor thermostat wire (18 ga) from the switchbox to an outlet on the wall below. I use one pair of the four conductor wire to hook the NO and common on the I/O Linc to control wires to the fireplace. I replaced the switch with a Leviton decora momentary contact switch ($27) and I use the other pair of the four conductor to hook the momentary contact switch to sensor and ground on the I/O Linc. On the I/O Linc, run through the procedure to link the sensor to the relay output. In this way you have both Insteon and local switch control of the fireplace.

I would love to get confirmation from Michel on this because it would explain a lot. I just assumed that the PLM handled scenes the same way as the other Insteon devices, but it makes complete sense that would be up to the ISY and not the PLM (because it is not the same as a PLC or Insteon Hub). It would be possible, under those circumstances as well, for a program's invocation of a scene to be different from a user's invocation of the scene through the Admin Console (although I don't see that listed in Mike's comment).

And delete and re-add to the ISY with "Remove existing lincs." Make sure the plug they are in when you do the re-adding and putting them in scenes has really good communication with the ISY, and then you can move them to there final operational location afterwards. I will say I have trouble with my On/Off modules and ApplianceLincs pulled out for Christmas lights every year, and it also seems they cause problems with the other Insteon devices. I have tried to migrate them all to the latest dual-band modules, but there are still 4 or 5 legacy modules in the mix.

I have a very similar problem. I have a scene that includes a dozen or so On/Off modules that control my indoor Christmas lights. The scene also has a KPL button as a controller. A program turns the scene On and Off at 7:00 AM and 11:00 PM, respectively. Activating the scene through the ISY turns them all on or off. Using the KPL button turns them all on or off, but it seems like 1 out of 3 mornings at 7:00 am, one or two of them does not turn on. If I walk to the KPL and turn the scene off and then back on, I can get them all to come on, even if I do it at 7:02 am. Now, while I would expect the KPL button to be more reliable, there appears to be nothing about programs that would make them less reliably than other methods of turning on the scene through the ISY (Admin Console, Alexa, Mobilinc, etc.), and the fact that the program runs at 7:00 and 11:00 instead of sunset/sunrise suggests that it's not a problem with colliding with other programs. What I think it all comes down to is that Insteon communication to these On/Off modules is just not that reliable. And the mathematics of the situation makes it more noticeable in the scheduled program run because it runs every day while troubleshooting attempts such as activating the scene through the Admin Console are only done occasionally. In fact, I have precisely the same problem with another scene with outdoor ApplianceLincs that controls my outdoor Christmas lights between sunset - 30 min and 12:00 am. By comparison, my program that turns on and off my outdoor lighting scene containing all KeypadLincs at sunset and sunrise works flawlessly every night, as far as I can tell.

Thanks for the response. I'm leaning in the direction of not causing problems, so I only want to cleanup what is old, not remove something that is still integral.

Admin console. Just wanting to clean up as much as possible before going to 5.0.11A.

I have a disabled program QueryAll in my program list. It runs at 3:00 am and has Set "ISY" Query in the Then clause. It is disabled. Is this still required or is this legacy and can be deleted? I am running 5.0.10.

I have a tilde "~" in front of the "Auto DR" scene but it still shows up. I am running 5.0.10. Is there a way to hide this or is it legacy and something I can just delete?

I cannot for the life of me understand why there would be a system in place to disable specific functionality in an app like this based on region or account. I can see such a system for limiting streaming content or live events, but why in the hell would Amazon care if Canadians had the implicit targeting feature for their Alexa devices?!? That makes no sense whatsoever!

I think you need to read a page or two back in this thread. It's all there. Sent from my iPad using Tapatalk

The Alexa mobile app is needed to create Smart Home Groups that contain an Alexa device (Echo, Dot, etc.) to enable the “implicit targeting” feature.

I reset my whole system for a new house in October of last year by just deleting every device from the ISY, factoring resetting the PLM and installing it as a new PLM, and then connecting the ISY to each moved device as I installed it by address and selecting the "Remove Existing Links" option. Worked great, and I got to keep all my old programs to modify or delete as I saw fit.

At least not an Insteon Hub AND an ISY.

This was fixed in the Portal update Sunday morning. You can now specify in the Portal how you want ISY devices and scenes to appear in the Amazon app (LIGHT, OUTLET, SWITCH, or SCENE)

Working for me too. I appreciate the responsiveness of this update!

You can use variables.

Thanks. I think Benoit's summary is right on point.

I think the roadblock here (other than changes to the ISY firmware and Admin Console) is that it is still a limited developer preview. They say in the announcement linked above that they will only be choosing a subset of the Skill developers that apply to open the functionality up to, and all the general developer documentation for the ASK side has no mention of this functionality whatsoever as of yet. So unless UDI applies and is accepted, they will have to wait for the functionality to be made available to all developers (which is probably a more likely scenario, really). In addition, we don't yet know if Smart Home Skills will qualify or if it would have to be part of the non-Smart Home ISY Skill (Ask Izzy).

I think I have completely failed at describing what is an otherwise simple concept. I will let someone else take a whack at it.

But you can't add your Alexa devices to a group (your Echo, Dot, Show, Tap, etc.)

I think the only way it works is 1) the user authorizes the skill to send notifications, 2) the skill adds notifications to the user's single notification queue (by account, not per device), the ring light on the Alexa devices turns yellow, and 4) the user says "Alexa, what did I miss" and she reads all notifications in the user's queue from all sources (Amazon shopping, Dominos Pizza, ISY, etc.)

Ii just check the PC interface again (alexa.amazon.com) and, no, it does not have that ability to add Alexa devices to Groups. You will have to use the iOS app or the latest Android app.

So they just announced an Expanded Developer Preview of Notifications for Alexa Skills on Nov. 28 and are asking for Skill developers to apply: https://developer.amazon.com/blogs/alexa/post/833b9af4-26e6-47d2-a13d-bdbd9a257512/expanded-developer-preview-of-notifications-for-alexa-skills Benoit, are you going to sign up?