Michel Kohanim

Hi io_guy, thank you. I shall give it a try. Candide, those errors (especially 503) means that the server is down or not available temporarily. Have you tried changing the station and see if there's any improvements. I know for a fact that WB servers sometimes go down for maintenance. But, it should not last so long. With kind regards, Michel

Hi BrianH, Yes, of course! With kind regards, Michel

Intellihome, You do not need to telnet to ISY nor would ISY allow you to telnet to it if the file system has not been initialized. So, simply replace the SD Card, and then power up ISY and see if you still have the same errors. With kind regards, Michel

Hello all! Please follow us on Twitter for new firmware and other announcements. See you there! With kind regards, Michel

Hello all! Please follow us on Twitter for new firmware and other announcements. See you there! With kind regards, Michel

Hello sperok, Can you please take a look at the regular log (Tools | System Log) and check the activity on or around that time? With kind regards, Michel

Hello tim2u, You need both modules. And, temperature variables come from WeatherBug and thus, YES, you can use them in your programs. With kind regards, Michel

Hi wrj0, Not really. With kind regards, Michel

Hello ketchup318, It probably says "Not connected" which means that the PLM is dead. This is especially the case if your PLM is blinking instead of having a solid on LED. With kind regards, Michel

Hi wrj0, Based on our experience, SanDisk is the most reliable followed by Lixar. With kind regards, Michel

Hello intellihome, Yes, you can restore your 2.7.15 backup on 2.8.16. Please do make sure you have a good backup before formatting the SD Card. With kind regards, Michel

Hello Candide, Would you please check the error log and see what type of errors you see for CLI-WBUG? With kind regards, Michel

Hello bocaray, Please read the following article: http://www.watchguard.com/infocenter/ed ... 135177.asp At the bottom they have instructions for setting up NAT 1:1. With kind regards, Michel

Hello gadgetfreak, The nodes behave as follows: 1. Fan ... the status of the FAN 2. Heat ... the thermostat is CALLING for heat 3. Cool ... the thermostat is CALLING for cool Please note that "calling" is NOT the same as mode. Mode is what you expect the thermostat to do and "calling" is what is currently happening in the thermostat. With kind regards, Michel

Hello gadgetfreak, © is for Cool setpoint and (H) is for Heat setpoint. With kind regards, Michel

Hi guys, thanks so very much for the update. Illusion, the forum duplicate was my bug ... I hit the submit button then quickly pressed back to check something (thinking that our slow forum would never be able to actually post the topic in that short amount of time) and then submitted again. Unfortunately I have yet to figure out how to merge the posts. With kind regards, Michel

Hello sperok, Size of queues are event dependent. This said, having programs that check for conditions and set variables or call other programs are not a problem; you can have 100s of them all happening within fractions of a second. The problem arises when your programs call device dependent activities (such as querying a large scene or turning on/off 10s of large scenes quickly and outcome of which would cause other programs to call other scenes, etc.). In short, you would want to limit things such as: Query My Lighting every 1 second (the query itself takes a lot longer than 1 second and with all the events generated, you will eventually fill up the queue). With kind regards, Michel

Hello Elvis, We do surely take these issues quite seriously and this bug was an oversight. This said, however, as reliable and robust we would like ISY to be, it was never designed with those application in mind. This is clearly stated in our Disclaimers & Terms/Conditions of Use and especially since we added support for door locks. In any case, I do apologize and this shall be fixed as soon as possible. With kind regards, Michel

Hello Elvis, You are 100% correct; the fact that you are 1000s of miles away and with a system that does not respond is quite bad. I had no clue this bug would show itself under any other circumstances besides having ELK RP connected and thus kept postponing this fix till we have our ELK module. I do apologize and this shall be fixed in the next release. Hello dennisric, Are you referring to the number of columns on the AJAX interface? If so, you would not actually see any change unless you are on a mobile device with a low resolution. With kind regards, Michel

Hi Ski, Yes, but if and only if you do not have the latest 2413S. Please make sure you take a backup before you do anything. With kind regards, Michel

Hello Elvis, Thanks so very much for the detail steps to reproduce. Have you tried 3.1.5? The main issue is that ISY makes a connection to ELK and keeps that connection open. Obviously, the system should not hang when ELK/router are rebooted but, at the moment, ISY does not know that any of those systems are rebooted. I think that during reboot, ELK sends a command/status that ISY does not expect. We do not use watchdog timers since we would never ever be able to figure out the root cause. We will definitely look into this and see if we can fix it before the ELK module. With kind regards, Michel

Thanks IM! Thanks Mark. With kind regards, Michel

Hello rossarmstrong, As you suggested, it's quite subjective! My personal preference is using scenes wherever they have already been defined and if you have more than just a couple of devices. From my perspective: Pros for using scenes: 1. All devices respond at the same time 2. Less INSTEON traffic 3. You can add/remove devices from the scene, change on levels/ramp rates, without having to change the programs (one at a time for each device) Cons for using scenes: 1. Not as reliable especially if you have SWL v35s With kind regards, Michel

Hi IM, My pleasure. Can you please verify the fix in 3.1.5? With kind regards, Michel

Hello johnnyt, What you need to do is to have your motion sensors close to you (and the PLM). Look at the Admin Console and when you see a Green "Writing" arrow as the icon for the motion sensor, then put the motion sensor in programming mode. With kind regards, Michel