stusviews

This is, of course, only between fun for us. Anyone can offer to place a bet, but it has to be accepted. If someone wants to bet against me, then they better make an offer I can't refuse. They would also have to agree to my terms. Actually, any two (or more) can bet between themselves without involving us at all. We've covered the U.S., coast to coast. It's time to go international

Nope, my acceptance was in response to asbril's prediction. You may be welcome to join in, but you haven't stated which side you're on

CCTV cameras provide privacy,

Accepted. Lunch or dinner and/or breakfast and a place to stay when you're on the other coast.

rossarmstrong: From the smartphone app, select Smart Home. Does the "Kitchen Night Lights" appear under the Devices tab? under the Scenes tab?

Z-Wave started as a protocol as did X10 and Insteon. Z-Wave evolved into an alliance, which made the protocol freely available. That's good as it allows manufacturers to freely produce compatible devices. But is also allows manufacturers to add features that they can patent or even not include. It's debatable whether that's good or frustrating for the buyer. I am very comfortable with Insteon and their much wider selection of products. But I have no problem buying and praising Z-Wave device when they exceed what Insteon offers. Oh, what's the bet and how soon is soon? After all, it should be easy. The Insteon solution is practically identical to extant RF fan controllers including size and shape And enjoy the upcoming year to your fullest.

What are you entering for the address? It should be the Insteon ID printed on the bulb. The name has a drop-down list or you can select Auto Discover.

The Echo Dot is bargain priced now for just 30 bucks. Or you could opt for a refurbished Dot at $45

See the last sentence of post #58. A monopoly does not allow compatibility on any feature at all and refuses to even offer a feature at any price.

I do use Z-Wave. There is no Insteon compatible device that has nearly the features of Z-Wave locks. I already installed same key Schlage door locks and dead bolts when we purchased based on their style, features and reputation, later upgrading to push-button control (one less key to carry), so transitioning to Schlage Z-Wave look-alikes was easy. I did not like their fan controller and went back to Insteon. And I do use a z-Wave plug-in motion sensor.

The reference, "willing to pray the price," was in reference to other manufacturers paying to use some or all the features of a patent to the patent holder, in other words, to make a compatible device. It was not meant to be a cost comparison for retail items. I should have been clearer. BTW, there are actually few Insteon compatible devices. Those manufacturers were willing to pay the price that Insteon Labs asked for, probably after a bit of bargaining

Based on anything I know about Insteon and monopolies (more than a lot about both, but not an expert on either), the Insteon protocol is not a monopoly, but a patented idea, based on another patent that has since expired. Some patents are licensed out. X10 did that. Leviton did that with a Z-Wave feature. Not everyone is willing to pay the price. But that's precisely what a patent protects. Apple, too, can be considered a monopoly--but that's not what a monopoly is. There are other computer operating systems available as there are other home automation networks available. Insteon did monopolize on features they offer. But so did Sony, BMW and even Amazon. Can I include Google (Android)?

If the scene is already created, added to the portal and also to the smartphone app, then select Routines and click on the + (top, right). Instructions will follow. Need more help? Where specifically are you stuck?

Create a folder. Add the condition to the folder, for example: =================================================================================== BR <--this is the folder Folder Conditions for 'BR' If Status 'EX / Devices / EX Side Door-Sensor' is Off Then Allow the programs in this folder to run.

Alexa computer groups are not the same as Alexa smartphone groups. I use smartphone groups on when I want a particular Echo device to control the group. In that case, I set both devices and scenes to be Alexa Category Light. If I just want to be able to set the On-Level using a voice command regardless of which Echo responds, then I create a computer group also adding the device(s) and scene(s) to the group. I do not categorize anything. If I ask Alexa to turn on the light, then the light turns on at the level set by the scene. If I ask Alexa to set the light to x percent, then the light turns on to x%.

Better, I break bread and/or slice it myself.

Most of our KPLs are gathering dust. We use voice for nearly everything that can be controlled by the ISY, that includes devices, scenes and even programs. The original installation is a bit involved, here's a link to the Wiki. You'll find that the Echo sometimes doesn't understand what you said, but that's true of people, too. There's a lot you can do, but that's way too lengthy to post. It's best if, after installation, that you ask specifically. A quick tip: Voice commands do not run program conditions, On runs Then and Off runs Else. But you can have Then run a program's conditionals. If (leave blank) Then Run program x

The earlier motion sensor is not a flawed sensor at all. The newer sensor will not be fully recognized until v5 makes it out of Alpha,

That you can include an Echo as a member indicates that you're using the smartphone group. That app has requirements that the computer app does not, for example, no member of the group should have "light" as part of the spoken if you name the group "light." I just looked at a couple of smartphone app groups and noted that I added devices first, but that was because devices appeared first. In any case, the devices turn on at the preset On-Level. The same is true for the computer app, but that app doesn't allow selecting an Echo.

Hmm, another duplicate post.

I don't have a Google Home, so I can only offer what works with the Echo. There may be a similar setup for Google. Echo has what's called "groups." This is for the computer group, not the smartphone group (they're somewhat different). Create unused spokens for both the scene and devices (e.g., LR Device, LR Scene). Add both to a group. Name the group an appropriate spoken (e.g., living room light). Edit: misspell correction.

"For" can be used to bypass the common error of forgetting to specify "Next Day." I don't know it that was the intent, but anything that minimizes a common programming error is good

No, it does not matter in which order the devices/scenes are added.

A home automation "scene" is defined by the protocol and may or may not have any relationship to how another protocol (or industry) defines a scene. An Insteon scene is anytime one or more devices are linked to one or more other devices. Each device can linked as a controller, responder or both. An Insteon device can be a controller of one and only one scene, but it can be a responder to many scenes. ISY scenes differ a bit in that if the device is a scene controller, then it's also a scene responder. Because the On-Level of any responder can be On or Off (or any level in-between if the responder is a dimmer), the scene itself has no status, only the devices which are members of the scene do. Thus, turning an Insteon scene off turns all its member off, turning a scene on can result in multiple On-levels including Off. Note that an Insteon scene does not need to have any controller (as defined by the Insteon protocol) at all. When a scene is turned on or off by some other method, then that method is considered a trigger, not a controller (in Insteon terminology). BTW, the Insteon protocol has its roots in X10 to which we owe the All On/All Off phenomenon (and which has subsequently been deleted from the Insteon protocol).

My motion sensor requirements are twofold, first and foremost, an established ISY version. Even a version that's not perfected is adequate, as every system has bugs. An Alpha version is nowhere close, no matter how many users find praise. A second requirement allows the device to be a scene controller, minimizing the response time. I understand that ISY v.5+ meets the second requirement (for both Insteon and Z-Wave), but not the first. zippo, for me, there's no search, just waiting--unless, of course, an unanticipated solution occurs. I have no prediction at this time., it is, after all, unanticipated I don't know what will happen next, but I can hardly wait.