MWareman

Even with the local Hub emulator, your voice goes up to the cloud for processing then back down to Alexa for processing before being sent to the Hub emulator. There is no measurable loss of latency with Alexa sending the voice to the cloud and it simply getting processed there. At least, I'm not seeing any significant latency with my Alexa => (cloud) => IFTTT => Maker Channel => (back from cloud) => Custom .php => ISY setup. Sent from my Nexus 9 using Tapatalk

To complete this... 'Alexa, trigger kitchen light' results in Alexa saying 'Sending that to it'. The light responds before Alexa finishes saying the response. That being said, I have had a few times today that Alexa responded properly, but the IFTTT trigger was not called. Not sure why. I'm using a simple .php script on my SSL protected Apache host so I don't have to store my ISY credentials with IFTTT. It also allows me to watch a log to see the Maker channel call my server and move the credential away from 'Basic' to 'key' based. This will be much easier with upcoming features to ISYPortal. I suspect many will subscribe as it will certainly make doing this easier, and eliminate the requirement for everyone to have their own SSL certificate (as well as deal with the complications involved).

General opinion is that it takes a lot of coordination and effort to have the Hub and ISY share devices. It can be done, but my answer to your question is 'No'. Soon, we'll have official and native ISY /Alexa integration via the ISYPortal. Better to wait for that IMO. Sent from my Nexus 9 using Tapatalk

FYI - the .php I'm using at at this post: http://forum.universal-devices.com/index.php?/topic/17278-Amazon-Echo-added-IFTTT&do=findComment&comment=154349 Having trouble keeping all the ISY/Echo/IFTTT threads straight... Sent from my Nexus 9 using Tapatalk

See http://forum.universal-devices.com/index.php?/topic/17278-Amazon-Echo-added-IFTTT&do=findComment&comment=154349 Michael.

If you have no trusted SSL on your ISY then yes, its a security issue. Even with a trusted SSL certificate on ISY, you are still trusting your ISY password to a third party. Two workarounds: 1) use a proxy script behind SSL, and the proxy script calls the ISY internally with the username and password. This is what I am doing (currently). 2) if you use ISYPortal, setup a secondary (non admin) user and use that credential against ISY portal in the Maker channel. I've not tested this - I suspect there will be 'interesting' escaping needed... Both of these need a trusted certificate. Trusted to IFTTT - that means a paid, real certificate. Not a self-signed one. Eventually, this will get easier with ISYportal (on good authority!). Until then, I advise the first option (a script proxy).

What details are you after?

Annnnd it's back. I've got a IFTTT setup now to call the Maker channel with a (secure) URL on my webserver in response to 'Alexa, trigger cabinet lights'. THe URL is a .php file that calls 'runIf' on a toggle program on ISY. Pretty sweet! First run had a few seconds latency - but newer runs happen very quickly...

IFTTT 'down for maintenance'.... Too many Alexa users linking up? [emoji14] Sent from my Nexus 9 using Tapatalk

So it seems either X10, or Echo, or Siri. You cannot have more than one.... :/ Sent from my Nexus 9 using Tapatalk

Can the Hub control X10? And have the X10 devices be assigned names (for Echo)? (I've seen mixed reports on this....) If so, couldn't X10 be a bridge protocol between the Hub and ISY programs?

Don't know about other mobile apps, but Mobilinc can (securely) connect to the Portal without the need for a certificate or port forwarding. Sent from my Nexus 9 using Tapatalk

Just out of interest, how long were the last recertification cycles? Michael.

That's a question you'd have to ask AT&T. As far as I'm aware, this is standard for their email-to-sms service. I've had success using the network module to send SMS via Twilio, but its not a free service. You might be able to use IFTTT to forward emails to SMS and have a consistent number as well.

Can't speak to most of the rest, but given that the main reason people get the ISY over the Hub is this. I'm pretty confident that you'll lose this ability going the other way.

Hopefully, it will be approved soon.... And the viral marketing from us early adopters can commence in earnest!

I agree with the static IP on ISY being the likely cause, but changing the subnet mask on the router won't help. If a client on 192.168.0.4/24 needs to talk to a server on 192.168.1.4/24 (on the same broadcast domain) the subnet mask on both the client and the ISY needs changing to /16, not the router. It would be best to simply add a secondary IP on the client, so 192.168.0.x/24 is default, and 192.168.1.x/24 is a secondary IP, and leave the router alone. That way, the client will be able to communicate with both.

Thanks for the information - even though it's not good news.

No fan control options on the thermostat. Besides, the fan is controlled by a separate Honeywell vent controller. I'm also confused - the document says both 'single speed' and lists that multiple speeds are possible.

Thanks for this! Very helpful. Seems the motor is claimed to support multiple speeds, but I'm not sure how to use that. I'd like the furnace fan to run full speed for heating or cooling, but low speed for periodic air mixing. Not sure how to do that - I guess I need to RTFM...

Sounds like its time to put a clamp meter directly onto the fan - to see if it's that or something else.

So, 'Alexa, ask my home to water the lawn'.... I like it!

I will say, the HVAC system is very tight. Extremely low leakage - all joints taped, all returns ducted. I personally checked every joint before the drywall went up! The builder installed the ventilation controller and there is a solenoid damper that opens to allow ventilation. As far as I can tell, the main fan is a single speed only, but I am *very* surprised it draws so much power. My moving average is about 350 watts, and it consumes more power than my pretty extensive MythTV system when it's recording on 4 tuners, transcoding and playing back all at the same time. Honestly, at this point I'm not sure if this is 'normal' or not. It's a carrier, and supposed to be pretty efficient....

We have a Honeywell ventilation controller hooked to our system able to override the fan to distribute air separately from the heat or cool cycles, and it self adjusts to the cadence of the heating or cooling needs. Seems to have about a 1 on 2 off cadence to it, unless the stat is calling for heat (or cool). Problem I have is that while only the fan is running, the furnace circuit draws over 600 watts! (According to my Brultech meter). It's a new house (just passed 1 year), and a very modern high efficiency furnace.

Remember, as far as I understand there are two APIs UDI is going to be using. The 'Home Control' API and the 'Skill' API. Home control allows a very natural 'Alexa, turn on the kitchen light'. It does not require referencing a skill name, but is limited in vocabulary (by Amazon) to very common commands (on, off, dim, open, close etc...). This is the same API that Hue currently interfaces with I believe... So things that are currently possible to say via the Hue emulator should work this way via ISY once it it approved by Amazon. The Skill API requires the extra 'Alexa, (Tell|Ask) <skill>', but allows the implementer of the skill complete autonomy over the language after the name of the skill. So, things are possible with a skill that are not possible with the home control API, at the sacrifice of having to reference a skill in the verbal command.. Both are in progress, I believe. Michael.