bsobel

Tome, I ran into the same thing. Trying the upgrade from a Mac that never had the admin console on it before worked, I'm trying to determine what is indeed different between them to explain the behavior...

Update, something about my machine as I tried another laptop that never had the admin console on it and the upgrade worked immediately.

I can't seem to upgrade, I am on RC4 (installed yesterday) at this location and I'm getting an error stating File Uploading Failed: (reported size is invalid) Tried numerous times now. My firmware and UI both report the 3.3.7 version. Suggestions? Bill

Create a state variable and have your program set that to a value (say 1) that indicated your in low battery mode, the set the init of the variable to the same value (this will survive a reboot). Use that to trigger your reminder, not perfect but will mask the issue reasonably enough. Bill

I have both the iAqualinc and one of these devices installed http://www.autelis.com/wiki/index.php?t ... ndy/Zodiac Do yourself a favor and get one, it integrates very easily and coexists great. Bill

Many routers today have the option somewhere in their config. You enter your dyndns username/pw and they will automatically update the host name with the current IP when it changes.

I understand that I can detect a straight off case. This started as I wanted to test for all the non-off cases (bright, dim, on, fast on, etc)... In the end if control x not off is really a if not control x off for logic purposes. I still argue it's wrong (very given the rest of the programming model) but will work around it like everyone else. As to variable naming, you can name them as you wish. That is a personal style choice. I disagree in this case, but understand some people prefer to decorate them as such. Bill

Will act as a trigger only upon recipet of an "off" command. Will evaluate as FALSE when triggered. Evaluates as TRUE if program evaluation is triggered by another condition. This (finally) explains the behavior but as a developer I still feel strongly this is a bug. Logical statements should not evaluate to 'FALSE' when the evaluation succeeds. That is bug #1 however if you accept that is how UDI did this (a bit backwards from about any other system I can think of) then bug #2 is that the statement evaluates as TRUE in any case when triggered by another condition (an If Control should only evaluate to TRUE if the controlled item was activated) I realize both aren't bugs (one negates the existence of the other) but do you 3 really think this is 'intended' behavior?

Do you have your router or another device setup to update dyndns automatically? If not when your IP changes (and for some ips that can be hourly for some it might only be every few months) you'll have this issue.

That appears in complete opposite to what LeeG stated "Press the device On paddle/button, the Programs | Summary will show the Last Run Time does not change. With If Control the command received has to match the command specified in the If for the Program to be triggered." I agree your reading *should* be how it works... Bill

Here is the actual program: If Control 'Living Room Keypad E' is switched On Or Control 'Living Room Keypad E' is switched Fast On Or Control 'Living Room Keypad E' is switched Bright Or Control 'Living Room Keypad E' is switched Dim Or Control 'Breakfast Entry Right.E' is switched On Or Control 'Breakfast Entry Right.E' is switched Fast On Or Control 'Breakfast Entry Right.E' is switched Bright Or Control 'Breakfast Entry Right.E' is switched Dim Or ( $Owner_At_Home > 0 And From 6:00:00PM To 6:00:00AM (next day) And ( Control 'Guest Room Motion-Sensor' is switched On Or Control 'Master Closet Motion-Sensor' is switched On Or Control 'Master Main Lights' is switched On Or Control 'Guest Room Main Lights' is switched On Or Control 'Kitchen Keypad.1' is switched On Or Control 'TV Room Sconces' is switched On ) ) Then $Owner_At_Home += $Default_Occupancy_Time_In_Hours Else - No Actions - (To add one, press 'Action') If I change: Control 'Living Room Keypad E' is switched On Or Control 'Living Room Keypad E' is switched Fast On Or Control 'Living Room Keypad E' is switched Bright Or Control 'Living Room Keypad E' is switched Dim Or Control 'Breakfast Entry Right.E' is switched On Or Control 'Breakfast Entry Right.E' is switched Fast On Or Control 'Breakfast Entry Right.E' is switched Bright Or Control 'Breakfast Entry Right.E' is switched Dim to Control 'Living Room Keypad E' is NOT switched Off Or Control 'Breakfast Entry Right.E' is NOT switched Off The 'then' clause runs in a very tight loop. No user is 'clicking' (I fully understand control versus status btw) the switches for this tight loop to occur. It is if the evaluation is occurring as a status evaluation. My gut still says this is a bug. I know the system pretty well (I think) and am not seeing why that change would evaluate to a true everytime. I realize that $Owner_At_home is a state variable so when it gets added to the evaluation occurs again. But the evaluation should be false on the second run (since there is no active control events at the time).

Sorry guys, was in Israel and India. Back home. I'll dig out the code when I'm next at that house and post it. That said, LeeG with the example you posted I'm hardpressed to see how you don't consider the behavior a bug. The If should evaluate a condition to true. You may have documented how it's currently working, but I have a strong suspicion that is not what was intended as the flow doesn't make sense in context of the overall programming language. The correct behavior is to trigger the then clause on any control event which is not the type specified. I seem to seeing an additional bug that the statement evaluates as a status vs a control in some cases...

Lee that behavior first off makes no sense and second off is clearly not what I am seeing. The then clause of my if was being invoked in a tight loop...

I had a program that triggered on a keypad button being turned on. That button activated a bunch of items that are turned off for power/security reasons when I am not at the guest house. Recently I had a friend visit and realized his attempt to turn the button 'on' was read a 'bright' (guess he held the button too long). So I change my logic from 'if control KEYPAD.E is ON' to 'if control KEYPAD.E is not off' I thought this would trigger on any physical interaction with the button other than off. But instead I found the program began running in a tight loop. The behavior seemed like the 'control is not' was acting like a 'status is not'. Can anyone else confirm if this is the correct behavior? Thanks, Bill

A bit of a hack, but the ISY programming language constraints sometimes encourage that... ,) Create a variable say "Thermostat_Manual_Control " and set it to 0 init at 0 In your programs when you change the thermostat set the variable to 1 before your work and reset it to 0 after your work. Then in the programs you want to respond to a manual thermostat change use 'if Thermostat_Manual_Control is 0' AND state THERMOSTAT... That should let you (reasonably) filter manual vs automatic commands. There is always some risk of a direct collision (you changing state while someone touches the control unit) but you would have had that collision anyhow...

You can certainly do this but it won't be fully integrated, you'll have to create network resources for all of the remote devices you want to manage (e.g. they won't show in one tree). I had a similar issue and one recommendation I received was to run a line voltage line from the 'good area' to the 'new area' and put a wireless access point there. This creates a bridge between the two areas. I really wish someone would create an insteon over IP repeater, I know I could certainly use a few of those. Bill

Lee would it be possible to add a 'Startup' as a schedule option in programs? This way the two programs cab be collapsed into one: If Sunset or ( Startup and (Sunset to Sunrise) ) then Actions....

Yes just the scene triggered by ISY would be useful. That said, I clearly don't understand part of the system. I thought the PLM was a scene member for every scene so I'm surprised you said you don't see the event when triggered by physical control of a scene member. Thanks for the consideration, it would certainly be nice to not be coding in device ID's (which can change if a device fails) into Roomie and rather use scenes who's id's are basically static once created.

Michael, I realize there is an issue with scene state, but not with scene control. If I send a scene a faston then the scene gets a fast on. That detection is what I'm asking for, does that help? The second part, what state is the scene in agree doesn't make sense since each members state can change after the control command. Best, Bill

Hi Michael, Today they can not do programs but I did suggest it to them. Best, Bill P.s. if technically possible please add a +1 to scene control events in programs

I started playing with the iOS remote application Roomie since it has an ISY plugin and I've been looking for something fast for a few specific events (I usually use Mobilinc but it's not 'fast') Anyhow, Roomie has the capability to send commands to scenes (scene on, off, fast on, fast off, etc). However is there any way in an ISY program to see this events? My list includes just items so unclear how to trigger a program on say a scene fast on. If this isn't supported today, is it something that is likely to be added? It seems it would be very convenient to send a scene a command versus a specific device (so if the scene membership changes the programming stays the same) Thanks, Bill

So each button generates a message to both the PLM and the item it controls (or is it a scene/group message?). Makes sense, but hadn't realized that. Oh well, off to find plan B

Hi, I am looking at the RemoteLink2 for use in my car and I would (ideally) like to carry one and link it to multiple ISY99 networks (e.g. buttons 1/2 ISY #1, button 3 ISY #2, button4, ISY#3). Is there any safe way to do this without overwriting the links made by one ISY when making a change on another ISY? Thanks, Bill

This is normal. Instead of operating on the device itself (keypad do your operations on the scene you created that liked the two devices. Operating on the 'scene' will give the behavior you want. Best. Bill

Quicker than the link, in a command shell: pkgmgr /iu:"TelnetClient"