paulbates

Calling this done, with the exception of putting it in a project box. It's working well for those cloudy days when its dark well before dusk. Here is the parts list for those interested: - 2443-222 Micro On/off module - Solus SPC-320Z 120V Automatic Dusk to Dawn Photocell - Look that up on Amazon, $12.45 us - 120v AC power cord with black/white leads. Notes: - Wire it as shown in the picture a post above. Wire the red lead from the Solus sensor to the yellow sense lead from the 2443-222. Cap the purple lead or cut it off. You can wire it as needed in your case, including possibly fitting it in a lamp post and wiring the lamp post light to the 2434-222's load terminals, or the red lead from the sensor, whatever is easier / safer / best for wiring. - The Solus SPC-320Z works with the 2443-222. It's likely that the design of these sensors use triacs, could cause bleed voltage on the red line that will make it appear on all of the time to the 2443-222 or other flaky behavior. If you choose to try a different sensor you'll have to find out how that works. - Use the out-of-box Latching mode for the 2443-222. Double check by opening options in the ISY and making sure every option box is un-checked. How to use: - Use the 2443-222 as the controller for any Insteon devices you want switched on when the photocell detects dark, and/or switched off when it senses light. I'm not doing this as it switches on & off twice a day about 20 minutes apart as it decides dusk/dawn. Also, it decides on dusk about 30 minutes sooner than I like. - ISY programs. I'm using programs, adding a delay via eISY wait commands in a program to delay the actual turn on of the lights. When the solus does its second trigger for dusk, it restarts the program and lands close enough to my desired "on" time.

The motion sensor can be set to send an "on" to a device or scene when it detects motion, and then sends an "off" after a specified amount of time. You'll need to look at the manual for 2842-222 as well as options in the admin console to change the settings. Some things can be set in ISY options and some things are jumper pins on the back..but its not hard to figure out What type of light is it.. regular, LED, fluorescent, low voltage? An unreliable "off" command could be because the light you are turning on is injecting line noise and possibly cause the "off" message to not reach the switch once its turned on...unlikely but possible and easy to eliminate: To test if the load is the problem, remove the light bulbs if possible and retest. If that doesn't solve it, add to your program's then clause, put a 3 second wait at the end, and another turn light off. The motion sensor does this, it sends 2 "Off" commands a few seconds apart

Do you have an eisy and a functioning python dev environment set up to work in? Here are some things to review to get started, assuming you answered "yes", twice, above: There's an python API that defines communication with the eisy resources and formatting of data appropriately: https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:Python

@IndyMike and @Geddy Thanks for responding The same happened to me Mike... a while after discussing it here, I made some mods, another program I left alone, and they all went to where they should be for Next Scheduled Run!(?). Included in this was no longer having it wait a day to start a new program with a schedule. Calling this one closed, thanks again

Thanks @IndyMike. Could be something that's been there all along and didn't notice or forgot. I'll update it and let it run and see what happens.

Thanks @Techman. I created a new program with only the schedule condition to trigger at dusk minus 30 minutes and no other conditions. Its first "next scheduled runtime" is tomorrow, thursday at 5:53pm, and dusk today day is 5:17, so it will be a few minutes before that. Wondering if you or someone could create a test program like above with the only condition being if time = sunset - 30 minutes, save it and then look at next scheduled runtime. If it doesn't happen on other systems then I'll know it's something specific to me and I'll submit a ticket. Thanks in advance if a couple of people are willing to try that

I'm guessing its dst related, but I'm writing new programs on a new eisy so can't be 100% sure I'm writing programs that look at time. At this point I'm not worried about the one running the next day vs today. The problem is the "next runs" are all times that look correct for before DST took effect.. an hour after the sun has set. The eisy reports the correct DST at the top, but next run is ~1 1/4 hour behind. Am I doing something wrong? The "Lights on at Dusk" program was working as written before the time change Take a look: (Sorry about the eye strain on the last one, it can be "zoomed in on"

An Insteon Dusk/Dawn sensor using a on/off micro module and lamp post photocell survived bench testing and sample program. I'm putting it on the front porch today and see how it does and think about a project box and a final home for it... if it works

I have an eisy with the latest iox. While my system did successfully change time related to DST, I have a problem with this program: Lights on Dusk - [ID 0003][Parent 0002] If Time is Sunset - 30 minutes Or ( 'Premise Lighting / Back Patio Lights - Kitchen' is switched Fast On Or 'Premise Lighting / Back Patio - Living Room' is switched Fast On ) Then Set 'Premise Lighting / Premise Lights' On 75% Else - No Actions - (To add one, press 'Action') When I look at the program summary tab, it's next scheduled for tomorrow @ sunset - 30, not today. I had this same problem initially when I first set up my eisy.. I wrote this program, earlier in the day, and the "next scheduled run" was the following day... not the day of as it should have been. The problem cleared up after letting it run the following day and its been fine... until DST change. I have 2 time of day programs that shut these lights off at specific times and they are both scheduled appropriately. I just rebooted the eisy, no change.

Looks like you have a 99i? These threads cover some things to try:

Also possible-to-likely is that the new router's ip4 subnet is different than the old router's. Via the mobile app: Settings Systems Pick your isy Scroll down to "local connection settings" Your ip and ports will be listed there

As it's deprecated, the 994 is not receiving updates, including the added ability to support new insteon i3 devices. It requires the eisy.

I'm enjoying using udm... I'm on a several week camping trip and able to check in on eisy.. easily. I'm in the transition period of being less reliant on the AC and learning things I have to do there versus udm My question is about the refresh circular icon at the top right. Operations of the eisy, programs and insteon control/status events, seem to make it to the app on their own and instantly. Some local AC changes like programming updates or insteon network changes don't seem to make it right away and the refresh captures it Is there a time frame for local changes to catch up, or is it best to refresh app instances after making AC changes?

Yeh I'm not going for precise room to room control. As you'd expect, the second floor is off a few degrees from the first; direction depending on the season. With the venstar colortouch, 'averaging' could be selected between the stat and the remote. That helped a lot without doing zone surgery to an existing hvac system, other than a few one time adjustments to the registers and paddles in the ducts. This cut down on the "why is it hotter/colder up hear" comments.

I had venlink that led to nodelink for many years at my previous house. I set everything up, and it just worked including integrated notifications through pushover. And to your point, I kind of forgot how I did it. Almost forgot the logins to the rpi. It's hard to see that these programs appear to be fading away. @io_guy has provided this community much and is very responsive and his software did my property a lot of good for a long time. Now I'm starting over at a new house with an eisy. I'm looking at an ecobee, but to @larryllix's comment, I'm not sure what functions I need to automate it with the eisy. The ecobee is very capable on its own. I'll put it and a remote temp sensor in and see where that gets me.

@PGannon - I just got an eisy and have a program to turn on premise lights 30 mins before sunset, and had a similar experience yesterday. I got home and the very simple program hadn't run. When I used the admin console and looked at the programs tab, and then summary sub tab, the program's "next run" was scheduled for the next day, not that day -- and it was well before 30 minutes before sunset. I added a hard time condition in addition to the 30 mins before sunset as I was going to be gone. That ran, and then the "next run" was for the following day (tomorrow) which is right. Not sure why this was necessary, but once I got past the programming running once on hard time, it was fine.

My previous house had older Insteon devices that had been running for a very long time, years. Occasionally link tables in certain devices got 'confused' needed to be restored after running for long periods... especially those on the signal/wire feet edge of the Insteon network. Right click on the device and select "restore device". That helped frequently especially with older devices.

I'm just getting back into the ISY after a few years of not touching it, only using the functionality my old system provided at the house I recently sold. I just got an eisy and have an older w10 desktop in an inconvenient place in the new house. I got it setup yesterday and tried the "cloud" version of VNC to access it as my main device is an ipad. Works well, the usual remote AC eye strain & tweaking fonts and window sizes. After reading this thread, I gave the mobile app a try. It does a lot. Granted my setup is small right now and only a couple of small programs, but it's workable, small changes happen much faster IMO. The only thing during setup that the AC can do that the app couldn't is the Insteon diagnostics. Out of the box, the new Insteon PLM would not be recognized by the eisy, and factory resetting it worked and could be verified on the AC.

@dex Yes it seems like a simple enough requirement, but hard to get to 100% right all the time. For the old insteon motion sensor with a dudk/dawn sensor method, I had it as "on only" during a time window... Once it was on, it stayed on fot the night and didn't react to on until dawn timeframe The either station seems good if it's close enough to the house to be the same conditions

What types of things are controlled in your smart home structure you wish to bring with you? There's to groups of HA enthusiasts; part of the answer depends on which of those you see yourself in and what you are automating: Hands off Automation - you want events to happen on their own by schedule and/or sensor Assistant Automation - you want to tell Alexa, google or your phone to turn something on and it turns devices on or does things. Which of those 2 sounds like what you want to do? If you're looking for the second type 2., that suggests you have relatively low latency internet available, regularly.

@IndyMikeYep thanks, you covered the climate / latitude topic better. Going back to my x10 days i added a photo cell to the 10 io module.. as there were many days the schedule programming did what it was told to do, but missed the right on-time because of clouds. I lost all the notes and emails on that from over 20 years ago about that solution. I do remember that the same circuitry setup would not work on the Insteon version of io module, and was very glad when the last gen Insteon motion sensor came out, it got it right most of the time

@IndyMike Sorry Mike, I wasn't clear about that. In this house I'm sticking with an all Insteon network, and looking for a solution goes "switched on" when it's actually dusk outside. I'll consider the other ways you mentioned. At my previous house I did use io_guys precursor node servers for a few years on raspberry pi's, and then his node link, and then add UDIs geofencing and a few others. That house was older and had old house problems and the ventstar stats I had and programmed in nodelink did a lot for comfort, heat and humidity. That was all good learning, but this house is relatively new and doesn't have the old house problems. This time around I'm keeping it relatively simple and mostly marking a few virtual circuits and adding premise lighting. @elvisimprsntr Thanks and that's sound logic. I did have a setup at my previous house that used time offsets as you're suggesting , but some days mostly due to weather it got darker earlier. The dusk/dawn sensor in the last rev Insteon sensor worked great. There was an ISY dusk dawn program that used schedules but also switched on if the dusk dawn kicked in. I have an idea I looked at in the last few days using an Insteon embedded module and cheap lamppost 110v dusk dawn sensor. It'll either work, or not.. not to much spent if it doesn't

I'm adding Insteon switched premise lighting to my house. I'm looking to re-create the dusk/dawn node capability of the previous gen Insteon motion sensor. The question: Is there advice on getting that capability sensing open/close with a photo cell and/or other parts?

Thanks Geddy and Larry. That helps me figure out how to proceed. I like the familiar: stability, reliability, flexibility and what I know. The node server and portal features were more important on the 994i at my 75 year old last house and there I used io_guy's server to manage comfort / humidity. I'll get a few more virtual circuits going for scheduled exterior lighting control and go from there.

I've not been active for a few years, its best to say new life and new house. My 994I & Insteon devices worked fine for years and sold with my previous house; I left the new owner the email account, passwords, a google doc with basic info and recommendations. I'm starting over from scratch and simply. The owner/builder of my new house wired very atomically with switches galore, so I've been adding a few virtual circuits at a time. I've watched the Insteon business and manufacturing turnaround and it was easiest for me to wire switches in and link manually without a controller. I'm not motivated to leave Insteon's flexibility. But, hey, its me.. relatively soon I'll want a controller. The Insteon hub hasn't changed much capability wise, so it'll be an eisy and a new 2314U. I want to make sure I traverse the 994I to eisy gap successfullY. I read @lilyoyo's eisy questions doc from last December (Thanks, great job). I think I get it but will make a few assertions and hopefully I can get confirmation or corrections: Maybe new product names, but it's the same solution architecture: BSD under the hood, java app on a windows PC that finds the eisy on my (wifi) network? Same tabs device, programs, interface etc? Same basic Insteon device/network config capabilities, network crawl? UDI and Insteon still have as good a relationship as they've had in the past The I3 gap was successfully closed Anything else to know from the past 3 - 4 years?