Xathros

See my previous post - I posted a screenshot of one of my Net Resource rules. This one points the cam to position #1 I use the web console in firefox to capture the command being sent to the cam by it's web interface and then translate that into a role. I suspect the IE Dev console is about the same thing. -Xathros

Hi Mark- I have an older version of that Cam and am doing exactly what you want. You DO need the network module. You won't be using /REST commands for this. /REST is for setting/getting data and commands to the ISY. Network module allows the ISY to talk to other things on the network. All of that said, the Trendnet cams have performed very poorly for me. I have had much better results with the Foscam PTZ cams. Here is one of my Net resource rules for my Trendnet: -Xathros

Correct. If using the state variable to force a check every 5 minutes, we need to break it into 4 set point programs to avoid conflicts with the else blocks. If you don't need the forced check every 5 minutes then you can use either the original 2 programs or the 4 program version (without the state mvar) to achieve the same result. In that case, its just a matter of what you like better. There are often several ways to accomplish the same end result with the ISY and often it comes down to a matter of style or what you find easier to read. I sometimes use more programs than I need to just to make things easier to follow. -Xathros

The reason to use 4 over 2 is illustrated in my second example where we force a check every 5 minutes. If we don't need that, then there is no difference and is simply a matter of preference. -Xathros

Yes they do. All the ISY does when you create those relationships is write the controller and responder link records into the devices so that they are aware of each other. If the ISY goes offline, programs will not run but all of your defined scenes will continue to work just fine. -Xathros

Assuming "Catch up schedules" is enabled, depending on the time at startup, one or both may run but my understanding is that they would run in sequence. As long as comms are good to the thermostat, then it should work as planned. If catchup schedules is NOT enabled, then the stat will remain at its last set point until the next trigger time rolls around. Unless, both programs are selected to Run at Startup in which case there will be a race condition between the two else sections and the stat will most likely be set wrong. Neither of these programs should be set to run at startup. All of that said, my last post (above) details another method that should enforce the correct setting every 5 minutes but requires 3 more programs to pull it off. -Xathros

ISY is event driven. The From and To times are the events that drive these particular programs. The only way I see an event like these being missed is if the power were to fail and a fro or to time passes while its out. There is a setting in the ISY configuration "Catch up schedules at restart" that forces the ISY to run all time based programs in sequence starting from the previous midnight. This will resolve this for you but may have other side effects if you have other time driven programs. Many of us do not use the catch up feature for this reason. If really necessary, we could add a state variable to the if sections of your programs to act as an extra trigger and build another program to increment that mvar once a minute or every 5 minutes as follows: Time Trigger program. Set this one to Run at Startup. If Time is From 12:01 am To 11:59 pm (same day) Then Repeat every 5 minutes s.TimeTrigger =+ 1 Else Then modify your other 2 programs as follows: If From 6:00:00AM To 9:00:00AM (same day) and s.TimeTrigger > 0 Then Set 'AC - 1st Floor' Mode Cool Set 'AC - 1st Floor' Fan Auto Set 'AC - 1st Floor' 70° (Cool Setpoint) Else If From 9:00 am To (same day) and s.TimeTrigger > 0 Then Set 'AC - 1st Floor' Mode Cool Set 'AC - 1st Floor' Fan Auto Set 'AC - 1st Floor' 75° (Cool Setpoint) Else This way, the program triggers at both the from and to times and every 5 minutes in between. You will need to create 2 more programs to handle the remaining time slots: If From To (same day) and s.TimeTrigger > 0 Then Set 'AC - 1st Floor' Mode Cool Set 'AC - 1st Floor' Fan Auto Set 'AC - 1st Floor' 70° (Cool Setpoint) Else If From To 6:00 am (next day) and s.TimeTrigger > 0 Then Set 'AC - 1st Floor' Mode Cool Set 'AC - 1st Floor' Fan Auto Set 'AC - 1st Floor' 72° (Cool Setpoint) Else Since we are using a State variable here, and programs that reference state variables in their If sections are triggered anytime the value of the state variable changes, we are able to force the evaluation of all for setpoint programs whenever we change the value of s.TimeTrigger. The first program simply increments the value of that variable every 5 minutes. We can't use the Else blocks anymore because all of the setpoint programs will trigger every 5 minutes and three of the four programs should evaluate to false each time. -Xathros

You could accomplish all 4 set points with 2 programs as follows: If From 6:00:00AM To 9:00:00AM (same day) Then Set 'AC - 1st Floor' Mode Cool Set 'AC - 1st Floor' Fan Auto Set 'AC - 1st Floor' 70° (Cool Setpoint) Else Set 'AC - 1st Floor' Mode Cool Set 'AC - 1st Floor' Fan Auto Set 'AC - 1st Floor' 75° (Cool Setpoint) If From To (same day) Then Set 'AC - 1st Floor' Mode Cool Set 'AC - 1st Floor' Fan Auto Set 'AC - 1st Floor' 70° (Cool Setpoint) Else Set 'AC - 1st Floor' Mode Cool Set 'AC - 1st Floor' Fan Auto Set 'AC - 1st Floor' 72° (Cool Setpoint) Each program will trigger twice each day. Once at the From time (running then) and once at the To time (running else). -Xathros

GLENN52- No Problem. Always happy to help. -Xathros

Select the Keypadlink entry below the scene name in the tree. Adjust the OnLever slider. Xathros

Hi Grayson- Since one of the 2 works, I will guess that the Keypad is not the issue but rather the IOLinc in the garage. Can you operate that door from the admin console by sending a FastOn to the affected IOLinc? If not, you need to look at comm issues to theat IOLinc or possibly IOLinc failure (I lost one not too long ago - very same symptoms) -Xathros

Anytime. -Xathros

You need to make sure that the ISY is not powered when you replace the PLM. Plug the new PLM into power first. Start up the ISY then log in and select Restore Modem (PLM) from the menu. -Xathros

If the second router is doing NAT then yes, you would need to do this at both. Double NAT is often a problem for other things as well and not generally a good idea unless you really know what your doing and need it that way. If the 2nd router is just an access point and only the main router does NAT and DHCP, then you only need to do this at the main router. I have one main DD-WRT router and many access points. I filter at the main router. -Xathros

Very possible. I use my mini remote almost entirely with programs rather than scenes. You may have to build the toggle logic into your programs if there are other controllers involved or be aware that you may need to press a remote button twice to get the right action. Without more info, I can't be more specific. -Xathros

Run the Event Viewer at level 3. Press each of your buttons a couple of times. Look at the trace to see if the ISY is sending the X10 A1/On. If it is, then oberkc has identified your problem. If not, post the trace and we will see where we go from there. -Xathros

Exactly. Sorry. What I posted is what my system does. If an outside light is turned on during the day, it turns back off instantly. No need to have it on in daylight - even for a minute. -Xathros Edited for spelling

OK. That makes more sense. From what I have read here since the dual band devices started rolling out, these devices have rather minimal range and are often very directional making them poor choices for bridging a significant distance. I would think a pair of access points arranged as close to line of sight as possible would be a better choice. I have to wonder if you are actually communicating via powerline through a common utility transformer rather than via RF. -Xathros

For what its worth, I believe that the IOLincs are NOT dual band devices and therefore, they are NOT sending RF but rather powerline only communications. I have some Insteon devices at the far end of a 300' run out to my barn that work quite well but there is nothing out there that could generate noise or attenuate signal beyond the extreme wire length to get there. 100' should be just fine if noise makers and signal suckers are filtered. -Xathros

Welcome to the forum! Many of us do something quite similar. There are several approaches to this. You can have one program monitor the status of many devices and send a scene Off to the All Outside scene if one or more are on during the specified time frame: If ( Status Ouside Light 1 is On or Status Outside Light 2 is On or Status Post Light 1 is On or Status Porch Light Is On ) And Time is From Sunrise to Sunset (same day) Then Set Scene AllOutsideLights Off Else Or you can monitor each light individually: If Status PorchLight is On And Time is From Sunrise to Sunset (same day) Then Set PorchLight Off Else Depends on your needs. -Xathros

One other note on this: Don't toggle between Enabled and disabled more than once every few minutes or DD-WRT (mine at least) becomes unhappy and needs a reboot. As long as you wait for the last request to become effective before placing a new request, its all good. -Xathros.

I agree, though I don't suspect it would be any more confusing than the IOLinc trigger reverse when queried issue. And since they decided to ship the wrong type switch with the Garage door kit, it might help the situation to some extent. I also share your viewpoint on SmartLab's willingness to listen to/react to end user input. -Xathros

Sorry, I didn't read that carefully enough and missed those pairs. My understanding has been that Level 0 is LED off and level 15 is LED as bright as it gets. Your tests seem to indicate that the LED on level can get one step brighter than 15 by setting On to 0 and Off to >0 or did I misinterpret your results? I was kind of hoping that your test would show the ability to reverse the LED state by setting an Off level higher than On level but this clearly proves that isn't possible. I wonder if it would be worth a request to SmartLabs as that is likely something they could change in firmware for future models. Once again, UDI is ahead of the game with support for a feature that SmartLabs hasn't even considered yet. Thank you for all of your time on these tests. I hope someday soon my schedule will lighten up enough for me to have more time to experiment. -Xathros

Possibly. I thought it was holding it on, but I may be confusing it with other devices. I think some very old devices (Icon maybe) entered linking mode by holding On for 5 seconds. Even my oldest v.31 Togglelinc has a combo set button/airgap switch. -Xathros

So then it seems that SH dropped the forced 8 difference at somepoint in the later firmwares. All of my KPLD's are V41 and this backs up what I have found with my limited batch of settings. Did you happen to test the 0 On Level with a Off Level greater than 0? Xathros