BCreekDave

MobiLinc is I think the most popular. Sent from my iPhone using Tapatalk

Bump. Surprised no one has tried this. Sent from my iPhone using Tapatalk

Any of these items still for sale? Sent from my iPhone using Tapatalk

Agreed. Just didn't know if the original problem was endemic to the design or the cheap components. If design the problem may reoccur but just later. I repaired mine 3 years ago and it's going strong. Original lasted 3 years I think. Sent from my iPhone using Tapatalk

Is anybody tracking if REPAIRED PLM's are starting to fail? This thread is a few years old now, so we may start seeing them. Maybe this is a permanent fix? Sent from my iPhone using Tapatalk

Nothing in home automation seems very stable. No wonder most folks who are interested won't take the plunge. http://www.cepro.com/article/sigma_designs_owner_of_z_wave_home_automation_tech_ponders_sale_or_divestme Sent from my iPhone using Tapatalk

I've got analog sensors wired into an EZIO 2x4 module that auto on-off the fan. Works rock solid for two years running. The relay wall switch for the fan can override for 15 (normal) or 30 (fast on) minute intervals. Sent from my iPhone using Tapatalk

Has anybody had s self repaired PLM fail yet? The repairs have been out there for two years now? I would think some would have failed by now. Sent from my iPhone using Tapatalk

I know this is controversial, but I think an unattended garage door can be made to close safely. I use a combination of motion sensors, signage, flashing the garage lights and and an Elk 124 voice module to issue warnings of the impending door close along with the standard door threshold optic sensors and careful adjustment of the opener close force. It also sends me a text message to my phone and I can then use Mobilinc to view the camera to verify the everything is clear. Once a month I verify that everything is working properly. Just like technology will eventually allow us to have driverless cars, a faceted approach to home automation can allow safe operation of entrance systems. Sent from my iPhone using Tapatalk

I think what Brian was saying is that the EZIO device uses the power supply board that is the same as the one that often fails after two years in the 2413 PLM. When it does this in the 2413, the link table in the 2413 is corrupted. When it happens in the EZIO device, it may stop sending status updates to the ISY. Unfortunately Smarthome used this failure prone power supply board in many devices Sent from my iPhone using Tapatalk

Better hurry. If smarthome catches wind of this I can see the blank buttons going to 50$. Sent from using Tapatalk

Thank you very much for the help. Sent from using Tapatalk

Does anyone happen to know what the minimum setpoint is on the 2441TH? I am investigating the possibility of installing one in a garage where the normal winter setpoint will be 35 to 40F. I am thinking of when the garage door is open via the IOlinc, I can with the ISY disable the furnace. Thanks, dave

It sounds like you have found a good solution so the following is probably moot at this point, but if others are interested In addition to the other solutions presented here, there is also this: http://smartenit.com/product/ezeye/ which is used in conjunction with one of these: http://smartenit.com/product/ezio4o/. The possible advantage could be its calibration to "Human Eye Accuracy" which I think means it is tuned to the range of wavelengths that the human eye sees, or it could be "sales-speak". Again, as others have mentioned, the ISY can only read discrete values. In this case the analog to digital conversion is done in the ezio4o module.

I have the same situation but in my case the root cause was that the switch I was air gapping was the slave (non-load controller) in a 3 way setup. When I air gapped the load switch everything functioned as expected. Sent from using Tapatalk

Has the video ever been made available or is this thread basically a non-issue? For a single family type of home, it seems like with the limited RF range of insteon as an attack point it would take someone sitting right outside your home trying to gain entry. For an apartment dweller, maybe that's more of a concern. Or did I miss the point?

Wellll...if you are feeling adventurous you could start with this: http://www.ebay.com/itm/Analog-Sound-Sensor-Board-Microphone-Mic-Controller-For-Aduino-/151535155655?hash=item234832f9c7:g:TQcAAOSwc3ZUo0Bd and a Smartenit EZIO 2X4 to power it and sense the signal output. This would "listen" for the chime-bell when the cycle is complete. Usually these are pretty loud. The nice thing is that it's all external (no messing with the existing washer-dryer wiring) Besides the EZIO device cost (~$105.00) it is cheap. The challenge would be to tune it for the chime. You would want to locate it as close to wherever the sound comes out of the washer. The downside would be possible false-positives from other sounds in the area. You could get creative with the isy to "arm" it whenever the washer is running by a using one of the other inputs on the EZIO. If you happen to have a sound meter you can benchmark the chime sound to see how much louder it is than other normal sounds in the area to see if this is viable. The EZIO device has other inputs and outputs that can be used for other things also. I use one for checking humidity in bathrooms.

I want to post a follow up on this. Thinking the issue was my particular implementation with the door sense switch monitoring the door open rather than the typical door close position, I moved the switch to sense the door close, which also I think is intrinsically safer, given the limitation of the single input on the iolinc. This did not result in the desired solution. While the system worked triggering from Mobilinc or from the keypadlinc or directly from the PC via the isy admin console, triggering the door from the manual push button or the in-car button was not reflected in a status change on the keypadlinc button. Further investigation showed that when I replaced the caps in the 2413s, the link tables became corrupted and several devices had to be rebuilt. One of these was the keypadlinc. Looking at the button function for the garage door showed it to be missing as a responder for the scene for the garage door, in my install this scene is Garagedoormain. Once I rebuilt this link, than everything is back to working OK. Thanks for the help from oberkc and Xathros.

I agree that trying to trace through the code is tedious and perhaps not the best plan of attack. Unless the author (Jimbo) or someone else has slayed this exact dragon in the past. It may very well be a timing issue. I am going to work on my setup to match the switch function to switch closed when the door is closed. This is the way that the program was originally intended, and may be more intrinsically safe. The "i" and "s" are in fact indicators of integer and state variable. I have confirmed that the commands are getting through. I can see the state and integer variables change, but it is hard to tell if they are changing at the right time. I am also going to disable the lights. While I can unhook the door, my neighbors must think I am nuts with the lights going on and off all the time while I debug. I will work on it on Saturday. Too many other projects going on before the weather turns. Thanks everyone for the suggestions. I am using this as always as a learning experience. By the way oberkc, hello from Beavercreek. I live close to 675. If you are driving by, look for the garage lights flashing!

Yes, it is a long program. I think there is a lot of error checking with state and integer variables to verify that the door achieved the desired result and if it didn't, to be able to notify the user. There are sub-programs for power outage etc. I tend to like this for something like and entry door where security and safety is an issue. This along with a well placed camera.

Xathros Code as follows: One other note. I have the keypadlinc button setup as a controller and responder for a scene "GaragedoorMain" The iolinc is set as "Momentary B" with "LED on TX" checked. No other options checked. I have a momentary hold time of 0.2 seconds which seems to work OK. =================================================================================== Main Garage Door - [ID 0046][Parent 0024] Folder Conditions for 'Main Garage Door' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Allow the programs in this folder to run. ----------------------------------------------------------------------------------- 000 ButtonOff - [ID 002E][Parent 0046] If $i.GDM_Dontwatch is 0 And Status 'A Mud Room Entry Keypad / B OpenClose Garage Door (GDM)' is Off Then $i.GDM_Requestedstatus = 0 $s.GDM = 1 Else - No Actions - (To add one, press 'Action') Function: When the button state is changed, remember if it was changed to on or off and start up the state machine. Details: All the '000' programs monitor the status of the KPL that is tied to the GDM Scene. We only have to monitor one of them, since when the scene is changed by any of KPL or Mobilinc it will affect all of them. The main state variable for all GDM programs is s.GDM, which tells us where in this state machine we are. We do not monitor that state variable in the 000 programs because other programs within this state machine will toggle the scene on and off, which in turn changes the button state, so while the state machine is running we ignore running the 000 programs using the i.GDM_DontWatch integer variable. The i.GDM_RequestedStatus stores if the request was to close (0) or open (1). from :http://forum.universal-devices.com/topic/11099-garage-door-control-with-kpl-and-mobilinc/page-3#entry152166 ----------------------------------------------------------------------------------- 000 ButtonOn - [ID 002D][Parent 0046] If $i.GDM_Dontwatch is 0 And Status 'A Mud Room Entry Keypad / B OpenClose Garage Door (GDM)' is not Off Then $i.GDM_Requestedstatus = 1 $s.GDM = 1 Else - No Actions - (To add one, press 'Action') See '000 ButtonOff' for a description. ----------------------------------------------------------------------------------- 001 DoorStateFalse - [ID 002F][Parent 0046] If $s.GDM is 1 And ( ( $i.GDM_Requestedstatus is 0 And Status 'Garage Main Door IOLINC-Senso' is On ) Or ( $i.GDM_Requestedstatus is 1 And Status 'Garage Main Door IOLINC-Senso' is Off ) ) Then $s.GDM += 1 Else - No Actions - (To add one, press 'Action') Function: We have just entered the state machine from a KPL button changing state. If the requested door status does not match the door sensor status then go to the next state. Info: It seems that we could tie the check of the sensor status into the 000 Button* states, but that does not work correctly because it would trigger the 000 state when the sensor status changes but the button status has not changed yet. This is because I have the sensor as a controller for the GD scene because I want to see the sensor as part of the scene in Mobilinc. ----------------------------------------------------------------------------------- 001 DoorStateTrue - [ID 0030][Parent 0046] If $s.GDM is 1 And ( ( $i.GDM_Requestedstatus is 0 And Status 'Garage Main Door IOLINC-Senso' is Off ) Or ( $i.GDM_Requestedstatus is 1 And Status 'Garage Main Door IOLINC-Senso' is On ) ) Then $s.GDM = 10 Else - No Actions - (To add one, press 'Action') Function: We have just entered the state machine from a KPL button changing state. If the requested door status matches the door sensor status then we are done. Info: See DoorStateFalse for info. ----------------------------------------------------------------------------------- 002 Init - [ID 0031][Parent 0046] If $s.GDM is 2 Then $i.GDM_Dontwatch = 1 $s.GDM_Counter = 10 $s.GDM += 1 Else - No Actions - (To add one, press 'Action') Function: The door was requested to move, so initialize variables used in the state machine and go to the next state. i.GDM_DontWatch: 1=Don't watch the state changes of the KPL's s.GDM_Counter: Loop counter for '002 Loop' program s.GDM: Main state variable, go to state 2 ----------------------------------------------------------------------------------- 002 Trigger - [ID 0032][Parent 0046] If $s.GDM is 2 Then Set 'Garage Main Door IOLINC-Relay' On Else - No Actions - (To add one, press 'Action') Function: The door was requested to move, so trigger it. Note: This could have been done in the Init program, but that delays the flashing of the scene for longer than I like... The IOLinc relay is in Momentary B mode so it is triggered by both on and off. I think this is important since I don't turn it off, although I could, but I don't care what state the relay is in. ----------------------------------------------------------------------------------- 003 DoorStatusClosed - [ID 0033][Parent 0046] If $s.GDM is 3 And $i.GDM_Requestedstatus is 0 And Status 'Garage Main Door IOLINC-Senso' is On Then Set Scene 'GarageDoorMain' Off $s.GDM = 10 Else - No Actions - (To add one, press 'Action') Function: While in the state and the door was requested to close, when the door is closed we are done. Make sure the scene is off and go to the cleanup state. Note: Logic "And Status" inverted due to my switch location ----------------------------------------------------------------------------------- 003 DoorStatusOpen - [ID 0034][Parent 0046] If $s.GDM is 3 And $i.GDM_Requestedstatus is 1 And Status 'Garage Main Door IOLINC-Senso' is Off Then Set Scene 'GarageDoorMain' On $s.GDM = 10 Enable Program 'Garage Lights SubRoutine' Else - No Actions - (To add one, press 'Action') See DoorStatusClosed for a description. ----------------------------------------------------------------------------------- 003 Loop - [ID 0035][Parent 0046] If $s.GDM is 3 And $s.GDM_Counter > 0 Then Set Scene 'GarageDoorMain' Off Wait 1 second Set Scene 'GarageDoorMain' On Wait 1 second $s.GDM_Counter -= 1 Else - No Actions - (To add one, press 'Action') Function: Toggle the scene on and off so the KPL buttons and Mobilinc icon change state. This gives visual feedback that we are waiting for the door. Decrement the counter s.GDM_Counter each time, which tracks our timeout function, and causes this program to restart until the counter reaches zero. We could have made the counter be the s.GDM... Oh well... (I wish the 'Wait' could use a variable!) ----------------------------------------------------------------------------------- 003 Timeout - [ID 0036][Parent 0046] If $s.GDM_Counter is 0 And $s.GDM is 3 Then $s.GDM += 1 Else - No Actions - (To add one, press 'Action') Function: If the s.GDM_Counter has reached zero while we are in the waiting state, then the door did not reach the state that was requested! So go into state 3 which handles the failures. (I had a reason for not handling them in this state, but can't remember why...) ----------------------------------------------------------------------------------- 004 FailedClose - [ID 0037][Parent 0046] If $s.GDM is 4 And $i.GDM_Requestedstatus is 0 Then Set Scene 'GarageDoorMain' On Send Notification to 'Daves MMS Text' content 'Garage Door Failed to Close' $s.GDM = 10 Else - No Actions - (To add one, press 'Action') Function: There was a request to close the door, but we timed out waiting. Make sure the scene is on since this state machine toggles the scene we are not sure where it ended up. Send a notification to tell us that there was a problem! Go to state 10 which does the cleanup. Note: I wonder if there could be a race condition... If the door sensor status happens to change after TimeOut and before this is triggered? But I really don't think that will happen... ----------------------------------------------------------------------------------- 004 FailedOpen - [ID 0038][Parent 0046] If $s.GDM is 4 And $i.GDM_Requestedstatus is 1 Then Set Scene 'GarageDoorMain' On Send Notification to 'Daves MMS Text' content 'Garage Door Failed to Open' $s.GDM = 10 Else - No Actions - (To add one, press 'Action') See FailedClose for a description. ----------------------------------------------------------------------------------- 005 GaragedoorPowerOutage - [ID 003A][Parent 0046] If $i.GDM_Dontwatch is -1 And ( Status 'A Mud Room Entry Keypad / B OpenClose Garage Door (GDM)' is Off Or Status 'A Mud Room Entry Keypad / B OpenClose Garage Door (GDM)' is 100% ) Then $s.GDM = 10 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- 010 GarageDoorDone - [ID 0039][Parent 0046] If $s.GDM is 10 Then $i.GDM_Dontwatch = 0 $s.GDM = 0 $i.GDM_Dontwatch Init To -1 Else - No Actions - (To add one, press 'Action') State machine is all done so start watching again.

Hi Xathros, Due to the quantity and length of these programs, can you suggest the best method of posting? I somethines use the "Copy to Clipboard" or just the "Export" function. Thanks dave

Thanks for the quick reply, Xathros. I tried again the restore device but it didn't help. I had tried this at least twice already, but wanted to be sure. For just a bit more info, the keypadlinc does not update when the in-car button is used either. This is not a surprise, but I just tried it to verify. I agree about the position of the door. I am looking into changing either the placement of the chain-cam or going to the EZIO unit. Dave

I have had this running for several months now and have only one small problem. Perhaps it is my particular implementation, but the keypadlinc button is not updating its state when the original manual push button is used. This button is mounted in the garage on the wall and is therefore the most convenient method of closing-opening the door when I am in the garage. I think based on this statement in the original post by the author this function was intended: "Of course, it also properly handles everything when the door is manually opened or closed..." It seems like it may have at one time worked for me, but I had to re-cap my PLM a month or so ago and some switches got kind of flaky afterward and the link table had to be somewhat re-built. I am not sure if it did ever work and I have rebuilt the iolinc and keypadlinc (deleted and replaced) and the PLM link table shows them to be OK. My install is maybe somewhat different in that I am using a limit switch (normally open contacts) mounted on top of the opener that is tripped by a cam-block attached to the openers chain near the trolley. Functionally, I am sensing when the door is open instead of the typical magnetic switch which is usually mounted near the floor and senses when the door is closed. I have changed the program slightly (003 Doorstatusclosed -> sensor on and 003 Doorstatusopen ->sensor off) to compensate for this. Was this the original intention of the program? If so, can you point me in the direction of how to debug this? It may be a timing issue as my method does not immediately update the door open until it is fully open due to the switch location. The door has to be fully open for the limit switch to change states. Conversely, my install does immediately sense when the door is closing. I can't say I am really happy about using the IOlinc in this type of install. It seems that due to only having one input, the doors position can only be positively sensed either fully open or fully shut. I have a EZIO 2x4 that I am thinking about re-purposing due to this. Thanks for any help anyone can provide. Dave

I don't have much experience with strobes. Do they thermally like being held on for 4 seconds? Sent from using Tapatalk