Jump to content

picc02766

Members
  • Posts

    15
  • Joined

  • Last visited

picc02766's Achievements

Newbie

Newbie (1/6)

0

Reputation

  1. This has resolved the problem for me as well - 1and1 email is now working. Thanks!
  2. Thanks Michel, the NTP sync works fine although it was off by 2 seconds when I manually synced it a few minutes ago (it's set to sync every 24 hours). FYI, the temporary email credentials provided by you do work well, I'm just trying to get t working with my own email servers. Also, I regularly access my ISY99i system remotely from an iPhone so the internet connection is solid. I will upgrade to 2.8.1 when I have a chance and try that... regards, Rob
  3. Thanks Rand, finally got around to trying this. Even with my email address in the "From" field I still get the same error, with or without TLS on either port 587 or 25. I'm still at 2.7.15. Thanks, Rob
  4. Hi Michel, 1) I'm not sure, still checking into this - their instructions for configuring Thunderbird seem to suggest they do require TLS. However in all my Outlook accounts, the encryption setting for the smtp server is configured as "none" (other choices are TLS and SSL) and it works OK. I must admit all I know about TLS is that it is some sort of encryption or security protocol. 2) The "From" field? No, I have been leaving that blank. I put the account info in the UserID field - now I'm really confused. 3) 25 or 587 both work Thanks! Rob
  5. Must be a similar issue with 1&1? (1and1.com) I have several email accounts with them and no matter what I try I cannot get the ISY email to work. Never had a problem with any other clients including iPhone. The ISY error generated is "-50001 Mail Server failure (password not accepted)" but I am positive the password is correct. It does seem to work OK with an SMTP account I have with Comcast, but it would be nice to get my automation specific 1and1 accounts functional. Thanks for your help! Rob
  6. Hi, sorry if this was discussed already but I could not find any reference to it. In regard to the second paragraph above - As I was an early adopter of 2.7.8/2.7.9 and my implementation began the last week in December, I don't have a useful backup prior to 2.7.8, if any at all - am I reading this right then that with 2.7.10 I'll need to start from scratch? Also, is there a way for me to tell with what version a particular backup was made? Thanks, Rob
  7. Exactly! It is two-way. That's the scenario I was trying to convey in my post above. Use HomeSeer event structures and keep it all wireless to the HomeSeer side. Then, have HS events fire when X10 wireless actions are detected via the AC-RF2 plug-in setting HS devices (which are really ISY "variables") since these can be made known to HomeSeer via Bob's ISY plug-in. The advantage to this method is no X10 gets or needs to be transmitted on the powerline. The disadvantage is setting up a lot of events to handle the X10 wireless traffic diverted from the powerline. This was my goal as well - with ACRF2 I eliminated all of the X10 RF traffic from the powerline. For me this made a huge improvement in response delay controlling Insteon modules - I went from annoyingly perceptible with X-10 retransmit (via TM-751's) to essentially instant via ACRF2 when pressing an X-10 RF remote button. Not to mention much better coverage and reliability with the W800. Also, we like the small X-10 keychain remotes much better than the clunky RemoteLinc, and with this setup they perform equally well, if not better. Reluctant to go back to inserting any X-10 on the powerline to trigger ISY scenes/programs, but do want to get off Homeseer eventually. I'm still not clear if the EZX10RF will allow me to eliminate X-10 on the powerline to trigger the ISY from an X10 RF device, but if there is going to be a direct W800 type of interface it sounds like that would be the way to go anyway. BTW, for ACRF2/ISY plugin combos in Homeseer, it is possible to trigger an ISY program (and therefore a Scene) without any events in Homeseer, just using the ACRF2 module. I created a program in ISY and "called" it directly from ACRF2 with a Shadowing entry, like so: ACRF2 Shadow Entry in Homeseer: Source Destination 1 Destination 2 A9 Flag - Kitchen HS Motion A9 None ISY Program "Flag:Kitchen HS Motion A9" (Not Enabled) If - No Conditions - (To add one, press 'Schedule' or 'Condition')[list=] Then Run Program 'Kitchen:Motion Sense' (If) Wait 1 second Run Program 'Kitchen:Motion Timer' (If) Run Program 'Flag:Kitchen HS Motion A9' (Else Path) Else - No Actions - (To add one, press 'Action') First of 4 Programs that are the logic for the kitchen motion lighting. All 4 programs are set to be NOT enabled. This one senses X-10 RF via ACRF2 using Shadowing which eliminates any X-10 on powerline. The wait command is primarily there so the program trigger can be seen in the ISY Program Summary. Next, this program calls "Kitchen:Motion Sense" which checks to see if the motion sensor has been disabled (via another program "Kitchen:Motion Disable") and if the lights aren't already on then turns them on. Next, this program calls "Kitchen:Motion Timer" which has a test for evening or daytime, then counts down and runs the appropriate scene based on the time of day. I found that the programs must remain separated like this in order for subsequent triggers of the motion sensor to reset the countdown timer. With the Shadowing entry configured as shown, an A9 ON transmission will call the THEN entry point and A9 OFF will call the ELSE entry point in the program shown above. This code example is for a motion sensor and I don't care about the OFF transmission from it, so the "Run Program 'Flag:Kitchen HS Motion A9' (Else Path)" statement preemptively clears the status of "Flag:Kitchen HS Motion A9" program back to FALSE. This approach saves the step of having redundant events to manage in Homeseer and may be slightly more efficient. Regards, Rob
  8. Hi, new to ISY99 and converting my lighting from Homeseer. So far I am finding ISY makes it easier to do the things I want with my lighting. I have just been going thru my Homeseer "Events" and converting them to ISY programs. I have a few Events (such as Sunset) that I want to turn on individual lights and scenes in sequence over a period of time. I have simply created an ISY program using the "Wait" command between "Set" statements to create the desired delays (see the Code example) - is there a better way to accomplish this? Does this approach unnecessarily use processing resources? Rather than the one Program, should I break this up into several Programs for each of the time triggers? Also, based on the little testing I've done so far, the Wait commands appear to run in sequence and are cumulative within the program. This differs from Homeseer where each item in the event can have an explicit ON and/or OFF delay associated with it. Thanks! Rob If Time is Sunset - 20 minutes Then Set 'GreatRoom:Sconce' On Wait 5 minutes (Random) Set 'GreatRoom:Peninsula KL-Pendan' 35% Set 'GreatRoom:Side Table Lamps' 25% Wait 5 minutes (Random) Set Scene 'MasterBed:Table Lamps Scene' On Wait 5 minutes (Random) Set Scene 'Global:All Ext. Coach Scene' On Send X10 'D6/On (3)' Wait 5 minutes (Random) Set 'Porch:Xmas Icicle' On Wait 30 minutes Set Scene 'Global:All Ext. Floods Scene' On Wait 1 hour Set 'Flood:Driveway' Off Else - No Actions - (To add one, press 'Action')
  9. picc02766

    Dimmable cfl?

    If you don't need a lot of light I have had excellent results with the CCFL's (Cold Cathode) from home depot. The last time I checked they come in 15W equivalent (3W) for about $4 and a 2 pack of 25W equivalent (5W) for about $9. Soft White color temp. Brand is EcoSmart - they come in a blister pack with green colored labeling. These are candelabra base but come with a standard base adapter. I use them as sconce lights for the front, side and garage doors. Plenty bright for that application , especially the 5W model. Typically I do not dim them but they are dimmable - as others have said they can not be dimmed to extremely low levels like an incandescent. They are more tolerant of the cold and seem to "warm up" much more quickly than a regular CFL. And FWIW they do claim a 9 year "life". I have been running 14 of these these for about a year and have had only one failure (HD replaced it). I also use these indoors with very good success as mood lamps. I have 6 mica sconce fixtures that were running with 2x 40W incandescent bulbs each dimmed to about 50% - replaced with the CCFL's at 3W each and get the same effect with a major power savings.
×
×
  • Create New...