Michel Kohanim

Hello everyone, Thanks so very much for all the feedback. ISY needs to have an Echo ID (currently tied to an account) for each Echo and this is not in Amazon APIs. This said, however, we did suggest this feature to Amazon and they were very receptive. So, hopefully they can implement it. All this said, there might be another "untested" solution which requires two accounts: 1. Get a new Amazon Account and tie your 2nd Echo to the new Amazon account 2. In ISY Portal: a. Create a Subaccount under your account b. Create a different user under your new Subaccount c. Add your ISY to the new Subaccount d. Go to Admin Console | Portals | Approve the access from the Subaccount e. Login to ISY Portal using the subaccount credentials f. Follow the same procedures for linking ISY Portal to Echo but this time use the Second Amazon account (#1) Please do let me know whether or not this works. With kind regards, Michel

Hi afschmitt, All you have to look at is the first line: HTTP/1.1 200 OK In this case, 200 = command succeeded. So, the main question is whether or not Hue actually did what you asked it to do. With kind regards, Michel

Hi Matt, Thanks so very much. Perhaps it's time to do a remote session to your computer to see what may be going on. Please do be kind enough to submit a ticket. With kind regards, Michel

rrehart, Please do NOT enter anything for username/password and retry. With kind regards, Michel

Hello Automate The World, I am so very sorry that you had to go through this and, yes, we should definitely have some indication of the number of nodes used. With kind regards, Michel

Hi WetCoastWillie, Thanks so very much. This is definitely not normal. Can you please let me know the firmware version for M1 and M1XEP? With kind regards, Michel

Hi GT, We have not heard from Nucleus. With kind regards, Michel

Hi Zesudog, Do you have ISY Portal OR MobiLinc Connect? With kind regards, ​Michel

Hi MWareman, LOL ... well, hopefully 5.0.x will solve some of these problems. This said, we still have to abide by our licensing agreement with HAM. With kind regards, Michel

Hi rebirth24, You do need to close all your browsers (they keep a cached cookie from Amazon) and then redo: Login to the Echo app Click on this link With kind regards, Michel

Hi rebirth24, It was fixed a long while back. With kind regards, Michel

Hello Automate The World, Unfortunately no count anywhere. This said, you can definitely use Tools | Generate Topology for a high level view of where you are. With kind regards, Michel

Hi WetCoastWillie, 1. What is 119.97.146.76? It seems that this device is trying to get to your ISY but does not have the correct credentials 2. I do not see any errors in the log which indicates that ELK had to reconnect 3. Are you using any mobile app that might be doing this? 4. What's your firmware version? With kind regards, Michel

Hi fryfrog, Please do be kind enough to send your request for discount to sales@universal-devices.com. We will definitely consider discount on a case-by-case basis till we figure out what's the best way to address this specific issue. With kind reagrds, ​Michel

Hi Andy, I don't think it can be done: 1. Both Echos are on the same account 2. There's only one ISY 3. The names have to be unique With kind regads, Michel

Hi fryfrog, We do have installer discounts. If you are registered as one, please send an email to sales@universal-devices.com and we'd be delighted to help. With kind regards, Michel

Hello guys, Scott, cyberk does NOT want to open port to M1XEP. This has nothing to do with ISY so I am not sure what ISY/SSL has to do with this topic. cyberk, if: 1. You already have eKeypad 2. Your eKeypad is configured to work with ISY 3. You have the ELK Module 4. YOu have ISY Portal Then, you can simply have eKeypad configurd to ISY Portal (as if it's an ISY) with your portal credentials. It should work. With kind regards, Michel

Hello all, Thanks so very much for the feedback and so very glad that it's working faster for everyone. With kind regards, Michel

Hi Tim, No, you shouldn't have to do anything else at all. As long as you see MobiLinc Portal in Help | About, you should be OK. With kind regards, Michel

Hi Michael, I am quite certain that what is being done is illegal (and we did check with our lawyers). They are providing the service as a commercial entity. There's also an additional aspect: tech support. HAM has been relatively good with tech support and fixing issues. And, this is because we have a licensing agreement with them and SLAs. Perhaps 5.0.x will help those who want to use other weather stations. With kind regards, Michel

Hi Tim, You can definitely move back to MobiLinc Connect. All you have to do is to send a request to sales@universal-devices.com and request for a refund. Please note that MobiLinc Connect might not be supporting the Connected Home API (i.e. Alexa turn on x) and instead you might have to say something like (Alexa tell mobilinc to do x). So, please do consult with them. With kind regards, Michel

Hi Scyto, Yes as long as ISY is not connected to the portal. If it is, then try Discover Devices. With kind regards, Michel

Hello all, The last two service requests were related to MobiLinc Connect Modules still being active. If you have MobiLinc Connect Module (Help | About), please send your UUID to support@universal-devices.com. With kind regards, Michel

Hi interactii, Please send your error log and UUID to support@universal-devices.com. With kind regards, Michel

Hi Mack, ISY's error log. With kind regards, Michel