MWareman

Definitely before then. It was right when the Maker channel first showed up on IFTTT. 2014-ish I think...

Interesting. Maybe something changed - it's been quite a while since I first tested this.... they used to r next SSL connections ey were not able to establish trust to. I guess that probably changed...

IFTTT cannot call an API with a self signed certificate. It *must* be a paid, trusted certificate (no, cacert or letsencrypt will not work - I've tried them).

You may need to locate separate threads... there are several steps involved and it's not for the non-technical amongst us... From the top of my head.... You need a router capable of registering a dynamic dns name to your home IP address. You need a domain name with a cname record pointing to your ddns name. You need a trusted SSL certificate using the cname correctly installed onto your ISY. (It's rare to find certificate authorities that will issue certificates to ddns names, and the cname trick works around this) You need to port forward tcp port 443 to your ISY. You need to NOT be using an ISP that uses cgnat. Then, you can configure webhooks on IFTTT that can trigger scenes, programs and devices (refer to the API documentation n the wiki). You will need to trust IFTTT with the password to your ISY. Michael.

I have some battery sensors drive a program that turns a state variable to 1 or 0 (for on or off) and also sets the init value. My logic is then driven from the state variable rather than the sensor. That way, if the ISY reboots state is preserved... However, if the sensor changes while the ISY is off then they get out of sync. So, it does not work for all situations.

Forgive me (no coffee yet).... Got some mixed up logic. The not switched element is if you want to ensure that the correct then or else paths are followed when the on or off control signals are sent. Since you don't have a need for the else path, it's not relevant to your situation.... Personally, I'd separate to two programs. The first has the 'If' as you do now, but it simply runs the second programs 'Then' statement. The second programs 'Then' is the same as you currently have, but it's 'If' is empty. This prevents it from terminating at the 'Wait' if the condition changes, allowing the off command to run after then timeout...

The other thing to try is to prevent the trigger from evaluating false when the motion turns off... Change: And Status 'Motion Back Door-Sensor' is On To: And Control 'Motion Back Door-Sensor' is On And Control 'Motion Back Door-Sensor' is Not Off Then, a false condition won't occur when it turns off, but it will restart the timer each time motion is detected....

You mentioned 18 months. Could it be 24? It's pretty common for PLMs to fail in and around the 24 month mark...

Problem is, all geofence apps rely on IOS APIs. So, all are going to behave about the same... On Android, I'm holding out for Agave to add a geofence function (registering the device against ISY Portal as well as managing locations to fence). Another option, now the Locative app is open source, any IOS developer should be able to take that and add ISY Portal registration and location management to make it a better product. However, basic reliability likely won't change because it all depends on device APIs.

This is based on the portal you subscribe to, not the app you use. If you subscribe to 'Mobilinc Connect' - you need to connect Google Home with Mobilinc. If you subscribe to 'ISY Portal' - you need to connect Google Home to Universal Devices. If you don't subscribe to either portal, neither will work...

Insteon is not encrypted, and messages can be spoofed and/or blocked. It requires the attacker to be nearby, but I would never advise trusting Insteon with securing your house or garage.

This can happen if you use an iolinc in certain modes and have trigger reverse enabled. When the 'query all' runs the iolinc will flip state if trigger reverse is enabled. Best solution is to not use an iolinc to control a garage door. It's neither secure or reliable. I also use my Elk, but there are some secure zwave options as well...

Recent IOS and Android versions do not support the old encryption that the 99i supports. Your use may be limited to LAN without encryption.

If nearby, and with a SDR, it's technically easy to sniff and determine the address of the PLM and then any arbitrary device, by sniffing and observing. Find a house with the garage door kit and you'll be able to open the garage door at will. Oh, and there are in fact Insteon interfaced door locks (morninglinc).

It's also common for companies with agreements like the above to have NDAs in place that prevent talking about the other parties plans, products and sometimes even the fact that there are any agreements in place. Sent from my iPad using Tapatalk

The ability to work without a PLM was introduced when the 994 got zwave (or shortly afterwards). It's not available with the 99i. Without a PLM, it will always boot to safe mode I believe... Sent from my iPad using Tapatalk

You cannot send direct Insteon messages to non-primary KPL buttons. You must put each button into a scene (as a responder - to create scene responder records) and then turn the scene on or off from your program to light or extinguish the KPL button as you need.

I have not tried this yet, but for the scenario where you have a KPL and LampLinc in scene, why not assign the spoken to the LampLinc and have the status change of the LampLinc run a program that turns on (or off) the scene so the KPL follows? The KPL would operate the scene, so it works naturally locally. Google Home can get the status of the device when asked. The KPL will update when Google Home directly controls the LampLinc. The only issue comes up if the LampLinc is in multiple scenes, but if that is not the case it may work around the issue. Sent from my iPad using Tapatalk

Before Agave, I used only Tasker to control the things I wanted, and AutoRemote for updating widgets based on iSY events. I now use Agave, but have kept the AutoRemote bits. And yes, I purchased Mobilinc (Android) a long time ago. It's shelfware now mainly because it simply hasn't kept up. Anyway, my Tablet is IOS, and I do use Mobilinc there. I actually like the solution on iPad.. Sent from my iPad using Tapatalk

By the question, I assume you have the Android version. The IOS version has seen improvements over the last couple of years, but the Android version got Tasker support, then all development appears to have stopped on it. Most of us have switched to Agave.

No real need. It's pretty easy. Log onto https://my.isy.io Next to your ISY, select the 'ISY Web Access' tool That's it. Michael.

The basic steps (out they are not basic really) are as follows: Configure your router to update a dynamic dns provider when the external IP changes Purchase and install SSL certificate onto ISY for the dns name Configure port forwarding on your router to allow external machines to access your ISY SSL port Access remotely using the native web browser on just about any device via https://dns.domain.name (whatever name you got). Not many ssl issuers allow carts for ddns names. I work around that by doing ddns with my own domain name. You can do this with a cname dns record pointing to your ddns name - and then getting the certificate for the cname. An alternative is to subscribe to either ISY Portal or Mobilinc Connect - both provide remote proxying to the web interface. No port forwarding, ssl certificate or ddns tinkering required. Sent from my iPad using Tapatalk

Our local code inspector requires wire nuts to be electrical taped. Not sure why. Sent from my iPad using Tapatalk

Do you have more than one ISY? It was my understanding that this was not necessary anymore as the Portal should auto select the ISY when there is only one in the account. It's mentioned on the Alexa page, but in the context of more than one ISY registered to the account. You are absolutely correct though that this is missing from the Google Home page. Sent from my iPad using Tapatalk

To use the ISY Portal, that's a different module. The purchase of the module enables a two year subscription to the portal. The Mobilinc module ($1) is the module needed to connect to the Mobilinc Connect subscription portal service. You cannot have both (as you are finding out). You will need to contact support to have the Mobilinc module removed and refunded if you wish to continue using ISY Portal.