thedishking

Quick update- Last night I noticed my lights did not come on at the specified time, and sure enough, the time was an hour off again. So, after taking your advice on "custom location" I had the ability to set offset to -5 (from default setting for of -6). Question - Is the daylight savings time setting not taking affect as it should? Anyway, thank you for helping with the work around. thedishking

Thank you for the tips. Shortly after posting this, I did the upgrade to 4.2.5, and noticed the time was corrected. I did a location select of Minneapolis, MN and have never used anything else. I do believe there was a bug at some point; I have a 99 running now too, and with the same location select and time server settings, the time on it is correct. I will keep an eye on it over the next few days now that I am on 4.2.5 Thank you for your help!

Hello, I have a question with regard to time. I have NTP server enabled, and it is set to pool.ntp.org I have it set to synchronize every 24 hours, and have both location and daylight savings time enabled. Trouble is, my clock is always 1 hour behind (I am on central time, ISY shows mountain time). I have synchronized with computer time many times, but it appears as though pool.ntp.org trumps this when enabled. I really would like to keep the NTP server enabled. Any thoughts as to why this may be an hour behind? I am in Minneapolis, MN and not near a time zone boundary. It is very annoying as my sunrise / sunset events, as well as timed events are all not triggering correctly. Thank you for any advice on this!

Hello! I have a question on the 2441TH Insteon thermostat. I'd like the ability to set it to a temperature, and have a script in the ISY know when it has reached the set point, and turn off. I am using this thermostat to control a heated floor, with a 240V normally open Insteon load controller, and it works great, with one exception. The thermostat and the load controller are in the same scene in the ISY, and the thermostat is the controller of the scene. The problem is the thermostat is very "precise". In other words, the floor sensor (hard wired in place of the factory thermistor in the thermostat) varies a bit, especially at 73 degrees F. So, if the floor is at 62 degrees, and I tell it to heat to 73, it does function as expected. The problem is once the floor reaches 73 degrees, the thermistor seems to vary a bit (wanders from 71 to 73, within seconds) and the thermostat turns the load controller back on, and off, etc. This takes place many times over the course of a minute, turning on and off, and back on, and off. Two questions: 1. Can the ISY detect when the thermostat has reached the set point? Since this is a heated ceramic floor, it holds the temperature for a long time, and does not need to turn on and off so often. Once an hour would be acceptable. 2. Can the thermostat be told a "range"? In other words, heat to 73, and turn off. Don't call for heat until you reach a -3 degree change (70 degrees) or so. Any advice would be greatly appreciated! Thanks! thedishking

Glad to help! It is a very nice front end when you get it up and running.

Hello! I am very sorry for the delay with the reply. I am glad to hear you got it working! thedishking

THANK YOU Xathros! I REALLY appreciate your help!!!!! Your code worked perfect!!! Happy Holidays! thedishking

Thank you VERY MUCH for the advice! I will give it a try tonight. thedishking

Are you trying to do this through the iRule ISY module? If so, it is pretty easy. Pull up the ISY by going to the IP address, and don't login to the admin console. Then, go to devices, or programs, and note the ID by hovering your pointer over the program. This will expose the actual code behind the program name in the bottom left corner of your browser. This is the data you will want to enter into iRule. Lastly, you will need to define a gateway on your tablet with the ip info of your ISY, along with username and password. I am not sure if posting external links is allowed, but here is the link to their tutorial video. http://www.iruleathome.com/support-cont ... videos#isy

Hello! I am using an I/O Linc connected to an outdoor motion sensor to activate a program in the ISY. This is so I can turn a scene of lights on, as well as get an email when motion is detected. I have it working, but the problem is I get a large amount of emails (literally every second) when motion is being detected Can anyone help me "clean up my code"? I would like to get an email when motion is detected, and only if the timeout expires (lights turn off after 2 min), then send an email? The lights are working perfectly with my code, I am just getting too many emails. I have posted the picture of the code below. Thank you very much for any advice you can provide. thedishking

I don't know if it is helpful, but the unit locked up around 7 or so last night. I rebooted (power cycle) unit around 10 or so last night. Travis

Hi Michel, I will answer below in blue 1. Do you have any devices to which you cannot communicate (i.e. red ! marks next to them)? No, everything looks good. I do have some scenes that fail diagnostic test, but they appear to work. I have added a few programs lately, trying to migrate everything to ISY from HomeSeer. 2. If you look at your logs, do you see a lot of X10 activity (if any) right prior to the hang? Not that I can see. I don't have any X10 in my home. 3. Is your router Linksys Exxx series? If so, are you certain that you have the latest firmware on it? Nope, Netgear R6300. To be perfectly clear, I do have a Linksys E3000 running purely as an AP (DHCP turned off, running only with LAN port enabled), with DD-WRT Firmware. The Linksys stock firmware crashes too much for me. 4. If you have DirecTV, has anything changed on your setup? Nothing has changed. Only the occasional reboot of the HR34 IRD. ISY Error Log.v3.3.4__Fri 2012.11.30 04.21.06 PM.zip

Hello, I just upgraded to 3.3.4 a few days ago, and my unit locked up last night. I had been running official release 3.2.6 since it was released, and did not have to reboot once. Should I post my error logs? Or should I email them to Michel? Thanks! Travis

Thank you for the advice, this worked as you had mentioned. Travis

Thank you very much. I'll give it a try. I am trying to move all programs to ISY from some other systems I have been running. Travis

Hello, I am sorry if this question has been asked in the past. I have not found an answer, so I thought I'd post for all to see. I would like to setup a timer for my bathroom fan, to turn the fan off, after the light has been off for 10 minutes. I understand I can use light turning off as a trigger, and then wait 10 minutes and turn fan off. However, this leads to problems when multiple people are coming and going. In other words, if I turn the light off, this is the trigger, and the timer starts counting down. If someone comes in to the bathroom 7 minutes later, the fan will then turn off in 3 minutes. I would like to avoid this, as I want to keep the fan on, until the light has been off (and stayed off) for 10 minutes. Does anyone have any advice? Thanks!!!

Hi Lee, It is a 6 Button KeypadLinc Dimmer, version 5.9 I did do some experimenting with mutually exclusive buttons after creating and troubleshooting the scenes. Because of the manual programming, I wanted to leave button C for testing after I heard from this forum. Travis

This release did offer one fix for me. I had a scene that had 5 controllers, and was unable to "remove from scene" on previous release. When I would right click, and remove from scene, it would not do anything to that particular scene. This release did offer the ability to finally remove a device from scene successfully. However - I did try creating a new scene, specifically with a 6 button keypad. I wanted to include the local load (.1 / ON-OFF)) to be a responder with various buttons (a, b, c,) and while it did look like the local load was added to the scene, pressing button A, B, etc. did not do anything. I ended up manually (by hand) linking the local load (.1 / ON-OFF) to buttons A, B, etc. Travis

3.1.16 has locked up twice for me thus far. Once over the weekend, and again today. Should I email you the log file?

IR is working flawless for me. I saw someone else had a problem, just thought I would chime in here. Seems to be very stable from this side. Travis

I am experiencing lock ups on 3.1.7 every few days. Right now I cannot get to the unit on the LAN, and it appeared as though IR was not working. It turns out it is not accessible via the LAN, however IR is delayed by about 90 seconds. If I power cycle the unit, it does come back, but it is only a matter of a few days and it will need to be power cycled again.. Running on a static IP on the LAN. Any ideas?