After most of my NSs have been migrated with some still with problems I was introduced to a new problem at 3 AM for the last two days. This seems to be an eisy_ui issue. At 3 AM the program QueryAll runs and causes some programs into running due to their if statement being true and playing their voice messages by the audio player. Before this issue I had set the 'Missed Schedule Grace Period' to 10 min. as it was in the AC. I have set the grace period back to '0' and disabled QueryAll. Hopefully no more awaking at 3 AM.

Gary

What is your QueryAll Program? This was legacy in 994, but removed in version 5.x

I have been unable to recreate this behavior during the day but this is the QueryAll program. This is the only program that runs at 3 AM. I will keep trying to reproduce the event

Thanks Gary

I have been able to recreate the event. If the eisy-ui is rebooted and then run the QueryAll program the event will happen. Since I needed to reboot the eisy-ui daily because of the migration that is why it has been happing lately.

Thanks

Gary

3 hours ago, Javi said:

What is your QueryAll Program? This was legacy in 994, but removed in version 5.x

@Javi I didn't know QueryAll wasn't required.

Is it handled differently now? Or just not required?

My understanding is that the original purpose of query all was to true up the state of ISY internal tables with the state of insteon (maybe also X10) devices. With the advent of dual band (RF as well as powerline) communications and users becoming more sophisticated about improving comms this became less necessary. The flurry of signals from the query all program can introduce its own errors, with devices turning on for no evident reason.

While UDI apparently eliminated it in clean installs with v 5, it survived through upgrades (install from back up) in many user setups.

2 hours ago, mmb said:

@Javi I didn't know QueryAll wasn't required.

Is it handled differently now? Or just not required?

Not required. It is odd that it remains, it used to show as a program error after migration.

1 hour ago, Javi said:

Not required. It is odd that it remains, it used to show as a program error after migration.

There are likely others like me that still have many single band wireline devices that as they break I replace them. Comms is much superior now but some of the witeline only devices do occasionally get out of sync with eisy and its a way once a day to get all back in sync.

Also, I don’t recall it ever resulting in a device turning on but I feel based on program having if control vs if status it could trigger something unintended.

Edited 18 hours ago18 hr by hart2hart

In my case I had (still have) a micro open/close (or on/off) that twice within a month opened in the middle of the night at the time of the query all. Initially I saved the state of the device before the query all and then reset it after to deal with the problem. The device was not mentioned in any other program that was active at the time. Since I have no problems with devices getting out of sync, I then disabled query all. This was around 2016, I think. No problems since.

Additional thought: I can't remember but it's possible a failing PLM was part of the problem.

Edited 16 hours ago16 hr by stillwater
added additional thought