
intellihome
Members-
Posts
174 -
Joined
-
Last visited
Everything posted by intellihome
-
Something like this would be nice. Then if you can look at a chart that shows each device's average communication performance over a period of time. Green, Yellow, Red. You would then know where (geographically) and/or what device(s) are "weak". I seem to have virtually 100% stability while running scenes and programs. I get intermittent communication faults only when the ISY is writeing to devices. while adding buttons to scenes or restoring a device. I assume this is because of the extended time for these tasks.
-
Tome, As I understand it, being the programs are Event based, the "If" is evaluated when the "Event" (3am) occurs. So when 3am occurs the status becomes "True". Being there is no other event in the "If" statement that effects this program it will not be re-evaluated. When 3am rolls around, the program is evaluated again and the status again is "true". If there were another part of the If condition such as... If Time is 3:00:00AM And Status 'lamplinc' is On Then Set Scene 'My Lighting' Query Else - No Actions - (To add one, press 'Action') Then the program would be re-evaluated when the lamplinc is turned on and then the program would become "false" because it's not 3am. I guess it would make sense for the status of the program to go false at one second past 3am, but it doesn't work that way. It takes an event to occur to make the If statement False. This program would turn the program status False when the time was 3:21AM. Of course if the query was still running at 3:21AM the program would Stop because the If became False. If From 3:00:00AM To 3:20:00AM (same day) Then Set Scene 'My Lighting' Query Else - No Actions - (To add one, press 'Action')
-
Yeah, I know that's why you put it in the Smarthome area but I posted here before I realized that it's the adapter sending humidity updates. Either way, it probably belongs here also, until we (I) understand the situation better. I had the V2 installed with 2.7.7 and the logs don't show any Humidity updates. So it would be nice to know... 1. If this traffic was always present with 2.7.7 but the ISY logs did not log it? Or 2. Did 2.7.9 turn something on in the V2 adapter? If it's the latter, then maybe the UDI guys can look into it. This is a pretty big concern (Insteon traffic virtually every minute in my case).
-
I now know where all the T-stat insteon traffic is coming from...the humidity sensor, which I don't even have. Is there something we can do about this? I went from a simple query every 15 minutes that worked perfect to a update every minute or two. I wish I never sent back my V1 adapter.
-
I upgraded from 2.7.7 to 2.7.9 following the posted instructions. The upgrade was fast with no issues. Everything looks good. Notification list migrated nicely. I added additional notification lists and tested with no issues (regular email and Verizon vtext). I created a few new scenes and made some adjustments on others. All Good. My V2 T-stat is updating the ISY on its own. However, I did notice a lot of traffic in the event viewer for the T-stat. I don't know how to interpret the information. I need to look into it though, I have traffic every 5 minutes. Any thoughts on all the traffic from the T-stat? I got a screen shot of my event viewer but don't seem to be able to paste it to this post? [/img]
-
Steve, I'm not a salesman or anything like that but just to let you know that the Waterbug is on sale ($20 bucks off)
-
Thanks for the question and response. I was wondering the SAME thing. Sounds like two steps forward, three steps back.
-
Steve, i use the fairly inexpensive Waterbug system from Smarthome http://www.smarthome.com/7160B/Battery- ... 350/p.aspx It's an alarm in itself but I also hooked up the dry contacts to an I/O Linc. This gives me the flexibility to get notifications, close water valves etc You can add additional sensors also.
-
http://www.smarthome.com/30408/Venstar- ... 4RF/p.aspx Smarthome has a couple of remote sensors that will report to your new Venstar T-stat (they are Venstar options). As to your question though...Does the ISY have the ability to "see" this option? I don't know.
-
Mike, thanks for the info. I thought the only difference was the number of programming days. Turns out there are a few more differences. I collected the following info from Venstar's site. The humidity module appears in the standard list but then is highlighted in the 7-Day unit's features. I'll call Venstar for confirmation. Standard Features for both 1-Day and 7-DAY ... Heat pump compatible Backlit, color-coded keys and legends Large, easy to read backlit display Configurable programmable or non-programmable Configurable manual or auto changeover LED indicator glows green or red to indicate cooling or heating Service filter and UV light indicators Fahrenheit or Celsius display Non-volatile memory Keypad lock Accepts the IR remote control accessory Accepts the humidity module accessory Accepts the EZ Programmer Accessory Accepts the Comfort Call Telephone Accessory Model T1700 (1 Day) All of the standard features 1-Day Programmable with up to 4 time periods Auto changeover 2-stage heat, 1-stage cool for use with gas/electric, heat pump, electric & hydronic heat Model T1800 (7 Day) All of T1700 features plus 7-day programmable 3-Heat/2-Cool Controls to, or monitors a 2nd sensor 3-configurable outputs Hi/Low outdoor temps of the day Programmable fan Accepts humidity module Energy Save Energy-Star rated
-
I too was asking myself this question. I ended up with the Venstar 1 day. Using the ISY for control, I can think of no reason to have a 7 day programmable T-stat (Heck, we don't need the 1 day either). According to Venstar the communications port is for several other control options besides the Insteon adapter. I'd imagine if your schedule was always the same you could rely on the Venstars programming to set the climate and just use Insteon for temp alerts or changing the temp via a remote or KPL during uncommon conditions. IMO the 1 Day programmable is all you need for unlimited control with the ISY. Mine has been working flawlessly.
-
Problem is fixed! (the only problem was me!...as usual) I had the dam light plugged into the Passthrough outlet...not the controlled outlet. My New Years Resolution!! 1. Try not to be an idiot. Read and understand everything before jumping to conclusions! 2. Double and triple check the basics of setup and installation! Michel and Sub-Routine thank you for your time. Michel, you usually say don't be sorry but in this case it is very warranted. I cannot waste your valuable time on something this dumb. This ISY has been an amazing device and any issues I've had have been self induced.
-
Yes, I plugged each one directly on the PLM passthru with the same results. The odd thing about this problem is when I first got my ISY, I used one of these LampLinc's as my very first Insteon device to test it. It worked, from there I went to work linking all my existing Insteon devices (that were in X10 mode) and installing new devices. (all of this with 2.7.0). Since then, I never used the LampLinc. Now with 2.7.7 and about 30 Insteon and/or X10 devices all working great, I found a need for the LampLinc but encountered this communication problem. That's when I tried the second "brand new" LampLinc with the same results. As I mentioned in my last post, being that the ISY does in fact communicate with the devces well enough to add them to "My Lighting" with the correct device type and Rev, does that confirm the ISY is in fact communicating with the devices. Is the correct discovery of each device "every time" (I've removed and reinstalled several times) different then controlling a device in regards to communication?
-
FYI I use the ISY mail server for notifications and get email response in about 15 to 30 seconds very reliably. My Homeseer2 takes about the same time via my ISP SMTP.
-
So, does it make sense for two LampLincs to be discovered by the ISY but fail to comminicate with them? If they were correctly discovered as noted by the correct device and correct rev, doesn't that mean the ISY CAN in fact communicate with them?
-
I do have loads on the lamplincs. The query seems to run without error but the status always returns Off when they are actually on.
-
Does anyone know if there are any communication issues with older Lamplincs. I dug out a couple of "New" LampLinc's that I bought about three years ago (when Insteon was haveing so many problems). LampLinc V2 #2456D3 REV 2.4 I installed them via "New Insteon Device". I manually entered the address and let the ISY auto discover. It appears to install them correctly (it lists them as LampLincs Rev 2.4). However when I turn them On or Off I get a communications error - "Cannot communicate with (address) please check connections" I tried them both in several outlets with same results. I installed a new ApplianceLinc with no issues.
-
I also have had issues with dimmable CFL's (both GE and e-lightbulb) in regards to linear scaling. With a setting of 50% on two of the same brand and wattage bulbs, I "sometimes" get a different level (one bulb looks brighter then the other. The other thing with CFL's is (in my experience) they don't last as long as advertised. I have since went back to regular incandescent bulbs where I can set all the on-levels and fades I desire. My switches are too expensive to not utilize their functions fully. "Everything nice...costs more" (unfortunately)
-
Keep in mind the MS link to the lights is independant from the MS to an ISY program. If the lights are linked to the MS then they will come on regardless of an ISY program and if an ISY program shuts the lights Off, the MS will turn them back on if your still in the area. As I understand it, your program will turn off the lights after 5 minutes regardless of the jumper setting on the MS for On-only. It sounds to me you don't need a program at all. Just the MS with the jumper set to ON/OFF. In my application, my basement is huge with a lot of areas that the MS will not "see" me. So I set the MS for On-only and use my switch to turn the lights Off on my way out.
-
tome, The On-only is a nice feature, especially if you are going to leave it to the ISY to turn the lights Off based on your criteria. What's nice about the MS is that even though you set it for On only, it still does the 1 minute count down from the last time it saw motion. During this count down it will not retrigger an On command. An example would be when you are leaving the area, you can flip your switch Off and the MS will not turn the lights right back ON while your still in the area (walking past the MS while exiting). With On Only, you will never be left in the dark because you were in an area outside the MS range or were very still for the countdown.
-
Killervette, I have a similar setup (basement lights). My switch is inconveniently located behind the door. So I put a MS at the top of the stairs. However I disabled the OFF command (jumper 4). Flipping the toggleLinc on the way out is fine with me. It's actually preferable because I don't want the lights shutting off while I'm down there. A great feature in the MS is that even though I disabled the OFF command, the MS still counts down from 60 seconds from the last movement. During this count down it will not send an ON command. Therefore when I flip the ToggleLinc off, the lights go out and will not turn back on while moving past the MS. When the 60 seconds elapses, the MS is ready for another trigger ON.
-
Thank you Mike! My problem was that I set the KPL B button as a responder (thinking, that I only wanted the button to act as an indicator and not a control button). With both devices as controllers all works great. I'll have to revisit the topics on what older rev KPL can and cannot do.
-
I did some searching and think I may be out of luck on this one due to my older rev KPL. I thought I'd do a quick check with the forum to make sure... I have a togglelinc relay switch. I want a KPL B Button's light to match the state of the Togglelinc Relay. KPL V2.9 Any thoughts?
-
Thanks for the update. I have one on the way. It'd be nice to get rid of the query. Not that it is a problem but the less traffic the better.
-
So yours is over 90 days old?