Michel Kohanim

Hi shannong, Quite interesting indeed ... Looking forward to your finding. With kind regards, Michel

shannong, You cannot set Master mode in UI as it's not in their APIs. Do you have HouseLinc running at the same time as ISY? With kind regards, Michel

Hi shannong, Sincere apologies, I didn't understand the question. Scenes in ISY do not have a status. We have had long and fruitless debates as far as what constitutes the status of a scene and never arrived at a solution that satisfied everyone. Of course you can And the status of each device in the scene as a condition. This said, it seems that you are just looking at temperature, no? If not, what's the status of the scene? As far as the second question, if this is an urgent requirement for you, then - and as you suggested - I am afraid ISY is not going to meet them. If not urgent and can wait 3 months, then we will have that feature (already designed, working, and being tested in the lab). What you can do in the interim is pretty ugly: basically setting a variable for each discrete temp. With kind regards, Michel

Hi shannong, Are you using the same PLM as the one used with HouseLinc? If so, did you do a factory reset on it? If not, can you please go to Tools | Diagnostics | PLM Info/Status and let me know your PLM version? As far as this specific thermostat, my experience has been: 1. It may go to sleep mode (especially if the battery is low) 2. If it's not set to master mode, then it may not get registered to ISY and, furthermore, you may not get status updates from it when added With kind regards, Michel

Hi shannong, Short answer, yes of course. Long answer: http://wiki.universal-devices.com/index ... e#Programs Another great source of information is the User Guide: http://www.universal-devices.com/docs/p ... 5%20v2.pdf Unfortunately you cannot yet set variables to status of devices. This is coming very early next year. With kind regards, Michel

Hi shannong, Welcome! Please make sure your thermostat is close to another dual band device and/or access point. Or, perhaps you can move your ISY/PLM to the same location as HouseLinc used to be. Also, please note that ISY and HouseLinc cannot coexist. And, finally, please make sure you are in master mode and that your thermostat is powered through an adapter otherwise it might be sleeping. With kind regards, Michel

Hi Xathros, I am not sure I follow. They are there without the "Enable", no? With kind regards, Michel

Hi Harold, Indeed you got an IR model. Consider it a gift for the holidays . With kind regards, Michel

Hi Harold, Thank you. Questions: 1. In Help | About dialog, what's the product id? 2. Do you have a little IR sensor through the hole? With kind regards, Michel

Hi Nathan, ISY would have no way of knowing that the PLM is disconnected unless you reboot ISY. Please do keep us posted. With kind regards, Michel

Hi ES1400, thanks so very much for the update. Appreciate it very much. With kind regards, Michel

Hi Harold, That option is only available on the PRO series. With kind regards, Michel

Hi benpeart, If these are older devices, you might need to an airgap (take the set button out and then push it back in) to the switch for the settings to take effect. In which case, it would not make sense to use programs due to the manual nature of these devices. What's the model#/firmware version of these devices? With kind regards, Michel

Hi duncanM, Welcome to our forum! Can you please explain (or post) what's a "no-go"? We do not have such a thing. Also, I think a quick review of tutorials would be quite beneficial: http://wiki.universal-devices.com/index ... e#Programs With kind regards, Michel

Hello Banichi, I am so very sorry to hear and sincere apologies for tardy reply: our mail server were down all day today. My first questions: do you have any baby monitors or INSTEON thermostats? If so, please disable them. If not, please move your PLM to a different outlet. There have been many cases where there's too much noise on the outlet where the PLM is plugged into and it's intermittent. With kind regards, Michel

Hi Les, Apologies for tardy reply. Admin Console is the only UI that allows you full device-configuration of ISY. Dashboard should be used only if: 1. You want a nicer UI to control devices 2. OpenADR 3. Smart Meter 4. Network configuration With kind regards, Michel

Hi John, Here's a list of others: http://wiki.universal-devices.com/index ... _Variables With kind regards, Michel

Hi EricK, Understood. As far as scenes: 1. You have controller only devices (such as Motion Sensors, TriggerLincs, Leak Sensors, etc.) in which case ISY does NOT let you make them into responders in a scene 2. You have responder only devices (such as IRLinc TX and old ApplianceLincs) in which case ISY does not let you make them into controllers in a scene 3. And, finally, you have the rest which can be controllers and responders: -- If you want multiple KPL buttons to respond to each other and follow each other (in an 'n' way scenario), then you put them all in the same scene and make them all controllers (you can choose) -- Now, let's say you want to be able to control the backlight on some of the buttons on a KPL, and thus you will put them in a scene as responders -- There are no limits (except for the number of links a device supports) as to the number of scenes a responder can belong to. So, your KPL button can be a controller in one scene and responder in 100 other scenes -- There's a limit as far as a device/button being a controller in a scene. The limit is 1. This means that if a device/button is a controller in one scene, ISY will NOT let you make it a controller in any other scene (this is unlike HouseLinc) I hope this helps + some tutorials on scenes: http://wiki.universal-devices.com/index ... ide#Scenes With kind regards, Michel

Hi JSchuman, It's not! ${alert.action} means the last value for the property of the device that causes the program to run. With kind regards, Michel

Hi isyrocks!, Are there any network end points on your computer? If not, it would be very difficult to have ISY call your computer. With kind regards, Michel

Hi AJ, Would you be kind enough to: 1. Submit a ticket with: 2. Your remote IP address 3. Please change your userid/password 4. Please change your https port By FQDN of ISY, you mean the UUID? If not, then what? I'll try to login and see what's going on. With kind regards, Michel

Hi EricK, Thanks so very much for your order! The reason you need the PRO is for the batch feature without which every change requires you to wait for all programming to be written to devices. Unfortunately you only have 3 choices when you register devices in ISY the last one of which (import existing links) is the only option that preserves the links. And, this is the option I do not recommend. So, my advice is to start small from one section of the house least used and then expand slowly. With kind regards, Michel

Hi Eric, Thanks so very much for your interest. It's quite appreciated. From migration perspective, I can tell you from 6 years of experience, when you import links (even though there might not be any half links) - and if you have MANY scenes - you are going to spend most of your time trying to figure out which scenes are what and which devices are which. ISY does not know your existing scene names and they all show up as Scene#1. Furthermore, ISY adheres strictly to INSTEON specs. So, you cannot have one button be controller in two scenes (but a device can be responder in as many scenes as you would like). In houselinc, they allow you to do that but not without using half links. Now, doing a simple math, assuming: 1. Each of your devices have 15 links 2. You have 20 regular INSTEON devices and 20 I2CS devices Then, in order to crawl (regardless of importing links) your whole network, ISY will spend: 1. For older devices: One command to read each byte of a link record. Each link record has 8 bytes, and therefore 8 commands. Each command takes 500ms (if everything goes well) + 200 ms. for the PLM to be ready again. So, each record takes about 6 seconds to read: 6 (seconds) x 15 (records) = 90 seconds (1.5 minutes) 1.5 (minutes) x 20 (devices) = 30 minutes 2. For newer devices One command to read the whole record @ 1 second 1 (second) * 15 (records) = 15 seconds 15 (seconds) * 20 (devices) = 5 minutes So, you would be sitting there for about 35 minutes while ISY is crawling the network and, at the end of which, you still have to go figure out which scene is what (in case you import links). Also, ISY's scene management paradigm is very much different than HouseLinc. ISY is hierarchical where as HouseLinc is tabular. So, there will be some getting used to the concepts. My recommendation is this: 1. ISY994 PRO 2. If you have addresses for your devices, then use the first option (do NOT import devices and do NOT import links). If you don't have addresses for all your devices, use the second option (only import devices but not links) 3. Once all devices are registered, put ISY in batch mode (Automatic Write button is grayed out) 4. Create all your scenes ... in batch mode, ISY does NOT reprogram devices but it keeps them in memory till you click on the Automatic Write again. So, you can quickly create your important scenes, then click the batch button again, go for a coffee, and then come back and do more complex ones Hope this helps. With kind regards, Michel

Hi mfranzel, As far as the KPL, I think it's defective. Are you certain ISY's IP address has not changed. I also responded to your ticket with some suggestions. With kind regards, Michel

AJ, The root/intermediate certificates MUST be installed in your computer/client (under trusted certificates) and not in the ISY. What CN did you use to get your certificate? Is it your ISY's remote IP address or internal IP address? With kind regards, Michel