mvprj84

You don't have to install it. Since my phone is rooted I dropped it into the /system/bin folder which means I can call it from a Tasker "Run Shell" script just by starting the command with "curl". I'd assume that you'd be able to drop this on the SD card portion of your phone as well, but you'll need to use the full path to the curl executable.

I just wanted to follow up here with the solution I'm using while the Mobilinc dev continues to work on Tasker integration. What I ended up doing is downloading cURL for Android, and then set Tasker to run a shell script like this: curl https://ISY_URL/rest/vars/set/2/5/1 --insecure That REST call sets a variable in my set up. The key here is the "--insecure" flag which tells cURL to ignore the SSL certificate warning.

Are you getting an error that looks like this: "Input/Output error for https://example.com/blah: javax.net.ssl.SSLHandshakeException: java.security.cert. CertPathValidatorException: Trust anchor for certification path not found..." If so then it's probably related to you using a self-signed SSL certificate. Here's a message I posted to the Tasker forum about it a little while back: https://groups.google.com/d/topic/taske ... discussion

Ah, guess I expected the high/low to correspond to how hot/cold it will be outside and not how hot/cold it was outside. Thanks for the heads up.

This is what my the email template looks like: Outside Temperature: ${mod.weather.temp.current} Outside High: ${mod.weather.temp.high} Outside Low: ${mod.weather.temp.low} Feels Like: ${mod.weather.temp.feelslike} Rain Today: ${mod.weather.rain.today} And yes, every time I check the admin console I pretty much see this. What it seems like to me is that when pulling in the info in the morning the high temperature is equal to what the current temperature is. If I look at the data at night the high temperature is equal to the warmest it got during the day. I switched to a different reporting location earlier today so I should probably know tomorrow whether it just happened to be that particular station. The other thing I'll do is compare the data to their website tomorrow. That should help determine whether the data isn't getting pulled correct, or whether it's WeatherBug that is messed up.

I have a program that triggers based on the WeatherBug high temperature for the day, and it seems to be incorrect most of the time. Generally I have it send an email out between 8AM and 9AM every day, and for the most part the current temperature almost always equals the high temperature for the day which really throws things off. Since I only collect the data through email taking a snapshot of my inbox seemed to be the best way to show the various values (from left to right: current, high, low, feels like): If I watch the temperature throughout the day the "high" frequently adjusts to match roughly what the current temperature is. The "current" temperature is always accurate from what I can tell. I'm currently using the 3.3.2 Beta, but this has been a problem for at least a couple months so I didn't think it belonged in the Beta forum.

Man, that will teach me not to check back here in a two-week period. I can't believe we are getting variables! I can't wait to see how they mature over time, but they will definitely simplify some of my programs as they stand right now.

Perfect here, too. I'm just wondering though... something that I've noticed that has happened for quite awhile for me. Do any other Mac users notice that the software always starts with all folders expanded, regardless of whether you go through and collapse them? This obviously isn't a very important bug, but I just wanted to make sure there isn't some sort of workaround or something that I'm missing. I've never had this problem on Windows though... it seems to remember the state I left the folders on there. (and I've cleared out my Java cache plenty to see if there is something screwed up there)

To people having problems upgrading... are you on a Mac? The upgrade failed from two of my Mac's, but worked from my Windows machine (all of which are wireless).

Same error for me too.

As always, let me know if there's anything I can do to help debug. I had been experiencing this for awhile... not having realized that downloading it "locally" fixes the issue, but it was never a big deal to me for the one or two times I open it each day.

I'm using Mac OS X 10.6, and running Java 6. As others have noted using the http://isy/admin.jnlp file is "immune" (for a lack of a better word) to these prompts. It's just the one I download from your site that performs an update check each time.

I also get the same "download update" prompt on my Mac. So definitely not OS specific.

Well, here's an overview of my problem. If I set "trigger off" the garage (more specifically the IOLinc) will not always return the expected status when queried. These scenarios may help everyone understand what I'm seeing: Garage is CLOSED, Sensor is OFF, Relay is ON: Querying the sensor causes the sensor to switch to ON (then I turned the relay off by pressing the off button, which doesn't really do much since only the "on" event of the relay is what opens or closes the garage...) Garage is CLOSED, Sensor is ON, Relay is OFF: Querying the sensor causes the sensor to remain ON (then I opened the garage by pressing the on button of the relay...) Garage is OPEN, Sensor is ON, Relay is ON: Querying the sensor causes the sensor to switch to OFF (then I turned the relay off by pressing the off button...) Garage is OPEN, Sensor is OFF, Relay is OFF: Querying the sensor causes the sensor to remain OFF (then I closed the garage by pressing the on button of the relay...) Garage is CLOSED, Sensor is OFF, Relay is ON: Querying the sensor causes the sensor to switch to ON (note that this last result is the same as the first one, and so the cycle repeats) At first this whole thing didn't bug me too much, but it's starting to a bit more now that I have some triggerlinc's hooked up to doors around the house. When a door is closed the trigger is off, but with my garage it's the opposite. So I have to try and keep the two things straight in my mind.

No, they didn't contact me. I didn't realize that they were going to?

I decided to give this a whirl again with 2.7.8 (I saw there were some IOLinc changes), but just wanted to report that it still doesn't work for me when the "trigger off" is checked. I also removed and readded the IOLinc just to cover all bases.

Here's what I want to do... I have a keypadlinc where there's one button that opens the garage door, and I'd like to have the respective light on the keypadlinc light up if the garage door is open (even if it was open by some other method, which i'm trying to do by checking the iolinc sensor). My problem is that I can't even set any of my keypadlinc buttons to "on" through a program. If I try to set a keypadlinc button to "on" in a program it doesn't seem to register it. The weird thing is that I can throw the keypadlinc button in a scene, and toggle that scene on/off without any problems. When trying to interact directly with the button, however, it doesn't work. Oh, and I upgraded to 2.7.8... but I can't see where I can adjust the led lighting of the keypadlinc using a program. It said it's possible in the changelog, but my programs only give me on/off/query options in the dropdown when creating a program. Happy New Year! 10 seconds till the ball drops for me. -Ryan

I'm getting a bunch of motion sensors hooked up, and I'm trying to determine the appropriate logic for some of my programs. Here's the different cases of what I'm trying to achieve: 1. Motion sensor is triggered - light turns on. Light turns off when no motion is sensed. 2. Motion sensor is triggered - light turns on. Then a physical light switch is pressed "on" to keep the light on, which overrides the motion sensor from trying to turn the light off. The light will need to be turned off manually. 3. Light switch is pressed on before motion is even sensed - this disables the motion sensor like in number 2, and the light will need to be turned off manually. I didn't have a problem coming up with programs to accomplish all of that (my code is below), but my real problem is when the light is turned on from a non-physical switch (a.k.a. the ISY Java app or an iPhone app). I noticed that the ISY logs these events as an on/off command, but classifies it as a "web" event which, as far as I know, can't be explicitly used in a program. Meaning I can't build an "if" statement when an on/off command is issued through the web interface. This would solve all my issues, but I don't think it's possible. From my understanding, in terms of creating programs, the "status" is called whenever the status of a light changes (via the web interface, a program, or a physical switch), and the "control" is called whenever a physical switch is pressed. There is nothing designed for catching the web-issued commands. I know I can detect whether the light was turned on because of the motion sensor, but what I'm trying to avoid is having to turn a light off and back on again if I want it to stay on. I should just be able to issue an "on" command from the switch itself or through the web and have it override the motion sensor that way. I appreciate any insight you guys can give me! This is what I've got thusfar... --------------------- Cabinet Lights - Auto Off This is disabled by default, and is only enabled if the lights are automatically turned on. --------------------- If Control 'Motion - Kitchen' is switched Off Then Set 'Kitchen - Cabinets' Off Disable Program 'Cabinet Lights - Auto Off' Enable Program 'Cabinet Lights - Auto On' Else - No Actions - (To add one, press 'Action') --------------------- Cabinet Lights - Auto On Disables itself once triggered since it isn't needed again until the lights are turned off. --------------------- If Control 'Motion - Kitchen' is switched On Then Set 'Kitchen - Cabinets' On Enable Program 'Cabinet Lights - Auto Off' Disable Program 'Cabinet Lights - Auto On' Else - No Actions - (To add one, press 'Action') --------------------- Cabinet Lights - Manual Off When the physical light switch is triggered off this will re-enable the motion sensor. --------------------- If Control 'Kitchen - Cabinets' is switched Off Then Enable Program 'Cabinet Lights - Auto On' Else - No Actions - (To add one, press 'Action') --------------------- Cabinet Lights - Manual On When the physical light switch is turned on this will disable the motion sensor. --------------------- If Control 'Kitchen - Cabinets' is switched On Then Disable Program 'Cabinet Lights - Auto Off' Disable Program 'Cabinet Lights - Auto On' Else - No Actions - (To add one, press 'Action')

Tim - That's interesting though because I don't have any specific responders I want to link it to. I'm just controlling it with my iPhone.

Sounds good... I set it so that I'll get notified on new replies to the forum in case you need me to test/change/debug something. Or you can PM me.

Hmmm... still seems to have that problem anytime the "Trigger Off" is checked. Here's a picture of what the options look like when I'm having issues: And I'm using this kit from SmartHome, which is basically what MikeB referenced (except mine included the IOLinc). http://www.smarthome.com/74551/I-O-Linc ... Kit/p.aspx I've played around with it for about an hour to try and get some solid info I could give you on what's going on, but it's rather puzzling to me. All I know is that if I enable the "Trigger Off" feature it will always set the status to "on" when queried. I followed the instructions on the wiki and they didn't seem to resolve anything. http://www.universal-devices.com/mwiki/ ... e_Door_Kit I'm not sure how this affects things, but I don't have any physical buttons tied to the garage door (my focus is on using the iPhone/iPod for controlling these things). For that reason I didn't create the scenes you had mentioned in the wiki article. I thought maybe that was the issue for some reason, but even after creating them I still got the same results when "Trigger Off" was enabled. Now, I should also forewarn you that I'm not exactly an instruction-reading kind of person, but am fairly technical. So when setting this up I looked at the wiring diagram to figure out what wires to connect to which ports on the IOLinc unit, looked at the pretty screenshots on your wiki article to determine configuration settings, and it seemed like it was working (until the overnight query) so I left it at that. I went back and looked at the instruction paper and I noticed that it talked about holding the set button down on the thing like 20 times, but I'm hoping I accomplished the same thing by going through the ISY interface. I'm content with the way it's working right now, but am more than willing to do whatever I can to help figure out the issue if you still want a stab at it. If a more real-time conversation would be easier just let me know and I can email you my IM address.

So I upgraded to 2.7.7 (I guessed the download URL, hope you don't mind), and still had the same trouble. What ended up resolving it for me, however, was unchecking the "trigger off" option in the settings for the relay/sensor. This ended up reversing the detection signal (eg. "on" used to represent the garage being opened, but now represents being closed), but all queries maintain the correct status of the sensor. I just want to say Michel that you are doing an unbelievable job here in the forum. Your prompt responses help encourage an active community. I'm actually writing an article on the ISY99i and some accompanying devices, and will be sure to point out this forum as an excellent resource. Hopefully we can drive some sales your way (we're not huge, but do have about 70k feed readers). Thanks again.

So I have a v.36 IOLink and am having this problem. What's the resolution since mine can supposedly be queried and return the status of the sensor? What version of the firmware should I be running for this to work (I'm currently using 2.7.6).