larryllix

As per LeeG above. IOW: ISY does not know the actual status of anything...only what the last thing it has been told. Some more recent heartbeats never send Off... just On = "I'm alive!" Some device can be queried forcing them to send their status. Otherwise ISY just remembers on the last signal it saw that changed the device's status. If the heartbeat is always an On signal, ISY thinks the status is always On. Think about this one. If the battery goes dead, you didn't expect it to send a signal telling anybody that, did you? I know MS units are supposed to but many are reporting they never do. I have had three MS batteries go dead without a peep, now.

Most of my Heath -Zenith motion sensors lights are on for every snow storm. Every brand I have ever had does this. I doubt they detect heat but rather iR spectrum light. The better units have two sensors and detect differential changes. The cheap ones just detect ambient light changes due to only having one sensor. The sensor may be composed of two sensors on some. The Insteon units seem fairly stable and do not false much, that I have seen. The X10 units will trigger with ambient lighting changes, car lights passing, etc.

Wouldn't swirling wind and/or snow set them off constantly. Weather sets all my other 120vac MS light units off constantly. This would be good to hear from others using Insteon MS units outside.

You have to watch your fonts and their text aspects when you post in this forum. Font attributes seem to initialise randomly. You can click edit, select the text, and then change the size or probably undo the subscript. I can't even make out what you posted on my screen.

Read LeeG's post above. You show them set to 9 minutes.

Use "devices" or "Insteon" dependingv on your f/w version.

Some programs posted did not have the shutoff.

Are you using += ?

Factrory reset them both and do a Restore on them both. It's always worth a try and it's really easy.

I thought it was niggardly using the SwitchLinc somewhere else.

I wouldn't bother doing scenes for that. Just set the levels you want in the programs.

Now take a model 6260 and label the 60 minute button "ON" and label the 10 minute button "Off". There you have DIHA. (Distributed Intelligence Home Automation). I have seen some of these units with more logarithmic scaled times. More like 10,30,60,120 minutes.

That's all that simple bathroom fan timers do. You press a button usually labelled 5,10,15,20 minutes and get that many minutes before it turns off.

A simple nonInsteon timer would have saved a few bucks unless a cyclic program to vent the bathroom on a weather dependent schedule is also wanted

Does that mean your lights came on alternately, A or B but never together?

Start a new thread. Different topic and more will find it and possibly join in.

If the fan is wired to the same switch you want to turn the fan off with you are basically out of luck. Once you tap the bottom of the SwitchLinc paddle the fan is turned off without Insteon or ISY programs or scenes. However, you could turn the fan back on and then time it off or use another signal to turn it off. For a double tap on the top (fast on) that could work. IF control fan is switched fast on THEN wait 10 minutes set fan off ELSE (optional) This way whether the fan is running or not the timer will be initiated and the fan should shut off. The danger is you could miss the double tap and there is no feedback to the success. In view of this do not get rid of your basic program with a very long timer like this (have both) or you may come home to your fan still running. IF control fan is switched on AND control fan is NOT switched off THEN wait 30 minutes set fan off ELSE set fan off You could also acknowledge by flashing the LED or beepig the SwitchLinc but I doubt you would hear it with a fan running. IF control fan is switched fast on THEN set fan SwitchLinc LED 0% set fan SwitchLinc LED 100% set fan SwitchLinc LED 25% <--- or whatever brightness you like wait 10 minutes set fan off ELSE (optional)

No. I am saying the flashing of the LED doesn't indicate anything, except you pressed that button, and is not a debugging tool. Scenes do not detect a device is operated from anywhere. They only detect signals from the devices that are controllers defined in that scene. Something has to initiate every scene. Random devices, not in a scene, operating a device, that is in that scene, do not activate that scene.

All my keypad buttons flash when I press them and they aren't linked to anything. The 2-3 flashes after any keypress is built in to the device and not related to scenes, communications or ISY programs.

Without having the syntax handy right now.... Just send the rest command to set the same variable to ISY setting it to -999 or 999. Setting the thermostat directly from Echo control would be suicide IMHO. That would be like putting your thermostat on the coffee table for every child and big kid to play with it. Good joke the rejected vacuum cleaner salesman setting your heat up to 40 degrees C just as he leaves your home. ISY can sort out the value it gets in the variable, apply scaling factors, check for reasonability, interpret the values for special command like Up/Down, and apply situational logic (time of day) to values to further check reasonability.

If the echo cannot do any conditional logic, can you have Echo send a 999 and -999 for Up and Down, respectively? ISY could sort this out easily by filtering out ridiculous values and making exceptions like the values below to run a program that looks at the current setpoints or temperature, adds/subtracts half or one whole degree and changes that setpoint.

More history on this. http://forum.universal-devices.com/topic/12934-isy-support-for-insteon-hub/

I would make sure it is returnable. Many report having them in their tool box but I have yet to hear anybody using one successfully but then the need for such a device is waning.

This equates to 0x3B7516 and I can't see any new bits in the quantity. 16,38410 would have been a different story.

I had one about two years ago when I first started with Insteon. I thought it would translate X10 code to Insteon. It did, Another feature of the EZX10RF was to repeat X10 signals. I thought this would be a good idea. it was not. It repeated X10 signals so that things got the signal twice. X10 does not have enough intelligence in the protocol or devices to handle this properly. However the unit I had also did another bad thing. It not only repeated every X10 signal it repeated the previous X10 unit code combined with the current house code and command. eg. Turn A4 off X10 = A4 select, House A off Turn B5 on X10 = B5 select, House B on The EZX10RF would now send B4 select, B5 select, House B on This would turn B4 on which was not sent or desired. I had to resurrect my old home brew monitor software to find this. I concluded this was not a bug in the manufacture but a bug in the engineering design. The repeating of X10 was too intelligently done to be a bug in the firmware. and I eventually found a company person bragging on a forum about how they added X10 code repeating after a certain version. The unit went back as defective. I haven't touched any of their products since and they have some nice I/O devices. Too bad for Insteon users. Hearing about some of their other product design flaws has only reinforced my opinion. According to their claims the device should be a perfect fit for your application. The PLM will receive X10 signals on the powerline only and work with other X10 bridges that you must already have.