Michel Kohanim

Hello everyone, We would love for MobiLinc to support ISY Portal and we'll reach out to Wes. With kind regards, Michel

Hi majorlance, What I think the issue is that whatever is opening the socket (is it Startech?) is not closing it and thus the error. I think GC100 will help. With kind regards, Michel

Hi David, Thanks so very much for the excellent feedback. We do have virtual devices in 5.0.x but this specific issue is not going to be fixed in 5.0.x either. For now, and just for expediency, Benoit programmed the Dim function to dim 3 times (instead of one). We cannot do more since the Echo connector will timeout. With kind regards, Michel

Hi jerlands, Since we are not yet making on our app, the main question is whether or not MobiLinc would be able to work with ISY Portal. As such, I will have to leave this to Wes at MobiLinc. With kind regards, Michel

Hi doogledb, Yes, many. Please checkout the information on the first page of this post: http://forum.universal-devices.com/topic/4810-the-global-cache-wf2ir-works/?p=37381 With kind regards, Michel

Hello everyone, Thanks so very much for the feedback. It seems that we are going a little in circle: We are adding support for Dim/Brighten to scenes and sending multiple dim commands will work (incrementally). Asking ISY, the Portal, or REST commands to have a loop and send n number of Dim commands automatically is not a good idea regardless of how it's accomplished: 1. Scene commands create more traffic especially due to all the cleanup messages 2. If the scene is large, the caller MUST put a wait between each invocation (i.e. you are going to see incremental dimming) 3. There's no guarantee that all devices in the scene will have the same level to begin with. So, if A is 100%, B is at 75%, and C is at 50%, Dim to 50% will turn off C 4. Iterating through devices in a group/folder - and depending on the number of devices - may cause an Echo timeout The least ugly of all these ugly solutions is what Banichi suggested: a. Create a 50% dim scene and call it b. You can also use Adjust Scene in ISY Programs to change the on level of devices in #a according to some time or some event (warning, this might take a long time especially if you have too many devices in that scene) With kind regards, Michel

Hi David, Yes BUT you have to create a new sub account (under your account), assign ISY and the new user to it, and make sure you approve the request in the Admin Console. With kind regards, Michel

Hi Lee, That's very odd since I worked with a customer just a couple of weeks ago and setup volume up/down using an INSTEON KeypadLinc button which worked perfectly. Are there specific commands that exhibit this behavior or is it all commands? With kind regards, Michel

Hi ccclapp, Based on our measurements (you can test this yourself), every dim command you send to a scene, usually dims the members by 2-5% (varies depending on the device). The main issue is that, unlike devices, you cannot send a level to a scene with INSTEON. With kind regards, Michel

Hi ccclapp, See my previous post. Programs would need to iterate through and calling dim. This is ugly since each invocation will take 1 second ... less ugly solution would be to have a 50% scene instead. With kind regards, Michel

Hi David, With INSTEON, that would be impossible unless: 1. We have logic in the portal that keeps calling ISY to dim 'n' times (not very efficient) 2. Have an ISY program that loops and dims 'n' times (ugly) 3. Create another scene with your desired dim levels and just turn on that scene (not practical) With kind regards, Michel

Hi David, Please checkout: http://forum.universal-devices.com/topic/18060-dimming-scenes-with-echo/?p=165643. With kind regards, Michel

Thanks Teken! Just so that everyone's aware, dimming and brightening scenes will only dim by 3% (or something like that defined by INSTEON) for every invocation. So, if you want to dim a scene to 50%, you will have to tell Alexa to dim about 17 times. Also, it's important to note that you cannot send a % dim to a scene. So, the main question is: what is everyone expecting dim/brighten do for scenes? With kind regards, Michel

Hi waterbaby64, 5006, 5012, 5014 errors are related to clients that subscribe to ISY such as the Admin Console, MobiLinc, etc. ISY expects subscribers to gracefully unsubscribe before shutting down. This said, most clients don't especially when they go to sleep. As such, ISY actively sends heart beat signals to all subscribers and checks the packet counts to make sure they are still online. If they are not, then ISY expires the subscription and releases all the resources. So, all those 5011 and 5012s are related to clients not gracefully unsubscribing and I wouldn't worry about them. 5006 simply means that a client unsubscribed with a subscription ID that no longer exists. With kind regards, Michel

Hi huddadudda, It works with http://yourhome.honeywell.com/en/products/thermostat/wi-fi-smart-thermostat-rth9580(which is the topic for this post). With kind regards, Michel

Hello all, Unfortunately I have lost track of the issue. Is the issue not being able to dim a scene? i.e. Alexa, dim x where x is a scene? With kind regards, Michel

Hi jmac, Thank you but it's quite odd that it took 2 hours to restore modem. With kind regards, Michel

Hi David, If the router is changed and ISY is not setup with a static IP address, then everything should work fine. The only issue might be that MAC's hostname might still be pointing to the old IP address. For those cases, it's best to try: http://wiki.universal-devices.com/index.php?title=Troubleshooting_Help#ISY_Finder_does_not_find_ISY With kind regards, Michel

Hi All, This is for Comfort API. Just got the thermostat and sent it over to Benoit. With kind regards, Michel

Hi all, thanks so very much for the lively discussions, levity (Bob P.), and kind words (accd). We really do appreciate it very much. I didn't realize there's an Eliza app for Echo. I had to develop one for one of my AI courses and it was loads of fun. I spoke to it regularly! Thanks again. With kind regards, Michel

Hello jmac, Restore Modem should not take more than 60 seconds per each non-battery operated devices IF AND ONLY IF there are not communication errors. Restore Devices will take significantly longer as ISY will have to rewrite all the links. Which one did you do? Also, are you seeing any communication errors? With kind regards, Michel

Hi Keith, Thanks so very much for the feedback. Let us check into it. With kind regards, Michel

Hello everyone, Thanks so very much for the feedback. So, the only thing you are asking to be stored is the email address, correct? If so, should there be a timeout on the cookie? With kind regards, Michel

Hello all, It seems that Java->Browser does not work on some operating systems and the ID is truncated. We're looking into this. With kind regards, Michel

Hi Keith/Teken, When you login to the Portal, are all those information filled out? i.e. when you setup your account, did you put long description, contact information, etc. ? With kind regards, Michel