Michel Kohanim

Hello everyone, We will have a maintenance release next Sunday 02-19-2017 at 5:00 AM PST. You should not experience a downtime of more than couple of minutes. This release includes a Node Server implementation for 5.0.9 firmware release. Our initial Node Server will be for Geo Fencing using any app that can call URLs (we tested with Locative): - Basically, mobile devices can be grouped under a Location node which allows for such things as "Home", "Home larger radius" and "Country house", etc. @MWareman, thank you for the idea! - The status of a location will be true if any of the member devices/nodes is true - You can also have standalone mobile devices (e.g.) not grouped under a location. For example, you could have "at work" entry, not under a location. The idea is that you don't need to create a location if you are to use only a device in it This is a huge milestone for ISY/Node Server since it provides us with the ability to add other Node Servers in the future without the need for firmware updates to ISY! Thank you Chris! Thank you Benoit! With kind regards, Michel

Hi Greg, Apologies. Yes, that's correct. With kind regards, Michel

Hi Greg, Scenes that do not support Adjust Scene will not be listed. Adjust scene does not work on X10 devices. With kind regards, Michel

Hi Teken, 1. Unfortunately no ETA since each and every release depends on the bugs we find 2. Yes, Polyglot has been refined and many contribute to it and especially einstein.42 With kind regards, Michel

Hello all, Just an update: we have not heard back from them. Since the original submitted form did not even produce a confirmation, I thought perhaps I had done something wrong. So, I submitted it again and it seems these forms go into a black hole. I just hope this does not become another Harmony Hub. If anyone has any contact at Google Home, please do not hesitate to use them! With kind regards, Michel

Hi all, Has anyone tried our Polyglot version? http://forum.universal-devices.com/topic/18643-polyglot-sonos-nodeserver/ With kind regards, Michel

Hi Al, 4.4.6 has expired certificate. Please use: http://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Icon_on_Your_Desktop With kind regards, Michel

Hi jtara92101, Thanks so very much for the information. We do have a gating factor and that's OS agnostic "app development" within our budget (which is very low). Currently, we are using Locative as is and, Locative, supports iBeacon. With kind regards, Michel

Hello everyone, Thanks so very much for all the feedback. Scott, Thank you for recommending DOT. We'll test both and keep you all abreast of our findings. With kind regards, Michel

Hi glacier991, 400 means "bad request". Are you certain you are formatting everything properly? With kind regards, Michel

Hello all, For our CEC project, we must implement GeoFencing support through ISY Portal and ISY firmware 5.x using node server framework. Mobile geo-fencing using GPS is already implemented and being tested. This said, however, we do also need to test iBeacons for presence detection in the venue and thus the reason for this post: we need your input as to what iBeacon device do you use and which do you think is most accurate. Thanks in advance. With kind regards, Michel

Hi RichTJ99, We are waiting for Google to send us permission/APIs to use Direct Actions. With kind regards, Michel

Here you go: https://assistant.google.com/developer/eap/ With kind regards, Michel

Hi fasttimes, Yes. Google's current APIs (Actions) are very much like Alexa without the Smart Home Skill. So, you would have to say something like "ok google, tell izzy to xxx". The Direct Actions is not available to everyone so we had to request for it and have not heard back. With kind regards, Michel

Hi glacier991, MobiLinc might be the cause if you do NOT see your ISY online in the ISY Portal. The best thing to do would be: 1. Go to http://echo.amazon.com and login 2. Click on the Smart Home menu on the left 3. Scroll down and click on Forget All Devices 4. Click on Discover devices and test again With kind regards, Michel

Hello sandpiper, You are always welcome to submit a ticket or call our tech support. We'd be delighted to help. With kind regards, Michel

Hi Kevin, ERR = status of the node: whether or not it's in error. In case of Z-Wave/ISNTEON, it means whether or not ISY can communicate with the device. Err = 0 = No Error (normal condition). Err = 1 to Communication error. The reason this is there is very much the same as other status/control things ISY does. With Control, for EVERY communication error, this Control is set to 1. With kind regards, Michel

Hi Don, This is browser cache issue. After you unlink, close all browsers, reopen and retry. With kind regards, Michel

Hi sandpiper, Click on the rule and choose whatever rule you wish to use. US / Canada is the default. With kind regards, Michel

Hi Steve, I already responded to your ticket. With kind regards, Michel

Hi sandpiper, Please click on the Change Location button and choose your Daylight Saving Rule. With kind regards, Michel

Hi MFBra, Thank you and I agree. I was just offering alternatives till such time that we have enough time to implement. With kind regards, Michel

Hi Kentinada, Thanks so very much for the update. Most probably the issue was browser cache. With kind regards, Michel

Hi PhanTomiZ, Apologies, yes, it's status. Yes, this program is evaluated when something that you try to communicate with does not respond. It's no different than trying to figure out whether or not the PLM is still working. With kind regards, Michel

Hi kentinada, I very much doubt your settings are being saved. Please make sure that local settings is set to blank and remains blank. With kind regards, Michel