Michel Kohanim

Hi blakevh, THANK YOU! With kind regards, Michel

Hi Leon, The range extender is a good idea (if they have it). The load controller might not be since: 1. It depends on the meter sending DRLC events 2. ISY cannot do anything with it With kind regards, Michel

Hi Leon, Correct, the channel is 21. I do not think channel is an issue. I think the major issue is the wall between your meter (outside) and ISY. What you can do is to get a coax cable (not too long) and bring the antenna closer to the meter. Please note that you do need a 2.4Ghz antenna (you can use the antenna that comes with ISY). With kind regards, Michel

Hi Leon, Repeaters must be Smart Energy profile certified. So, the link to SmartenIt will definitely NOT work. Do you have any other devices that talk to your meter? With kind regards, Michel

Hi Leon, As Teken correctly pointed out, you will need to purchase SEP repeaters and they are expensive. KevinNH is also correct. Can you please check the channel in the Dashboard (under summary)? With kind regards, Michel

Hi EddieRock, Thanks so very much for the update and I am so very glad you got it figure out. Correct, all you need are ports 443 and 8001 to my.isy.io. With kind regards, Michel

Hi EddieRock, Please do make sure that you do not have MobiLinc Connect module installed. Please also make sure that ISY can get out to the internet and, specifically, my.isy.io is NOT blocked on port 443 and 8001. You do NOT need any port forwarding. With kind regards, Michel

Hi rehills, I am so very sorry to hear. ISY can only support one portal: either MobiLinc Connect or ISY Portal. Please send an email to sales@universal-devices.com and let us know which you wish to keep and we'll process a refund for the other. With kind regards, Michel

Hi Rob, I think it would be best to submit a ticket so that we can login to your computer and see what's taking place. With kind regards, Michel

Hi Harold, I am so very sorry to hear. Please submit another ticket and we'd be delighted to get to the bottom of the issues you are having. With kind regards, Michel

Hi universe, It depends on the firmware on the unit. Older versions only support up to 1G and thus my recommendation. With kind regards, Michel

Hi Rob, Ok, in this case, we definitely do need the output from the Event Viewer. With kind regards, Michel

Hi Rob, In that case, do you get status updates from your devices in the Admin Console? i.e. physically turn something on/off and then see whether or not its status gets updated in the Admin Console. With kind regards, Michel

Hello whywork, jerlands is correct. There are two issues: 1. We updated the portal to include aliases 2. Echo does Discover Devices on its own (once in a while and the algorithm for which we do not know) So, if you had NOT done Forget Devices (and rediscovered) after the update for aliases, Echo auto discovery would create duplicates. All you have to do is to Forget All devices and rediscover. With kind regards, Michel

Hi binaryman, I think Steve already responded to your ticket. If this is not yet resolved, please attach a screenshot. With kind regards, Michel

universe, First, you cannot unzip the upgrade file into an SD Card and hope that it works. This is what I suggest: 1. Unplug ISY 2. Put a blank SD Card in 3. Plug ISY back in 4. Do a factory reset (press and hold the reset button for 30 seconds) 5. If RX and/or TX are solidly on, then ISY cannot communicate with the PLM: if you are sure the PLM works with the other ISY, then the unit you got is defective 6. If error/mem lights blink, then you have networking issues. If your router is on DHCP, and you are certain the network cable/router port are OK, then the unit you got is defective 7. If only error light blinks, then the SD Card is corrupt (it can NOT be more than 1GB) or the unit you got is defective 8. If the only light that stays on is Power, then: -- Clear your Java cache -- Go to http://isy.universal-devices.com/994i/admin.jnlp -- If your computer cannot find ISY, then check firewall on your computer or use the IP address of your ISY in ISY Finder 9. Upgrade the firmware to 3.3.10 With kind regards, Michel

Hi Rob, Unfortunately we need the output of Event Viewer (not telnet or shell). One more question: when it disappears, does it appear again without restarting the Admin Console? With kind regards, Michel

I have no clue what they mean! With kind regards, Michel

Hi AJ, You do need the following outbound ports NOT blocked from ISY to my.isy.io: 443 - dispatcher 8001 - proxy You do not need any inbound port mapping. Are you sure your security settings are correct? Please make sure HTTPS Client setting is set to TLS 1.2/Strength All/Verify should be UNCHECKED. With kind regards, Michel

Hi Rob, I need the Event Viewer (Tools | Diagnostics | Event Viewer) ... don't need another ISY/PLM. The only interesting thing in your error log is -5012 which means that ISY could not send a hearbeat to the Admin Console (or other clients). This would NOT cause connect/disconnect and topology. What we need is the output of the Event Viewer on level 3. With kind regards, Michel

Hi Rob, Event Viewer is very important because it is the only tool that has real time debugging information (on Level 3). So, we need to figure out a way to get to the Admin Console/Event Viewer/Level 3 once the bar is active. With kind regards, Michel

Hi David, Thanks so very much for the feedback and I had completely forgotten the mapping (we needed to do this to improve performance). Amazon was very receptive with respect to location. Furthermore, not really wanting to buy Sonos, I hope they come up with multi zone (or grouped) audio and video (Fire TV) distribution as well! With kind regards, Michel

Hi Rob, Does it ever happen the first time that you open the Admin Console? Or, does it usually happen when the Admin Console has been left on for a while. What you might want to do on the latter case is to open the Event Viewer, change the Level to 3, and then see what ISY is complaining about when the bar goes away. With kind regards, Michel

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