MWareman

When I tried to clear a spoken name, it gave me a 400 error. It also filled all spoken name fields in with the device name, most of which are structured for ease of use in the Admin Console, and are not suited for voice recognition. As an aside... I think an ISY level option to have Alexa ignore the natural device names would be useful. I also think that spoken name fields should default blank. That aside, are you saying I should delete the device on Portal?? Or just clear the spoken name field? When I adjust the spoken name field on Portal - does this sync back to ISY? They don't appear to - which makes me wonder why the recent changes to allow them, and have them show up in the topology report.... Michael.

Benoit, Will we be able to tell the portal to exclude a device/scene/program from the skill? I have over 200, and I only need less than 10 for my Echo (given its location in my house). I'm sure that by filtering devices/scenes/programs, a better, faster match to verbal requests can be made. Thanks! Michael.

I don't think so... But I'm an Android user.

You can pass credentials in the url, but its a function of the browser to do it correctly. It works fine from the Maker IFTTT, but you have to url-encode the username (die to the @), and also possibly the password (if URL illegal characters are used). Michael.

Clever!

In the skill instructions - it tells us to 'Alexa, tell izzy to refresh devices' after the spoken name is changed. I just spent some time adjusting my spoken names on my ISY - then issued this command only to be told that this was no obsolete - and to update spoken names via the portal. So - I logged onto the portal and sure enough there is now an 'Amazon Echo' option on the menu... So far so good. Now the issues... It's worth noting that all my device names are encoded - so I need to use spoken names throughout... 1) Changes on the ISY don't appear to be propagated to the portal. How is this supposed to work... I would have thought that 'Refresh' should have retrieved the latest spoken name fields from the ISY but it does not appear to do that. 2) Portal does not list programs. How do we trigger programs now? 3) It seems inaccuracies (at least in my case) come from having nearly 200 devices with encoded names... all of which appear to have their node names 'copied' to the spoken field on the portal. If I try blanking out the spoken names of devices I don't want to control - I get an error 400.... I don't want all devices to have spoken names!! Can we, by default, not assign one??? 4) In the list - I like the 'Search'... Can we add the ability to filter by type? In my case - I only want to assign spoken names to scenes (and programs). It makes no sense for me to see devices. That's it - so far. However, after manipulating names in the portal, my skill has gotten *way* more accurate and responsive. Michael.

Yes, but I'm not sure how it can be implemented without help from Mobilinc itself. I don't think it's possible otherwise. It would be easier if you were able to figure out how people can keep both Portal modules active if they wanted to - Mobilinc Connect (for IOS users who want these additional features) and ISY Portal (for Alexa and other futures). Us Android users don't really mind (since we don't lose anything), but IOS users do lose functionality by switching, any some don't seem aware of it.

Mobilinc (IOS) when using Mobilinc Connect has support for selecting events to trigger pop-up notifications in app (delivered from the Connect Portal servers via the Apple push messaging service). It just used the incoming stream of events from the ISY connection and does not need any changes on ISY itself to work. Us Android users never had this, so we are (mostly) using services like Pushover (which works on IOS as well as Android) and the networking module on ISY so deliver push notifications. The only downside is you have to configure your notifications on the ISY, you cannot do it from your mobile device.

Geofencing and notifications are a feature of Mobilinc Connect. They won't work at all on ISY Portal. I cannot speak to the status issue. I'm on Android, and I initially had the same issue. After a few hours it resolved itself for me.

Don't know about ekeypad, but Mobilinc works via the ISY Portal. Just configure it as any direct connection to an ISY, but use HTTPS only, the host name my.ISY.io and your ISY Portal credentials.

What is the firmware and UI version of your ISY? Some newer devices don't work correctly with older versions on ISY firmware. Michael.

They have. See http://wiki.universal-devices.com/index.php?title=INSTEON_Random_All_On_Events Michael.

I always advise to never hook a garage door opener to an iolinc. Insteon does not contain the needed security protections.

In my case, the portal offers Alexa integration (although still early in development) as well as multiple usernames and passwords. This is useful for my families mobile devices. If my Daughter loses her phone (again), I only have to change her password instead of messing with hundreds of resources credentials after changing the single password that a native ISY connection supports. Worth every $ to me - even in its current form.

Something is wrong. ISY Portal didn't exist in 12/2014. It only came into existence a few months ago, but definitely not until well into 2015. I'd advise a ticket, assuming that UI and Firmware are up to date and the latest.

After you've got the UI in sync with the ISY version, try right-clicking the PLM and restoring it. It sounds like the PLM may be showing early signs of problems. How old is it?

Don't know about the others, but the Hub uses an online proxy that Amazon connects to. Everyone Hub connects, and Amazon only has to connect to Smarthome proxy. This is how the ISY works with the Portal.

You could also use a program. When button 3 'control' on, turn on the two scenes. When button 3 'control' off, turn off the two scenes. There will be a small delay between them though - the two scenes will be adjusted sequentially instead of simultaneously, but it will reduce management. It's another choice.

Michel, I just sent a follow up email. For some reason, Mobilinc is now getting status updates real time with changes. This was a couple of hours after initially configuring Mobilinc to my portal account. Very strange - but it's all working correctly for me now. Michael.

Confirmed: the uuid is in the preferred ISY field. Also, only one ISY is in my account. Although now the ststus is populated on starting Mobilinc on the tablet as well. I'll send the uuid to you. Michael.

I tell a lie. Just reconfigured Mobilinc on my Nexus 9, and I'm not getting any status at all - even on start.

When I start Mobilinc, the devices current status fills in now. However, when I change a device, the status does not update. There appears to be no push status back to the app currently. The portal itself updates though, and the device responds quickly, which is nice!

Not sure name prefixes should be there, because the list is going to get HUGE! If we are though, let's add: Zoe's bedroom Moms bedroom Dads bedroom Mom and Dad's bedroom Master bedroom Guest bedroom (The missing singular version) (Can you guess what my Daughters name is?)

I believe so, yes. If the output of the IOLinc is driving the remote then the programming is identical.

Why is 'Door' a device? Shouldn't it be in 'postdevice'?