-
Posts
8205 -
Joined
-
Last visited
Everything posted by stusviews
-
I'm happy with Schlage BE469 Z-Wave deadbolts. I have a program that locks them all at night and I use KPL buttons and a Mini Remote to lock and unlock them. A program can engage the lock some seconds or minutes after it's unlocked. A hidden door sensor can disable the auto-lock program if the door is left open, for example, when carrying somethings in or during warm weather and then re-enable the program when the door is closed. You can probably do that with other locks (not Insteon), but I've been using Schlage for quite some time and have been very satisfied with both their performance, including battery life and, most especially, their customer service.
-
Anyone can modify, add on, or otherwise make use of a Homekit with no penalty nor law suit as long as it's not for profit nor "widely" distributed. If you want to do something with a Homekit device you own for yourself and/or a few friends go ahead and do it. But keep it private.
-
All the MSs I have send a low battery signal once, then change their state to off. Here's a program I use based on what Larry posted If Control 'IN / Devices / IN Front Hall-Sensor / IN Front Hall-Dusk.Dawn' is switched On And Status 'IN / Devices / IN Front Hall-Sensor / IN Front Hall-Low Bat' is Off Then Wait 26 hours Send Notification to 'automate' content 'Motion Sensor Battery' Set 'IN / Devices / IN Front Hall-Sensor' Write Device Updates Run Program 'Front Hall MS Battery' (If) Else Wait 5 minutes $iMS_Front_Hall_Battery = 2 Send Notification to 'automate' content 'Motion Sensor Battery' Set 'IN / Devices / IN Front Hall-Sensor' Write Device Updates The variable, $iMS_Front_Hall_Battery, is an integer variable with an initial value of 1. This is the custom message: Subject: A low motion sensor battery has been detected at the location below with a status of "2": Body; <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <title>New Page 1</title> <meta name="GENERATOR" content="Microsoft FrontPage 6.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> <meta name="Microsoft Theme" content="expedition-1 011, default"> </head> <body> <p class="MsoPlainText"><b>Courtyard</b>: ${var.1.8} </p> <p class="MsoPlainText"><b>Front Bathroom</b>: ${var.1.9} </p> <p class="MsoPlainText"> </p> <p class="MsoPlainText">--Status Key--</p> <p class="MsoPlainText">1 = <b>Battery</b> OK</p> <p class="MsoPlainText">2 = <b>Battery</b> low</p> </body> </html> Select HTML as the format, Alert, Default Subject and Variable to add a variable. Most of the code is automatically entered when you choose HTML
-
Open the scene, select the FanLinc light, adjust the On-level and ramp rate for the FanLinc light; select the KPL controller button, adjust the On-level and ramp rate for the FanLinc light.
-
If the KPL is a controller for the FanLinc, then the load (red) wire at the KPL should be capped. All control should be via scenes.Once that's done, it doesn't matter what the ramp rate of the KPL load button is. The On-level and ramp rate for the FanLinc light is controlled by setting the appropriate rates in the scene for the FanLinc light, not the KPL.
-
Somebody actually makes an electronic device that's meant to last ten or more years (on the average)? And here I am thinking that the Y2K problem eliminated any possibility of that ever happening again
-
I have a Dine Out button that controls 59 devices and/or buttons. Four devices are turned on to a specific On-level and eight additional are KPL buttons that are turned on (controllers of the devices that are turned on). One scene has control of all the devices. The Dine Out button is a controller of the scene and is set to non-toggle on. Setting the button to non-toggle On made it easier to turn some lights on and others off. There are actually two Dine Out scene controllers, one for the side door which leads to the garages and the other for the front door. Each egress button has a different program to control the exterior lighting (driveway or walkway). And both have a command that turns off the button's LED. Dine Out Side door If Control 'DR / Devices / DR Side Door Light / DR Side Door B Dine Out' is switched On (Side Door Dine Out button) Then Set 'DR / Devices / DR Ceiling Light 50' 50% Set 'DR / Devices / DR Side Door Light' On Wait 1 minute Set 'DR / Devices / DR Ceiling Light 50' Off Wait 6 minutes Set 'DR / Devices / DR Side Door Light' Off Set Scene 'Dine Out Buttons' Off <--Turns off button LEDs (scene that includes only the two Dine Out buttons as responders) Else - No Actions - (To add one, press 'Action') Dine Out Front Door If Control 'LR / Devices / LR Ceiling Light KPL 20 / LR Light KPLD Dine Out' is switched On (Front Door Dine Out button) Then Set Scene 'EX / Scenes / EX Walkway' On Wait 5 minutes Set Scene 'EX / Scenes / EX Walkway' Off Set Scene 'Dine Out Buttons' Off <--Turns off button LEDs (scene that includes only the two Dine Out buttons as responders) Else - No Actions - (To add one, press 'Action')
-
I haven't yet played with various names for the dining room devices as I have for the living room and bedroom. And yes, I've tried various requests such as tell and ask Izzy, turn/set/switch, relocating the command (e.g., turn on device/turn device on). Nothing works for switching/turning/setting the dining room light off. Everything works to turn it on. And the fan device has no difficulty with "dining room." Both scenes include a wired SwitchLinc dimmer as a controller. The fan is a 2476D and the light is 2477D.
-
The same can be said of your, "more spare Insteon devices than I have spare light bulbs." I still had some unused single-band devices when dual-band was introduced. But, I can wait longer to get one or two devices than I can when the PLM fails
-
I added two scene names, "dining room light" and "dining room fan. "Alexa, ask Izzy to turn dining room fan on/off" works every time. So does "Alexa, ask Izzy to turn dining room light on." But,in response to "Alexa, ask Izzy to turn dining room off," Alexa responds with, "I could not find device dining room. Turn off which device?" Echo does hear the command correctly. I have not had any success with turning the light off using the Echo, but not because of an ISY communication problem. Alexa can't find the device only when an off command is issued. Edit: I posted in this topic because of the unusual response to device names.
-
I have two spares, a Version 1 that hasn't yet failed and a spare Version 2
-
Are you selecting the scene or the device? You should be selecting the scene name and not the device name for the first line of Adjust Scene.
-
Select Adjust Scene. There will be two line, the first is the scene name, the second is the device name. BTW, do you actually have two scenes that you want to control? Or one scene with multiple device (e.g., Motion Sensor, SwitchLinc, etc.)
-
Tip: search Amazon for the PLM
-
Something is amiss. If you can't ping the IP address, then either the address is incorrect or the router that the ISY is wired to cannot see the ISY or you have a conflict. Disconnect every router except the one that the ISY is wired to. A connection to the internet is not required. Search the attached/connected devices list for the ISY. AFAIK, the MAC address should start with 00:21:B9.
-
Did you assign a port other than 80? What is the result if you ping the IP address?
-
It's possible that your PLM has aged to the point where it's no longer reliable, usually at about two years of use. What is the age and version of you PLM. BTW, there's a 4-digt number on a white label on the back of the PLM that will give the week and year it was produced.
-
What is the current method for using Amazon Echo through the UDI Portal?
stusviews replied to ScottAvery's topic in UD Portal
Michel suggested instead of saying, "turn on device", say, "turn device on." But I believe that increases reliability. It may not correct not finding the device. -
What is the current method for using Amazon Echo through the UDI Portal?
stusviews replied to ScottAvery's topic in UD Portal
Each time you add or change a "Spoken" name, you need to tell Alexa to ask Izzy (or ask Alexa to tell Izzy) to refresh devices. BTW, I've never gotten any device to respond to a name that includes "computer," for example, computer, computer light, computer room, computer room light, etc. Others have reported success with that word. -
You really need to observe only one pair of devices showing the correct response consistently to achieve successful bridging. Additional dual-band devices serve to increase reliability and range of the Insteon signal.
-
Have you ensured that the opposite legs of the split, single-phase electric supply are bridged using the 4-tap/beacon test?
-
When you replace a wired device you don't need to name it at all. The replacement procedure will 1) give the new device the replaced device's name, 2) replace the old links and scenes with identical new links and scenes and 3) assign the new device to programs that referred to the old device. After the replacement is complete the ISY Administrative Console will close. When you restart, everything will appear as it was, but the replaced device will have the new Insteon ID. That's the only way you'll be able to see the change. You can then drag the replacement to its original folder.
-
It's best to copy and paste the actual program(s).
-
You do NOT need to add a new device in order to initiate a "Replace with." You do need to remove the device from any folder it may be in. The replace option is not available if the device is in a folder.
-
Bad idea. You may be placing an undue load on the neutral wire (e.g., as a return for two circuits on the same leg of the split, single-phase electric supply). The correct procedure is to bridge the opposite legs by installing at least two dual-band devices, one on each leg as indicated by the 4-tap/beacon test.