Jump to content

System Busy on ISY Boot

MikeD

By MikeD
in ISY994

Recommended Posts

MikeD Experienced

MikeD

Posted
Posted

Hi all,

 

For some unknown reason my Z-Wave dongle was not responding this morning. I was getting updates from my devices if queried but just had a "! Z-Wave dongle not responding" selection from the pull-down in the admin console. I rebooted the ISY and everything is back to normal.

 

However this bothered me... Every time I cold-boot the ISY it takes about 5 minutes to completely come back up with System Busy in the lower left corner of the admin console (where you normally see Ready) and a System Busy dialog box with a progress bar continually going from left to right over and over. I thought to bring up the Event Viewer at level 3 to try and see what was happening.

 

Below is a portion of the capture that indicates communications with my Hidden Door Sensors. I have 4 of these sensors installed and looking at the log it appears they are the cause of my LONG boot-up time.

 

Can anyone explain what is going on and why this is happening?

Is anyone else that has (2845-222) Insteon Hidden Door Sensors experiencing this?

 

Thanks ~Mike

--- ISY Boot-up ---
--- Did not catch preceding ISY log events from start of boot process ---
--- These are all (2845-222) Insteon Hidden Door Sensors v.43 ---

Mon 09/29/2014 02:00:04 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:00:04 PM : [INST-ACK    ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:00:13 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:00:13 PM : [INST-ACK    ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:00:22 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:00:22 PM : [INST-ACK    ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:00:26 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:00:26 PM : [INST-ACK    ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:00:35 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:00:35 PM : [INST-ACK    ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:00:44 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:00:44 PM : [INST-ACK    ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:00:48 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:00:48 PM : [INST-ACK    ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:00:57 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:00:57 PM : [INST-ACK    ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:01:06 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:01:06 PM : [INST-ACK    ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:01:10 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:01:10 PM : [INST-ACK    ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:01:19 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:01:19 PM : [INST-ACK    ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:01:28 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:01:28 PM : [INST-ACK    ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:01:32 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:01:32 PM : [INST-ACK    ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:01:41 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:01:41 PM : [INST-ACK    ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:01:50 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:01:50 PM : [INST-ACK    ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:01:54 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:01:54 PM : [INST-ACK    ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:02:03 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:02:03 PM : [INST-ACK    ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)

--- Some Z-Wave comms were here (Removed) ---

Mon 09/29/2014 02:02:12 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:02:12 PM : [INST-ACK    ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:02:16 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:02:16 PM : [INST-ACK    ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:02:25 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:02:25 PM : [INST-ACK    ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:02:34 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:02:34 PM : [INST-ACK    ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:02:38 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:02:38 PM : [INST-ACK    ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:02:47 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:02:47 PM : [INST-ACK    ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)
Mon 09/29/2014 02:02:56 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2
Mon 09/29/2014 02:02:56 PM : [INST-ACK    ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06        (00)

--- More Z-Wave / Insteon comms were here (Removed) ---

Mon 09/29/2014 02:03:21 PM : [        Time] 14:03:21 0(0)

--- ISY completed boot process ---
Xathros Advanced

Xathros

Posted
Posted

There are 2 settings on the Configuration / System tab in the admin console that may have an effect here.  Query at startup and Catch up schedules at Restart.  The first will do a query of all devices at boot and the second will try to run any programs that should have been run based on time prior to the restart.

 

Try de-selecting both of these options and see if that helps.

 

-Xathros

MikeD Experienced

MikeD

Posted
  • Author
Posted

Hi Michel,

I rebooted the ISY again just to make sure, no green icons.

2B.0D.E1 is the Inside Garage Door sensor

2B.0F.03 is the Front Door sensor

Attached is a screen shot of the System Busy in progress.

 

post-3657-0-60732600-1412101697_thumb.png

~Mike

 

 

Michel Kohanim Wise Elder

Michel Kohanim

Posted
Posted

Hi Mike,

 

Thank you. This does not make sense: if they are indeed hidden door sensors, they should go to sleep mode and ISY should not be able to communicate with them.

 

It seems as though ISY is programming them. Do you have any programs that use these devices either in If or Then/Else (you can use Find/Replace on My Programs).

 

Also, please click the + button at the top to expand the tree. I cannot see whether or not there are any devices with green 1011 icons.

 

With kind regards,

Michel

MikeD Experienced

MikeD

Posted
  • Author
Posted

It seems as though ISY is programming them. Do you have any programs that use these devices either in If or Then/Else (you can use Find/Replace on My Programs).

Yes, and that must be why the Query at Restart?

If
        Status  'z-Door Sensors / Front Door' is On
 
Then
        Resource 'FrontDrSensorOpen'
         
Else
        Resource 'FrontDrSensorClosed'

~Mike

 

MikeD Experienced

MikeD

Posted
  • Author
Posted

Hi Xathros,

 

Thanks for the suggestions. Query at Restart and Wait while busy reading were the only ones that were checked. I first unchecked Wait while busy reading and rebooted - that did not help. Unchecking Query at Restart did solve the System Busy problem on boot up however I think that is a questionable solution.

 

My next question I have (for Michel) is why don't the Leak Sensors exhibit the same symptoms on ISY restart, since I also check the Status of their Wet node in an If statement?   :?

 

~Mike

Xathros Advanced

Xathros

Posted
Posted (edited)

Mike-

 

This would indicate to me that you have a number of programs reacting to the change in status of devices as they are queried. This does not mean that the devices actually changed state but rather that the ISY is seeing a status change from unknown to whatever the query returns as it runs.  You can likely verify this theory by de-selecting "Query at startup" then reboot the ISY and wait a minute to make sure its up and running then run the 3am query and see what happens.  I would expect the same result as what you were seeing at startup with "Query at startup" selected..

 

-Xathros

Edited by Xathros
MikeD Experienced

MikeD

Posted
  • Author
Posted

Hi Xathros,

 

Query at startup produces the same System Busy and Event Viewer results. I have a Hidden Door Sensor startup program configured to run at ISY startup. It is very similar to the Leak Sensor startup program that many here are running.

If
        $iDoorSensorStartup is 0
 
Then
        Run Program 'FrontDoorHeartbeat' (Then Path)
        Run Program 'InsideGarageDrHeartbeat' (Then Path)
        Run Program 'UpperPatioDrHeartbeat' (Then Path)
        Run Program 'LowerPatioDrHeartbeat' (Then Path)
        Wait  2 seconds
        $iDoorSensorStartup  = 1
 
Else
   - No Actions - (To add one, press 'Action')

Each Heartbeat program is similar to this one below and is a status of 'Running Then' after ISY restart.

If
        Control 'z-Door Sensors / Front Door / Front Door - Heartbeat' is switched On
     Or Control 'z-Door Sensors / Front Door / Front Door - Heartbeat' is switched Off
 
Then
        $iFrontDoorMissedHB  = 0
        Wait  48 hours 
        Resource 'FrontDrSensorNotResponding'
        $iFrontDoorMissedHB  = 1
 
Else
   - No Actions - (To add one, press 'Action')

None of the programs associated with my Hidden Door Sensors, including the one that checks the Status (Post #6) changed the time displayed in the 'Last Run Time' column on the Programs / Summary tab when I ran Query All (Then Path) a few minutes ago.

 

~Mike

MikeD Experienced

MikeD

Posted
  • Author
Posted

Also, please click the + button at the top to expand the tree. I cannot see whether or not there are any devices with green 1011 icons.

 

Hi Michel,

 

Unfortunately if I clicked the + button you would not be able to see all my devices on one screen. I did check on my last ISY restart and there were no devices with green 1011 icons.

 

Can you explain why my Hidden Door Sensors are queried during the '3 AM Query All' given the information in the last few posts?

Are they so different than a Leak Sensor that is not included in the Query All?

 

Thank you,

~Mike

Xathros Advanced

Xathros

Posted
Posted

Personally, I wouldn't expect ANY battery powered device to be queried at startup or during the 3AM query run.

 

-Xathros

MikeD Experienced

MikeD

Posted
  • Author
Posted

Personally, I wouldn't expect ANY battery powered device to be queried at startup or during the 3AM query run.

 

-Xathros

That is the way it should be. Bug?

 

~Mike

Michel Kohanim Wise Elder

Michel Kohanim

Posted
Posted

Hi Mike,

 

As Xathros suggested, none of those devices can be queried and are NOT queried. Furthermore, the fact that they are responding, in and of itself, is quite strange. They should be asleep and not responding.

 

My hypothesis thus far:

1. Those addresses are not for door sensors

2. Door sensors are alive for some reason

 

You can mimic query at restart by Right Mouse click on ISY node | Query. Please open the Event Viewer on level 3, do the aforementioned, save the contents and send to support@universal-devices.com.

 

With kind regards,

Michel

MikeD Experienced

MikeD

Posted
  • Author
Posted

Hi Michel,

 

Email sent with Query results and Topology attachments.

 

Thank you,

~Mike

Michel Kohanim Wise Elder

Michel Kohanim

Posted
Posted

Hi Mike,

 

Thanks so very much. LeeG also provided diagnostics (Thank you LeeG). It's definitely a bug and will be fixed. The only issue is that these devices report their battery status upon query. So, we have to figure out a way to allow that.

 

With kind regards,

Michel

Guest
This topic is now closed to further replies.
Go to topic listing
×
×
  • Create New...