Techman

@paulw Verify that you're connected to the internet. Try accessing the admin console via the cloud to verify that you're connected. I believe the from field needs to be populated The from field format should be: ISY:(your email)@gmail.com

The format the IOLinc uses is not a bug. It's most likely built around the alarm system format which uses NO (normally open) contacts. When the alarm system is armed all the contacts are closed. If a contact is opened or the wire to the contact is cut, the contact reverts to the NO state thus triggering the alarm. This is the protocol (NO) the IOLinc uses. I'm not familiar with Home Assistant but they may not follow that protocol. With UD controllers, nothing has changed over the years, why you didn't experience this with your Polisy may be the way your program was set up, or maybe you used trigger reverse and didn't run the 3 am query.

Your motion sensor (14 72 B6) appears in almost every log entry, so chances are this is the device that's causing you problems. Disabling the device does not stop it from sending spurious data into the Insteon network. You need to remove its battery in order to completely disable it. You should also look for a program that may be running around the time of your issues

It's possible that the default mail server is down. It's probably best to use Gmail. For Gmail setup take a look at this wiki article: https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings

If you use a Normally Open reed switch, and don't enable trigger reverse, then the green led on the IOLinc will be on when the door is closed (when the magnet is in contact with the reed switch), the 3AM query won't then affect the status. This is the way it has always been with UD controllers.. There hasn't been any changes in the IOLinc or the controller firmware that would affect the device status.

Are you using a reed switch and magnet to trigger the IOLinc, if so is the switch normally open or normally closed?

Can you expand on what you mean by synchronizing them. What is it that you want to do with the KPL?

I just took a look at one of my programs that has a 15 minute wait and the LAST RUN TIME and the LAST FINISH TIME show the 15 minute difference. Not sure why you're not displaying the correct finish time. Are there any other conditions in your program? What controler and firmware are you running?

What version of PG3 were you running prior to the upgrade

Are you currently running PG3x 3.2.27 and IoX 5.8.4

A restore would not transfer Zwave to the new controller, migrate does. If your Polisy is running a different firmware version than the Polisy, the Polisy firmware could be downgraded by using the ISY994 firmware which may not be compatible with the Polisy. There are probably additional factors, but these are two that come to mind.

@NYHeel You should use a 12 volt, 1 or 2 amp power supply. They're out of stock at the UD Store. Amazon should have them

@larryllix I just took a look at several of my ON/OFF modules and the only option was on or off, no percentage options. Did you use the REPLACE WITH option when you replaced your dimmer module with the on/off module?

Can you post a screen shot of your scene. Most likely your scene is not configured properly. When you press a button on the keypad can you see its state change in the admin console?

The current Insteon switches are a bit smaller than the ones sold several years ago. Is your 3 gang box metal or plastic? Was it installed when the home was built or was it added later? What controller are you using. Do you currently have Zwave? Is your current installation all Insteon?

When you replaced the keypads did you first add the new keypad, and then right click click on the keypad you're replacing, point to the new keypad and then click replace with? If you didn't replace the KPL using the above format, what steps did you take for the replacement?

When you do your testing keep in mind that a X10 device does not send its state back to the controller. The controller assumes the state of an X10 device based on the command sent from the controller. For your test programs it's best to use Insteon devices.

It's possible that you have a marginal communication connnection between the lock and the controller. Try moving the lock closer to the controller. You may have to add an Zwave repeater midway.

Take a look at this article https://wiki.universal-devices.com/INSTEON_Random_All_On_Events Insteon Motion sensors with low batteries can wreak havoc on an Insteon network, especially the 1st generation sensor. What is the (6 digit) address of your motion sensors? Do they show any activity around the time your issue starts It could also be one of your older single band Insteon devices that's failing, especially if it's 15 years old. The newer devices have improved firmware and hardware and are less prone to failing.

What's also strange is that the all events are all happening at the exact same time and affecting different devices.. It could be a device that's failing. You could try disabling the a few of the devices at at time to see if you could narrow it down. Do you have any programs that run around 4:52 am? Were all the devices purchased as new?

Best way to work through this is to write some test programs using your Hall Light and Door Light.

You most likely have a program that is either being triggered by a device or another program. Take a look at your log to see if there's any activity at the time your programs are being triggered. The log will only show if a device turned on, not program activity. You may have to go through each of your programs to track down the issue.

In the example I gave your earlier, The IF statement looks at the existing state of the door light. If the door light is ON and the light swtch is turned on by pressing the switch paddle (control), the IF clause would be true. Both statements in the IF clause would have to be TRUE for the THEN clause to run. If you turned the Hall Light switch OFF or if the door light is OFF when the Hall Light is turned ON or OFF, the IF clause would be False and the ELSE clause would run assuming that it was populated.

Control - when a device is manually turned on or off Status - is the current state of the device. If you wanted to check the status of a device and perform two diffenent functions depending on its state, then you would need two programs. One that would equate to true if the device was on, and a second program that would equate to true if the device was off. The following program will will trigger the THEN statement in the program if the light switch is physically turned on at the switch, and the door light is currently on. IF Door light status is ON and Hall Light is switched ON THEN do whatever ELSE

If you run the Topology report, and scroll down towards the bottom of the report, it will show all the devices in a scene. For programs there aren't any real time options to view the associated devices.