Jump to content

Please pass through portal commands to both of my ISY's


starmanj

Recommended Posts

This is starting to cause me problems.  My partner gets very upset when suddenly her commands stop working because I'm working out of my other ISY.

I know this is something you guys said you would fix, but how hard is it to simply send my commands to all my registered ISY's?  For some reason it's blocked now.

Link to comment

Right.  All my devices are uniquely named, I just want to control my devices wherever they are, on both ISYs, without having to switch "favorite" ISY in the portal.  Just send my command from Alexa to both ISY's.  Let the ISY ignore the command that doesn't control the device.  I don't want two separate Amazon accounts...

Link to comment

I want to give a verbal echo command and have it execute on either one of my ISY's.  I can't.

My problem is when I am at one location, I have to go to the portal and change the "preferred ISY" to that location.  I am switching ISY location constantly, so nothing works until I change portal settings.  I want to manage all my echo's with one login, not two.  I am asking the option to have a single Amazon login, and give an echo command from any device, and have the portal send that command to both ISY's and let the ISY execute.

An alternative is to specify which ISY to send the command to within the Portal, so the command is sent to the correct ISY (and not both).  Eliminate "preferred ISY".

Make sense?  I love the portal!  It just doesn't work for me because of this issue.

Link to comment

I wouldn't be surprised if this is an issue with the google and amazon api.  I think they are both two way communication (Google is for sure).   IFTTT is not limited to the preferred ISY, so you could run it through IFTTT/portal.  But last I checked, all IFTTT commands via Echo had to start with the word "trigger".

Or get a second Amazon account.

It would be nice, however, if the portal could map it all out to multiple ISY's.  But, your situations is probably only a very small percentage of their customers and they may prefer putting their resources towards things that have a higher customer usage.

Link to comment

That may be, not many of us likely have two ISYs, but why put in the functionality into the Portal to have multiple ISYs in the first place?  I purchased the portal when I saw it could handle two ISY's, but now discover it can't without a significant disruption to me-- why should I need two Amazon accounts?  I do everything, buy everything, have Amazon music etc., through my one and only account, that I pay for via Prime.  And I can't believe merely allowing broadcast of Portal commands to both ISYs (vs just one) is a major software change...

Anyway Benoit thought my request made sense...

Link to comment
2 minutes ago, starmanj said:

That may be, not many of us likely have two ISYs, but why put in the functionality into the Portal to have multiple ISYs in the first place?  I purchased the portal when I saw it could handle two ISY's, but now discover it can't without a significant disruption to me-- why should I need two Amazon accounts?  I do everything, buy everything, have Amazon music etc., through my one and only account, that I pay for via Prime.  And I can't believe merely allowing broadcast of Portal commands to both ISYs (vs just one) is a major software change...

Anyway Benoit thought my request made sense...

I agree, it does seem like having multiple ISY's on the same account serves limited functionality to anything other than the "preferred".

If you don't have a ton of stuff, you can relay commands from one ISY to the other.  You would create webhooks for the secondary ISY and then have the primary ISY send the webhook.  You would write programs that trigger a network resource with the webhook.

Link to comment
17 minutes ago, starmanj said:

Great idea, way beyond my abilities sadly...

Nahhh.  It is hardly any different then setting up Amazon commands.  Just use the portal to create a webhook just the same as creating an Amazon command.  Then copy and paste the webhook into ISY network resource.  Then write a program that runs the network resource from the "then" clause and a second webhook to turn the light off goes in the "else" clause.

Now ISY 1 has a program that runs a light on/off in ISY 2.  So Amazon controlling ISY 1 now has control of ISY 2 via the webhook "relay".

Link to comment

So I write a program for each device it controls?  I have a tremendous amount of devices...this adds a level of complexity, defeats the reason why I'm using the Portal (I could easily just use my own server to execute amazon/google commands on the ISY but don't have time to caretake that).

Link to comment
35 minutes ago, starmanj said:

So I write a program for each device it controls?  I have a tremendous amount of devices...this adds a level of complexity, defeats the reason why I'm using the Portal (I could easily just use my own server to execute amazon/google commands on the ISY but don't have time to caretake that).

Well most people don't care/want/need to control every device via Amazon.  But c'est la vie.

Link to comment

That is interesting.  I thought once the portal gets the API command from Alexa, the portal simply passes the command to the "preferred ISY".  Therefore the Portal could just pass the command to both ISY's instead of just one.  Or the Portal can pass the command to the ISY associated with the correct device.  Why would Amazon be involved after passing the command to the Portal?  I might not understand where the logic is done on the commands...

Link to comment

Archived

This topic is now archived and is closed to further replies.


  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      36.6k
    • Total Posts
      368.3k
×
×
  • Create New...