larryllix

Yup, battery saver. It is supposed to last 10 years.

To find out the easier way do this. Adjust the light level number in the MS. Point the MS into a space for the light sensor to test for at least 3 seconds. Tap the link button seven times quickly. Watch the MS device page in admin console. This method eliminates the 3-5 minute delay on the sensor for calibrating/proving the adjustment.

No custom names here, not for the wakeup phrase. Only 'echo', 'alexa', 'computer', and 'amazon' now. Rethinking this...., I guess they are using the nickname for the other device, 'Tall Echo', 'White Dot', and 'Black Dot', aren't going to be satisfactory then.

I guess this means custom names for our Echoes are finally hapenning, too.

I tried the sensitivity lowering jumper for a while on one ofmine but it eemed like it delayed longer before sending the On signal too. I figured they may have just damped the response to be less sensitive to light change "blips" and took it out again. Very hard to tell when you test it, approaching. Was it just delayed or really didn't see you until you were closer?

Thanks Jimbo. I didn;t know they had changed. Mine are all purchased within a few years and the last two, within a year(ish) and they all need to still be tapped to reset. IIRC my latest is rev2.3 4314...hmmm... time flies! I do have one that will send Wet ON and Off depending how long the tap is... That's dangerous, worrying about whether I will have to reset everything again when I attempt a reset .

Now you're cooking with ISY! Personally I would have used 12:01 AM to 11:59 PM just an indicator the times are all inclusive for when you look at your program a year from now and think... .... WTF was I doing here? What is the significance of those exact times? Just me. Good on ya' mate!

The usual process for the Insteon Leak detectors is:- the Wet ON and Dry Off signals are sent upon feeling water. - the Dry On and Wet Off signals are sent upon the user tapping the button on the LD. There is no automatic "clearing" of the alarm condition. Therefore, if a clearing operation is not done, there is no new change of status to be detected again. ..."If you don't reload the gun, it won't shoot"

Not a problem. We've all been there! That's what the forum is for.

You select the variable from the pulldown list and click the button to insert it. XXX and YYY will be the variable page number and the variable number on that page.

Your variable should look like the other nodes you inserted into the email. Use the same button at the bottom to generate the code. ${var.xxx.yy)

V5.0.10 is being called alpha. I do not have any Zwave (the newer implementation in v5) and I see no problems with it. In fact I have used full release versions from other equipment that have many more bugs. If you jump to v5 early in the game you will never appreciate not having abilities to write device analogue values to variables, use "repeat while" conditional loops, and more. I have been using it for two years and don;t know what I would be missing, except for wondering why people sound so crippled with v4 problems. For now the double time frame should do your trick, though, all in one program, too.

Your time frame is from May 1 to Oct 31 if it is a weekday, all inclusive. One way would be to double up your time frame filter. Leave what you have there and add into your If section. AND from 1:01 PM ....To 6:59 PM (same day) Note the times are inside the original time frame so no race occurs with one being enabled before the other is ready. V5.0.10 has much better ways of doing this by using the ISY clock features available. If the last line to stop a program is itself, it is not required and serves no purpose.

I have 340 programs, I control multiple heating stats, hRV, record oeprations inside ISY, security, and lighting 297 Integer variables, I use banks of them for constants 90 State variables, try to keep them to a minimum for CPU load 50 Network resources, mostly for RGBW LEDs and bulbs 39 Notifications 15 Scenes, I avoid scenes as much as possibe. I don't see the point and I believe in ALL ON or ALL OFF phantom events, rather they are phantom Scene triggers. ALL ON/OFFs do not dim and scenes do not record in ISY.

I think Michel needs to get involved with that one. UDI will probably want to know also, as it may be an unfound bug yet.

I have never seen that, but perhaps a failing PLM?I don't know if that would indicate that ISY has lost it's links for the device (no Restore). Need Michel on that one. I never ran any v4.5 firmware. I advanced as soon as I could and don't know why it even exists anymore.

Yes.

If you factory reset the device then all links are gone, even the ones to ISY. When you do a restore any link that ISY knows about will be written. Without any link to ISY, ISY will not listen to the remote device and IIRC the remote device will not send anything to ISY. Sent from my SGH-I257M using Tapatalk

IIRC you never need to delete or re-add a devce to factory reset. Factory reset any device, and the restore it from admin console. (While in linking mode if a battery device). It's really easy and quick.

Did you factory reset the device and then try restore?

What kind of range and battery life do you get from them?

Thanks @ B - no I didn't...corrected. My random scene activations did not seem to be based on my usage without a timer but according to the blamed suspected problems and watching event logs, it can bog down the Insteon comm pretty badly. It may turn out that too many Insteon devices in one box may be a bad thing for Insteon signal cramming. In the end, a wait 2 seconds, is never noticed here, and real cheap to implement. My random scene activations seemed to disappear after Wait insertions, but still, without analysis equipment mine were based on a run amuck OnOff module sending it out on normal non-scene ISY controls. ISY reported errors and the scene activation was simultaneous +/- 1 minute, each occurence. Too much off-topic though.

Welcome to the UDI forums! You have an ISY. You can easily write a program with all the separte light statuses ORed togther and control the KPL via a scene to control it. I would use a few second (Wait 2 seconds) delay timer though, in your program, since sending immediate responses to KPLs and some other compound devices may be related to causing the Insteon device ALL ON phenomenum. The delay will not likely be noticeable and may save you some headaches down the road. If ...status of Light A is On ...OR ...status of Light B is On ...OR ...status of Light C is On ...OR ...status of Light D is On Then ....Wait 2 seconds .....set .KPL.button.A.scene On Else ....Wait 2 seconds ....set KPL.button.A.scene Off

Exactly. The paddle action sends the control from the manual paddle action, and when the dimmer electronics change, the comm circuits send the new status of the dimmer Of course it's all the same electronics, inside the Switchlinc case but two different sensing sources, the status being another result of the manual or remote control of the dimmer. Sent from my SGH-I257M using Tapatalk

Control is sent from the keypad/ toggle/paddle. Status is sent from the dimmer or relay changing state. Sent from my SGH-I257M using Tapatalk