Xathros

I think his issue was with the D button not the big off button. Not sure if that makes a difference here. I dont have any KPL6s to test with. -Xath

Not sure if this is possible with mutually exclusive buttons or not - try setting the fan off button to non-toggle-off mode. -Xathros

Hi Dodger- I can assure you that the ISY works just fine with the MAC. I use all MAC's at work and home and access the ISY all the time with them. What exactly seems to be the problem? What version of MAC OS are you using? Do you have Java 7 installed? What version of the ISY firmware do you have running on your ISY? I'm sure we can get you up and running once we know what the problem is. -Xathros

Agreed. My wish is for a 3 position slide switch on the face of the dualband devices but hidden under the switchplate. Up- RF Only, Dn- Powerline Only, Center- Dualband. -Xathros

tome- If you really want to test for wireless comms, you can isolate the device in question by connecting the device to an appliance cord and plugging that into the filtered outlet of a filterlinc to eliminate powerline comms. If it still responds after that, then it is communicating via rf. -Xathros

jrini- Have you checked the scene definition for Fan-High and verified that the on level for the A,B and C buttons is set to 0? -Xathros

No Problem! Happy to help. -Xathros

Hi BriG- That test in the If is related to another program call. I have a Midnight door check that closes the door if it is open by calling that If. It isn't needed otherwise since other than that, I never call the If. You could remove that line if you wanted. Currently the status is managed by a combination of the 2 programs. I "run then" to open or close the door. Then the monitor program will "run else" on the openclose program when the door sensor says closed. Mobilinc uses the True(then)/False(else) status of the openclose program to display the door status. -Xathros without an "n"

If it worked there before but not now, then I suspect something else has changed. Have you moved or added any other electronics, power strips, ups, chargers etc? Something is inhibiting communication. Run the event viewer at level 3, cycle a few devices on/off from the admin console and run a scene test or two. post the trace. -Xathros

I agree with oberkc on this. When you control a device directly from the admin console, that is a direct command and the ISY expects an ack in response from the device and will retry several more times unless it receives the ack from the device. Scene control is different and the ISY assumes the device reacted. I think you need to filter the network devices (especially the UPS) with a filterlinc or AF120 if you expect the load may exceed 10 amps. -Xathros

I would move the incrementing of the integer mvar to a program that runs once per day just after midnight and have it call a second program that says if mvar >= 22 then mvar=1. This way you can have more than one event per day based on this data. -Xathros

Or, you could leave the switchlinc in place, cap the red load wire, and link it to the fanlinc's light node. -Xathros

Baja- No. The RL is a battery powered device and is only awake momentarily when you press a button or when placed in linking mode. The rest of the time it is asleep and does not receive status updates from other linked devices. If the RL is in toggle mode, you may have to press a button twice to get the desired result. The status displayed by the ISY is based on the last command received from the RL. -Xathros

Brian- First, you should not link devices outside of the ISY. The ISY will not be aware of those links and will eventually overwrite some or all of them. You should factory reset both the switch and motion sensor then restore device on each from the ISY (Assmuming that they were initially linked to the ISY). Then for the programs, I think these will do what you want: Program 1: BedroomTimer If Status BedroomLight is On Then Wait 15 minutes Set BedroomLight Off Else Program2: BedroomMotionResetTimer If Status BedroomLight is On and Control Motion Sensor is switched On Then Run BedroomTimer If path Else The first program just does the countdown timer and turns off the light if on after the delay. The second program restarts the timer program anytime there is motion when the light is on. Hope this helps. -Xathros

Hi jeff000- The IOLinc is not a dual band device as far as I know so being in RF proximity to dual band devices makes no difference. The question is: are there any other Insteon devices on the same circuit as the IOLinc? Can you move the IOLinc temporarily to the same circuit as the PLM and try the add again? Can you capture an event viewer trace at level 3 while adding the IOLinc and post that here. Are the buttons that came with your openers just basic buttons or are they multifunction? The IOLinc is going to act as a dumb button (dry contacts) and won't work with many of the multi function button systems. -Xathros

All- I have been using the Admin.jnlp on both Windows XP and Windows 7 without any issue through the whole 4.x branch. Is there any reason you launch from IE each time instead of saving the JNLP shortcut? To create the desktop shortcut: Visit https:///admin/admin.jnlp This will download and Admin.jnlp. Once downloaded, double click the admin.jnlp which will download the admin console to java cache, create a desktop shortcut and launch the console. From there on out, you can just use the desktop shortcut and not need the browser. -Xathros

Gotcha. It will require the use of variables to remember the current fan state. Are both fans always remain in the same state or do you need to track them individually?

Rana- I'm not sure how you arrived at your existing code. For fanlinc status is only see: Responding, Off, Low, Med and High. I do not see "On" as a valid status. Given your requirement, "On" seems rather useless anyway. How about this: If Status 'AC - Cool Ctl' is Off And ( Status 'Master Bed Room-Motor' is Off Or Status 'Master Bed Room-Motor' is Med ) Then Set 'Master Bed Room-Motor' High Else - No Actions - (To add one, press 'Action') If Status 'AC - Cool Ctl' is Off And ( Status 'Living Room-Motor' is Off Or Status 'Living Room-Motor' is Med ) Then Set 'Living Room-Motor' High Else - No Actions - (To add one, press 'Action') If Status 'AC - Cool Ctl' is On And ( Status 'Master Bed Room-Motor' is High Or Status ''Master Bed Room-Motor' is Off ) Then Set 'Master Bed Room-Motor' Med Else - No Actions - (To add one, press 'Action') If Status 'AC - Cool Ctl' is On And ( Status 'Living Room-Motor' is High Or Status ''Living Room-Motor' is Off ) Then Set 'Living Room-Motor' Med Else - No Actions - (To add one, press 'Action') -Xathros

jmed999- At a minimum, I would try a factory reset on each switch involved followed by a restore device for each from the admin console. If there are any links created outside of the ISY, this will clean that up. -Xathros

MMS is covered by my unlimited texting plan with AT&T. I had problems with SMS taking days up to a week to deliver when sent through their email->sms gateway. MMS seems to be handled differently. -Xathros

whywork- Sorry about that. I just checked and my thermostat (Venstar) is the same in regards to not being able select less than 1 for a test. So then, how about: If Temp >=1 and temp is <=45 Again, hoping and assuming that the invalid temp will register as 0 in this test. -Xathros

whywork- I suspect that the invalid (blank) value when your thermostat is not displayed is treated as < 45 and is triggering the send. Maybe you could say: If temp >0 and temp is <=45 -Xathros

whywork- I had to change the character encoding in Thunderbird from UTF-8 to Western (ISO-8859-1) to fix the degree display in my ISY emails. Dunno exactly how to do that in Outlook. Oddly, My iPhone always displayed it correctly. -Xathros

jmed999- I don't have irrigation gear yet so I am just guessing here. Is there a setting for the valve controller that set a maximum open time for any valve? Seems like it would be a good safety feature to prevent a flood due to a missed communication event. -Xathros EDIT: Thanks LeeG!

Oberkc- The network module will be required to control the Digital Loggers Web switch. whywork- The Rest interface is useful for connecting other networked devices and having them query or set variables, scenes, programs and device states in the ISY. For outbound control from the ISY, the network module is what you need. I would recommend that you skip rest for the first month or so then read over the documentation on rest in the developers docs. It will make much more sense after you understand the basics of the ISY first. Rest is very powerful but also quite simple. Flags: I assume you are referring to variables here. I have a few used in my system that are exactly what you are asking about. HomeAway - A state variable. 1=Away, 0=Home Occpancy - Another state variable. 1=Ocupied, 0=Vacant. HomeAway is manually controlled by via Admin console or Mobilinc. Occupancy is system managed with overrides via admin console or Mobilinc. Occupancy is set to 1 anytime motion is detected, a device is manually operated or when various phones are detected on my wireless network. There is a 15 minute countdown timer that is restarted on any such event. When the timer expires, occupancy is set to 0 and various things happen (set back thermostat, shutdown various appliances, turn off all lights etc.) I generally organize scenes, devices and programs into folders but only rarely use folder conditions as described by oberkc above. Instead, most of my programs that care about home/away/occupied/vacant all refer to the above variables in their IF sections. I do see value in the ability to use folder conditions and I likely will use them more when I get into the irrigation phase of my implementation. Integer Variables vs. State variables: All ISY mvars can contain signed integer values. The only difference between Integer and State is that a state mvar can trigger th evaluation of a program's if section when it's value changes while an integer variable will not trigger an evaluation. Status vs Control: When Status is used in a programs IF section, evaluation will be triggered any time the status of the referenced device changes for whatever reason (Manually controlled, activated by a scene, activated by Mobilinc or the admin console). When Control is used, the program will only be trigged when the specific manual control event occurs. For example: If Status BedroomLight is On Will be evaluated whenever the status of BedroomLight changes. If it is changed to 100% on, this IF will evaluate true and run the then section. If it is switched Off or dimmed to anything less than 100%, the program will evaluate false and run the else clause. If Control BedroomLight is Switched On Will Trigger only when the Bedroom light switch is manually turned On by the paddle. It will trigger if the light is already on and the switch is pressed On again. It will NOT trigger when the switch if switched off or dimmed or brightened unless you test for those control events too. It will not trigger if the light is turned on from another controller, scene, admin console or Mobilinc. If Control BedroomLight is Switched On or Control BedroomLight is switched Off or Control BedroomLight is switched FadeUp In the above example, the program would run the then clause anytime the Bedroom light switch is turned on, off for held up to brighten. Like above, only manual control at this switch's paddle will be considered control events. If Control BedroomLight is switched On and Control BedroomLight is NOT switched Off Will run the then clause when the the light is switched on and the else clause when the light is switched off - again, only by the local paddle. Hope this helps. -Xathros