Randy Ide

@paulbatesMS II works for me on .15a. I'm only using the motion detection. I can't speak to the temperature or light level but I do see the reports in the admin console. I see the full range of Options under Options.

Or consider picking up the original motion sensor from e-bay or try a z-wave if you have the ZW card. Prior to whole upgrade "fun" I was using a z-wave ceiling mount motion detector from Enerwave. I had it positioned so it would capture motion just a couple feet into the hall as I entered the kitchen. There was still a slight delay as the motion detector triggered the program and the program set the light to on, but the placement of the motion detector helped to mitigate the lag. Also I theorized that using the z-wave for the motion detector vs insteon cut down the communication lag as you didn't have to wait until the motion detector communication cleanup to cleared before setting the light to on. I don't know if this is actually true, but it did seem faster than using the Insteon motion detector with the same program. Adding a simple, single function motion detector to 4.73 was pretty straight forward.

The move to v5 by itself wasn't too bad but at the same time I decided add some z-wave. Honestly, the z-wave stuff has been a PITA with some devices having various compatibility issues. Once I made sure I had sufficient coverage for z-wave plus repeaters I have not had issues with the Zooz motion detectors. I don't know yet if the z-wave issues I'm having are related to 5.x or the specific devices. As for the upgrade to 5.x, the programing changes I made were related to motion detection and related how quickly the lights come on. This was mostly self inflected and a labor of love. In 4.x I had motion detectors directly linked to lights as you have and was using the adjust scene in programs to adjust on levels at various times of day. In 5.x, after I made the required changes to the adjust scene, I realized the ISY was trying to write to motion detectors every time the scene was adjusted. They are battery operated so the writes failed, but technically the on levels did change because the change is on the responder side. This issue probably existed in 4.x but I just didn't notice. So then I moved to controlling Lights On through programs and addressed the delayed on situation a little differently. I added sensors and programs to "pre-light". As an example if I come down the hallway leading to the kitchen, then the kitchen lights come on at 30%. If I don't actually go into the kitchen within a minute then turn the lights off. I spent a whole bunch of time working out all the logic, motion sensor placement, etc but only because this is a hobby. There is probably a better way to do all this but I was in it for the fun. If you don't have the need for any more complicated logic or not in it for hobby, then my recommendation would be to stay with what you have. If you love to tinker, then clear a weekend an dive into 5.x. Read through the documentation carefully, backup, export you programs, etc. I recommend taking screen shots showing with programs are enabled and disabled as you will need that info. Make sure you manually disable any previously disabled programs after the upgrade. Also recommend taking screen shots of any programs using Adjust Scene. Most my programs converted just fine other than those with Adjust Scene. Comments where automatically inserted into programs that had adjust scene and they were left unsaved after the migration. It wasn't too hard to figure out from the comments that were inserted how to recreate the adjust scene lines. I only had one z-wave device prior to migration so I just reset the z-wave dongle to factor default before the migration and started setting up z-wave from scratch after the migration.

@Gouldc Yeah, I went to 5.x when 5.15 came out so I could finally use the M2. You really can't do much with the M2 on 4.x. Although, personally I have not been that impressed with M2 motion range detection and sensitivity compared to the older versions. I found it is fine for hallways and smaller rooms, but still ended up keeping the older versions in larger rooms for occupancy sensing use cases. BTW Insteon support told me 1 is least sensitive and 255 is the most sensitive setting for motion detection for the M2. They also said the jumper doesn't do anything, but I read on an Insteon forum that it connecting the pins reduces sensitivity. I'm still search for the best sensor for occupancy sensing in low activity rooms. So far I like the latest version of ZooZ (z-wave) for its ability to detect small movements and respond quickly. I can't tell you how painful it is for me if lights go out on my spouse

Your settings look fine for the M2. Although if you don't have anything else you more complicated you are trying to do, it might be simpler to just use a scene rather than a program. You would need to add the M2 as a controller, change report "on only" to report "on&off", and set your timeout to 5 minutes. Also agree that you should look at the event viewer and try to see if you are having signal issues. To follow up on larryllix comment, I have started to use a slightly different approach in my motion programing to reduce the traffic and potential traffic jams. I've created separate programs for turning on vs turning off so you don't have the traffic associated with setting the light to on over and over again when it is already on. Turn On If Motion Sensor is Switched On And Status Light Off Then Set Light On <optionally Stop Program Turn Off> Turn Off If Motion Sensor Status is Off Then Wait 5 Minutes Set Light Off Have you used the older generation Motion Sensors and if so how do like the new version?