MWareman

The Lifemaster Elite 8500 (aka Chamberlain) is a MyQ device with Security+ 2.0. If you have the smart button you cannot wire the IOLinc outputs in the same way. There are no formal instructions for using this device with the IOLinc - its regarded by Smarthome as incompatible. I purchased an additional (wireless) button, opened it up and connected the output (of my Elk, but the IOLinc is the same) to the solder pads on the button. This works flawlessly. An alternative is to use the Python library elsewhere on the forum for MyQ network control, but this will require you to have the MyQ network interface, and will additionally depend on an Internet connection to function.

I believe I may be having the same issue - I just don't use Mobilinc very much and hadn't noticed it.

The ISY separates client and server settings in the Dashboard. SSL server settings affect incoming connections (like the web interface and API), its strength will affect the security and performance of incoming applications, like Mobilinc. SSL Client settings will affect outbound connections, like TLS when sending email and outbound HTTPS network resources. If you changed the ssl client to 'All', it shouldn't affect Mobilinc at all - because they use two separate settings.

I think the reason IFTTT matches well is that it's only trying to match against full phrases that you have defined, rather than breaking your speech into separate words and trying to determine what phrase was spoken from separate words. IFTTT with its whole phrase machine will always be more accurate IMO. However, you have to define each specific full phrase. So 'trigger turn on family light' is very different to 'trigger family light on'. They are different solutions with different benefits and limitations.

All of the details of other options are at the wiki. http://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface Michael.

AFAIK - you must buy a portal module for each ISY separately. You can then add the uuid of each ISY (with an active portal module) to you portal account. I also would like to know about the mentioned fee for multiple ISYs in a single portal account. It doesn't make much sense to me since the portal is subscription and the module is also a purchase, per ISY. We could always create two separate portal accounts each with a single ISY.

This morning, I tried 'Alexa, ask izzy to switch dinette on'. According to app - she heard 'Ask izzy to switch dinosaur' She responded 'For which ISY? Please tell me the alias used in UDI portal.'. I responded 'Home' and she said that the ISY had been switched. Not what I wanted indeed. She should have at least responded that there was no device named 'dinosaur'. Using 'Switch' seems to cause the Alexa to interpret that we want to change to a different ISY (at least in my case). I only have one in my portal account. Michael.

I posted how in a different thread. I'll try to find it. Michael.

Yes. HTTPS is SSL, and it takes serious computation to establish a connection.

I don't really have any recommendation, because I have mine wired to my Elk system for control and monitoring. Looks like that one should work for you though.

Mine is doing this as well with 'ask Izzy to switch ...' Tell Izzy still doing as before...

In my case, the scene for my dinette light has had 'dinette' as the spoken work - all lower case (if that matters). If an exact match is needed - is it case sensitive? In my case though, its not even close on 'dinette', while the Maker channel is spot on each time (this is not using the spoken name - its a command called 'dinette')

'alexa, ask izzy to turn on kitchen' works 'alexa, ask izzy to turn off kitchen' works 'alexa, ask izzy to turn on kitchen island' works 'alexa, ask izzy to turn off kitchen island' works 'alexa, ask izzy to turn on kitchen' works 'alexa, ask izzy to turn on dinette' 'turn on which device?' 'dinette' 'turn on which device?' etc.. I logged onto http://alexa.amazon.com/#settings/dialogs It shows that Alexa is thinking I'm asking izzy to 'turn off doing that'... :/ odd. Then 'buy that'... also odd.. I have a IFTTT/Maker rule for 'Dinette' that calls an ISY program to toggle the light. 'Alexa, trigger dinette' works perfectly - every time. Some words just don't work well I guess, or the IZZY lexicon is large enough that there is greater confusion. I've been thru voice training and it still didn't help with this word. Otherwise - it's working well.

Does it not recognize spoken words with a space in them? Can't seem to get any to work. Single word spoken elements appear to work very well (and fast!). Great job!

Yeah, getting the same thing... I also cannot seem to get discovery to re-run after editing some spoken elements... Edit: Got the refresh to complete. 181 devices this time (160-something last time)...

No. The rfc specifies how a URL is handled. The username[emoji14]assword@ before the fqdn is base32 encoded and added as an 'Authorization' header by the browser, and sent with the GET request after the encryption is negotiated. This means, its safe - assuming you have a trusted certificate making it obvious if you are accessing thru a man in the middle proxy.

I (accidentally) had a capital letter in my email address, and it told me 'unrecognized email address'. Two things: 1) The email address shouldn't be case sensitive... The password should. 2) You should never tell an attacker that the email address didn't exist. You should only ever say 'Access Denied'. Otherwise, an attacker can enumerate valid email addresses in the system. Otherwise, discovery successful. Over 160 devices (in my case). Alexa asked me if I wished to wait a couple of times. Nice. Now I have to go assigning some spoken works to objects. Thank you!!

There are also some zwave controllers that would work more securely.

Iolinc + garage door opener = bad combination...

Not everyone has the skills or the patience/time to setup ddns/port forwarding/SSL certificates/VPN. Clearly, your using HTTP within a VPN. That's why you don't see the SSL performance penalty. I for one don't want to use a VPN. Many others don't. A proxy (such as the portal, or my personal Apache based proxy) with a SSL accelerator chip will be orders of magnitude faster than SSL termination directly on ISY, especially with 2048+ bit certificates. I get instant response using my SSL accelerated proxy, and 5-6 second response using SSL directly to ISY. Alexa needs the portal because Amazon requires the service Alexa is connecting to to be a cloud service. It cannot connect to thousands of individual devices - they must have a single API for accessing all devices. That what the portal provides, and is why its required.

Disappointing to be sure. I hope the certification process is a swift one...

I have a lock command as part of my 'Alexa, send goodnight' program that is sent via the Maker channel. Not at all comfortable having any way to unlock the door via Alexa.... even with an alarm system. I just won't do it!

On the 'Select Tools' menu, select 'ISY Information'. It will pop-up. It uses JavaScript, so if you use an ad blocker you may have to whitelist my.ISY.io. Michael.

Try using Lastpass to automate password entry.

Remember all, the features in the portal are still under development, and (to my knowledge) more functionality is forthcoming. The value proposition is only going to go up. In addition to what was just mentioned, the speed of establishing an SSL connection from clients like Mobilinc and Tasked is orders of magnitude faster that establishing an SSL connection directly to the ISY, due to the computational expense of new connections. Portal has a hardware crypto accelerator I believe to make this really fly. Portal supports more than one credential, and you can turn off a credential if you want without breaking others. Direct ISY access only has one account - and that account is fully administrative. So, use a portal credential in you Mobilinc and lose your phone: just disable that credential. Lose your phone with direct Mobilinc, change your ISY password then spend hours fixing up all the places you used it. There is an even easier token based authentication on its way as well - for better, secure authentication to ISY Portal from services like the Maker IFTTT channel. Plus we can feel good continuing to support UDI, who are working hard to bring us all this goodness...