dbroere

Tuchman: thanks for responding. still trying to fully understand the Universal Devices Administration Console... M/R (8button). added several buttons as a controller to a scene. when a button is highlighted in admin -- the Membership lists controllers and responders. Do you think this is just a programming oversight. and if so, can it be noted? was a bit confusing at first.

Am I correct on this... a RemoteLinc 2 (Mini Remote) can NOT have membership in scenes as a Responder. The Mini Remote is not "awake" to respond to commands from other controlling devices in the same scene. As a result, controlling inputs by other scene members will cause the Mini Remote toggle sequence to go out of sync.

I'm having the same issue. if these extra nodes are being added when you add a Z Wave device -- then there must be something in the U/D Z Wave "inclusion" programming routine that's adding them. Why? There must be a reason. I would think someone from U/D should know. Maybe it would be helpful if someone from U/D could clarify what's happening so we can find some logic to the situation. BTW, adding my Jasco Enbrighten ZW4009 switch added similar number of nodes, although not with the exact same names and not in the same order as your device.

was able to add several Z Wave devices to a Polisy running mainly INSTEON. the node list for added Z wave devices is a bit confusing. Many nodes for each device (different than INSTEON). Need to be able to form scenes with multiple INSTEON and Z Wave devices. Is there somewhere I can go for help? Most information is for older U/D devices. attached screen shot is for a Jasco Enbrighten ZW4009 smart switch Thanks

Looking at the back of the POLISY box, Left to Right, the connectors are: DB9 -- custom serial PLM Cable RJ45 -- Main Ethernet connection to Polisy box RJ45 -- ? RJ45 -- ? USB/USB - USB PLM cable, Z Wave Dongle, USB Hub to handle more than 2 USB devices. Power Connector What are the second and third RJ45 connectors are for? Can you have both Z Wave and Zigbee dongles? (Thanks)

Is there a way to completely reset an INSTEON device i.e. - a factory reset, through ISY programatic control? There seems to be a major conflict here between security and the factory resetting function. From what I've seen, SmartHome recommends things that require physical access to the device in order to push various buttons that will perform their factory reset. That's problematic in large INSTEON installations where many devices are enclosed in wall boxes. Can you imagine dropping the fan to reset a FanLinc? Maybe this isn't the right question so here's why I'm asking: I've arrived at this point of frustration by my hand -- poor device housekeeping. This home system had been through Several PLM's, several ISY's and other controllers. I find now, that my INSTEON devices have bogus device address contamination. Most folks recommend factory resetting everything. Sounds like a simple solution but it's really not. 99% of the lighting in my house is controlled by INSTEON stuff. The stuff talks to each other while I'm going around resetting things. I believe this re-contaminates reset devices with old bogus addresses. I have quite a few devices that would require removing the fan or going inside electrical boxes to reset. SO -- to me, the key seems to be a way to factory reset devices by some sort of programatic control.

that's clever. I have a similar situation. an insteon device keeps responding as though it were part of a scene that gets triggered once each day by a program. I can't find where the device is part of the scene so I don't know if it's ressponding to the actual scene or one of the other devices in the scene (like pushbuttons). I've tried factory resetting the device and it doesn't solve the problem. Is there a way to fix this?

you might consider monitoring the open/closed state of a a window or two and making the fan_ON conditional, based on the windows being open. There's no single device to do this but I believe it could be done with a magnetic sensor and an INSTEON device to measure the condition of the sensor. If you do duct vent control, you're almost obligated to also do temperature measuring. you wouldn't want to trigger this process when it's 0-degrees outside. you also wouldn't want to do it when it's 90-degrees and real humid outside. I've thought about taking the make-up air directly from the outside, rather than taking it from inside the house. You cool the attic but don't bring in cool air to the house. It's a trade-off. To get the whole thing NOT to do something inapropriate, you'd need temperature and humidity sensing. There's very limited outside/inside temperature, humidity, and time of day conditions when venting the attic air helps. That's what the programming flexibility is for.

First, Thanks to EVERYONE involved in this discussion. There's so much good informatino here it almost blows my mind! It's nowhere else and that's part of the problem. I've owned my ISY for a little over two years and have been totally frustrated by the programming model. And I can't find a good document that can help me learn it. I mean this in a constructive way -- I've found that the whole Universal Devices area suffers from poor (if nonexistent) documentation. There's the out-dated manual that shipps with the unit. For programming it's little to no help at all. The programming section is (I'm sorry) a joke. All that's available are a few good (but extremely complex) threads in this forum, then the Wiki which is a poor subistitute for a programming or operating manual. This thread, for example, is EXTREMELY hard for anyone trying to learn anything to follow. I know you guys have put alot into it. I'm sorry, but the end result is a geek-to-geek discussion with examples, corrections to examples, and changes. For the past hour, I've attempted to clip the entire thread out of the forum and restructure it so that I could save it in a form that anyone trying to learn ISY programming would understand. I FINALLY GAVE UP! IT's just too complex. There's changes to changes to modificaitons and on and on. My wish is that there was a way to sort all this out and provide something usefull to someone trying to learn ISY Programming. You guys are the experts - if you have any ideas, I'm willing to write and compile learning and/or reference documents. Problem is, I can't do it by myself because my level of expertise is relatively low. DB

Help About reports the following: ----------- INSTEON Devices: uuid: ... - Insteon_UD99 v.2.7.15 Product: ISY 99i Pro (1040) -- Open Auto-DR (21010) -- Weather Information (21020) -- Networking Module (21040) My URL: http://192.168.1.52/ Internet Access: Disabled ----------- address is a DHCP reservation, based on the MAC address of the ISY attempt to do File, Enable Internet access results in the error message: Failed Enabling Internet Access Can anyone help get me on the right track? I'd like to see this device from outside my home network. DB

Rand - Thanks! I've had several programs that wouldn't perform the way I thought they should - They can all be traced back to this little ANOMALIE...whatever you want to call it. It all comes down to knowing what causes IF conditions of a program to trigger and be evaluated. I've never found anything written that talks about this. Don't mean to dump on you guys but, like so many other things about the ISY, it's not described in a manual. It's like you just assume folks would know it. I can tell you, from the perspective of a programmer that's trying to learn your "language", THIS IS VERY FRUSTRATING!!! It appears that, whenever the conditions of ANY DEVICE in the IF statement changes: (1) ALL the 'IF' conditions are immediately re-evaluated. (2) if the 'THEN' processes are currently executing - they all stop. (3) the 'THEN' processes coditionally execute, based on the new evaluation of the IF conditions. I've NEVER seen a programming envrionment behave this way! Once a series of 'THEN' processes have begun, NOTHING should be allowed to interrupt it. IF re-evaluations processing should be suspended while this is going on. I suppose, once you've become accustomed to this, it might seem logical but, right now to me, it seems really wierd! Dave

back to the old test board to try and further examine this issue. Found out what appears to be a problem: If Status 'TestBoard 2' is not Off And Control 'TestBoard 4' is switched Off Then Set 'TestBoard 2' 50% Wait 5 seconds Set 'TestBoard 2' Off Else - No Actions - (To add one, press 'Action') Test: turn 2 on (full) turn 4 on (full) turn 4 off program runs 'then but only executes the first line then quits. Leaves 2 at 50% turn 4 back on turn 4 off program runs 'then' runs all 3-lines. second and third line don't seem to run unless 2 is already at 50%! both switches are 2476D's V4.35 (isy v.2.7.9)

Referencining the following program: If Status 'MBR Bath Fan' < 95% And Status 'MBR Bath Overhead' < 5% Then Set 'MBR Bath Fan' 85% Wait 8 minutes Set 'MBR Bath Fan' Off Else - No Actions - (To add one, press 'Action') the MBR Bath Fan runs continuously. When it's shut off, it restarts in about 15-minutes. My problem is how to properly trigger 'Then' conditions I'd like to trigger them when the fan is on at 100% and when OFF is pressed on the MBR Bath Overhead switch. the fan is an ICON switch the MBR Bath Overhead is an INSTEON Dimmer I've tried several different combinations of status and control conditions and can't get this to be repeatable. Any Suggestions. If the 'Then' portion of a program is executing and the 'If' conditions are toggled from false back to true, will the program reset and restart the 'Then' portion again? if the 'Then' portion of a program causes the 'If' condition to toggle to false, while 'Then' is still running -- what happens?

With the WeatherBug module installed, I'm trying to develop a way to have outside lights activate, based on the amount of light. I believe this will be more accurate than relying on sunset/sunrise times. On overcast days, for example, the lights need to come on earlier than clear days. A LIMITATION: WeatherBug reports a zero value while there's still a considerable amount of light outside. There's no measurable difference between this point and "real dark" conditions. Anyhow, given the limitation, this what I have to start with: If From Sunset - 1 hour For 2 hours And Module 'Climate' Light < 1 Then Set Scene 'Outside Early Evening' On Else - No Actions - (To add one, press 'Action') I want this program executing one time, as soon as the light level gets to less than one. Not sure how to keep it from executing repeatedly. Even with the "From/For", I'm afraid it will repeatedly execute for the two hour time period that "From/For" sets. FYI: I shut this scene down at 11PM, then start a night light scent that will turn off at "Dawn", using a similar technique - in reverse. (1) HOW DO I MAKE SURE THIS ONLY EXECUTES ONE TIME - WHEN THE LIGHT LEVEL GETS TO LESS THAN 1? (2) DOES ANYONE HAVE ANY EXPERIENCE WITH THE WeatherBug Light= PARAMETER? COMMENTS???