Xathros

Hi Kentinada- It sounds to me like your hosts file is damaged or has the wrong permissions. Bring up the Terminal program and type: cat /private/etc/hosts And see what is returned. You should see a line included that says: 127.0.0.1 localhost Have you run a repair permissions since upgrading to Mavericks? If not, launch the DiskUtility and click RepairPermissions - See if that helps. -Xathros

Hi Drew- If the Other scene that turns on the light but not the KPL led is the issue, then the KPL button needs to be added to the OTHER scene as a responder. Sorry, I had misunderstood your original post. If the KPL is operating a scene, it must already be a controller in that scene. I guess I need a cleaner understanding of your scene definitions and what exactly you want to happen with this KPL button from both a control and feedback standpoint. It sounds like you have some overlapping scenes and you may require a program or two to accomplish your goal. -Xathros

Drew- If you want the KPL button to also turn the linked light(s) on/off, then the button should be a CONTROLLER in the scene along with any other devices that you wish to control the scene. If the KPL LED has not been accuratly representing the status of the scene as a responder, that indicates a communications issue to me. -Xathros

Some UPS's have dry contact alarm terminals that you could use to drive an IOLinc or Open/Close sensor (if you want battery powered). If yours does not, you could just drive a pair of 110V relays - one coil powered with the ups output and the other with the line then wire in series through the NO contacts on the UPS powered relay and the NC contacts on the line powered relay. A completed circuit indicates UPS power with no line power. Additionally, you could use the NC terminals on the UPS powered relay to indicate complete power fail. -Xathros

Elk is in my longer range plans as well. I do believe that you can take advantage of all of the Elk sensors from within the ISY. Line Powered Pet-Immune motion sensors to replace all of my battery operated insect detecting Insteon motion sensors! I can't wait! -Xathros

Rolled my own laundry monitoring with a combo of some MT-800 current transformers and a CAI Web Control board. As for the locksets, it depends on the lockset I guess. I have a few BE599's From Schlage that work well with the ISY alpha Zwave and have been pretty good in terms of manual use and battery consumption. I have a Schlage BE469 deadbolt that I haven't been able to use with the ISY (yet) but I think in a few weeks that will be resolved with the beta. The 469 has what they call a touch screen (actually a backlit membrane keypad). Its working great so far but I have a feeling that the keypad is the weak link on this unit. I suspect the plastic outer membrane will degrade with weather/UV exposure and once it cracks, it will be all over for that keypad. Of course, all of these locksets have manual key override so a dead battery is not the end of the world (as long as you have your key...). I expect I will be able to monitor battery status and alert will in advance before they quit. after about 6 months installed, I had to change batteries in the oldest 599. That one gets the most use but I think the replacement name brand batteries may last longer and since the kids have gotten over the newness of that lockset, It's seeing alot less usage. -Xathros

Just counted. 85 (including PLM and 3 access points) - Many more nodes as I have 4 KPL8's, 7 Motion sensors, 4 Open/close sensors, 3 IOLincs, 1 Stat all of which have multiple nodes. Will be adding a few more SwitchLinc relays and probably some door sensors after they release and are proven. I have 7 ZWave devices (locksets, dimmer, and some outlet relays) that are included in the count. -Xathros

I fully agree that it should work the way you are asking for it to. Hopefully, this last bit will pin down whats causing this. -Xathros

Not having one of the Insteon TStats to play with, I'm afraid I'm running out of ideas on this one. I have not seen this behavior reported here before and can only attribute this to program activity. Can you monitor the ISY Log and see if there are any entries at the time the stat reverts back. Also check last run times on programs for a matching time stamp. -Xathros

I wonder if Mobilinc is enforcing the scene for you. I don't use scenes with my TStat which might explain why I don't see this problem. I have my programs simply change the setpoint rather than call a scene. Try this when you are home. Instead of using the phone, use the stat to change the set point up or down a degree or two. see if it changes back on it's own after a few minutes. If not, take out your phone and refresh - again, see if it changes. -Xathros

I just reviewed your programs and see no reason why the stat would revert to the Work scene after a manual change. I wouldn't think that a change in the temp reading would trigger "Status Mode is Heat". Is there anything changing your AwayMode button? -Xathros

Actually, now that I look at it again, you only need the master program: FireToggle (ALWAYS DISABLED) If Status 'Fire-Relay' is Off Then Set 'Fire-Relay' On (Then Path) Else Set 'Fire-Relay' On (Else Path) -Xathros

Sorry, I'm at a loss. -Xathros

Right. That is a system variable - not a user defined one. See this section of the Wiki for more: http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Custom_Email_Substitution_Variables -Xathros

Since your triggering the master program manually, you might as well just leave it disabled. No need to disable/re-enable. How about this instead: MASTER PROGRAM (DISABLED ALWAYS) - the only one that I call directly (typically from SIRI -> ProxyServer -> Ruby -> ISY99) If Status 'Fire-Relay' is Off Then Run Program 'fireOn' (Then Path) Else Run Program 'fireOn' (Else Path) TURNS IT ON/OFF (ALWAYS DISABLED) If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Fire-Relay' On Else Set 'Fire-Relay' Off -Xathros

My BAD! Wrong () Should be {} Try: ${sys.node.22 17 8E 1.ST} -Xathros

2441TH - INSTEON Thermostat OK. I don't own that model so maybe someone else can comment on it's desire to return to 57. I still don't believe it should do that on its own. I believe this IS the model reported with a very directional antenna so IO am going to stick with my recommendation to install an access point across from it. -Xathros

What model stat is this? This certainly does not sound like the right behavior to me. I still think comm failure. -Xathros

That cabinet is certainly not helping it's rf capabilities and as I recall, that power block has a sure suppressor. Quite often surge suppressors contain noise filters that adversely affect Insteon signaling on the powerline. The fact that you haven't noticed any problems up till this stat issue is a good thing but I think you may have some marginal communications. Launch the admin console and open up the event viewer, set it to level 3 then using the admin console, turn on/off various devices around the house and make some changes to your stat. Look at the data returned in the event viewer for Max Hops=3, Hops left=0 or 1. if you are seeing a lot of 0's or 1's in the remaining hop count, that indicates poor communications. -Xathros

Your home electrical feed consists of 2 110V legs (phases) and a neutral with 220Volts from leg to leg and 110 volts from either leg to neutral. Generally, half of the circuits in your home are on one 110V leg and the other half are on the other. Insteon signals do not travel well from one leg to the other through the utility company's transformer out on the pole. We use access points (or other dual band devices) one installed on each leg and both within rf range of each other to couple (or bridge) the legs of your home's electrical feed so that signals can travel from one leg to the other. The general guideline is to install 2 access points on opposite legs (phases) near the main electrical panel. If you have a dual band PLM (2413S), you may consider that to be one of the access points and simply install a second access point in proximity but on the opposite leg. -Xathros

Good. then we are on the right track here. Can you copy and post one or two of your programs please. Your stat should not revert to 57 unless your programs are telling it to. Right click program name in the tree, select "Copy to Clipboard" from the bottom of the menu and paste into a post here. -Xathros

Do you already have any access points for coupling the legs of your electrical mains? If so, you could try moving one to across from the stat to see if it makes any difference, if not, you might consider picking up a few. -Xathros

Where are the programs? In the ISY admin console? Or in the Stat? -Xathros

Jerry- This is why you need to look at the stat in person. If you look from the phone, you see what the ISY thinks the stat is set to. If it was in heat mode with a 67 set point and the temp was 62, the furnace would have been running already. When you changed the set point, that message got through and changed the set point from 62 to 68. Then you backed it down to 67 which was still higher than actual temp. Dual band devices don't always work as well as access points due to the fact that they are installed in boxes with wires and other items in close proximity. It also appears that the antennas in some of these thermostats are very directional and prefer the access to be from in front of them rather than to the side, above or below. -Xathros

Next time it happens, go look at the stat first and see if the stat setpoint agrees with the phone/admin console. I suspect it won't. As I mentioned in another thread, I think you are having comms issues with your stat. Adding an access point across the room from the Stat can often resolve these issues. -Xathros