Michel Kohanim

Hi j.rieff, More information on setting up gmail account/ISY: http://wiki.universal-devices.com/index.php?title=ISY994:Configure_Mail_Server_Settings#Configuring_gmail_Account With kind regards, Michel

Jimbo, I am sorry for the insinuation. Your comment below was perhaps misunderstood on my part: "It could be done if UDI chose to, and make it an option to control a scene as a group" I took this as: UDI does not choose to do it. Regardless, multi protocol scenes are supported in 5.0.x and thus this whole topic is moot. So, everyone, let's not let this one get more out of hand than it already has. With kind regards, Michel

Hi kurelgyer, Yes, definitely. This said, we are still investigating ... need to make sure there are no stumbling blocks before we have a dedicated forum. It should not be long though. With kind regards, Michel

Jimbo, It seems that you feel we have all the resources and time in the world and should just drop everything and do this one feature (regardless of what is supported in 4.5.x and how to handle legacy vs. INSTEON vs. Z-Wave vs. all the other requirements). Of course we can and it's called multi-protocol scene in 5.0.7. With kind regards, Michel

Hi adrianp, It would be best to submit a ticket. From the history of this post, I think what may have happened is that you did a Restore Modem on a dead PLM. If you have a good backup, what you might want to try is explained in this link: http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Devices With kind regards, Michel

Hi pmhgeneral, I do not think this has anything to do with firmware. Please reboot ISY, then go to Tools | Diagnostics | PLM Status/Info. If it says "Disconnected", then: http://wiki.universal-devices.com/index.php?title=INSTEON_Safe_Mode_Dialog If not, you might want to move your PLM to a different outlet and one which is not shared with other transformers and power supplies. With kind regards, Michel

Hi Kevin, Thanks so very much for the update and contributions. I sure hope someone will pickup your code and commercialize it (we would do it had we had resources). With kind regards, Michel

Hi Tony, First of all, thanks so very much for your willingness to help. We all appreciate it very much. I agree with jtara92101; I think it's much better to help with Wiki and its organization. If you would like to have login access to our Wiki, please do let me know. With kind regards, Michel P.S. Wiki is back up!

Hi Jim, We are working on extended logging for 5.0.x. With kind regards, Michel

Hi kck, This is wonderful! Any intentions of making this into a commercialized product? With kind regards, Michel

Hello everyone, Thanks so very much for all the feedback and your trust which we will never ever take for granted. This said, this was a disturbing bug: not that it would have any security implementations but because we didn't catch it. The original reason for this performance test was: 1. Amazon measures response times between Echo invocations (discovery) and service response 2. We have about 1% cases where the response time is more than expected. This used to be higher due to inactive accounts (for which subscribers got emails from us) 3. For holiday, Amazon expects a dramatic increase in the call volumes and thus they wanted to make sure all partners can handle the traffic 4. We tested everything in the portal and concluded that the issue is in Amazon OAuth servers for which we submitted a ticket Again, sincere apologies for the inconvenience and the alarm. With kind regards, Michel

Hi auger66, So very sorry, I had to remove the picture. With kind regards, Michel

Hi fasttimes, Password is necessary if and only if your device requires a password. You can use default ISY web interface (http://wiki.universal-devices.com/index.php?title=ISY-994i_Initial_Browser_Screen) or you can use a direct URL: http://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface#Networking (/rest/networking/wol). With kind regards, Michel

Hi fasttimes, ISY does NOT store IP address. When you enter the IP address, ISY calculates the broadcast address and that's what you are seeing. With kind regards, Michel

Hi Gary, Yes, indeed it is. The good news is that Google Home is cloud based so very minimal dependency on what we are doing with 5.0. With kind regards, Michel

I got it now... LOL!! With kind regards, Michel

Hello everyone, We'll keep you posted with the progress. With kind regards, Michel

Hi AJ, Please do the following: 1. Forget all devices 2. Discover devices 3. Settings | history 4. Please make sure Echo hears what you are asking it to do Hi larryllix, Didn't get spit/keyboard comments. Sorry! With kind regards, Michel

Hi kevkmartin, Please do NOT forget to also upgrade the firmware. With kind regards, Michel

Hello all, The issue is related to a performance test we had to do with Amazon. If you see spurious names, please do Forget All and then Discover Devices. With kind regards, Michel

Hi Sachelis, Complete instructions are here: http://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration With kind regards, Michel

Thank you asbril. We'll investigate shortly. With kind regards, Michel

Hello everyone, http://forum.universal-devices.com/topic/20547-echo-dot-stops-responding-new-mystery-devices-showing-in-alexa-app/?do=findComment&comment=198050 With kind regards, Michel

Hello everyone, Sincere apologies. Definitely a bug was introduced when we were asked by Amazon to investigate performance issues in OAuth authentication. This is now fixed. Please instruct Alexa to Discover Devices. With kind regards, Michel

Hello everyone, Sincere apologies. We're looking into this issue right now. Please do not discover any devices. Will keep you posted. With kind regards, Michel