larryllix

You have to scroll to bottom of all your devices and click the delete all (no exact name) before doing a further discovery in the Alexa app or it will just keep accumulating names for the same element. Amazon likes to hide things.

Mine appeared to be a "run-away program" inside an OnOff module that was sending out a bad Scene On code, after ISY would switch it on or off. I don't believe Scenes send out status changes from devices so there is no logging of status changes. This drove me crazy for months changing and turning on certain lights at random. I could query the affected units and find exact dimming levels. Then I recognised the pattern as a scene I created. ISY had no awareness of the event or levels. I still use the module to control my humidifier. Ocasionally when ISY would cycle it, the ISY log would show a bad response. After unplugging the module and then plugging it back in, it hasn't done it again since last fall. It seems it would send out a totally unrelated Scene On code, instead of an ACK. PLM was not involved with this. Insteon modules contain CPUs running code and can go into runaway loops just like any other software.

This is one of the confusing logic puzzles ISY has. Took me awhile to absorb this one. The best example I have is to use a SwitchLinc Switch Status has two states = On/ Off. This is the status of the electronic switch controlling the light. Along comes the switch handle with four states. Tapped up, Not tapped Up, tapped down, and Not tapped down = think two devices for just the paddle. So now the tap up detection = ISY "Control switch Switched On" signal has two states. Happenning now or not happenning. Also the tap down detection = ISY "Control switch Switched Off" signal has two states. Happenning now or not happenning. When an event like a SwitchLinc paddle is tapped down , the ISY engine scans all the programs to see who cares. If ....Control device is switched Off would get evaluated by the ISY engine finding it true and running Then but ....Control device is NOT switched Off, would get evaluated by the ISY engine finding it False and running the Else section. Let's see if I can confuse you further another way. The line can never be true. If the paddle is not tapped down, the program logic line, if it is ever tested, will always be False When the paddle is tapped down, the program logic line will be tested and the Not will make it False.

Turn On and Turn Off run the same program. On runs Then section. Off runs the Else section. If ....--- = nothing required for Echo vocals Then ....turn light On ....Wait 6 hours = lest yee forget. ....turn light Off Else ...turn light Off You can turn on scenes or use direct commands for any quantity of devices. Slight ramp rates cover up different reponse times, to the human eye.

As per smokegrub's program..just set a timer to notify you and let the control/switched event of the pump detection keep resetting the timer. If ....control pump is switched off (status doesn't work well here) AND ....control pump is NOT switched on (cancel Then running = off is coming) Then ....Wait 120 minutes = offtime x 2 (maybe missed one signal and eiminate nuisance notifications) ....send notification to you Else ....--- You also may want another reboot program to initiate this in case of a power failure. Enabled to run at power up. If ...-- Then ....Run (then) program above Else ...---

I have programs installed to record any leak detector that triggers in a single Integer variable list. I have to manually clear it from the admin console. I had a few basement floods (minor) and you will be inside the admin console to see what happened. It's the only way to see if it actually reset. OTOH: I developed a policy that I haven't completely implemented. anything that notifies of a problem has to notify when the problem goes away.

I don't have a float tube in my current brine tank. I forgot about those. Perhaps a very strong magnet (coated with epoxy or other salt resistant material) could trigger a reed sensor outside the tank in a safer environment. On second thought an Insteon Garage Door Kit would probably work well. The supplied sensors can pick up the magnet from many inches away, and the ioLink comes with it and wire making it everything you would need.

In the few softeners I have owned the brine tank salt levels are always higher then the liquid levels, unless the brine tank is almost empty of salts. I converted my old one to an iron filter by dumping out the resin and adding a different granular material and flushing it with some powerful, toxic, purple solution every so often. It did spring a leak at the bottom and I had to get rid of it after about 20 years of the combined functions.

Hey Teken!! Ready for some summer at the north pole? You may have misunderstood the request (Or maybe I did?). OP is looking to detect softener regeneration by brine or water flow in a totally mechanical water softener, not when low on salt. Somebody needs to design an inside pipe impeller, with magnetic induction pulse output, we could use for flow rates and/or just flow period.

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.