larryllix

When power resumes the bulbs may send out their statuses before the ISY has booted and initialised. A query would definitely be necessary as well as a reboot of ISY detector. One programme I have always installed in HA systems is an "all_devices_off" at about 4am. That way no matter what the cause lights get killed each day and all statuses are assumed to be known. This was particularly important in X10 HA, which I still use a few. With LED bulbs the important of energy savings, with lamps, isn't so important anymore, though.

What is the dual-brite signal? My MS has an AC output connection that lights up whatever load you connect to it. The dim output is the same connection with some method of reducing the effective average voltage.

ISY is going to complain about not finding your bulbs every time you turn them off and run your admin console. The bulbs will not respond to queries.

If you want your mail delivered in the rural you place your mailbox exactly where Canada Post tells you to. You also have to clear the snow away from your mailbox so the delivery person can get to it. I have to blow the snow back to the box level as a drive by ramp up to and past the box so the delivery truck can stop beside it close enough to deliver the mail an arms length from inside the truck. Several times per winter I have to clean out the snow from the asphalt to the mailbox so that the snow on top of it falls away and the box can be found inside the snow bank. In a rough winter like last year the street narrows as the ploughs have no place to push the snow to. My banks were higher than I can reach last year. I had to blow a tunnel to the mailbox about 8 feet long so the mailman could walk from his truck to the mailbox to access it down the cut path. The snowploughs don't usually hit the mailboxes but the heavy snow rubble coming off the plough at 40 kph can tear the box right off the 4x4 post or just break it off. Many techniques have been tried including having your mail delivered to the post office and picking it up every day 10-15 km away. If you need out of your driveway the snowplough has to come. My helicopter is on order while I am in Florida right now. While I am gone I am saving myself about 12-16 gallons of gas and an hour of labour every day.

Far as I can tell on mine the DualBrite just puts a half wave diode in series with the output for half power lights. It doesn't work well for LED bulbs as the LED bulb power supplies absorb power when they can while the cycle is live and then the bulb barely dims. My front lights are only 6 watts each so more than half power is not a problem anyway. have no problems with flickering or bulb life using LEDS though. It's hard to tell what the input to the micro-module looks like (I don't have one) but I doubt it would hurt it, only activate it when the sun goes down every night, depending on the DC polarity of the output to input match. Just turn the feature off. I have gone through three of these Heap-Zenith MS on my front lights and two on the back of my shop in 6 years. The rest of the manufacturers have been chased away in every store I can find so I cannot find a replacement for their junk. The Insteon MS will also tell your ISY when it gets dark for other automated functions/lights in your system. The micro-module method won't.

I have two different firmware versions of the 2441ZTH thermostats linked to my ISY. The older firmware - ISY can set setpoints, heat,cold, & auto modes, fan not sure, The newer firmware - ISY cannot set anything. Appears it can and ISY shows it changed but a query sets it back to actual setting. Neither can query to receive a temperature update, only modes and setpoints. ISY does not show Setpoint Up or Setpoint Down for either and IST, despite being able to insert these lines of code cannot do this is programs ISY does not contain the 2441ZTH as a model on the device selection, so I assume the support was never complete by UDI. Humidity updates on a regular basis (1 minute on AC adapter) in lieu of a heartbeat detection capability. Temperature only updates by exception to the stat's internal rules = temperature change and n degrees change from the last temperature reported. This seems to be about 1.5 degrees C. Also causing temperature updates are some hardware buttons being pressed. I only use mine as probes to ISY. Recently I have added a freeze backup heater in my utility room via On/Off module in my utility room, and a high humidity/temp vent fan via On/Off module in my cold cellar.

Use the same trigger logic that triggers Scene 2. Or Put your enable/disable in your first program. Without any further influence to Scene 2 you should have a locked out logic that may not be resettable.

Remember this is a real time system and anytime the if section is retriggered by the involved devices changing state the If section is re-evaluated and the Then and Else section is either restarted or stopped and the other section started (retriggered).

For the local lamp the dimmer can be set to a slow ramp and ISY programs/scenes can override the ramp with it's own brightness and faster ramp setting for the bulb. Double Tap produces an immediate full on/off so the double brightness change becomes obvious and annoying so cannot use this technique.

Unfortunately, the repeat information in this linked wiki is stated incorrectly as are the syntaxes of both forms of Repeat in the ISY programming. The descriptions should read: "Repeat Every Time causes the Repeat block to repeat with a Wait time specified amount of time (hours, minutes, seconds) on each repeat loop." ie. The loop time in a "Repeat Every Time" will be the total of Time plus any Wait times used inside the Repeat loop statements. "Repeat For Times causes the Repeat block to execute the specified number of times." ie. "Repeat For 1 Times" does not repeat the lines inside the Repeat For any times but rather executes the inside code lines only once without any repeat.

I found this same syndrome quite common among electricians that worked outside in cold weather too much. They would come in for lunch. Crank the stat up to 85 and go back outside after lunch. Guess who breaks out in a sweat that afternoon before discovering the setting? LOL.

Yes I have both my wall switch dimmer and my mini remote operate many programs in parallel, so to speak. This way my wife and guests can understand the actions for scenes to operate the same style. Once they they understand the progression of brightness achieved via fast off , off, dim, brighten, on, fast on commands the mini remote works exactly the same as the wall switch dimmer. Just insert an "OR" in your "If" section of each program with both device's similar commands and have each program turn on the wanted scene for each of the actions. Mine controls a whole room full of lights to different scene brightness levels. If WallSwitch is switched FastON OR MiniRemote is switched FastON Then set FullBrightnessScene ON Else --

I had one of those cheap CFL bulbs drive me crazy for a while. This was not Insteon but my rf remote in the car. The range to open was hundreds of feet but the range to close was only about 15-20 feet.

A CAI WebControl board with case and power supply can send real time from Internet sources into ISY with a minimal program learning curve. Ay date or time value could be then tested from the variables sent into ISY. Later, cheap 1Wire temperature probes, or other sensors, could also be added for temp/humidity values in ISY. http://www.ebay.com/itm/Programmable-analog-temp-humidity-I-O-relay-control-HTTP-email-alert-WebControl-/261778027152?pt=LH_DefaultDomain_0&hash=item3cf32fb290 http://www.ebay.com/itm/WebControl-timer-temperature-humidity-I-O-controller-network-relay-ctrl-chassis-/270809014985?pt=LH_DefaultDomain_0&hash=item3f0d79a2c9 Also, X10 previously had alarm clock looking devices that could send X10 coded alarms to ISY based on an alarm clock style settable device. I am not sure if these are still available.

I don't believe the MobiLinc company can access your ISY. It would have to have your password and IP address to do that. Unless the app is "ratting" on you the MobiLinc company doesn't have that, only the app does. That is no different than any remote access app or even your OS that keeps passwords for user convenience.

http://forum.universal-devices.com/topic/13900-use-of-sysextip-variable-in-notifications/

If they block things like porn access via some third-party service or list it would make sense DynDNS would be too. DDNS servers are just proxies that could get around a simple site-blocking list so it may make sense for them to block DDNS servers for workplace and public access points. I would like to personally thank Grizzy for that email / IP discovery. I have been chasing UDI for access to our external IP address as a variable that we could have ISY send us our new IP address should it change. This is ingenious, I thank you, and I can't believe I didn't think of that simple technique, myself. I already send myself a home status update each morning, when we are away. I am cheaper (relative scale) than that, also, and don't have kind of money to burn on things like that. It's not a negative thing. Necessity is the motherhood of invention.

Inline comments, at the end of each program line, was requested for v5 that could definitely help this problem. We'll see. With the advancement of programming complexity coming on the ISY, this feature will become much more important, also.

I learned from the masters.

Hey! Xathros had to pound that into my brain for a few nights before I caught on. It isn't intuitive or syntactically correct but where else would UDI put it? I could feel your confusion and couldn't sleep.

I went through this same dilemma with controlling scene parameters and it took me a long time to get it through my head. It appears you are still selecting the scene to control instead of the controller (found in the scene pulldown list) When you select the scene in your programs scroll further (probably up) for the "controller device of the scene" in the list. Mine were all at the top of the list above where the pulldown menu displayed on the screen. The "controller device of the scene" is not, in fact, a scene at all, but still on the list. I see no mention of a device that looks like your Door sensor in your programs. In Scene 'Laundry Room / LaundryLamp-On' <---- This should be the "Door Sensor"

Well thought out, and self-documenting variable names, are important for their usage to keep things understandable. State variables can get obscure because when you change the value of one you can trigger programs based on them and there is no apparent and obvious program flow by reading the program tree. In a mostly subroutine flow system they can make program flow branches especially hidden.

I have a few programs that manipulate State variables and result in programs being triggered. As much as this simplifies programs the logic flow is very obscure. I use this with caution but it is the true spirit of event driven software.

Wild cards. We have to have wildcards. Geeesh! There must be a pulldown calendar built into Java already. All the hype for a product that was laying on it's death bed a few years ago ( "We will never produce a 64 bit version"), surely they must have some fancy tools in the API.

+1 ...and a clock?