MWareman

Just what I want... Find a Android or IOS phone... With weak security... (As most are) 'Ok Google/Siri, navigate home' 'Alexa, disarm the alarm' 'Alexa, unlock the front door'

I do this as well, but not for the public facing stuff that I need third parties to talk to. I have an API that receives IFTTT triggers and text messages from my VoIP provider for example. If the certificate was not publicly trusted it simply wouldn't work.

I don't know... Think of the zwave chip as a small independent embedded computer. My understanding is that a regular ISY backup does not ask the zwave chip to backup first, so if you never do a specific zwave backup you'll never back that piece up. However, chances are you could do a factory reset of ISY and your zwave network will still be intact on the zwave chip, and those nodes will automatically come back. I think... [emoji14]

I believe the zwave backup backs the zwave chip data up onto the ISY. It's then included within the ISY backup. I could be wrong though...

Every trusted free cert I've come across is short lived. I'm not going to mess importing certs more than necessary. Which CA are you using? The procedures vary by the CA - but most will have an intermediate that you have to separately import into ISY, along with the root. If it's a CA I've used before I might be able to help. If not, it's been on my list to document, so I'll give it a try for you. Michael.

Choice is good, as are opinions. Nothing wrong there. I do find it a shame that incorrect causes are blamed for issues though. Also, competing simply by downplaying your competition does not sit well with me. I believe people are moving away from Mobilinc Connect because of the neglect of Android as a platform for so long. There did not used to be a choice, now there are. For a couple of years, I was a Mobilinc user (and Mobilinc Connect subscriber). I had the camera and Elk plugins as well. Then I switched to Android, purchased Mobilinc (without research - silly me) then the next day went to add the Elk and camera module and - sorry. No modules on Android. Literally years later, this hasn't changed. I went to the effort to build my own SSL proxy and set of Tasker routines to replace Mobilinc, integrate my cameras and Elk and life has been good. Mobilinc lost me as a subscriber because they don't support Elk and Cameras on Android even before ISY Portal came along, and I'm certain I'm not the only one. ISY Portal has allowed me to remove my custom SSL proxy. That on its own is worth the price of admission, for me. If you are on IOS, and plan on staying there, the combination of Mobilinc (app), Mobilinc Connect (portal) and ISY is actually very good though. I really liked it while I was using it. Just accept that IFTTT integration means you have to give your Mobilinc Connect password to IFTTT. The combination of Mobilinc (app), ISY Portal and ISY is also very good. You'll benefit from the upcoming multi location awareness, you'll just have to install Locative since the Mobilinc geofencing is tied to the Mobilinc Connect portal. If you are on Android, I simply cannot recommend Mobilinc at all. Other solutions provide greater benefit either for the same money or less. Unless you really like the UI.

You know you can use Mobilinc (the app) with the ISY Portal (or even with no portal at all)? Personally, I like the ISY Portal better that the Mobilinc Connect portal. The integration with IFTTT allows keys on the ISY Portal, so you don't have to expose your portal password to third parties - a big security no-no. That being said - the benefits really come down to what mobile device you use. If you use IOS, there is more benefit to the Mobilinc Connect portal. As has been said, development of Mobilinc on Android has really lagged, so you would be better served getting the ISY Portal and using Agave instead.

Remote access works fine against the ISY Portal. For geofencing, look to the (free) Locative app. Currently, you can report location events via an IFTTT URL on the portal, but soon there will be full multi device, multi location functionality...

Paul, I'm interested in finding out more about your humidity control algorithm, and how you've implemented it on ISY. Looking to do the same myself! (Currently, I manually adjust down the humidistat as the outside temp drips... Not good!) I have most of the hardware interfaces done (ISY can turn on/off the humidifier, one-wire temp sensors in the air return, air send and outside). Just need a humidity sensor that can feed data to ISY... Michael.

Another way to think about it. Once triggered, a programs 'Then' and 'Else' clauses run 'atomically' - they will complete without interruption - EXCEPT when 'Wait' or 'Repeat' is encountered. If the triggering condition has changed when 'Wait' or 'Repeat' is encountered then the run is aborted and 'If' is reevaluated. So, if you have a program that triggers on a state variable being 1, and in the 'Then' you set the state variable to 2 in the first command and 3 in the second. If you then manually set the state variable to 1 it will result in it being set to 3 - since without a wait the trigger will not be rerun on the first step. If you insert a wait between the two set variable commands - the 'Then' will trigger and change the variable to 2, the wait will be encountered allowing the 'If' clause to be evaluated again. If is reevaluated (now being false) WI run 'Else'. Nothing there so the variable ended up at 2. Sent from my Nexus 6P using Tapatalk

Hopefully, if it does not work for your mailbox you will find the tags utility useful in other areas. For instance, fridge, freezer and attic temp/humidity monitoring. Hopefully, it will work well for you where it did not for me - not sure why.

Benoit, might be worth suppressing the menu option if the ISY version is < 5.0.8T1 - that way it won't cause tickets in the meantime... This should probably be a standard thing when a portal feature requires a minimum specific ISY version to operate properly...

It's accelerometer and gyro based sensor - not a magnetic, reed or other mechanical tilt sensor. There does not appear to be a place to connect anything, but the do have an alternate product that does use a magnet the may work. I'll have to pick one up to see... As far as power output - there does not appear to be a way to set it - but there is a way to test what it's doing. The tags will lower their transmit level until the tag manager does not hear them anymore, then raise it again. Looking at the graphing a the tag is at max power, and the manager simply cannot hear it. However, when the mailbox is closed the manager can send to the tag (it beeps when I send an arm command, for instance - but the ack never gets back to the tag manager). It's very odd - especially since the mailbox application is one specifically called out by them for these tags.

It's a PRO tag. I have no issues with the standard tags inside the fridge and freezer - both are further away from the tag manager even. I have two other new tags that I'm going to attach to my gates. They are also further away, so I'll see how they go. The mailbox tag only appears to work when it's separate from the mailbox - even just being attached to the door with Velcro seems to kill connectivity...

The tag manager is needed to receive the wireless signal from the tags, and relay it to the cloud service. The Kumoapp server generated the rest call, and sends it to the tag manager to send to ISY. So, yes. The Tag Manager is an assent ISP part of the system. In my case, my experiment is not working. Even though I only have about 12' between my tag manager and tag, when the tag is in the mailbox I am unable to communicate with it...

Only one portal can work - either 'Mobilinc Connect' or 'ISY Portal'. Mobilinc (the app) can work with either, or with neither. Of course, it's easiest to use Mobilinc with 'Mobilinc Connect'. The other options are well documented in the forum and wiki (using the Mobilinc app against 'ISY Portal' or with a port forward directly to your ISY).

What version is the switch? All newer ones don't have the all-on code in them. Best to switch it around with another device that is an known all-on sufferer and reproduce. That way you know for sure.

Ahhh, yes. Sorry. Forgot about the 'Play' resource. I have my ISY program queue the resource then send play. Sorry about that! Play: POST /MediaRenderer/AVTransport/Control HTTP/1.1 Host: <ip.of.sonos>:1400 Connection: Close Content-Type: text/xml; charset="utf-8" Content-Length: 266 SOAPACTION: "urn:schemas-upnp-org:service:AVTransport:1#Play" <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <s:Body> <u:Play xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"> <InstanceID>0</InstanceID> <Speed>1</Speed> </u:Play> </s:Body> </s:Envelope>

I have my sonos directly play a .mp3 stored on my NAS with this network resource: POST /MediaRenderer/AVTransport/Control HTTP/1.1 Host: <ip.of.sonos>:1400 Connection: Close Content-Type: text/xml; charset="utf-8" Content-Length: 486 SOAPACTION: "urn:schemas-upnp-org:service:AVTransport:1#SetAVTransportURI" <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <s:Body> <u:SetAVTransportURI xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"> <InstanceID>0</InstanceID> <CurrentURI>x-file-cifs://<ip.of.nas>/announcements/alarm_set_to_arm_away_in_5_minutes.mp3</CurrentURI> <CurrentURIMetaData></CurrentURIMetaData> </u:SetAVTransportURI> </s:Body> </s:Envelope> Change <ip.of.sonos> to the IP of the sonos zone device, and <ip.of.nas> to the IP of the storage. The storage must have a share set to allow 'Everyone' read access (since the sonos will not authenticate). This way - you can define many network resources, each pointing at a separate .mp3. The permissioning of the share on the nas was very finicky though....

True. I use MythTV, and when MythTV is playing something I opt for network screen pop-ups instead. Much less distracting.

Tonight (when I get home), I'll find my .PHP script. I have built an API that calls the Google TTS service and references an mp3, saving the mp3 for future use. It then directs Sonos to play it. I'll see if it can be modified to be call specific mp3 files directly. I do everything thru a single zone currently though. I gave not looked into multi-zone announcements (yet)

I guess I should have said 'rain proof'...

I use them to monitor temp and humidity in several points around my house, including in my fridge, freezer and wine chiller. I just ordered three waterproof tags for outside use (mailbox and my two yard gates). Been using them for a while now, and am very happy with them.

On the first question, only you can decide. Just because someone else can access the hardware token does not mean they could logon as you. They need your password as well. The more important consideration is how long would it take you to notice it was missing if a guest removed it? Personally, I wouldn't (but that's mainly because I probably wouldn't notice for a few days....). On the second question. The Gmail app uses a variation of oAuth to authenticate (sometimes called 'bearer' authentication). 2FA is only used on initial setup to get the bearer credential and from then on the app 'just works'. No additional auth. If you lose your phone, you can revoke the oAuth authorization from your account online, and 2FA will be required next time to re-link. Another reason not to configure a recovery account on your phone's Gmail app!

Or you can put a switch in the strike plate to detect locked (hooked to an IOLinc)... Never done it myself, but there are references out there. However, a zwave device is better. Zwave is at least built for security, while Insteon is not. I wouldn't put any lock on Insteon.