larryllix

Mine is still in the package yet. It will be making an entrance soon.

It would appear, by definition, RF communications are synchronised, slowed down, and dependant on powerline zero-crossings as evidenced by this from the document:

And that must be based on a 60Hz assumption for the same reason no dates were on coins marked BC. Also based timing from the previous zero crossing it would put the signal right in the middle of the garbage from a modified sinewave zero noise and/or keep confusing the frequency with front end and back end zero-crossing timings. Who knows what evil lurks in the hearts of modules?

OK, I would have thought that the " Smoke / CO / Clear. It does however show OFF for Low Battery, Malfunction, Test, and Unknown Message" points KHouse mentioned would be considered status points. My terminology in this field is not up to par and it sometimes conflicts with my other fields of involvement. Either way they are not responsive to ISY end polls/queries, if I read you correctly.

Will an ISY Query update those points or does it require human intervention at the smoke detector?

So in ez1976's case he may be able to use the PLM with a stepdown transformer on 50Hz. It may only function on RF. OTOH: Didn't I read somewhere European Insteon modules using a different frequency for RF? Nothing like having a loose return policy.

IMHO A "pure sinewave" inverter should be used for sensitive electronic equipment like a PLM. The waveforms displayed are from a "modified sinewave" inverter. I would be surprised the Insteon signals would work at all if they are zero-crossing dependant. Modified sinewave has that pause between polarity switches that may play havoc with timings and also be load nature dependant. At least the pure sinewave inverters have a few more steps in the wave and can be filtered a little better but than we have a signal absorption box for any powerline signals. Maybe we only expect RF to survive to dual band units in this situation?

I noticed the two conditions right away. In HomeSeer, the timers were not retriggered but you could use a cancel_event command to retrigger them. Been too long for my old X10 system logic, now but they had one timer pending PER DEVICE. If . Time_is_late=true Then . Go_to_bed Else . pass_out Thanks for the education!

I haven't thought about "partial ONs" yet as I have no wall dimmers or switches but I have been aware of some of these "non black and white" states devices can have and trying to avoid the gotchas later with careful conditions code. Yeah? Who am I kidding? I change some code every day. I meant "every hour". Trying to reorganise my X10 addresses to accommodate TM751 RF modules around the house. X10 address movement is a grind with the ISY though. You make an address plan and then some MS won't reach that RF module. Plan G next. Thanks.

Yeah it will do anything you want it too. It has no "else" in the version I tried v2.3.x pro. ISY does and that makes programming a little easier. It supports a tonne of I/O systems just as ISY does. Of course it always takes hardware to do the actual communication. From what I could tell in my few weeks of testing it the Pro didn't offer much more than the regular version for about $200. I didn't want the voice package in it and spent the boot-up time disabling it everytime. That was the main difference I suspected. I would have purchased the regular version if the ISY hadn't come along for me. I like the idea of a PC to do "extra" things and it looked like it might be easier to interface to Having said that my PC just started having memory problems. It is too bad you can't get a EU adapter to work with ISY. I like it so far. It's a fair step up from y MsDos software with X10 modules. Mind you the Insteon system has a lot more quirks an is a little less straightforward. Problem solvers love this stuff anyway.

I kind of figured that one after previous indications that timers were all retriggerable. Glad to have it stated another way, to pound it in a little deeper. Thanks!

I was going to suggest a small step-down 220/120 transformer for the PLM if Israel runs 50Hz the signal sync-up protocol probably won't work.

I wouldn't say it was better or worse. I only loaded Houselinc for a few days with it but it sucked in MY Windows. The objects on the app were all placed at absolute pixel addresses and I couldn't even see most of the acknowledge or OK buttons on the bottom or right side. It became useless on two on my PCs with no way to scroll to the controls so I can't say what it did. I got the impression it won't do much compared to HomeSeer. HomeSeer can do it all, just like ISY events and conditionals, but appears to more of a hacker-type environment, so it depends where you are at with your development personality. You will need a computer on 24/7 to run it. There are self contained boxes, http://www.aartech.ca/automation-controllers but my wallet hurts too much. I didn't try any of the speech in or out features. You will require a third party module to interface to the Hub. It is available on their forum for free download as v1.9.xx but you will have to do some nitty-gritty file installing, etc., for the non-pay module. Look for the HomeSeer forum for lots of discussion.

I do a similar thing to Xathros, above. Every event that can be caused by a human (mostly motions sensors and keypads), after adjusting lights immediately, call House_Occupied. House_Occupied sets reasonable timers for expected future movement detection. Night time is the biggest problem when no movement is happening and I have to use 8-10 hours before resetting the flag/variable to get through to the morning. During the day the time out for Occupied status can be shortened to about 2 hours depending on how many motion sensors you have. A motions sensor where you typically exit the house can have a shortened time by making the assumption you are leaving. With my old house and X10 system I ran my furnace fan much less when Occupied = False. My heat takes a full day to recover so it only gets setback manually on the stat and returns by the manual timer set at that time.

The typo was in the forum. Just alerting him they were spelled differently. You never know.

Thanks! Just to clarify that: If a trigger condition changes and logic becomes negative, resulting in the "else" clause being invoked, the "then" clause wait timers (and following lines of code) get cancelled right where they are?

Mine reports that I have purchased a module before I owned the ISY. Perhaps a few bugs to work out in their purchasing software, yet. I am sure their staff would be able to help you out with that here, a call, or online help.

I have used HomeSeer Pro v2.3 with a Hub. It worked quite well but the versions I tested were quite early in development. HomeSeer offers a 30 day free trial and there are hacked older versions out there for longer trials. It's a little pricey for me.

Is there a problem just running programs with no conditions defined from the (if) entrance? I have been running programs (if) as subroutines, without conditions, and all seems fine. Is this asking for trouble down the road?

Just a few observations: -Your program call has an exclamation mark at the end of the name 'Shop side motion action disable!' and your listed program doesn't. (typo?) -If 'Shop side motion action disable!' is enabled for external triggers it should flash 'Driveway street lights' as the status is in a negative feedback loop. - What is in '1x motion beeps' (Then Path)? That should occur during the day. Perhaps a clue there? -What's with the additional seconds? Testing hangovers?

I don't own one of these devices but... You stated they were at "too bright" at an initial brightness of "0"? Later you stated "to 255 brightness it is not close to as bright" Aren't they at opposite ends of the scale?

I do this with my X10 motion detectors that directly operate an Insteon LampLinc. The LampLinc is set to slow response (unfortunately on and off have to be the same) and then my ISY has "Then" code that sets the Lamplinc "Fast On" and it overrides the slow on time. This way I can have immediate on times (with a slight visible starting ramp) and slow OFF times for a better high-tech look. As an observation, should your garage door control even support "fast On"? Although I have it ("fast ON")listed for manual controls in ISY the ApplianceLinc modules I have will not respond to "Fast ON" or "Fast OFF" at all. They don't support dimming and therefore cannot do ramped switching.

If you are in Canada here is a few to start with. I am not sure how the multiple zones can be done on this system. http://www.aartech.ca/insteon-thermostats

Damn! I guess I have to watch my model numbers closer. I didn't realise those were the ApplianceLinc units I can get at aartech.ca for $34. I ordered two that will be going back for that price! I hope they deal with that at the store even though I am two hours away from one. I could probably make use of a few but not for more money. Most of my X10 units I bought for $5-$10. The LampLincs at BestBuy and FutureShop online and stores look like the latest model though. Aartech.ca had the Motion Detectors on sale for $24 but they sold out quickly.

FutureShop still had both ApplianceLinc and LampLinc units, on sale, in the Waterloo, Ontario store, December 27, 2013. Hub Starter kit for $125.