Techman

Your main problem seems to be communications between your devices and the PLM How many devices and programs do you have? Are the devices dual band? Are you using any access points? Is the PLM plugged into a filtered power strip? Are any other devices plugged into the same outlet as the PLM? What did you do a factory reset on? Did you ever have good communications between your devices and the PLM?

How many devices and programs do you have? Try temporarily disabling devices and programs until you come upon the culprit. You may have a communications or/or other issues occurring at the same time. Take a look at your log to see if there is any unusual activity.

If you do a restore PLM there's a good chance you will free up memory as the restore deletes links that are no longer being used.

PC board jumpers try Radio shack or electronics supply

fahrvergnuugen, Split your program into two programs. The first program will trigger the 2nd program. Once triggered, the 2nd program will run its course even after the motion sensor shuts off. IF CONTROL 'Motion-Sensor' is On THEN RUN PROGRAM 2 then clause ELSE (blank) Program 2 IF (blank) THEN WAIT 5 Minutes Set Light On WAIT 10 Minutes Set Light OFF ELSE (blank)

do you have any programs controlling that switch, if so disable the program(s) and see if that helps.

It appears that your module 2B.D2.E1 is in a loop. What type of module is it? As Jimbo suggested, check your programs that interface with that module.

The heartbeat should be sent approximately every 24 hours. All battery operated devices must be put into the linking mode in order to write updates, however there are exceptions with the latest version of the beta ISY firmware

If you want the light to shut off after a period of time then you should add a wait clause If from sunset to sunrise (next day) and control motion sensor is switched on Then turn on light wait 2 minutes turn off light Else (nothing) Each time the sensor is triggered between dusk and dawn the light would come on for two minutes then shut off. If the sensor is triggered while the light is on the 2 minute timer would reset.

What Xathros is referring to is the motion sensor node that you've selected to control your program. The sensor has 3 nodes Sensor Dusk/dawn Low battery If you want your program to act based on motion being sensed then you need to use the "sensor" node and not the "dusk/dawn" node. This is done within your program and not at the sensor. If from sunset to sunrise (next day) and control motion sensor is switched on then do something else (nothing)

WayneW Thank you for the info. Seems that most of the ALL ON events that users have been experiencing are taking place during the early evening hours when electrical loads are high and household appliances etc. are on. I've been focusing on the possibility of voltage fluctuations and/or noise in the power line as a possible culprit. The fact that the ISY doesn't see the change in device status after an all on make me wonder if the PLM is sending and receiving the normal Insteon signal during the all on event. The PLM you're using has been updated, the current release is rev 2.0, v9E which addressed an issue in the PLM power supply and possibly the all on issue.

The specs for the IOLinc show an operating range of 32F to 104F

WayneW, About what time did the all on occur? What hardware/firmware version of the PLM are you using? How many all on events have you had?, are they always in the evening hours?

and be sure to clear your java cache first and delete all applications in java

How many programs can effectively be run at ISY startup without overloading the ISY? Will they all be processed or is it possible that some could be skipped? If the programs are based on a time schedule will the time in the ISY, at startup, be synched prior to running the programs? I want to make sure necessary devices are put in the correct state in the event of a long duration power failure.

I'm still running 4.2.18 for a while so I won't be able to test your theory just yet.

When I look back I think I pressed the time button on the stat shortly before my temperature display in the ISY went blank. It finally populated again after there was about a 2 degree temp change.

I guess I spoke too soon, the thermostat with the external power supply just quit reporting temperature. The ISY current state temperature node is now blank. All the other fields are OK, set points, fan mode, and humidity. If I do a query it has no effect on any of the readings.

F.Y.I. I have one thermostat running on batteries and another with an external power supply. When I query them it has no effect on the display.

hart2hart, In that case you may want to try exchanging it. My 2441ZTH's have firmware v.0D. Not sure what firmware you have, but they may have made some changes which could be causing issues.

dougos2 and hart2hart, Have you tried removing the external power supply and running it only on batteries? Are you using the 2441ZTH as a stand alone product or is it a slave to another thermostat? Have you tried a factory reset?

Take a look at your error log to see if you have any HamWeather related entries.

What type of light bulb are you using?

I noticed that the are not building the device but will sell the plans. Maybe UDI should look into this.

What's the advantage/disadvantage of unchecking the "send cleanup messages" box?