MWareman

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.

@larryflix - found it. There were no posts in the Tasker forum... It seems I've now become the first.

This brings up a 404 for me. I've added device toggles to the wiki page (http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Tasker) using the method detailed here by @oberkc. The load device is used for status then the 'Then' or 'Else' turns the scene on or off. Program is disabled and then run using the 'RunIf' task. Location awareness takes care of ensuring Tasker uses the best available URL (HTTP on the same network - HTTPS when roaming). No MobiLinc required. (I have it - I've just been getting increasingly frustrated with it's extreme sluggishness on my Android devices)

I agree. The more I get into it - the more I like it. I now have a 'scene' on Tasker with buttons that show the current lighting states - pushing one causes the associated light to change state. I have fan 'Up' and 'Down' buttons - and the whole thing is one tough accessible from the notification pull-down on my phone. Pretty sweet. Right now - I'm about to start figuring out how to retrieve state from ISY into a variable - so I can poll on start instead of relying only on the push.

That's much simpler than what I've been doing for some scenarios! However, if a device is 'On' and then turned 'Off' from a dimmer (or anywhere outside of the program) - how would the program state react? I suspect the next toggle would do nothing - which I'm trying to avoid. Also - have you not had the issue of program IDs getting messed up in Mobilice on an ISY sync - causing you to have to re-setup your Tasker/Mobilinc tasks? Instead - I have a program (triggered by a device turning on (then) or off (else) to send a '1' or '0' to Tasker (or '0', '1', '2' and '3' for fan states 'Off' 'Low' 'Medium' or 'high') (see http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification:Tasker) and then implement my 'Up 'Down' and 'Toggle' processes as Tasker Tasks. I wonder if (again - disabled): If LightA is not On Then Turn LightA On Else Turn LightA Off ..would work? Tracking state directly from the device. Tasker would run the If - and the device toggles (whatever it's starting state)? How would you do an 'up' 'down' program for a FanLinc? Would this work? (All disabled) Program FanUP If Fanlinc is Off Then Turn FanLinc Low Else Run Program FanUP2 Program FanUP2 If Fanlinc is Low Then Turn FanLinc Medium Else Run Program FanUP3 Program FanUP3 If Fanlinc is Medium Then Turn FanLinc High ..and then repeat for the down series... Running 'If' on FanUP would increment to the next speed up... I think that would work - thoughts?

I have started a Wiki page on the subject. Feel free to make suggestions here and we can develop this further! http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Tasker Having ISY send device state back to Tasker is here: http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification:Tasker (I plan on making this *much* better when we can include variables and device state in network resources as substitutions in version 5) By combining both together - you can create 'toggle' tasks (turn a device on if off, off if on etc) - or do 'Up' and 'Down' tasks for a Fanlinc. I have not written that up yet.

On boot, if the ISY cannot talk to the PLM, then safe mode kicks in. That stops everything running - even programs. Scenes will function, as the ISY manages link records directly, so scenes are autonomous. It sounds like you may have had a surge that took out hour PLM, and rebooted your ISY - resulting in where you are now. If you want, you can install the 'Z-series' firmware. Its basically identical to the regular firmware, but does not check for a working PLM on boot.