paulw Posted September 29, 2020 Posted September 29, 2020 (edited) Have an ISY994i that is running 5.0.16, was upgraded to 5 probably at least 6 months ago without any issues. Lately have found some commands not completing correctly so went looking at the log and found the attached loop. Need some help in interpreting it. Seems to me that something is issuing a time command. The only thing I can think might is the following: The 12.A0.4E is 'Hall - foyer / Front Lites' but I am lost at what the log is telling me. I might add that this program goes back many many years to version 4 without issues. Nothing here seem logical to me in causing a loop. I have powered down the 2420M (test motion old-Sensor) in the event it had an issue, disabled the program, issued a STOP. Loop keeps running. Anyone have any advice? Edited September 29, 2020 by paulw correction
larryllix Posted September 29, 2020 Posted September 29, 2020 Did you know the admin console has a search engine to find anything by Variable name, program name etc?.... Right click on any program name and select "Search and Replace" option on the pulldown menu. 1
MrBill Posted September 29, 2020 Posted September 29, 2020 I agree with @larryllix use search to see if you have another program controlling the device. Also sometime watching the "Programs" > "Summary" tab in the Admin Console can help find never ending loops. You can sort that page in various ways by clicking the column heading, clicking it twice reverses the sort order. "Activity" twice will put "Running" programs at the top (under any folders). "Last Run Time" twice may be beneficial also.
paulw Posted October 18, 2020 Author Posted October 18, 2020 Thank you both for your input. Had to go out of town for a while, just getting back to this issue. Can you point me to where I can find info on interpreting what I am seeing in the event log. Some of it I can piece together but I am a bit lost. I do believe I have something besides a loop. In the above event log I am seeing line 2 through line 6 repeating for hours. Have looked at different days, and have seen them repeat from a couple to over 4 hours. Can anyone tell me what I am seeing in those lines? I have had older dimmers go rogue but they have exhibited strange lighting sequences, just wondering if the addressed dimmer is going bad.
kclenden Posted October 20, 2020 Posted October 20, 2020 (edited) On 10/18/2020 at 3:11 PM, paulw said: Can anyone tell me what I am seeing in those lines? Line #1 - The ISY has passed a message to the PLM [02 62]. The message is intended for device 12.A0.4E. The message flags indicate a direct message (i.e. not a group message) that is allowed a maximum of 3 hops [0F]. The message contains an ON command [11] to Level 44% [70]. I calculated the level by hex 70/FF = 112/255. Line #2 - A program has started Line #3 - The PLM acknowledges to the ISY that it received the message and sent it Line #4 - Device 12.A0.4E acknowledges that it has received the command to turn ON at Level 44% Line #5 - The ISY translates the message received on Line #4 into easier to understand text Line # 6 . . . loop repeats My interpretation of the log is that you a have program (or programs) that do two things every second: Turn on 'Hall - foyer / Front Lites' to 44% Call a program Could be a program that: Turns on 'Hall - foyer / Front Lites' to 44% WAITS 0 Seconds (seems wrong but the ISY waits 1 second longer than specified) Calls itself Could be two programs that: Prog_1: Repeats while (some condition that never changes) Calls Prog_2 Waits 0 Seconds Prog_2: Turns on 'Hall - foyer / Front Lites' to 44% Or there are many other ways this could be implemented. The key is that it appears to be a loop whereby a program is called every second to turn on 'Hall - foyer / Front Lites'. I would think your best bet is to do what @MrBill suggested. Look on the "Summary" page for a program that is constantly running: You might also search your programs for instances of "Wait 0 Seconds" or "Repeat Every 0 seconds". Edited October 20, 2020 by kclenden 1
paulw Posted October 20, 2020 Author Posted October 20, 2020 (edited) kclenden, MANY thanks, big help!! Any recommendation where I can find info on understanding events? There are times I see over 50 [ time] in a row, any reason for this? Edited October 20, 2020 by paulw add info 1
kclenden Posted October 21, 2020 Posted October 21, 2020 (edited) 16 hours ago, paulw said: Any recommendation where I can find info on understanding events? Unfortunately I don't have any particular source to point at to help understanding events. Most of what I know comes from watching things happening in the Event Viewer and then tracing it back to what was happening at the time. For example the [ Time] tag. There seem to be a lot of things that can cause it to appear in the Event Viewer including: In the AC Saving a program Running a program While the ISY is running A program calls another program Time is ... passes (whether based on exact time, sunset/sunrise, or Last Run of a program)* When the start time of a "From ... To ..." passes * When the end time of a "From ... To ..." passes * * - Even if a program is disabled directly, or via a folder condition, and unable to run, a [ Time] tag will appear in the Event Viewer when the start or end time passes I've seen multiple [ Time] tags appear in a row, but generally they're related to either saving program, in which case I see four in a row, or the start/end time of a FROM statement in a disabled program passing in which case it seems to be somewhat random how many [ Time] tags I see. I've seen as many as 38 appear in a row related to a single disabled program with a FROM statement, but usually it's more like 10-20. Another odd thing about the [ Time] tag is the 0(0) that appears at the end. Sometimes it's not 0(0) but x(0) where the x represents the number of days my ISY has been running, like tonight where I'm seeing 86(0) and indeed my ISY has been running 86 days since it was last rebooted. Edited October 21, 2020 by kclenden
Recommended Posts