larryllix

A scene is a "preset" to eliminate much of the data traffic as well as some of the time delay to turn multiple devices on to a preset level and ramping speed. If we want custom, non-preset, one time settings, for a device we just issue a custom Insteon command to set that device to that level. ISY even goes so far as to make the Scene presets modifiable by injecting special communications on a pre-thought basis. It makes no sense to have a custom preset setting when we already have all the options. Just create another preset or scene and use it. Each devices can hold what?....250 scenes.

I believe one of the techniques was to just impersonate an existing link. An increase in initial contact security would be worthless. As long as the communications are unscrambled this problem will never go away without redesigning the whole Insteon protocol and tossing all devices. One of the stronger security items already existing may be that Insteon is synced with the 60Hz. I am not sure how important this is to the originator of the command signal. An Insteon modem running off a 12vdc car battery, parked outside your house, may not be able to sync with you existing house system 60Hz without some fairly sophisticated equipment to lock in and remember the phasing associated with monitored signals.

Development of an Insteon monitor with minimal hardware would be an awesome project! Obviously some hardware to input RF or clean up powerline signals would be needed. It would nice to observe some of this traffic from another vantage point possibly proving some other problems Insteon may have created. I did this with X10 and it allowed me to troubleshoot some networking problems much easier. I also found old modules I had forgotten I had plugged in.

http defaults to port 80 and is typical for ISY internally to your LAN. In the Admin Console look under Help|About DDNS requires a DDNS provider service. This sends updates of any changes in your external ISP IP address to the DDNS provider. Tthen you should be able to remotely access your ISY, using the URL they issue you, through their IP/port conversion to your router and it's IP/port conversion to your ISY.

If Or Control 'Door Sensors / Man Cave Door Sensor' is switched On Then Set '90" Flat Screen' to 'Off' Set '900W 7.1 Channel Amp' to 'Off' Set 'Massage Chair' to 'Off' Set 'Heating Pad' to 'Off' Set 'RoboVac' to 'On' Wait 1 minutes Set 'ComboDoorLock' to 'On' Set 'ManCave Lights' to 'Off' Set 'Staircase Light' to On Wait 2 minutes Set 'Staircase Light' to 'Off'

Cool! I see you use what appears to be constants also. I denote them with a $c...... prefix for easy reading like this. I also use some programming language style by using all uppercase but it is very abrupt and not sure about that one. $s_RackTemp < $cRackFanTempLimit

Remember we are east of you and will have this installed before you even get out of bed! :)

What is driving the horn? Are your wires intertwined with other wiring?

The switch itself generates six commands. Fast On On Brighten Dim Off Fast Off I use some as multiple scene commands toggling between the two. This is a simplified 'On' for the switch being my most common usage. When a gues turns on what they think is a normal switch they get TV watching mode. Another tap toggles it to Reading Mode, a little brighter in spots. My logic is always up taps or more taps for brighter so it is easily remembered and intuitive. Fast On turns on all my lights White and full brilliance with about 200 watts of LED lighting. It's like a hospital operating room. Fast Off is always a free command that isn't that useful for scene lighting in the room due to the sudden Off and no other lights match that abrupt ramp. If Control 'Dimmer' is 'On' AND $sRoomStateis not $cMODE.TV <---constant variable "$c" using integer variable for easy reading Then Set $sRoomState = $cMODE.TV Set TVWatching scene On Else Set $sRoomState = $cMODE.READING Set ReadingScene On Using the same scene variable I can rotate my coloured lights through and unlimited quantity of colour schemes. Too many can be problem as it takes time to rifle through too many scenes. Note I use a slightly different method to the method shown. I only set the variable to it and have a bank of programs that use the event triggering feature of ISY to actually turn on the scenes. So my Dimmer switch would look something like this .If Control 'Dimmer' is 'Dim' Then Set $sRoomState = $cMODE..MOVIE Set $sRoom.Colour = $cMODE.PARTY1 Else ---- Now two banks of White and Coloured light programs do the scene and dirty work (for Hues and MiLights using Network Resources) Something like this as two examples. If $sRoomState is $cMODE.MOVIE Then set scene MovieScene 'On' Else --- If $sRoom.Colour is $cMODE.RED Then Network resource Hues.All.On Network resource Hues.red Network resource MiLights.red ....... I also have a Mini Remote that duplicates the exact same sequence of button pushes so the style is the same and all controls are available from my easy chair.

I do like the lockout functions that many security schemes use. After three bad passwords a lockout of say 3-5 minutes would stop most trial and error password sniffers. Even my keypad doorlocks use this simple technique. A very common technique the lockout on password failure should be easy for UDI to implement and present very little or no hardship to any user. Three to five minutes would be about right to access your password vault (wife) and confirm your password.

I use my I/OLinc for my back doorbell sound. I set the I/OLinc to intermittent/pulse mode and I don't send an Off command. If I sent a fast series on On and Off commands like that (no Wait in between) no other Insteon signals would get through and the door sensor signals would go unnoticed a good percentage of the time or ISY would respond 10-30 seconds later.

I avoided using my Fast Off as an All Off scene command and used the single tap Off instead. I foresaw this as a problem using only the switch / dimmer My Fast Off is now the trigger to turn on my 13 coloured lights around the room perimeter and turn the white lights off. One Switch / Dimmer controls 15 different lighting scenes. I do not use a KPL and wife picked up how to control all the scenes quite easily. The whole thing has to be based on a guest operating the switch without any training so the Fast Off usage for lights Off was not compatible with that logic anyway.

Just need to add your own "Program 'Time is Up' (If)"

Multiple programs. ISY is an event triggered engine and does not support sequential line code well in this style without confused logic. If Control 'KpIrr A Zone 1' is switched on then Set Scene 'Irrigation Zone 1 Indicator' On Set EZRain 1 - Driop Zone' On Run program2 program2 If $Int_Irrigation_Time = 5 Then Wait 5 min Else Run program3 program3 If $Int_Irrigation_Time = 10 then ......

What unit would the variable specify? Seconds, minutes, hours, days or would the unit be specified separately, as it is now, and only the quantity be a variable? I would like to see all ISY settings using a parsing subroutine that accepts absolute immediate quantities or variables. Pulldown menus for analogue value condition matching would disappear from the whole interface.

I guess I could try this too with a LampLinc output. Probably need an incandescent load not to taint the waveform current or switching profile. Been too busy doing landscaping this summer. Just what I always wanted.

I use all dimmers and no switches for my lighting. I use many LED bulbs and always watch for dimming capability when I purchase them. I do have a few non-dimmable CFL bulbs on Insteon Dimmers and I just don't dim them, using Fast On/Off or only 100% and Off. They have never been a problem for me. Interesting when two wire wave chopping dimmers are used it is very difficult to trigger a triac right at zero crossing. For a three wire device having it's own constantly charged power supply zero-crossing switching is quite possible and common on specialty dimming circuits. Has anybody actually scoped an Insteon Dimmer to see if a piece of the waveform is missing at zero crossings? Insteon devices rely heavily on zero-crossing for timing. I have never noticed the lack of full brilliance on any bulbs on Insteon devices as is seen with more passive dimming devices. OTOH, I mostly use CFL and LED bulbs that could hide that phenomenon due to waveform-peak grabbing power supplies anyway.

Why hack the Insteon signals when you can hack the ISY for a lot more fun? Imagine the cool programs you could set up for a joke! Check the thumbnail pic. http://forum.universal-devices.com/topic/12599-anonymous-hackedattacked-isy/?hl=hacked

Dang! I want it now!! People spend oodles of time attempting to get analogue values into ISY. Autellis, RPi and WebControl, using 1wire sensors, are the common ways to get analogues in.

Ditto on that. I owned two Wink Hubs for a few days and I couldn't make them do anything Talking to their tech support the thing would only interface to other hubs via WiFi and never to any devices at that time despite their claim to multiple hardware interfaces. They went back for the refund. Completely useless, in my world, at that time. Be nice to see more on these advances in action and how they are accomplished.

Thanks Yeah it will be more complicated than that. This fan has no pullchains and the switching is all done in the light junction box hanging below the fan motor. The wall control sending unit is a PITA with it's tiny rubber pushbutton to control the light so we hardly ever use it. I have an MS linked to a bedside lamp that suffices for most of our bedroom traffic and reading using manual overrides from a MiniRemote. Trouble with the Insteon smart HA thing is selling the house later. Now I would have to replace all the original equipment.

Awesome! I agree about the HA not just being remote control. See my post above. This is what I want to accomplish as well. Occupancy detection comes into play as a factor also. Not just your dumb switch anymore.

This seems confusing. Doesn't the pullchain switch get removed from the box, not only to replace with the fanlinc control unit, but also to make enough room in these cramped wiring boxes? I am thinking of installing a fanlinc in my Honeywell ceiling fan but it currently has some fancy two wire (hot and neutral only) method of controlling the lights, with dimming, and the fan speed. Would be nice to know what protocol this things uses. It comes with a thermostat inside the wallswitch control unit but inside a wall box, but with dimming electronics heat, is not a good place for a temperature sensor. I have a 2441ZTH just waiting to be enslaved for graduated smart fan speed control.

I would be afraid that somebody would pull too hard out of frustration maybe and fracture the glass. Can they not be just stored above the glass globe and not dropped through at all or the pullchain switch bypassed?

I am not sure how the Elk event triggers work in ISY but give this a try. If From 10:30:00PM To 5:00:00AM (next day) AND { Elk Zone 'Family-Motion' is Violated OR other zone is Violated } AND { <----Elk triggers may not require this section. Elk Zone 'Family-Motion' is not Violated <----disables 'reminder' if motion starts again. AND other zone is not Violated } Then Wait 30 minutes Enable program 'reminder' Else Disable program 'reminder' Program 'Reminder' (disabled) If Elk Area '1' 'Armed State' is Disarmed Then Repeat Every 30 minutes Set Elk Speak Word 'Alarm' Set Elk Speak Word 'Is_disarmed' Else --