larryllix

In view of the frequent complaints I see here about the Insteon motion sensor, model 2842-222, I devised this program to monitor my MS units a little closer. Hopefully this will work to detect general failures, as well as low batteries, with improved reliability from just detecting the LowBatt signal that seems to get missed by others. I have not experience that yet. I hope the program should be self explanatory. - I have reversed the usual logic for the program name to make it less human confusing for Mobilinc viewing etc. - $MS_Battery_Status is a State variable that triggers notifications, - $cUTILITY_ROOM is one of a set of defined constants for passing room definitions and used by notification above, - The heartbeat style check-in is an easy logic for me but this negative "is not" tests my old logic brain, Anybody foresee problems with this?? Program MudRm MS.OK --------------------------------- If Control 'Mudroom / Motion.MudRm / LowBatt.MudRm' is not switched On Or Control 'Mudroom / Motion.MudRm / LowBatt.MudRm' is switched Off Or Control 'Mudroom / Motion.MudRm' is switched On Or Control 'Mudroom / Motion.MudRm / Dark.MudRm' is switched On Or Control 'Mudroom / Motion.MudRm / Dark.MudRm' is switched Off Then Wait 26 hours Run Program 'MudRm MS.OK' (Else Path) Else Wait 5 minutes $MS_Battery_Status = $cUTILITY_ROOM -------------------- Thanks!

We had many systems run on RF signals in our Electrical Energy Grid stations but the controls had 360 degree feedback from finish back to start so that measures could be taken if the control was not successful. Retries could be done and even right down to a Lineman taking a truck to the remote location and operating the device by hand. This was for manual operations though. Some cross province protection systems are operated by radio signals but always have duplicate or backup systems in place for a second line of defence. Inside a station only hard wiring was used even with a complete comm bus (Ethernet, RS485 or RS232) for information paralleling it.

More research is required but a few years ago there was no video decoding hardware and the first time a new method comes out (that never happens more than every month) the video hardware is obsolete again. It will probably be CPU only for a few more years yet.

Here is a way some use to cancel the whole thing without leaving the light on. If Status Kitchen Light is On And Status Laundry Light is On And Status Bathroom Light is On Then Set Living Room Light On Wait 30 minutes Run This_Program (else) Else Set Living Room Light Off

The first program can still re-initiate the second program's then will redo everything. IMHO this would be better. Use the "one and only one" technique. Program 1 --------------- If trigger event Then Run Program 2 Else --- Program 2 (disabled) -------------- If -- Then Disable Program 1 do stuff..... Enable Program 1 Else --

Have to second that one. SWMBO will not like it when you use the family TV for a monitor to setup the HA. Two RPis would probably be cheaper and you wouldn't listen to a computer fan while watching a quiet movie. I have an Antec case media PC running XBMC. It has two very large and quiet fans running on a slow setting. Video hardware is usually useless for media PC's. Good for 3D rendering but not video decoding. The encoding has always been in such a state of flux that hardware had never supported video decoding methods. Multiple cores never really helped XBMC either. You either watch a movie or run the GUI and access databases with the same core. In the past most experienced users agreed that one 2.0 GHz core was necessary for XBMC to run without any jitters on a Windows system. RPi is breaking this rule somewhat with it's 700MHz core running on a Unix-like OS.

Add your wants into one of the many existing threads requesting the same thing. It has been requested many times and promised as coming for almost a year that I have participated.

Some thoughts without completely understanding your programs. For the motion detectors in my bedrooms I use scenes to turn the lamps on and off. The advantage to this is I can change the brightness settings and the ramp speeds twice per day (or more if desired) so that the responding units respond quickly when motion is detected. This has worked well and the response is much quicker. The bathroom lights could be ramped on very slowly (using above technique) for quick-on blindness prevention while the shower light is turned on slowly, in the middle of the night while ramped very quickly during the day. Lights can be brought up to medium level and if motions is seen again, indicating you are extending your stay in the bathroom, brighten the lights to 100% for mirror usage. This logic gets tricky. A one minute warning by dimming the shower light slightly (and back?), could be used so that the showeree knows to cause some motion, resetting the timer, or he/she will be in the dark soon. This may also be used as a self-timer to encourage shorter showers or pickup time is approaching. The SwitchLinc dimming command could be used to provide preset dimming levels for bath soaking mood lighting.

Have your program stuff the current time from your program, every update into the boot-up copy of a variable.. say $LastTimeRecorded. This is available with the "Init to" command. When the ISY reboots have a program with it's "Run at startup" flag set that sends a notification to your email/SMS with the current time and the saved $LastTimeRecordedand let the receiver figure out the duration. Once the notification is complete set an $Initialised variable as a flag that allows your time program to resume recording the time. It will be out of sync with real time. Perhaps several resync times per day could reduce the error times after a power failure.

Perhaps for ALL battery operated devices we need detectors like this? If Control 'Gathering Room / Motion.GathRm' is switched On Or Control 'Gathering Room / Dark.GathRm' is switched On Or Control 'Gathering Room / Dark.GathRm' is switched Off Then Wait 26 hours $MS_Battery_Status = $cGATHERING_ROOM Else - No Actions - (To add one, press 'Action') andb $MS_Battery_Status ${var.2.14} is a State variable so the following programme should event trigger. If $MS_Battery_Status is not 0 Then Wait 5 seconds Send Notification to 'Text Larry' content 'MS Battery Low' Wait 5 seconds Send Notification to 'eMail Larry' content 'MS Battery Low' Wait 12 hours Send Notification to 'Text Larry' content 'MS Battery Low' Wait 5 seconds Send Notification to 'eMail Larry' content 'MS Battery Low' Wait 30 minutes Run Program 'MS Battery Low' (Else Path) Else $MS_Battery_Status = 0 Note $cGATHERING_ROOM is a constant defined by myself and is further used in the notification Alert! MS Battery Low ${sys.date} @${sys.time24} Detected in room ${var.2.14}. 10=RecRm,12=AftBr,13=EveBr 14=Libr,16=Util,19=LLand 20=GathRm,21=MBR,29=MudRm 30=Shop

It's just too bad that Dallas didn't make anything standard for these cute 1wire sensors so that we could plug in any new 1wire device that comes along and a standard device-control-block would just assume the position/data. Now every driver writer supporter has to incorporate a huge library of profiles for all these devices. Then again the complete openness of the beast is probably what makes it so capable and powerful. Eg. EPROM memory at the end a 1wire?

That's the big problem with UDI. They want to fix everything to work better, just like the rest of the crowd here. I don't know this is an ISY problem but.... Thanks.

Thanks. This sounds very possible if a speed typist doesn't use it. Of course this would be dependant on the Insteon congestion at the time I would think. I noticed in the video that the KeyPad lights stayed on indicating a record of each button pressed. I assume this is controllable so this wouldn't happen if desired? As a note: I have a few wireless keypads and the toggle, four unit, eight unit thing never made any sense. After trying different modes I could not detect any differences. Perhaps some study on that would push that into my brain more...assuming the units would similarly. (I know ISY can set the LEDs on and beeper on all it wants but there is none on the wireless ones)

Mostly in systems built 1995-2007. It started with these guys and has spread to most of the other brands now. http://www.classactionsnews.com/settlements/zurn-pex-f1807-fittings-litigation-settlement "Problems found to date are with the following products: IPEX Inc – sold as Kitec, PlumbBetter, IPEX, AQUA, WARMRITE, Kitex XPA, AmbioComfort, XPA, KERR Controls, Plomberie Amelioree ZURN PEX – sold as QPex (may not be sold in Canada) Uponer Inc – sold as Plasco Plumb-PEX, P Pex, MB Pex These companies are all currently involved in lawsuits."

Thanks guys! That is not exactly what I had in mind but interesting. There is no sequence required and the key sequence speed would not be quite as particular. I don't have a KeyPad unit to experiment with this as I have never really had an application for one before.

Do they make rockers so that the on/off button appear as one larger button like the four unit you mentioned?

Has anybody ever used a KeyPad as a combination input or Does anybody know how fast the KeyPad can send a sequence of key presses to the ISY? I am looking for a method of changing ISY house modes via program recognition of maybe a two or three keypress length sequence. Would the user have to press the sequence very slowly? Any other foreseen problems? Thoughts?

The actual events are really hard to track down and there are rumours and guesses everywhere on forums. From what I can make out some cheap brands of fittings had too much zinc in the brass and the zinc leaches out of the brass causing the fitting to collapse eventually. The best report I heard was that the "zinc accumulates in the PEX, causing a blockage and the pressure builds up until the PEX pipe bursts." I did notice most of the case studies had PEX-AL-PEX crimped with various rings, a complete no-no to crush the aluminum strength layer.

That thing has a 1wire port on it??? Does it work? Properly? Is it a hardware interface? What does it do with the data? Could this be a heating system designer's dream?

hmmmmmm... hard to test fro calibration. Put in the freezer and when you take out you should get a range of temperature reports but how would you know what the actual temperature is? ahhhh... brainstorm! Get a Styrofoam cooler for $1.98. Put the thermostat in the freezer for a few hours with a few bottles of water. Put them all into the cooler Poke a calibrating alcohol thermometer through the Styrofoam wall and record real vs. reading temperature on the ISY at of reading.. Establish any linearity relationship. There may be a pattern or mathematical relationship. We need an ISY995i with a USB port and driver install loader. ... Think of the possibilities for UDI. $19.95 per driver?

I believe thermal shock can separate the PEX from the concrete slab and then thermal contact becomes a problem for spotty heat zones. With PEX embedded in wood it shouldn't be as much of a problem. Are you aware of the de-zincification of brass PEX fittings? I believe the class-action suit is still ongoing for cashbacks. Looks for white powder on your fittings.

Anti-scalding and, lest we forget those that gave their lives, anti-legionella bacteria.

Speaking of flushing your buffers.

Racoon in your garage? Your off cycle always lasts about 3 seconds. Are you sure you don't have the darkness sensor being used?

After they turn it off. My kids previously told their friends "If you don't turn it on then don't turn it off". But now we go into our friends house and stand in the middle of the room thinking "How pathetic! The lights don't go on. What would I do if was carrying something with two hands?"