Xathros

Anytime. -Xathros Sent from my iPhone using Tapatalk

Some cfls have been problematic. Some only after they have aged for a while. Spme have been fine. Try unscrewing the garage cfls and test. -Xathros Sent from my iPhone using Tapatalk

No problem in that respect. Only issue is increased traffic on the powerline. -Xathros Sent from my iPhone using Tapatalk

What make/model is the door opener. I think that we need to verify that it can be operated with the IOLinc connected to the opener directly. -Xathros

Simply unplugging suspect devices and testing will usually lead to identifying problem devices. Often however, it is a combination of several devices that add up to being a problem making items harder to identify. Noise filtering power strips, UPS's AV equipment, chargers etc are all likely culprits. Line of site distance in this case is meaningless. The IOLinc is powerline only device so RF distance means nothing here. What else is on the garage ceiling circuit? How far by wire is it from the PLM? Is it on the same electrical phase as the PLM? Do you have a phase bridge solution in place? Create the following query program and set it to run at startup. If Then repeat every 5 minutes Set 'Garage / Garage Door IOLinc - Sensor' Query Else No problem. As always, happy to help. -Xathros

Since the hallway switch is the load control for the hallway light, anything that you do at that switch is going to affect the load, On, Fast On, Fade Up etc. To avoid that, we either have to take the load off of that switch and move it to something like a micro module or deal with this scenario programmaticly. One idea may be to use adjust scene to set the local onlevel of the hallway light to 20% between certain hours. Say 2 hrs after sunset to 1/2 before sunrise (next day). This way turning on the switch during these hours will only bring the hallway light up to 20% during the rest of the day, adjust to 100% or whatever level you like for daytime hours. Then have a program watch the hallway control during those hours and respond by bringing up the bathroom lights to 20% if the hallway is turned on between the dark hours. Have another program watch the hallway switch for fast off and turn off the bathroom scene when it sees a fast off from the hallway. This is not exactly what you wanted but close and does not require any additional hardware and avoids the hallway light getting brighter than 20% during the dark hours.. -Xathros

PittCaleb- Because the Hallway switch is controlling the hallway load, it is going to be difficult to get secondary actions to activate scenes without affecting the hallway load at the same time. If you can give me a little more detail about what you want to happen under different conditions, I may be able to offer some possible solutions. Based on this thread so far, I think you may want to consider swapping the hallway switch for a 6 or 8 button Keypadlinc Dimmer. If you want to avoid the keypad, another solution would be to use a micro dimmer module behind the Switchlinc or in the hallway fixture box and move the control of the hallway load to that. Then we can use programs to decide what the different events at the switchlinc should do. -Xathros

I believe this will require a second program. -Xathros

In my experience, this indicates intermittent communications between the IOLinc and the PLM. A few things can be done to help with this situation: 1) Add Access points to improve overall communication between the IOLinc and the PLM and provide phase bridging if you don't already have a good phase bridge setup. 2) Identify and filter noise makers and signal sinks. Many electronic devices, power strips, UPS's etc can either flood the line with noise or attenuate Insteon signals on the power line. Filtering such items with Filterlincs will improve your network reliability. 3) Add additional monitoring to the garage door. You can use a Triggerlinc wireless module to add an additional sensor to the garage door. Some place this such that they indicate when the door is fully open and keep the IOLinc sensor for fully closed. This gives you a second reading as to the current door status and since it is an RF only device, it is less affected by Insteon power line issues. 4) Set up a program that queries the IOLinc periodically. This will update the door status if a change is missed for some reason. You can follow that with a test of "Responding" against the IOLinc and send out a notification in the event that the IOLinc becomes unreachable/unresponsive. Others may have some additional ideas for you. Hope this helps. -Xathros

In addition to LeeG's response, your third program is missing the parenthesis that determine the order of evaluation. it should look like this: If ( Control 'Sala / Entrada sala' is switched On or Control 'Sala / Entrada sala' is switched Fast On or Control 'Sala / Entrada sala' is switched Fade Up ) And ( Control 'Sala / Entrada sala' is not switched Off or Control 'Sala / Entrada sala' is not switched Fast Off ) Then Disable Program 'EntradaSalaMotion' Else Enable Program 'EntradaSalaMotion' Remove Jumper #1 as per LeeG's suggestion and make the corrections to the third program then post your results. Hope this helps. -Xathros

Thats OK. A device can only be a controller of one scene but can be a responder to many. What you need to to do is: Remove the 2477S's from your first scene and add them back as Responders leaving only the KPL-A as controller. make 4 more scenes as follows: 1) KPL Button B as Controller and a 2477S as Controller. 2) KPL Button C as Controller and another 2477S as as Controller. 3) KPL Button D as Controller and another 2477S as as Controller. 4) KPL Button E as Controller and another 2477S as as Controller. In addition, you should add the KPL Buttons B,C,D and E to the first scene that you created as responders for the All On/Off scene. The ISY will tell you that these are all already controllers of another scene and allow you to add as responders. Hope that helps. -Xathros

Ahhh. Safari is a pain with the ISY.. Try firefox or chrome and you will be much happier with the results. Also be aware that the weather module is currently not available. It is being re written to use a different weather source as Weatherbug just pulled the carpet out from under everyones feet by completely changing their API and terms of service without much if any warning. -Xathros

The PLM connects to the ISY not to your PC. There is an ethernet type cable that runs between Port A on the ISY and the PLM. Another ethernet cable runs from the Network port on the ISY to your router or switch. Your PC connects to the ISY via the network, not serial. All necessary software runs on the ISY with the exception of the Admin console which runs on the PC in Java and accesses the ISY via the network. The ISY will NOT work with a USB PLM. -Xathros

Hi tunamangye- First, post the programs as you have them in your ISY. Right click the program name in the tree, select "Copy to Clipboard" and paste into a reply here. Second, Describe the current jumper settings in the motion detector and the settings in the options dialog for the motion sensor in the ISY. The configuration of the sensor can have a bearing on how the program should operate. Third, in the ISY admin console, select Tools / Diagnostics / Event Viewer. Set to level 3 at the bottom. Clear the viewer and then move in front of the motion sensor. Post any captured traffic and the address of the motion sensor. -Xathros

You can easily work around that as follows: If $s.StateVariable = $s.StateVariable Then $i.IntegerVariable = $s.StateVariable Else Then use the integer version in whatever program that you don't want triggered by a change in the state variable's value. Without seeing your program, it's hard to offer further advise. -Xathros

Hello pintu1228- You should have 2 wires connected to Com & N/O terminals and running to the opener. What happens if you short those together for a second? Does the door move? The wires on Gnd and S should be running to the magnetic door sensor. As for your programs, you only need one program to do the open/close and there should be nothing in the If section. The then should just set the relay on. Your IOLinc momentary delay is longer than necessary, set that to 1 second rather than 4. Post your results. -Xathros

Just to be clear, I don't believe the lack of status on local control from these devices is a failure of the ISY but rather a limitation of the z-wave devices due to a patent issue if I remember correctly. -Xathros

Assuming this is Insteon, your router is in no way related to the ability of your keypad to control your lights. Something else must be wrong. Restart your controller, air gap the keypad for 10 secs then return to normal position and try again. -Xathros

Other options that I can think of would be: A) Use Insteon switches for the affected areas. Use the right brand of ZWave switches that DO report status on local control (Leviton maybe? NOT GE or Intermatic for sure). -Xathros

Both will use the same. It does mean that you will need to keep the firmware in sync between the two ISY's so that the Admin console version can match the firmware in both ISY's. You will simply add the other ISY's remote URL to the Admin Console's Finder window. -Xathros

jmed999- There have been some recent posts that indicate that many zwave outlets and switches (certain brands) do not update their status in the ISY unless they are communicating directly to the ISY. If they have to use a repeater, the ISY can't see the change. This is also dependent in the ISY firmware version as well. I believe there was something added in 4.2.1 or 4.2.2 to get the status from those devices in direct comm with the ISY. You can check this by watching the status of the various devices in the ISY while operating them locally. If the ISY status does not update, then the program will not work as you want. A possible solution would be to write a program to query these devices once a minute. That may sort of fix the problem at the cost of added zwave traffic. -Xathros

I believe all you need to do is remove it from whatever scene that you want it to control then add it back to the scene and select "Make controller" during the add to scene process. This will work as long as it is not controlling another scene already. -Xathros

Shouldn't be a problem. -Xathros Sent from my iPhone using Tapatalk

Sorry, missed that. -Xathros

Just out of curiosity, are session tokens/cookies on the roadmap for the network module? I just bumped into this limitation again today with my Unifi access point controller. -Xathros