MWareman

Here is a link to the Word template: http://cache-m2.smarthome.com/manuals/12063_template.doc

Take your mini remote out of the scenes - but otherwise setup everything LeeG detailed. Then - you need programs triggered with the control function of the MiniRemote like this (psudo-code): If Control Mini B 'On' and Fan Off Then SceneFanLow On If Control Mini B 'On' and Fan Low Then SceneFanMedium On If Control Mini B 'On' and Fan Medium Then SceneFanHigh On If Control Mini B 'Off' and Fan High Then SceneFanMedium On If Control Mini B 'Off' and Fan Medium Then SceneFanLow On If Control Mini B 'Off' and Fan Low Then SceneFanOff On After this - your B button 'On' will increase your fan speed - and 'Off' will decrease - in both cases by turning the appropriate scene on. As each scene is turned ON, it will set the KPL buttons to be correct for the state.

Upgrade to 4.2.23. There is a fix for non-pro and MobiLinc SSL.

What version is your ISY? Is it a PRO or non-PRO? Google removed SSLv3 from Android 5.x, and older non-PRO ISY firmware only supports SSLv3.

@QuietMinded, please only use those parameters if that is the correct device! There are other Aeon devices with energy monitor capabilities, and (at least he clamp meter) uses very different parameters for things. For instance, parameter 1 sets the input voltage for the wattage calculation. The Pepper1 site should detail what you need though. Michael.

Got my Echo invite (finally) yesterday. Ordered right away, and they then tell me there is a 3 month delay until shipping. Hopefully, there will be an api figured out by the time I receive mine!

If your device is this one: http://www.pepper1.net/zwavedb/device/410 I found the following parameters to work well for me monitoring a washer and dryer: 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 ​Check this thread for our experiences: http://forum.universal-devices.com/topic/13055-aeon-smart-switch-dsc06106-zwus/ Michael.

You should be able to do that. You need to set a device parameter to tell the device to send the value after it changes by more than a certain %. See if you can find your device here to identify the parameters to set: http://www.pepper1.net/zwavedb/

Just in case it was missed..... Posted yesterday http://forum.universal-devices.com/index.php?/topic/15110-Trying-to-migrate-from-SmartThings&do=findComment&comment=128137 Woot! I wonder what 'shortly' means...

Crazy thing is, I used to use SageTV - until Google purchased the company that wrote it, and effectively killed the product. I had to switch to MythTV instead, and I haven't looked back!

We got a 'free' Nest with out new house - I sold it after I installed my Trane zwave stat. Nest is neat - I just didn't want to deal with the lack of openness and lack of spirit of competition that Google is displaying around the product.

To use it, you have to agree to terms, that apparently includes a commitment to not include demand/response power features in your derivative product.....

I thought I read previously that Google essentially said NO to UDI because of the ISY demand/response power integration, which prohibited UDIs participation. There may be more to it though.

I use Insteon leak monitors to monitor for leaks - and my sump backup has a dry output for reporting issues via my Elk. I fully agree with @Teken - don't automate your sump with Insteon. An all-on event or worse - a relay gone bad in the EZIO8 could cause a flooded basement. Just not worth it. Monitoring, fine. Control - leave that to a redundant pair of float switches.

I would guess that if you put 'if 1 = 0' and check 'Run at startup' then 'Else' would be run at startup instead of 'Then'. Not sure the utility of this, and not sure if true. Maybe I'll test someday.

@chrishick That's very nice! I now exclusively use Tasker, and have custom scenes setup to display status and present a UI. I've spent no time on custom graphics (yet!) but I see now that I must. Perhaps over the holiday!

Also, to trigger on variable changes (when the value changes), the variable must be a 'state' variable.

I just compared my v2 tag in the Kitchen to my zwave stat (very open floor plan) - my rev 2 tag seems to track a fairly consistent 1.3-1.8 degrees hotter. I have a IR thermometer - it agrees with the stat. This is at 71 (by the stat). I'll trend the unit outside to see how it reads.

You do need to calibrate them. Mine were quite off before I did that. My real question is after calibration, how well do they maintain accuracy as temp and humidity changes. I have no real way of testing that....

I'm using the second generation, after taking advantage of the 50% off. Reliability has been very good now. As to accuracy of the sensor - I don't have anything to really compare against - sorry. However, the values I'm getting seem reasonable. That being said, with as much of an investment in 1 wire that you have @Teken, I'm not sure it would make sense. Except - if you have a desire to make ISY REST calls in response to IFTTT cloud events then the tag manager can be used to do that for you. On its own, this is a very neat option. Michael.

I've long suspected this, and make use of it in many places. Good to see its supposed to work this way!

....Or change to an ApplianceLinc for the non-dimmable lights

I have some of these: http://wirelesstag.net and I push temp and humidity into ISY state variables with a Kumoapp. Edit: This thread contains the details. http://forum.universal-devices.com/index.php?/topic/8818-CAO-sensors-support&do=findComment&comment=114886 I have three in my fridge/freezer in the kitchen (three zones), and one in my chest freezer. Additional sensors on each floor and outside. All have worked well for several months now, reporting temp and humidity to ISY every 15 mins.

I use Notepad++ Michael.

I've confirmed that Mobilinc connects with HTTP on the local wifi (wireshark) - the sluggishness is due to the initial refresh that occurs when the app is started up. With Tasker - I'm working towards a zero latency solution. Even the initial SSL connection to ISY when roaming is orders of magnitude faster than what Mobilinc seems to be able to achieve. I don't really understand why yet. In my day job - I work with F5 units - and high end networking troubleshooting. This is why I'm able to dig into crypto, certificate and networking issues fairly readily and understand what's going on. Encrypted connections take an extended time to establish. The single biggest factor that helps is the math processing speed of the server you are connecting to. ISY does this math on it's main CPU - and given the complexity of > 1024 bit crypto math I'm amazed that connections times are as short as they are! Hopefully, UDI sees fit to include a chip like this (http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=C29X_FAMILY&cof=0&am=0) in the next hardware refresh of ISY to make strong TLS practical - even as an option that can be installed if a user desires. Me - for REST access to my ISY - I use one of these boards in my proxy server (http://soekris.com/products/vpn-1401.html) - and it works as an SSL offloader. Apache MOD_SSL seems to use it well. I have almost instantaneous connections using Tasker with SSL - but still high latency using Mobilinc due to it's initial refresh.