larryllix

As an alternative This could also be done with only six programs for the hour using a binary search algorithm is program count is a problem. Of course apostolakisl's other programs would still need to be integrated to keep track of the minutes. Trigger chain If Time is 0:00 OR 1:00 OR 2:00 OR ..... OR 23:00 Then Run Hour16 (If) Hour16 (disabled) if Time is from 16:00 - 23:59 Then $Hour.temp = 16 Run Hour8 (If) Else $Hour.temp = 0 Run Hour8 (If) Hour8 (disabled) If Time is 8:00 - 15:00 Then $Hour.temp += 8 Run Hour 4 (If) Else Run Hour4 (If) Hour4 (disabled) If Time is 4:00 - 7:59 OR 12:00 - 15:59 OR 20:00 - 23:00 Then $Hour.temp +=4 Run Hour2 (If) Else Run Hour2 (If) Hour2 (disabled) If Time is 2:00 - 3:59 OR 6:00-7:59 OR 10:00-11:59 OR 14:00-15:59 OR 18:00-19:59 OR 22:00-23:59 Then $Hour.temp +=2 Run Hour1 (If) Else Run Hour1 (If) Hour1 (disabled) If Time is 1:00-1:59 OR 3:00-3:39 OR 5:00-5:59 OR .......OR 23:00-23:59 Then $Hour.Temp +=1 $sMiinute = 0 $sHour = $Hour.temp

If you have more points to monitor and/or want ISY to be in control of notifications to your mobile or email you could use the cheap ($1.99) 1wire probes with an Autelis box, WC8 or Rpi with adapter. More complex but if you want to monitor several temperature points it could be a fun project for you. Probably looking at the $100-$160 range all done with enclosure etc.

Can't be done with ISY 4.x.x or earlier without having access to date/time in variables. With a real time clock inputting data into ISY or Apostolakisl's program sequence to break out the date and time info into variables. Just save a compound variable created from date and time along with the data to be saved. Notifications currently (v4.3.0) can send date and time in notifications but cannot save them without a technique stated above. Am I missing something? this sounds like a very simple request. Maybe my middle eastern Canuck accent?

I use a variable as a heartbeat from my WC8. The variable is formatted as MMDDhhmmss. I figured the year wasn't needed in ISY. After some experience with ISY becoming busy I have slowed the heartbeat down to every 15 seconds. Each time the new heartbeat / datime is changed and it is greater than 0101000000 (Jan 1 Midnight) I save the value in the "init to" register. When I ISY boots up a Boot-Up enabled program sends notification of the current date and time along with the last known WC8 datime variable IIRC I exploded the variable to look more human on the notification. This variable value could be stuffed into an adjacent variable (until ISY gets user defined indexed variable types Michel shudders!) with any recorded variable. After power failure I can tell from notifications how long the grid was out. A fairly constant boot time has to be subtracted from the time difference.

ISY RULES!!!

Ditto on the Belias programs for leak detectors. I use them with modifications. mainly names of the programs that make sense of function to me. I have nine InsteonMS units and have never had a problem with one yet. oooops... I did have one go bad and aartech.ca replaced it, just on my word, with a paid return shipping box. The range is good (look for the desensitise range jumper installed), even with my one room over 25 feet long from the corner mount, and with a direct link = scene the lights respond without any perceptible delay. I have had two false motion detections (I use them for a security system notification) in the last 9 months. One I write off to the unit seeing my bird move in it's cage at over 25 feet away, and the other I wrote off to lightning. I was away and could not tell but I knew that no other unit had triggered so either I had no intruders, or the intruder(s) went back out the same window. I have MS motion counter detectors so when I get house status reports I can compare counts with yesterday's and the day-before's counts. I also have tracking programs so I can see a history of MS units and the order they are triggered tracking motion. I find these units invaluable for real HA since I don't consider remote or local control of device HA, only control with no smarts. I find the Insteon MS units 99% as reliable as the hard wired DSC dual element motion detectors installed by professional alarm companies.

Good! Looks like the comm link was badly installed somehow. Note the manual says it can detect 7 watts to ??. I would increase your setting over that to insure function. Also you can increase the load setting, with the AV unit on, until it indicates 'Off' and then you know how many Watts the AV unit takes. Set much lower to insure no false triggers.

If you don't want the MS to retrigger the timer then use "Status" to trigger the program. If you want a manual override that the MS cannot cancelit takes two programs or more. Auto Program (enabled) If Control MS is Switched On Then Set Light On, Wait X seconds, Set Light Off Manual Program (disabled) If Control Switch is Switched On AND Control Switch is NOT switched Off (runs else) Then Disable Auto Program, Set Light On, Wait 6 hours, Run Manual Program (Else) Else Enable Auto Program, Set Light Off.

Good to hear!

You have the unit to send On at 2 Watts and Off at -3 Watts which will never be sensed. Read the manual. It tells you it cannot sense less than 7 Watts and describes their self calibration technique. If ISY doesn't update you may have a comm problem. Viewing the Event log in level 3 may show the number of hops left varies, indicating flakey communications. Did you Factory Reset the SynchroLinc before linking it to ISY? That would be my recommendation. -Factory reset the device. -Follow the downloaded manual (Google the model number and download from SmartHome's site) to set the unit to your AV load. -Link to ISY again. -Now you can view the set load factors from ISY and tweet them if desired. -Turn your AV equipment on and off to test while viewing the Admin Console status in ISY. -Do not allow the Admin Console to sleep in Windows or statuses may not update in Admin Console under Windows.

Usually a simple Then WAIT 1 second Send notification can reduce contact bounce and multiple sends before sending notifications.

I have two different versions of the 2441ZTH. The older unit can be set by ISY no problem while the newer unit cannot. I only use my two thermostats as probes and they update well based on their design. Humidity updates every minute and temperature only updates on a temperature change of about 1-1.5 degree C. Unfortunately they did not put a heartbeat temperature update or a "update -all" time based cycle to supplement the report by exception technique. When linking these units I find there has never been a 2441ZTH unit listed in ISY and I suspect that UDI thought the 2441TH profile would work sufficiently but many features do not function including increment and decrement temperatures for the 2441ZTH. That is totally internal to ISY firmware. As I reported here, SH has changed the communications profile somewhat and I suspect not released the new styles to UDI for update in their database of devices. Until better and proper support for the only native Insteon thermostats is produced for the ISY, I give up on attempting to do anything further or serious with them. They are just probes at the moment. See signature line for f/w version. I have updated with almost every version since 4.0. They never worked completely for me but I also suspect some features have quit in later ISY versions.

It is a load sense device. What do you have it sensing? If query gets an update OK then it should be working. When the load status changes (passes the threshold) it will send an update to ISY. You have to calibrate the thresholds from ISY according to the appliance you are monitoring.

They are stated as coming from amazon.com shipping and not SH if you proceed to the last step without committing to the sale..

Multiple dimming commands are not a problem with Insteon. If you use a ramp of 2seconds or more all bulbs will dim together. I have some bulbs that look faster responding than others so I set the ramp speed different and they all appear to dim or brighten together. Adding a level function to scenes would add more data to scene command protocols and yeah there is no hope for that in the existing Insteon protocol. I have resided myself that dimming will be done in discrete clicks at about 100%, 40%, and 15% for LEDs the rest is really not that much different in the mood department Scenes handle this quite well. Incandescents have a completely different response curve to dimming so the 40% would become about 70% and 15% about 30% Some LEDs will not light up from cold below 15%. Regardless, multiple scenes would work just as well without 256 steps.. I have four Hue bulbs and I am not impressed with their lack of green or blue capability, their price, and lack of setting memory. If I didn't have an ISY all their bulbs would be on full brilliance after every power failure in the middle of the night. My MiLight units, at less than $20, produce all beautiful colours but cannot mix white and RGB and only four to a hub. Yuk. I have two hubs now. Hopefully a Wi-Fi bulb with a reasonable price tag and features will arrive shortly.

Looking again I realised I also got my logic backwards. This may work better. Multiple time frames for weekdays vs weekends could be added. Careful with your parenthesis to group conditions. If From 10:30:00PM To 5:00:00AM (next day) AND Elk Area '1' 'Armed State' is Disarmed AND Elk Area '1' 'Armed State' is NOT Disarmed <---runs else if armed again. Then Enable program 'Reminder' Run 'Reminder' (then) <-----starts timing Else Disable program 'Reminder' Program 'Reminder' (disabled) If Elk Zone 'Family-Motion' is Violated OR other zone is Violated Then Repeat Every 30 minutes Set Elk Speak Word 'Alarm' Set Elk Speak Word 'Is_disarmed' Else --

Does this mean we can crack this unit open and use it for a voltage level crossing detector for other uses complete with a heartbeat and other functions? With a voltage divider this could detect any voltage for a feed into ISY for solar systems battery chargelevels or other analogue sensor inputs. Fabulous!

A scene is a "preset" to eliminate much of the data traffic as well as some of the time delay to turn multiple devices on to a preset level and ramping speed. If we want custom, non-preset, one time settings, for a device we just issue a custom Insteon command to set that device to that level. ISY even goes so far as to make the Scene presets modifiable by injecting special communications on a pre-thought basis. It makes no sense to have a custom preset setting when we already have all the options. Just create another preset or scene and use it. Each devices can hold what?....250 scenes.

I believe one of the techniques was to just impersonate an existing link. An increase in initial contact security would be worthless. As long as the communications are unscrambled this problem will never go away without redesigning the whole Insteon protocol and tossing all devices. One of the stronger security items already existing may be that Insteon is synced with the 60Hz. I am not sure how important this is to the originator of the command signal. An Insteon modem running off a 12vdc car battery, parked outside your house, may not be able to sync with you existing house system 60Hz without some fairly sophisticated equipment to lock in and remember the phasing associated with monitored signals.

Development of an Insteon monitor with minimal hardware would be an awesome project! Obviously some hardware to input RF or clean up powerline signals would be needed. It would nice to observe some of this traffic from another vantage point possibly proving some other problems Insteon may have created. I did this with X10 and it allowed me to troubleshoot some networking problems much easier. I also found old modules I had forgotten I had plugged in.

http defaults to port 80 and is typical for ISY internally to your LAN. In the Admin Console look under Help|About DDNS requires a DDNS provider service. This sends updates of any changes in your external ISP IP address to the DDNS provider. Tthen you should be able to remotely access your ISY, using the URL they issue you, through their IP/port conversion to your router and it's IP/port conversion to your ISY.

If Or Control 'Door Sensors / Man Cave Door Sensor' is switched On Then Set '90" Flat Screen' to 'Off' Set '900W 7.1 Channel Amp' to 'Off' Set 'Massage Chair' to 'Off' Set 'Heating Pad' to 'Off' Set 'RoboVac' to 'On' Wait 1 minutes Set 'ComboDoorLock' to 'On' Set 'ManCave Lights' to 'Off' Set 'Staircase Light' to On Wait 2 minutes Set 'Staircase Light' to 'Off'

Cool! I see you use what appears to be constants also. I denote them with a $c...... prefix for easy reading like this. I also use some programming language style by using all uppercase but it is very abrupt and not sure about that one. $s_RackTemp < $cRackFanTempLimit

Remember we are east of you and will have this installed before you even get out of bed! :)

What is driving the horn? Are your wires intertwined with other wiring?