-
Posts
4959 -
Joined
-
Last visited
Everything posted by MWareman
-
I agree on Jarvis. Love it! However, I don't think it's a good idea to allow Alexa to disarm an Elk. Or unlock doors. Just sayin'
-
Yep.... Agree with you here!
-
Not sure on protocol, but they have a very tight leash on distribution. You have to use their VARs to supply and install. Lots of $$.... I have a neighbor who does installs for a VAR - he doesn't have a system hiself. They don't even give discounts to their own installers.... We also have Crestron at work.... That system is a few years old. Mostly serial connected, some IP APIs. In summary - nice equipment. Lots of $$. And I can do more with my ISY...
-
19" horizontal. I have a 2 post rack, and I figure I should be able to fit 3 or 4 in 1U of space...
-
Awesome - thanks! I had an extra HTTPS:// in there. Thanks for confirming which one was correct. Got it to sync successfully, and I'm able to control everything. I'm an Android (6.0). Confirmed my suspicion that though - Mobilinc is still taking an age to sync on startup. Given it takes a long time locally over http it really does point to an application issue rather than a crypto delay caused by the low powered ISY as generally identified over on the Mobilinc forums.
-
Which URL did you use in Mobilinc?
-
@Xathros, Have you been able to configure Mobilinc to connect to ISYPortal? I've tried the 'Admin Console URL' (with and without the /desc) as well as the 'URL to ISY' (which I realize is the same as the admin console URL but without the /desc and also not encoded). None have worked so far. PErhaps I'm missing something - or perhaps I'm trying something that wasn't intended. Due to SSL on the portal being *much* faster than directly to ISY - I'm wanting to try using this against Mobilinc (which has fallen into disuse for me due mainly to the SSL performance issue). Thanks! Michael.
-
Michel, Can you let us know what the intent of the 'Last connected: 39 hours ago' (in my case just now) is? My ISY is currently connected - it's status shows green. I know the portal supports multiple ISYs - and it wouldn't make sense to report this stat there. I used the Admin console against the portal yesterday - so the number of hours exceeds this. I can only think that this is actually the last login time (browser to the portal)? Is that correct? If so - may I suggest that this changes to 'Last Login Time' instead of 'Last connected'? Thanks! Michael.
-
I'm still looking for a half decent 19" wide rack mount for multiple Pi 2's.....
-
Just to clarify. There are going to be two integrations between ISY Portal and Alexa/Echo. 1) Connected Home API. Limited functionality to whatever Amazon allows (mainly lighting commands), but natural language. 2) Skill. Requires 'tell ISY to...', but functionality expandable by UDI to include things like querying devices, non-lighting control etc. My main concern/question... I'm assuming (and it is confirmed above) that the connected home method will allow on/off (and dimming?) controls of devices and/or scenes. However, if possible can we be able to assign a spoken element to a program and 'Alexa, Turn the xyz on' calls 'RunThen' and 'Alexa, Turn the xyz off' calls 'RunElse'? That would really expand the natural language capability if possible.
-
Some (many?) two-packs of SwitchLincs come pre-configured as a 3-way set - linked together. I suspect that this is what you may have got.
-
Email sent! Thanks, Michael.
-
Be aware that there is no appropriate security on Insteon devices for use as a garage door opener. If your garage is connected to your house, make sure to keep the connecting door locked! (a good idea anyway...)
-
IFTTT only has a 15 min delay on some recipe triggers. Many are quick triggers and activate within a moment.
-
Michel, I purchased the ISY portal a couple of days ago, and after installing the Mobilinc Portal module was gone. That's fine by me - but for the benefit of others is this normal and expected? Or, did not renewing my Mobilinc connect somehow disable the module? Awesome to hear native IFTTT is on the horizon as well! Michael.
-
Yep. I purchased mine this evening as well. Ready now for when the Alexa connected home goes live with it....
-
Michel, I'll send you my uuid to do this. Would I wait on purchasing your portal until after Mobilinc is disabled - or will they co-exist... Thanks, Michael.
-
Virtual devices are on the roadmap I believe, not implemented yet. Michel would be able to confirm (or say I'm incorrect!)
-
I set my subscription to not renew over a year ago.... But the portal is still active in the ISY. I got tired of waiting for the IOS features to come to Android, and implemented them myself with Tasker and the network module.
-
Would this not be a solution for a virtual device, called 'TV'? Have a program trigger on the state of the virtual device. Then you could say 'Alexa, turn on the TV' and have the program 'RunThen'. (Not sure if virtual devices are in 5.x yet.... This would work with X10 devices as well I suspect)
-
Thanks for the correction! I use Android, so I have no use for the IOS only features....
-
Before I jump on this - to confirm that adding this will simply 'disable' the Mobilinc Portal module? I don't have to open a separate ticket to have you do that first?
-
I believe Michel means that you can configure the Mobilinc mobile app to talk to your ISY via the UDI portal - giving you the benefits of remote access (just as the Mobilinc Portal) with added Alexa and whatever else UDI is planning.... However, I suspect you will lose any Mobilinc/IOS specific features, like push notification, geofencing etc - unless UDI implement this is their solution as well. But I think this would require UDI developing their own mobile app.... Choices are good!
-
Why would the synchrolinc not be before the outdoor module? That way, your not cutting it off from power when the outdoor module is off - causing it to fail to respond in the ISY? Could you not simply switch them around and put the synchrolinc before the outdoor module?
-
In post. #26, the PLM link table was confirmed to have the controller records needed. I wonder if this was actually the PLM link table, or ISYs view of it? Possible to confirm that you get this from the PLM itself? Have you tried a 'Restore Device' on the PLM itself? I'm wondering if the link limit was reached in the PLM, especially if it's an older PLM. (Early PLMs had a much smaller link capacity if I remember correctly - I'm not sure if or how the ISY reports this condition....)