MWareman

@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.

Safe mode means the ISY cannot talk to the PLM. Try powering down the PLM and ISY, waiting a bit, powering the PLM, waiting a bit then powering the ISY. If that does not work, your PLM may have died.

The 4 tap function is described on page 4 and 5 of this manual: http://www.insteon.com/pdf/2443.pdf I believe that details are in most/all dual-band products manuals. It also describes much about placement and phase coupling. Michael.

I have a Android Wear device - I just have not spent time getting voice integration working on it yet. Pretty neat - but a long way to go yet. I was a Pebble owner before, and its much easier to do ISY integration with that - due to PebbleTasker. But, no voice recognition there.

I remember 'talking' Insteon via a TCP socket to a 'SmartLinc' device, which (unofficially) allowed access to the native messaging stack via a TCP socket. Its a shame that ISY (and most others) never supported this as an option for those that wanted to separate their ISY and PLM with an IP network rather than a serial link.

Time servers send the time in UTC. Conversion to summer/daylight saving hours (and the switch) should be handled by the OS itself. I seem to recall issues last change as well with a prior firmware, though I have not checked my ISY with the current beta yet.

Yeah, that won't work. 443 is SSL and 80 is not. You cannot (normally) port forward port 443 to port 80 and have it work. You also appear to have two definitions that include external port 443 this will cause a conflict. Remove the line labeled 'isy' (its the one that forwards all ports from 80 to 443!). I'm also not sure why you are port forwarding TCP/500 to ISY - but that won't affect your connectivity. Michael.

I'm not sure, but I think wireless devices will only relay to the wire, and from the wire to wireless. They don't relay wireless to wireless. Is this correct? So, the sensor send a wireless message, received by one KPL in the garage. The transmits on the wire in the garage. Its only received by the other KPL in the garage (due to the panel) and then sent wirelessly. We are at two hops (one hop left) with a wireless signal. Arriving in your house, let's say the signal is received on a device on the opposite phase as your PLM. Bang - no more hops left. Given KPLs are usually installed in grounded metal boxes, the range is extremely limited. Actual 'Range Extenders' may help - one in your garage panel, and one on each circuit in your house. Just a theory, and I could be fundamentally wrong. Michael.

I recently had a 6 button KPL (about 3 years old) working flawlessly controlling a fanlinc using only scenes. It was a relay device though - I wanted to change to a dimmer (for the light) - so got a new 6 button KPL (latest firmware). I could not get the scene method to work at all - I had to revert to button grouping. No idea why.

ISY is not really 'trunkating'. Its just only displaying the received header - not the body. The browser only displays the body, but not the header.

I beep a switch every 2 seconds in my laundry room when the light is on and the alarm is armed night. It stops my wife from forgetting to disarm the alarm before opening the garage door. Other than that, I've not found a use for the beep.

Also, the X10 dryer 'bridge' does not bridge Insteon traffic to my knowledge.

Many non-dimmable CFLs and LEDs can also cause the switch to buzz when on a dimmer - even at 100% brightness. I went with relay units where I didn't want to change the bulbs.

You could try changing And Status 'Hall / Hall MD-Sensor' is On To And ( Control 'Hall / Hall MD-Sensor' is switched On Or Control 'Hall / Hall MD-Sensor' is switched Off ) Or you could try programing a query of the device at 9:25pm.

It doesn't. Google have provided the ability to generate 'application specific' passwords that are stronger and random - for those devices that still need to authenticate but cannot do 2fa. ISY is such a device. If you use 2fa on a gmail account, you need to obtain an app password for the ISY to use to send email.

It also means you cannot connect a PLM at the same time, since it connects to the same port. I'm not sure why there is not a 'pass-thru' of some kind, and the ability to chain many together to enable multiple relays to be connected.

I think 'high security' in the google console is two factor security.... Nothing to do with SSL or TLS. When you enable 2fa in your google console, your regular google password will not work for SMTP. That by design. To use SMTP authentication, you'll need to generate an 'application specific password' to use with the ISY, and use that password in the ISY to authenticate (along with your gmail address). Michael.

Forgot that little nugget! Thanks!

With that as your only condition, no question the answer is Elk. I use it - and I'm very happy. Elk becomes a first class citizen in your ISY. However, DSC based systems can be integrated well as well using a RPI based bridge and dsclinc (http://forum.universal-devices.com/forum/40-dsclink/)

You are correct. Yes, to keep running true the conditions must remain true. Additionally, any reevaluation of conditions will cause 'Then' to start over. So, dimming one of the lights (still on though, and still evaluating true) will cause the If to reevaluate and restart the timer. Michael.