aawitek Posted January 10, 2015 Posted January 10, 2015 I upgraded my ISY 994i firmware to 4.2.18. Now when in the admin console a system busy window pops up. The progress bar of the system busy window goes from 0 to 100%, it closes, then it starts up again. I left the admin console open over night and the opening/closing cycle does not end. The text at the bottom of the system busy window reads: [ 2B D2 E1 1] DOF 1 Also, since upgrading, all my lights will flicker. It is not a constant flicker, they flicker once every 2 minutes or so. Has anyone encountered this or has a solution? Thank you.
Jimbo.Automates Posted January 10, 2015 Posted January 10, 2015 Open the log, or event viewer at level 3 to see what is happening. The only time this has happened to me is when I had an error in a program that caused it it continually rerun itself. Sent from my Nexus 7 using Tapatalk
Techman Posted January 10, 2015 Posted January 10, 2015 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.
aawitek Posted January 12, 2015 Author Posted January 12, 2015 It is a dimmer switch. Prior to updating the firmware this issue was not happening. I see the event log and it indicates a system error number -1 which apparently is a request failed error.
Techman Posted January 12, 2015 Posted January 12, 2015 do you have any programs controlling that switch, if so disable the program(s) and see if that helps.
larryllix Posted January 12, 2015 Posted January 12, 2015 I have this busy box on my Admin Console every time my WebControl sends it's heartbeat /current date and time. This is sent via the REST interface and is comprised of a single 32 bit value every 15 seconds. It appears to pause ISY processing and may be the cause of some severe program response delays I get occasionally.
Michel Kohanim Posted January 13, 2015 Posted January 13, 2015 Hi larryllix, Do you have any programs that do things based on the variable's state change? With kind regards, Michel
larryllix Posted January 13, 2015 Posted January 13, 2015 Hi larryllix, Do you have any programs that do things based on the variable's state change? With kind regards, Michel Yes I have a few heartbeat checkers but on different variables, not that same one.
Michel Kohanim Posted January 13, 2015 Posted January 13, 2015 Hi larryllix, What do those heartbeat checkers do? With kind regards, Michel
larryllix Posted January 13, 2015 Posted January 13, 2015 (edited) Hi larryllix, What do those heartbeat checkers do? With kind regards, Michel Here are the two that are triggered by this heartbeat. $CAI1_MMDDhhmmss is a state variable and gets stuffed by the CAI WC8 board every 15 seconds. I have watched the program status, sorted by "Last Run" and it seems to be at the top mostly. CAI Heartbeat.fail - [ID 00B4][Parent 003A] If $CAI1_MMDDhhmmss < 101000000 Then $CAI_Readings_Current = $cFALSE Wait 2 minutes Set 'Workshop / Shop Webcontrol Board' Off Wait 20 seconds Set 'Workshop / Shop Webcontrol Board' On Else $CAI_Readings_Current = $cTRUE Wait 1 minute Run Program 'CAI Heartbeat.fail' (Then Path) CAI Date - [ID 00B9][Parent 003A] If $CAI1_MMDDhhmmss > 0 And $ISY_Initialised is $cTRUE Then $CAI1_MMDDhhmmss Init To $CAI1_MMDDhhmmss $CAI_Time.Last_Known = $CAI1_MMDDhhmmss $CAI_Time.Last_Known Init To $CAI_Time.Last_Known Wait 1 second Run Program 'CAI Date' (Else Path) Else - No Actions - (To add one, press 'Action') Edited January 13, 2015 by larryllix
Michel Kohanim Posted January 14, 2015 Posted January 14, 2015 Hi larryllix, Thanks so very much. Is it possible to put all other programs that do not depend on this one in a folder and give it a false condition so that none of them are run. Then open the Event viewer on level 3 and a) monitor the traffic and see whether or not you still see system busy. In and of itself system busy is ok. The question is what is actually happening. With kind regards, Michel
aawitek Posted January 14, 2015 Author Posted January 14, 2015 do you have any programs controlling that switch, if so disable the program(s) and see if that helps. I disabled it and the same system busy loop is occurring. Additionally, now the green "writing" symbol is now shown next to a different switch. The switch is only controlled with a scene.
Techman Posted January 14, 2015 Posted January 14, 2015 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.
aawitek Posted January 14, 2015 Author Posted January 14, 2015 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. After disabling just the one light, the log looks clean, no errors and the issue is still there. I did a factory reset. I tried to reprogram all of my devices from scratch, however, when linking them i get communication errors and am unable to link, or they aren't even detected.
Techman Posted January 14, 2015 Posted January 14, 2015 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?
aawitek Posted January 14, 2015 Author Posted January 14, 2015 Your main problem seems to be communications between your devices and the PLM How many devices and programs do you have? 18 light switches only Are the devices dual band? I don't know Are you using any access points? No Is the PLM plugged into a filtered power strip? No, directly into an outlet wall Are any other devices plugged into the same outlet as the PLM? Yes What did you do a factory reset on? on the ISY 994 Did you ever have good communications between your devices and the PLM? Yes, before i upgraded to the latest firmware on the ISY 994 My answers are underlined above.
larryllix Posted January 15, 2015 Posted January 15, 2015 Perhaps you could attempt to re-download the firmware package and star again. Before or after that you should contact UDI for inside help.
Techman Posted January 15, 2015 Posted January 15, 2015 (edited) What is the model number of the switches? Did you have a fresh backup of the ISY before you did the factory reset, or before you did the firmware update? What steps did you use to upgrade the ISY firmware? Take a look at HELP | ABOUT and tell me what you have for FIRMWARE and UI What's plugged into the outlet that the PLM is plugged into as some electronics interfere with the Insteon signals Edited January 15, 2015 by Techman
Michel Kohanim Posted January 15, 2015 Posted January 15, 2015 Hi aawitek, I recommend moving your PLM to a different outlet. With kind regards, Michel
aawitek Posted January 17, 2015 Author Posted January 17, 2015 (edited) What is the model number of the switches? --> INSTEON 2477D (SwitchLinc Dimmer) Did you have a fresh backup of the ISY before you did the factory reset, or before you did the firmware update? --> Yes What steps did you use to upgrade the ISY firmware? Take a look at HELP | ABOUT and tell me what you have for FIRMWARE and UI --> Inseton_UD994 v.4.2.18 What's plugged into the outlet that the PLM is plugged into as some electronics interfere with the Insteon signals --> router, cable moderm on a power strip. The PLM is directly into the outlet, not on the power strip. Hi aawitek, I recommend moving your PLM to a different outlet. --> I moved it to a different outlet With kind regards, Michel My answers are above. Also, i recently moved the PLM to a different outlet with nothing else plugged in. I still get the same looping "system bust" and now there are "can not communicate" errors with some devices. Edited January 17, 2015 by aawitek
Techman Posted January 17, 2015 Posted January 17, 2015 aawitek, The 2477d is a dual band device meaning that it transmits both over the powerline and by RF which provides superior communication compared to the older single band devices. It appears that you either have some interference on the powerline or the two legs of your powerline are not properly bridged. Interference can be caused by defective CFL bulbs, TV's, UPS, etc. If your system was working well at some point in time then you may have added some electrical device that's creating noise on the powerline. Do any of your devices have a red ! or a green 1011 next to them.
aawitek Posted January 18, 2015 Author Posted January 18, 2015 (edited) aawitek, The 2477d is a dual band device meaning that it transmits both over the powerline and by RF which provides superior communication compared to the older single band devices. It appears that you either have some interference on the powerline or the two legs of your powerline are not properly bridged. Interference can be caused by defective CFL bulbs, TV's, UPS, etc. If your system was working well at some point in time then you may have added some electrical device that's creating noise on the powerline. Do any of your devices have a red ! or a green 1011 next to them. I have switches with both the red ! and green 1011 next to them, and the "system busy" loop is still going. My system was working perfectly fine until i did the firmware upgrade. I have not added any electrical devices at all. Edited January 18, 2015 by aawitek
Techman Posted January 18, 2015 Posted January 18, 2015 I would try disabling all the devices that have a "!" or "1011" next to them, right click on the device then click on disable. Does the "system busy" go away after the devices are disabled? If so, then enable the devices, one at a time, and try to query it. Hopefully you'll find a device that's causing the problem. How many devices are problematic? If your still having issues after trying the above then I would open a trouble ticket with UDI.
Recommended Posts