Xathros

Very strange. Backlight level is a device feature not a scene feature. I don't see how this could be scene related. -Xathros

I'm not sure. I usually see more of a response to me net resource rules than what you posted leading me to think that you weren't seeing the whole response. Increasing the timeout should not have caused it to fail so something else may have changed as well. Verify Ip address, username/pass etc. -Xathros

Change the brightness to something like 50. Than after that has been applied, go change it back to 0. The ISY will not send changes if it believes they match the current values. -Xathros

Ferdies- Increase your timeout to 2000ms and see if you get more of a response. -Xathros

WayneW- I do know that the ISY schedules tasks on a priority basis with I believe, Insteon traffic being the highest. I don't know where in the priority list logging comes in but I think it is possible to delay logging and possibly network resources by keeping the ISY busy with Insteon tasks. It may also be possible to delay logging with IP network tasks as well. Michel- Can you comment on this. -Xathros

Is the ISY clock correct? -Xathros

In this case it's ok since the mvar is an integer (not state) the second program does no trigger from the first when set to 0. Instead, I have to call the second program from the first (Run If) -Xathros

Sounds and looks to me like you have a program like: If Control RL2-D is Switched Off Then Set Bathroom Scene Off Else -Xathros

ferdies- No. The If section is looking at $i.internetTestEnabled while the then section is setting $i.InternetTest. Two different variables. -Xathros

it's a very quick ad simple test. Not hard work for the ISY by any means. The enabled mvar is used to enable or disable the test program. The test is initiated by my startup program and then runs on its own from there. -Xathros

Tom- Anytime! Happy to help. It has to be the 2413S. The U will not work. -Xathros

Nice! I nominate this for inclusion in the variables section of the Wiki. -Xathros

Excellent. Thanks for posting back. You should likely add a delay to the nighttime setback as well. Not sure why that worked when the other didn't but would be safer to add the delay to both in my opinion. -Xathros

Hi Tom- Is the 26 still connected to a PLM? If you connect the ISY 26 to your LAN, Connect the ISY 26 to the PLM then plug the PLM into power, wait a few seconds for it to start up, you should be able to log into it at it's old address assuming you didn't factory reset the ISY 26 at all. Also, you want to make sure you are accessing using the correct admin console. Before you try to access the ISY 26, make sure you clear your Java cache. I'm not sure if the 26 worked the same as the 99 and 994 but if so, you should try and access the console at: http://192.168.1.12/admin If that works, make your backup then repeat the process for hooking up and connecting to the new 994 but using it's ip instead. -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