MWareman

LeeG, that's what I meant by 'algorithm'. I should have said 'timeout'.

The Insteon motion sensors have a built in algorithm in them that prevents re-detection of motion within a few minutes of the last detection. You may be hitting that. This is to lower the power usage of this battery operated device. The first place to start is the dip switches in the motion sensor. The second item is to ensure that the sensor is just sending 'On' commands on detection. This is in options. Select the motion sensor in the admin console and you will see an 'Options' button. Michael.

I will be trying when I move into the house in just over a week. My opener is still its box. Michael.

True enough. I was really only addressing my experience with 'Rain Today' - but the need to feed full climate data from a local PWS into the ISY irrigation module is acute - if we want even close needed water calculations. I *really* hope this happens with 5.x. Data from more than a few 10s of yards away can really make a difference!

WeatherBug is no longer a valid source of data, to a change in how they license data access. You need to upgrade your ISY to switch to HAM Weather.

With ISY, no. Something like this can do that for you though: http://www.digital-loggers.com/lpc.html

The irrigation module really needs the ability to talk to a very local rain sensor to calculate ET. Even a half mile makes a massive difference! I'm having a new house built, and I'm currently living in a apartment less that a mile away. I had a cheap rain sensor at each location, same brand, for the last couple of weeks. One registers .78" and the other registers .09" over the same week. This is wildly different than what ISY is reporting for my closest station. I really, really, really want to be able to feed local information in, without having to poll a web service at all. Please make this possible in 5.x..

The Dev got back to me on this. I'm hopeful he will be able to reproduce and fix the issue soon. Meanwhile, Autovoice got an upgrade to allow direct recognition via Google Now, without having to root and run Xposed. That seems to work as well and allows some really advanced regex parsing of received commands, but with that power comes complexity. Commandr is much easier to use for simple things. I'll probably end up using both...

Nope. Spoke too soon. I clears the app data for Commandr, and this allowed me to go into the Tasker area again. After exiting, opening Tasker, exiting taker and going back into Commandr, it is again crashing when I try to go into the Tasker menu. Clearly a significant bug.

Found out what's up. I renamed a Tasker task that was associated with a Commandr action. After that, you cannot use Commandr . I had to clear the app settings and re set it up.

Secondary keypad buttons cannot be controlled directly. That's why there are no buttons. You need to put them into an scene and then control the scene. Don't know about the fanlinc though.

@MaddBomber83 is this your app? It seems to work very well on my tablet (Nexus 7), but on my phone (Nexus 5) it crashes every time when I click 'Tasker Commands'. Looking for ways to debug what's wrong... Too many Tasker tasks? (About 60 or so) Invalid character in a task name? I have many more tasks on my phone than I do on my tablet. Thanks!

That is awesome! Thanks for posting. I just got started playing with the Closed module that does a similar thing, but I like this implementation better (plus t does not need root!). I've not tested it yet, but I'll find out soon enough!

In my case, it fires once when the machine starts, and again once when it stops. However, it depends on power not dipping below 2W during use - at all. If that happens you may need to add a wait in the 'Then' of the programs before the notify - sort of a denounce wait of just a second or two. If the power recovers, the 'Then' will be canceled and the notify not sent. Michael.

No problem! Glad it helped. You actually don't need anything in the 'if' of your disabled program. Not hurting, just not required. In the first, change the 'Run If' to 'Run Then' to make this work though. I find it cleaner.

In my case, my Aeon Labs DSC06106-ZWUS is seen by my ISY as 'ZW 005 WASHER - Energy Meter' and 'ZW 005 WASHER - On-Off Power'. The 'On-Off Power' node switch the outlet on and off - and the device reports current usage thru the 'Energy Meter' node as 'Current Power - Watts'. The device also tracks 'Total Power' (in kWh) and 'Current Voltage'. I set the following as zwave parameters for the device: Parameter(bytes) Value Purpose 1(1) 1 Report Multisensor as Voltage 80(1) 1 HAIL on change 90(1) 1 Enable change reports 91(2) 50 Min W change for report 92(2) 5 Min % change in wattage for report 101(4) 4 Send Watt in group 1 102(4) 8 Send kWh in group 2 103(4) 2 Send Multi for group 3 111(4) 600 Time interval group 1 112(4) 600 Time interval group 2 113(4) 600 Time interval group 3 I have a integer variable to track the device - in this case iPower_Inuse_Washer. In my case - I find quiescent is tiny - but opening the door causes a light to illuminate - and I didn't want to detect that. So - I trigger on exceeding 2W. My program to detect the washer being turned on: If Status 'ZW 005 WASHER - Energy Meter' > 2 Watts (Current Power) And $iPower_Inuse_Washer is not 1 Then Resource 'Pushover L - Washing Machine On' $iPower_Inuse_Washer = 1 $iPower_Inuse_Washer Init To 1 Else - No Actions - (To add one, press 'Action') My code to detect the washer being turned off: If Status 'ZW 005 WASHER - Energy Meter' <= 2 Watts (Current Power) And $iPower_Inuse_Washer is not 0 Then Resource 'Pushover L - Washing Machine Off' $iPower_Inuse_Washer = 0 $iPower_Inuse_Washer Init To 0 Else - No Actions - (To add one, press 'Action') Hopefully, this is useful to a GEM - and it reports changes in the power value in such a way that programs can trigger from it. It sounds to me (from your report) like the GEM integration does not result in programs triggering in the same way zwave reporting does. Can the GEM call the REST API on triggers - and set or unset a variable on ISY that you can trigger from? Michael.

@Teken, I'm currently triggering ISY notifications from a couple of zwave switch/power sensor devices (http://www.amazon.com/Aeon-Labs-DSC06106-ZWUS-Z-wave-Energy/dp/B007UZH7B8), and its been working very reliably for me. If it will help, I'll post the programs when I get home. I, myself, will be installing a GEM in a couple of weeks... So I also have this fun coming I suspect.

Just 2. Power is supplied down the two wires from the motor and the unit communicates back to the motor wirelessly (MyQ is a two way protocol). The iolinc shorting the wires does not harm this directly (its a high impedance power supply), but it does interrupt power to the controller, causing all kinds of issues apparently. Some people have taken the button apart and wired directly to the push button, others have done the same to a secondary wireless button (as I plan to do).

I've not used it yet - but there are plenty of reported issues with the 'smart' wall buttons. Simply shorting the wires causes them to reset. YMMV. Personally, I'd start with a quick test by momentarily shorting the two wires (at the motor) to simulate what the iolinc does. The door will operate - but watch your button. Does it reset/beep/freak out? If not, you should be fine with the stock iolinc wired as the instructions say. This is the one my door motor came with: http://www.amazon.com/Liftmaster-880lm-Smart-Control-Panel/dp/B005FT4NNG Again, two wires and I know the iolinc messes this one up. I'm planning to have to work around issues with that one.

The iolinc won't control a MyQ door without some hackery, if you have the button in your garage with the LCD. Status is fine with the kit though, as long as you get the correct relay and do not use 'trigger reverse'. I'm going to be installing one of these in a couple of weeks, and plan to get an extra wireless controller to wire to the iolinc (well, actually I'll be using my Elk M1... But same concept). There is also an API, but its not friendly to the ISY. You have to call an authorization URL first to get an access token, then you call a different API to perform actions using the token. The token is only valid for a few minutes though... Edit: by 'not control' I mean the iolinc controlling the door power cycles the button controller because of the way it shorts the wires together to cause the door to operate. This normally wouldn't be an issue, but with MyQ doors it is apparently.

Not sure about the IF, but when it does trigger and the light turns on, the Then will immediately stop and the light will not turn off. You will need to separate to two programs.

I see mine back as well! Thanks for the work! Michael.

I don't have the IR, but I believe its line of sight, and only one (albeit very common) IR protocol. You should check the wiki before purchase for sure.

When / where did you get the 99i? If less than a year-ish ago, the seller should have told you that it won't work with many newer devices. UDI 'yelled' this news to the community with lots of notice. IR = Infra-Red capabilities. If you want to be able to trigger things on ISY with an IR remote, or have ISY control things with IR, this is the unit to get. PRO gives you more programs and devices, as well as stronger ciphers in the SSL features (SMTP connections and network module rules). You can always add PRO later if you want - its a software license change. The hardware is the same.

If its an ISY-99 you have, you cannot. It does not have enough memory capacity. You need to replace it with a ISY-994. There is an upgrade program available though to reduce the cost. Look at the 'Upgrades' section here: http://www.universal-devices.com/sales/products/