Xathros

Hi v101- Welcome to the forum and the world of ISY! Thanks for the intro. It sounds very much like my first experience with the ISY 5 years ago. -Xathros

It will help in situations where there is a lot of insteon traffic to prevent missed comms. With wireless devices sometimes having multiple message paths back to the PLM, I have seen odd behavior at times. Not sure this will fix it but I see no other reason that what you are doing would fail. -Xathros

Try adding a 4 second wait between the two set commands and see what happens. -Xathros

Hi davbow- When you select the scene name in the ISY, you are adjusting the scene settings that are used when the ISY is the controller - either activating from the admin console, dashboard, Mobilinc or an ISY program. -Xathros

Sounds like the email is being triggered by the leak sensor heartbeat signals. Post any programs that reference the leak detectors and I'm sure we can get to the bottom of this. -Xathros

Hi Andrew77- You sure can. Just add a program that looks something like this: If Control KPL-C is switched Off Then Set Scene AllBasement Off Else That assumes you have a scene defined that includes ALL of the basement lights. If not, just include the additional devices or scenes that you want to turn off into the Then section. You may need to add a 1 second wait between scenes or devices to prevent insteon traffic jams. -Xathros

Looks good to me. -Xathros Sent from my iPhone using Tapatalk

Hi Autonow- Mobilinc uses the Location Services features found in iOS devices to manage the geofence boundry crossings. iOS uses a combination of cell towers, known wifi access points and it's built-in GPS (this is called AGPS - or Assisted GPS) to keep track of it's location. -Xathros

Autonow- How did you accomplish the fwd/reverse aspect of this. As far as I know, the Fanlinc does not support fwd/rev. I am quite interested in gaining that capability. -Xathros

Hi noobmuch- It sounds to me like you have your KPL load wire providing power to the fanlinc. This should be wired so that the fanlink has constant (not switched) power and the KPL load wire is capped. The KPL buttons are then linked to the fanlink nodes with scenes. -Xathros

Hi Michel- That makes sense. What would the property name of the external (remote) temp probe be? Thanks. -Xathros

I agree. Why not just change the thermostat set point based on the home/away or alarm status and let it do what it was designed to do. -Xathros

Hi Michel- I guess the real question here is: Is the temperature (status) of the remote sensor exposed as a node and if so, what would be it's node number to follow the TStat's address ? -Xathros

Are you able to do more than one save per console session? -Xathros

OK, I am working with another user with an identical problem. Join the discussion for this on: viewtopic.php?f=25&t=12505&p=96131#p96131 -Xathros

Add a wait to filter the switch bounces: If Between Sunset - Sunrise (next day) And Garage Door status is Open Then Wait 2 Set Flood light' On Else Wait 2 Set Flood Light' Off This will add a 2 second delay before executing the floodlight operations giving the door sensor time to settl down. -Xathros

Then how are you setting the values for the variables XBMC and MCE ? With only that one program, I see no way for a loop to happen here. What does the Network Resource look like? I would think you would have a program that says: Program: Turn On XBMC: If MCE = 0 and XBMC = 0 Then Resource TurnOnXBMC XBMC = 1 and a program like: Program: Turn Off XBMC: If XBMC = 1 Then Resource TurnOIffXBMC XBMC = 0 and: Program: Turn On MCE If MCE=0 and XBMC = 0 Then Resource TurnOnMCE MCE = 1 and finally: Program: Turn Off MCE If MCE = 1 Then Resource TurnOffMCE MCE = 0 In the above examples, all variables are Integer - Not State variables. -Xathros

I think we need to see more of your programs. Specifically, I would like to see the programs that call the resources and set the values of the state variables. -Xathros

fox7- I am on OS 10.9 on my 13" MBAir and have no problem (or no more problems than in 10.8 ) saving ISY logs. What problems are you seeing? What version of Java are you running? I'm at: (build 1.7.0_45-b18) What level is your Java security set to? I'm at: High (minimum recommended) -Xathros

Hi Ed- While it is possible that this is an Insteon or Programming issue, I would not expect a problem like this to occur unless you happened to have made some changes that correspond to the time this problem started. A more likely cause in my opinion is that the down position sensor has come lose and is no longer in the right position to tell the door system to stop, causing the down pressure sensor (crush prevention) to reverse the door direction when it hits the floor. -Xathros

I have had 2 of my Foscams lose track of where the "home" position is after a few weeks of operation and as a result, all presets become wrong. A reboot of the camera fixes this. To avoid this, I have built a resource for each cam to reboot early morning daily. -Xathros

Installed Java (build 1.7.0_45-b18) here and have no issues with the ISY. This is on my MAC. I will test with Windows 7 and XP next. -Xathros EDIT: Latest Java update installed on XP and Win 7 - No issues to report with the ISY Admin console. With the exception of a certificate error, I am able to get to the purchase modules site just fine. It shows the modules I own and offers to sell me the ones I don't. Both MAC and Win XP tested.

As long as all of the devices being added are put into linking mode within the 4 minute window that the ISY remains in linking mode. -Xathros

Take a screen capture and save it as a .jpg. Then use the upload attachment portion of the post entry screen to upload and place inline. -Xathros

Well, thats good. Would be nice to know what happened though. -Xathros