Jump to content

Do not make adjustments to linked/attach devices...


Goose66

Recommended Posts

I get this message for 2 or 3 minutes after each reboot in the "System Busy" dialog. What exactly does this mean? Does this mean don't unplug or link my Insteon devices, or does it mean I need to make sure there is NO INSTEON TRAFFIC whatsoever during this period?

Link to comment

Hello kingwr,

 

Somewhat unrelated topic -

I also get the "System Busy" dialog for a long period of time after a re-boot or query of "my lighting". I have the X10 module installed and after looking at the "event Viewer", I've determined that most of this time is spent querying X10 devices that can't respond (one way devices). This causes a huge delay as the ISY/PLM must time out on each X10 query before proceeding to the next. The querying of my Insteon devices is actually quite quick.

 

I'm curious whether you have the X10 module installed as well?

 

It might be possible to eliminate this lag if the ISY team were to incorporate a flag to specify whether the X10 devices were 1 way (receive only) or 2-way (receive/transmit). In the world of X10, there are actually very few of the 2-way devices available.

 

I'm simply not sure how many ISY users have the X10 module installed. If only a few, this would be down quite a way on the priority list.

 

I get this message for 2 or 3 minutes after each reboot in the "System Busy" dialog. What exactly does this mean? Does this mean don't unplug or link my Insteon devices, or does it mean I need to make sure there is NO INSTEON TRAFFIC whatsoever during this period?
Link to comment

Hello Michel,

 

I actually encountered this several months ago. Rebooting the ISY (or querying My Lighting) would produce activity in the event monitor for roughly 30 seconds. The progress bar, however, would continue updating for several minutes. I noted several "strange" X10 response entries for devices that could not respond in my system (1 way X10). I theorized that this was causing the large time lag in the query. To troubleshoot, I created a "query" scene of all my Insteon devices. A query on this scene would complete in 30 seconds (progress bar closes).

 

I believed that the above proved that the X10 devices were causing the large delay in querying My Lighting - I was wrong.

 

I've been playing with things today and have found an interaction between my status programs the the My Lighting query. If I disable the status programs, the query completes normally after ~ 30 seconds. With the programs enabled, I can see them execute during the query. This apparently confuses the ISY and the progress bar again takes several minutes to terminate. I do not remember this being the case on older revisions of the ISY firmware.

 

My confusion at this point is why the same doesn't occur when I query my scene that includes all of my Insteon devices. The programs still execute, but the ISY seems to handle it gracefully.

 

Sorry for the previous mis-information,

 

IM

Link to comment

Hello IM,

 

Can you copy/paste your status program?

 

Progress bar is the best guess based on the number of operations on the queue and average time it takes to complete them. With every addition of commands, the number should increase and thus the progress bar might go multiple times.

 

With kind regards,

Michel

Link to comment

Hello Michel,

 

Absolutely -

 

The program is extremely simple - it monitors my second floor devices and updates KPL buttons to indicate the ON/OFF status of the second floor. There are 3 KPL's in the "2nd Floor Status" scene spread throughout the house.

 

I have a number of "status" programs that will produce the same effect, this was the simplest. Enabling this program by itself will cause a "several minute" progress bar if I query My Lighting.

 

Curiously, if I query the Scene that contains all of my Insteon wired devices ( No 2420's or remotelincs) the progress bar responds properly and terminates after roughly 30 seconds. The scene contains all of the devices listed in the program (program is run during the query).

 

As always, thank you for the support

IM

 

If
       (
            Status  '2nd Floor / David Switch' is Off
        And Status  '2nd Floor / Kath Icon' is Off
        And Status  '2nd Floor / Master Fan' is Off
        And Status  '2nd Floor / Master KPL 1 - Master Overhea' is Off
        And Status  '2nd Floor / Matt Inline' is Off
       )
Then
       Set Scene 'SC 2nd Floor Status' Off
Else
  - No Actions - (To add one, press 'Action')

Link to comment

Hello IM,

 

Thank you. Sincere apologies for tardy reply.

 

So, in essence, when these query programs are run (which turn on a few buttons on KPLs), the progress bar does not behave properly.

 

Now, is it possible that when the devices within the status scenes are updated, you have programs that do things based on the status of those devices?

 

I really do not think the problem is the status programs itself BUT it's the result of thereof which is probably causing a range of other device activities/querying, etc.

 

With kind regards,

Michel

Link to comment

Hello Michel,

 

Answers below -

 

So, in essence, when these query programs are run (which turn on a few buttons on KPLs), the progress bar does not behave properly.

 

Correct - with the programs disabled, the progress bar terminates is roughly 40 seconds.

 

Now, is it possible that when the devices within the status scenes are updated, you have programs that do things based on the status of those devices?

 

Not in this test - the above program was the only one enabled.

 

...BTW - I wouldn't call this a "tardy reply". We users may be demanding, but we do recognize that you need to sleep at times.

 

Thanks again,

IM

Link to comment

Hello Michel,

 

In a word - Yes. I do see the correct status after termination of the Progress Bar.

 

After the initial query (first 30 - 40 seconds), I can actually change linked devices and watch them update in the Admin console (progress bar continues for an additional ~ 5 minutes).

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...