Michel Kohanim

Hi sanders2222, Are you local to your ISY or remote? If remote, click on the Add button and then enter the remote URL for your ISY. If local, please take a look at: http://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Finder_does_not_find_ISY (MAC) http://wiki.universal-devices.com/index.php?title=Configure_Firewall_Software (PC) With kind regards, Michel

Hi Paul, Thanks so very much for sharing! With kind regards, Michel

Hi Rich, Either Groups (as Teken suggested), or make a program and have Alexa execute that program. With kind regards, Michel

Hello everyone, It seems possible but we have to make sure we can walk before we fly! With kind regards, Michel

Hi adam48, Can you paste a screenshot of Admin Console | Configuration | Network tab? With kind regards, Michel

Hi Paul, Thanks so very much for the update. We will be working on it as soon as we are a littel more comfortable with Google Assistant. Benoit is pretty much overworked at this point! With kind regards, ​Michel

Hello everyone, http://forum.universal-devices.com/topic/21243-direct-action/ With kind regards, ​Michel

Hello everyone, Just wanted to let everyone know that Google approved us for the usage of Direct Actions. We are quite excited and will shortly start working on the integration. With kind regards, Michel

Hi Javi, I will have to defer to Benoit. With kind regards, Michel

Hi Gerry, Correct. That's why you need the second program just in case the Wait is interrupted for any reason. Note that your variable does NOT have to be state in this case. With kind regards, ​Michel Actually, the variable MUST NOT be state. With kind regards, Michel

Hi Gerry, Don't know what 'evaluating' means in your vernacular. It will NOT go query devices and see whether or not the states are true. It does evaluate the conditions based on the values that have already been evaluated based on previous events. No to the latter. ISY evaluates programs IF AND ONLY IF something happened to a condition on which a program depended. With kind regards, Michel

Hi Gerry, Very simple: If And $hasAlreadyRun = 0 Then $hasAlreadyRun = 1 $hasAlreadyRun = 0 Another program just in case the wait is interrupted If Then $hasAlreadyRun=0 With kind regards, Michel

Hi Gerry, With regards to: It should read: IF statements that checked a Status of a device (vs Control statements) would be triggered when that status changed. It would not be triggered if the status does not change. i.e. if a device is ON and you turn it ON again, the program will not be evaluated (because the status didn't change). For Control, every physical action to that device causes the program to be evaluated. i.e. If the device is on and you go to the switch and press the on button again, the associated program will be evaluated/run. Run If, uses the last state of the program. If the state is true, it will run (then). If false, it will run (else). With kind regards, Michel

Hi Brad, 1. Does ELK already talk to NEST? If not, you would need an intermediary such as Polyglot (http://forum.universal-devices.com/topic/18655-polyglot-nest-nodeserver/) 2. Why would you need to use IFTTT? You can already do that with the Network Module which comes with ISY Portal: http://wiki.universal-devices.com/index.php?title=ISY-994i_Series_INSTEON:Networking:Network_Resources#Shades With kind regards, Michel

Hi GDM99, If the batch is selected (manual), then nothing is programmed into devices regardless of their type (except for when you are linking the device and the initial link). In this case, the battery button plays no role. If the mode is automatic, then battery button causes ISY not to write to battery operated devices (you will have to do them manually). Please note that this is only available for PRO series. With kind regards, Michel

Hi Russ, On older INSTEON devices, on level and ramp rate require an airgap/reboot of the device. As such, they won't work through programs. With kind regards, Michel

Hi Jimbo, Yes, but in a different and semi-related context. More information to follow soon. With kind regards, Michel

Hello everyone, We shall start working on the Conversational Actions this coming week. Direct Actions will come later. With kind regards, Michel

Apologies to everyone. We are spending every second of everyday trying to get 5.0.9 out. As such, not a lot of activity on the forum. Thanks so very much for your patience and understanding. With kind regards, Michel

This topic is now locked. Please stay on topic.

Hi MarkJames, 1. It only matters if you want to have immediately release of resources used by ISY for subscriptions. If not, not only you would get that error but also you would get the -170001 (information) about the socket (RSub = Regular Subscription) not being active (waiting for the client to close = 6). 2. UDQFull means that you have too many events in that Queue. That queue is for Network Resources so you might be putting more than 30/second network resources in the queue. With kind regards, Michel

Hi Marc, The USB connection gets you to ISY shell. You have the same exact options as telnet with some additonal benefits: 1. You can see debug messages (which are suppressed on telnet for security reasons) 2. You can see all boot up messages All you need is a mini USB to USB connector and a terminal application. The serial parameters are 115200, 8, 1, None. With knid regards, Michel

Hi Derek, Agreed. With kind regards, Michel

MarkJames, It means that the client that subscribed to ISY is no longer listening on the socket AND it did NOT gracefully unsubscribe. With kind regards, Michel

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