Michel Kohanim

Hi SteveSBE, Please review this article for some mitigation strategies: http://wiki.universal-devices.com/index.php?title=INSTEON_Random_All_On_Events With kind regards, Michel

Hi bgrubb1, Yes, in the portal: 1. Click on Select Tool for your ISY 2. Choose ISY Information 3. Copy the "URL to ISY" ... this is the URL to your ISY, so all the REST commands should be appended to this URL Please note that your credentials are portal credentials and not ISY's. With kind regards, Michel

Hi jddiebolt, Please do be kind enough to submit a ticket. It seems that your port forwarding rules were pointing to the old address. With kind regards, Michel

Hi jddiebolt, You can use DHCP reservations instead of using static IP address. They have the same effect with the advantage that if you ever change your router, you don't have to worry about resetting network settings for ISY. What's your ISY's firmware version? If not 4.3.26, please upgrade and make sure both your UI and firmware are the same. With kind regards, Michel

Hi dbuss, Are you connecting the Admin Console to ISY locally or are you remote? With kind regards, Michel

Hi MWareman, Thank you. So, basically a notification that pops up on the screen (instead of text)? With kind regards, Michel

Hi jdddibolt, I suspect ISY cannot get out to the Internet. If you have configured your ISY with a static IP address, please revert to DHCP or use 8.8.4.4 as your DNS. With kind regards, Michel

Hello all, All great solutions alas I think they would make life very difficult for the user. At the moment, and unfortunately, we have no plans of forcing things into Metric vs. English including temperatures. With kind regards, Michel

Hi DavidG, What is notification loss? With kind regards, Michel

Hi SirParadox, There are two issues here which are not related. One is enabling remote access and the other, and not necessary, is to install self-signed (or otherwise) certificates. For the first issue, it seems that your router is not UPnP enabled. And, it's really not a good idea to use UPnP to do port forwarding (that's why File | Enable Internet Access does not work). It's best to create manual port forwarding rules in your router to the https port on your ISY (do NOT forward to the http port): http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Remotely_Connect_to_Your_ISY#Configuring_a_Non-UPnP_Router Please note that File | Enable Internet Access and manual port forwarding rules are mutually exclusive: once you create manual port forwarding rules, you should NOT do File | Enable Internet Access. Once you have this resolved and you can access your ISY remotely, optionally, you may want to install a certificate: http://wiki.universal-devices.com/index.php?title=Main_Page#Network_Security With kind regards, Michel

Hi PhanTomiZ, I do not think you did what I suggested. Right mouse click on any Program then choose Status icons. With kind regards, Michel

Hi ronbo, Thanks so very much for the feedback and that's precisely the issue. We did start with literals but Amazon told us to use slots instead. I am not sure why the recommended it in the first place but this slot mechanism does not work very well and, on top of that, skills that are large (such as ours) cannot even be saved. So, in an effort to give Amazon more feedback, we went back and tried literal and, again, the only way it made any improvements was to have less samples. So, it seems that slots/literals both have an issue when the number of samples is large. With literals, there's another drawback: what Echo responds with has to be altered. We have provided all these feedback to Amazon and they said that they had sent it to their development team for review. And, we are waiting .... Thanks again and with kind regards, Michel

Hi stephan, PRO has the same processor. If you are not already on 4.3.26, then you should try it since it should take between 4-6 seconds for a 2048 bit certificate and 2-3 seconds for 1024. With kind regards, Michel

Hi Drexx3, Please make sure the host type is ISY in MobiLinc configuration and that the https URL is my.isy.io. In short, it really shouldn't matter unless there's a bug somewhere. With kind regards, Michel

Hi mwester, We would like to know about these bugs. What error were you getting before you rebooted ISY? With kind regards, Michel

Hi Joe, Thanks SO very much for the update and one which we shall use in our tech support documentation. With kind regards, Michel

Hi John, Thanks for the update. Was this a brand new device? With kind regards, Michel

Hi snowtech, First of all, thanks so very much for your interest in using ISY. I cannot give you a business idea. This said, I can tell you what our business has been like for the past 10 years and, pretty much, you are pretty much correct: "selling the idea that you can just control the lights with your phone doesnt even convince me..." This is precisely what we experienced about 5 years ago and it got worse with the introduction of SmartThings and Wink. i.e. Remote Control but very little automation. This does not mean that there's no market for simple control and alert systems. It just means that we are not that type of company and I am not sure you will be making money if you were to offer those solutions (since they can do it themselves). So, we shifted our focus to energy management and especially for commercial venues: tangible results of saving energy/money. With kind regards, Michel

Hi George, thanks so very much for your vote of confidence. It means A LOT to us and what we strive for. Hi James, thanks so very much. There is definitately a problem with how Alexa assigns things to slots. We have to wait for them to come back from vacation and work on it together. In the meantime, can you use names that you used for your devices? In the case of programs, it seems that one word names work better than two. Also, Alexa converts things literally. So, test 1 will not work but "test one" might. Thanks again so very much for the feedback and your patience. With kind regards, ​Michel

Hi mwester, It uses RS232. With kind regards, Michel

Hello john410, Quick suggestions: 1. Some LampLinc models require a load before you can link them. Please try plugging a load to it 2. Please go to Link Management | Advanced Options and make sure Automatic is checked (it should be because I see I2 traffic) With kind regards, Michel

Hi PhanTomiZ, Right mouse click | Status Icons. It should work remotely as well UNLESS you are not getting any status updates from anything (perhaps firewall?). With kind regards, Michel

Hi James, I was about to respond to your email just now! The main issue is the way Echo tries to put things into slots. And, on top of that, the manner in which it figures out what's permissible in each slot. When we got started, Amazon asked us to put as many samples as possible for each slot so that Echo can use them for inferences. After long and arduous testing on our side, it seems that Echo works much better with much fewer samples (perhaps it's timing out?) and we have reported these anomalies to Amazon. They're going to get back to us with an answer. In the meantime, please start with a program called test. Check your Echo app while you are instructing Echo and make sure it understands you as it should. With kind regards, Michel

Hi Joe, The issue is that you are using a browser bookmark pointing to your old ISY. Instead of using a browser, 1. Clear your Java cache: 2. Go to http://isy.universal-devices.com/994i/admin.jnlp With kind regards, Michel

Hi Amigo, In 5.0.x we plan to add support for multi-users and that's why you see those. This said, it's still a plan and I cannot give you any ETAs. With kind regards, Michel