larryllix

I had a router that wouldn't allow that. Other devices could not talk to addresses outside it's assigned space unless I changed the router to allow ad hoc mode. IIRC my current router allows it.

Do you have a heat pump system? You photo would seem to indicate you do and it is a Venstar T1800 stat not an Insteon stat..

Sorry. An update was missed fixing the other part. Hallway Auto Light - [ID 0021][Parent 0001] If From Sunset + 1 minute To Sunrise - 1 minute (next day) And ( Control 'Front-Door / Front Door-Opened' is Switched On Or Control 'Basement Stairs Door-Opened' is Switched On ) Then Set Scene 'Hallway Auto Light' On Wait 2 minutes Set Scene 'Hallway' Off Else <---- still need this for the end of the time frame. ie: Sunrise - 1 min Wait 2 minutes Set Scene 'Hallway' Off

I would set the new owner up with an Amazon account, installing the 3 way systems that you intend to pass on so they have some basic HA and it works. You don't want action started against you because you sold them a dud system and the realestate agent will be the go between provoking the friction without any technical ability. If a few things work, they will work as a simple demonstration with a simple explanation that more complex things are possible but will require personalisation of the system. Leave small fragments of each technology working in a demonstrable manner so "you left a defective unit" can never be claimed.

Did you make any recent changes to your router? While you are in your router check the IP Address reservation in the DHCP setup page for your ISY to see if the IP address is still locked in place.

This sounds like you still have scenes connected to your trigger devices. I see nothing in your program to ramp the light back on. I cannot tell what is connected to what from your program labels, but usually the Status in the first line is a problem for causing oscillation of programs. I don't know why people keep checking to see if a device is in one state before changing it but, in your case being Anded with an edge trigger line the program should be OK.

Use two programs. The "control" triggers wanted are installed in the first program. It's "Then" calls the second program. The second program must be "disabled". Here is where you put your elements you do NOT want to cause any triggering that could cause restarting, stopping or running Else. Note: Program Disable only disables triggers in the program and doesn't stop it running. The program becomes similar to linear program coding.

When the time frame triggers Then or Else (it triggers both) the door logic is also true causing Then to run. Time frame logic is a combination of status and edge trigger, making it a dual purpose logic condition. It can act like a status condition for another trigger (passive) , as well as trigger on both nodes (active). Use Control/switched logic instead of status logic. Then the If sensing logic can be true only when the sensors are initially switched On . Sensor status would be true during the whole time the door is open. Hallway Auto Light - [ID 0021][Parent 0001] If From Sunset + 1 minute To Sunrise - 1 minute (next day) And ( Control 'Front-Door / Front Door-Opened' is Switched On Or Control 'Basement Stairs Door-Opened' is Switched On ) Then Set Scene 'Hallway Auto Light' On Else Wait 2 minutes Set Scene 'Hallway' Off

Does Nest support remote sensors also?

Sump pumps have pressure and tilt switches that come with them or can be purchased separately. Hysteresis can be done with time delays in ISY. Sent from my SM-G930W8 using Tapatalk

I use ecobee3, ecobeee4, Venstar 7900, Insteon 2441ZTHs, and Tekmar stats. I like the ecobees the best for professional quality, and Venstar for the easiest to integrate with ISY. I was never impressed with the very low quality of the Insteon stats for a serious HVAC application. Hovever, the ecobees and Venstars take a third party box to interface to ISY.

I remember wondering what 388 meant inside certain clothing when I was a teenager. .

I have two RemoteLincs. They have no local indications on them and only send the keypress events. They are somewhat programmable for Toggle operation, dual button On/Off operation, or Independent button operations same as the KPL. I use one spare RemoteLinc (they are both spare since Alexa came) to initiate one of sixteen programs for testing. This was a leftover from a lighting animation I did for a circus tent ceiling once, using sixteen different animation speeds and styles, all controlled through ISY from the RemoteLinc on my person during the festivities.

Insteon Scenes are constantly argued about with people trying to turn them on 40% and wanting a boolean flag that tells them if the scene is still turned on. These are not really possible. Take an example of SceneTest. bulb1 = 100%, bulb2 = 80%, bulb3 = 60%, all with different ramp speeds. Now if SceneTest is turned On and then you adjust bulb3 to 30% brightness, is SceneTest still on or is it off? What if somebody adjusted bulb3 with a different ramp speed? Is it still on? The status of a Scene is not clearly defined as it contains multiple levels and ramp rates of devices to get there. (IN Insteon) The best you can do in you situation is to detect the major devices involved in your scene to determine whether you want to declare it still on or not. Also since dimming levels can vary slightly dues to round off in the math. eg: 99.6% may be considered 100% or 99%. So to be perfect we end up with: If bulb1 > 99% AND bulb2 >= 79% AND bulb2 <= 81% AND bulb3 >= 59% AND bulb3 <= 61% Then -------- So to be lazy you can just detect the level of one bulb or a range allowance for every bulb involved. You have to decide what is considered "On" from the scene remnants. To clarify the bottom lines I never post "Blah...blah....blah!", so the generic statement had to suffice.

Remote Cooking Off - [ID 001A][Parent 0001] If Control 'BRRemote-C Cooking' is switched On Then Run (if) Program 'Remote Cooking Flip' Else - No Actions - (To add one, press 'Action') Remote Cooking Flip - [Disabled] If Main_Scene_Device is its_Cooking_Off_Scene_value <----add as many devices as wanted to positively identify scene is on. AND Another_Scene_Device is its_Cooking_Off_Scene_value Then Set Scene 'Cooking' Off Else Set Scene 'Cooking' On

If you have v5 there is a completely self-contained method of extracting the date and time from inside ISY.

I gave up on that idea and went to having ISY keep track of it's last known time. Then on a power restore I notify myself with the last known time and current time. Sent from my SM-G930W8 using Tapatalk

Nice! I have to concude that it is the java interface with the video hardware. If you are running 4GHz you must be running some game based system with a fast GPU tie-in. My loads spend most of their time "Creating widgets for X". Only the last 5-10 seconds are shown as "loading the programs". I have about 300-500 programs, about 100 NRs, and 500 variables.

My Netbook, 2.0 GHz single core takes about four times as long as yours. This is based on amount of ISY programs, variables , NRs etc. and the speed of your CPU running the admin console. Mine has slowed down greatly running java apps and is almost too slow to load admin console at all. Total time to edit a program in admin console, about 8-10 minutes now. On a 2.8GHz 8 core CPU this takes about 1/4 that time for about 2-3 minutes total.

If stat.temp < 999 OR stat.humidity < 102% Then $sStat.comm.falied = $cFalse Wait 24 hours $sStat.comm.failed = $cTrue Wait 15 minutes notify Techman "Stat lost comms!" Else ---- You don't need to know what the temperature was, only that temp or humidity changed once per day (or less).

The same thing is accomplished by just creating a change of value heartbeat program and using a Wait for the same time span. Both methods look for a change in value. No temperature or humidity save to variables are needed. OTOH. I recommend v5.

The humidity gets updated every 5 minutes on battery but ISY programming can only detect changes to the value, not that is updated. However if an allowance of say 12-24 hours can be allowed a change of humidity should happen at least once per day. Use SmokeGrub's technique (above) and combine with humidity to reset a time out or time out variable. IIRC saving a parameter field requires V5+

It shouldn't matter if two sources of pullup to 10vdc are paralleled, as long as the pulldown output transistor can carry a few milliamps from each source. It makes sense the lighting or load device provides the 10 vdc supply for a simple rheostat on the wall. Where would the electrician get a source for 10 Vdc inside a switch box anyway? The unit Apostalakisl linked to said it was a 0-10 Vdc output sourced to ground or common. There should no problem parallelling two pullup resistors on a common line provided the polarities are the same. My guess is standards specify the polarity, anyway. Sent from my SM-G930W8 using Tapatalk

Nice find! Just need en enclosure, a UL/CSA 12-24vdc power supply and a place to put them.

I was thinking of a multiple contact output device...like iolincs x 2 or one of the third party brands. EZxIO?? I can't remember the number. Make a small resistor ladder for on 50%, 25%,12.5% using three resistors. UPDATE: With two output contacts only two dim levels could be handled. 100%, 50%, 25% and Off, four states. With a formC contacts (IOLinc) only one 100%, 40%, Off. If ramping is needed a small capacitor could slide the effective resistance from one level to another.