Michel Kohanim

Hi rogressem, Yes, one responder can be controlled by many scenes and many controllers. With kind regards, Michel

Hi to both, Please note that our next release 2.7.7/2 would allow for the thermostats to be in scenes as both responders and controllers. With kind regards, Michel

Hi fasttimes, for IR input/multiroom - and although more expensive - I recommend IRLinc. With kind regards, Michel

Hi backinthelab, ergodic is 100% correct: Motion Sensors are responder only and, on top of that, they are battery operated which means that they do NOT hear anything while they are in sleep mode. With kind regards, Michel

Hi guys, Network module can be purchased by going to Help | Purchase Modules on the Admin Console. The price is $49.00 and you would need 2.7.7. Here's some documentation: http://www.universal-devices.com/mwiki/ ... Networking With kind regards, Michel

Hi Paul, The errors with a very small batch of SWL35s were mostly signal sensitivity and unreliable group handling issues. Some of your SWLs might be from that batch but the best way to test is to do a Scene Test (Tools | Diagnostics | Scene Test) for one or more of your scene wherein there's at least one SWL35 and one non-SWL35. If the SWL35 fails randomly but the other device does not, then in all likelihood the switch itself is the issue. If you have used the third option (import existing links) when you added your devices to ISY, that would explain why you would get spurious links when you restore. Although it might take longer, but in the long run, you will be spending a LOT less time if you started from scratch for your most important devices. With kind regards, Michel

Hi Moshe, thanks. I do not think the problem was Cisco related. It's surely network related but we didn't have enough constraints in ISY to throw away bad NTP dates. With kind regards, Michel

Hi fasttimes, In ISY, the process is quite simple and done it 4 steps 1. Highlight all those switches and drag and drop them into a scene 2. In the next dialog, make all of them controllers 3. Have coffee while ISY programs all these devices with cross links To make all of the switches have the same on level ramp rate: 1. Adjust the on level/ramp rate at the Scene 2. For each controller that you wish to have the same on level/ramp/rate click a button called "Apply Attributes from Scene" For more information, please checkout our Wiki: http://www.universal-devices.com/mwiki/ ... ide#Scenes With kind regards, Michel

Hello jimkoke2, Unfortunately ISY does not yet have variable support. It is in our roadmap for version 2.8+ (currently 2.7.7). With kind regards, Michel

Thank you both ... support should be available shortly. With kind regards, Michel

Hi Paul, We have had cases where SWL 35s were the actual culprits. And, I am specifically talking about v35 ONLY. How old are you switches? Would it be possible to get replacement for them? With kind regards, Michel

Hi Moshe, it's possible that your ISY has gone back to 1941 (please check your logs to ensure this is the case). If so, this is a know issue and fixed in 2.7.7. If you are interested, please send an email to support@universal-devices.com. With kind regards, Michel

Hi Tome, Unfortunately not ... With kind regards, Michel Is there a way to watch a program run like in debug mode, or a log of steps or something? I can watch what happens in the event log but that is just commands issued and recvd, not program steps. Is there something available from the telnet interface? Thanks, Tome

Thanks so very much Tome. With kind regards, Michel

Hi David, Please send an email to support@universal-devices.com to get the latest device configuration file. What you need to do is to first figure out which device is a KPL. Then, by looking at the address of the device, all those ending with numbers above 1 are sub buttons. With kind regards, Michel

Hello oberkc, I assume this shows up as unsupported device. If so, would you be kind enough to send me the number after v. (center/top of Admin Console). With kind regards, Michel

Hi Tome, Not that I am aware of. But in 2.7.7/2 you can have the newer ones BEEP. With kind regards, Michel

Hi Walter, thanks so very much for the update. The next release will also support change of state events directly from the thermostat SO you might have to remove them from ISY and then add them back in (especially if you want to include them in scenes). With kind regards, Michel

Hello, 2.7.7 will not solve the problem. It will only allow different directories be used for temp files. Unfortunately the account settings in Windows Vista+ prevent writing files to the file system. With kind regards, Michel

Hi Frank, not yet. We are waiting for our to arrive. With kind regards, Michel

Hi Frank, we are waiting for ours to arrive. Currently we do not have support for it. If anyone out there already has this unit, all we need is the numbers after v. in the Admin Console (center/top). With kind regards, Michel

Hi Shad, very nice! On with a value of 0 means that the device will use its own stored on level. I assume your devices on level is 100%. Correct? With kind regards, Michel

Hi, You will have to do the query on the Low Bat node and it should go to off. As far as EZFlora, the only node that responds to query is the main node (the one with addressing ending in 1). With kind regards, Michel

Hi James, Bidirectional communications is currently out of our scope. But, if you want simple communications over the network, you can accomplish it right now using the Network Module. This said, you will have to have their configuration and specifications ready. With kind regards, Michel

Hi tahoe, The date for 2.8 depends on when we will have the official release for 2.7.7. Yes, your program will work. With kind regards, Michel