MWareman

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 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/

Does your KPL not show up with separate nodes for each button in the device tree? If not, you probably have a KPL that is not supported on the latest version of software for the ISY-99, as LeeG suggested.

You could create a disabled (so it does not trigger on conditions, but can still be run from MobiLinc) program on your ISY that (in the 'Then' area) triggers the door opening and sends you the text. Add the program to your daughters device, with 'RunThen' of this program as a favorite (along with the status node). Restrict MobiLinc to the favorites screen, and pin protect settings to prevent changes.

Its for reasons like this I have a meter - or a continuity tester - on hand during installation.

Interested as well. Holding off the purchase of a weather solution at the moment to see what happens with this, HAM, pwsweather etc. However, I would prefer to keep it local and not depend on an Internet connection for anything other than forecast data.

Thanks @Teken! Can the GEM directly send data to SEG? If so - that will likely be my initial solution. I do prefer on premise though - so I'll look into that once the crush of work from moving is over. I think I'll eventually be going DASHbox (now that I looked again at the Brultech site I found the link) once I have the main monitor installed. As far as ISY is concerned - I'll probably wait and see what UDI do. I'm invested in zwave - and do not want to lose that functionality to add Zigbee. Given the unclear direction, I need to know if I should buy a separate Zigbee ISY - or wait until the next hardware rev and hope it has dual protocol support (and live without ISY integration of the Brultech in the mean time). If only ISY could consume the data directly over the network without needing Zigbee.... Oh well..

I have to say - in my old house I had the Aeotec zwave monitor on the incoming supply. I was (as @Teken suggests) never happy with that - and wanted to get more information about individual circuits, decent trending etc. @Teken, thanks for posting what you did - both here and over at http://www.brultech.com/community/viewt ... ?f=2&t=929. I has pushed me over the edge, so to speak, and I just ordered the GreenEye Monitor from Brultech for my new house (I'll be closing on it in about 3 weeks - moving in 4 - and so will have some time I can install things like this with minimal disruption). You should get a commission! Other than the GEM and CTs (I ordered a package, with CT pack A and G initially) - do I need anything else? Is all the graph generation done on device - or did you need to hook the GEM up to a cloud service for this? Edit: Should point out that I have 1 ISY - with zwave. So no Zigbee is possible. I saw you mentioned something calls a 'DASHbox' to send data to SEG (http://smartenergygroups.com/api) - but I'm struggling to find details of this. I found this page: http://www.mypowerpanel.com/web-server/ but the 'Buy' link goes to a blank page. Thanks! Michael.

$40??? Other then that, not sure... The second edition is IP44 rated. Not sure if the first is.

Worth bearing in mind. Michel, can you make powering the ISY an optional feature of your PLM? Maybe a dip switch to enable it.

Sign me up!!!