Jump to content

Initializing system for a very long time


Hawkspoint

Recommended Posts

Every time I make any changes to any of the devices like sensors, the system takes a very long time (20 Minutes or more) to initialize.  In the middle of things it says System Busy, and it tries to initialize all sensors instead of just the one I tried to add or change.  

Is this screw up in version 5? Can I go back to something that works?

Thanks for any hints.

Hermann

Link to comment
Every time I make any changes to any of the devices like sensors, the system takes a very long time (20 Minutes or more) to initialize.  In the middle of things it says System Busy, and it tries to initialize all sensors instead of just the one I tried to add or change.  
Is this screw up in version 5? Can I go back to something that works?
Thanks for any hints.
Hermann

If you have the ISY Pro you can select the disable battery write. This will allow you and the system to update all of the hardwired equipment first. Once complete you can right mouse click and select one battery device and update.

Going this route increase writes and allows you to manage your time and update sequence.

Link to comment

Hi

Using Pro; I have several sensors in multiple locations.  It is impractical to go around and put them all in com mode every time I make a change to one of them.  

When I make a change to one, that is the only one that needs to be updated!  Right?

Link to comment
4 minutes ago, Hermann said:

Using Pro; I have several sensors in multiple locations.  It is impractical to go around and put them all in com mode every time I make a change to one of them.  

When I make a change to one, that is the only one that needs to be updated!  Right?

any that have a grey icon "1101" have pending writes waiting.  If you have pending writes for a bunch of sensors and then make a change the ISY tries to update all of them.

There is a reason I asked your firmware revision.  too much typing to explain if it doesn't apply to you...  an additional related question is "do your programs use "adjust scene"?"

Link to comment
7 minutes ago, Hermann said:

Thanks, firmware is 5.3.3 so is the UI

You're past the bug that relates to "adjust scene".... which creates a lot of need to write to wireless devices. 

To solve your problem tho, you need to get rid of all the 1101 icons sitting on the left side of the device name in the tree.  To get rid of them the devices needs to be put into linking mode and then "write changes".   Once you've gotten rid of them be hyper vigilant about allowing them to build up which as of 5.3.2 shouldn't occur from use of "adjust scene" by a program. 

 

From 5.3.2 release notes:

Quote

0000774 - Green icon appears on Insteon Controller Node after using Adjust Scene

 

Link to comment

Open tools > Diagnostics > Event Viewer

Change the dropdown to level 3.

"Clear" the window

Make the malfunction occur.

at the end press copy to clipboard (the button looks like a clipboard)

reply to this thread, press the "<>" in the toolbar then paste the clipboard here.

 

Link to comment
1 hour ago, Hermann said:

Hi

Using Pro; I have several sensors in multiple locations.  It is impractical to go around and put them all in com mode every time I make a change to one of them.  

When I make a change to one, that is the only one that needs to be updated!  Right?

Let me try to be a little clearer and expand on my reply. If you have a Pro version of the ISY Series Controller you have the ability to disable / stop all writing to battery operated devices. This allows you to press the linking button on a target device so it can be updated. This will absolutely cut down on waiting for the system trying to write to battery operated devices endlessly. 

This addresses the first issue you stated about waiting for a long period of time . . .

From a practical stand point disabling 1011 battery writes puts you in control and allows you to manage time. Another option (Doesn't always work) is to create a program to update all battery operates devices when the heart beat is seen. Again, this method is pretty much a trial and error and some have had mixed results vs others a very positive outcome.

I've used the program update since its release and it works for me for very specific hardware / revisions / models.

Link to comment

Adding to the above, only one battery operated device should be in the linking mode at any time. If multiple battery operated devices are put into the linking mode at the same time the link tables can become cross linked. 

The battery operated device must be manually put into the linking mode before you can write an update to it. 

Another possibility:  the following program worked with earlier ISY firmware versions, not sure if it's currently compatible.  Disable or delete  the program after you write the updates to the device.

If

        'South Stairs Motion Sensor' is switched On

 Then

        Set 'South Stairs Motion Sensor' Write Changes

 Else

   - No Actions - (To add one, press 'Action')

 

 

Link to comment
7 minutes ago, Hermann said:

the 1101s showed up after a restart; I had to go to all wireless devices and push/hold to write changes one at a time; took 2 hours

Keep your eye out for those.  If they come back we need to figure out why.  You're on 5.3.3 so you're past the point that the known issue was fixed.

Link to comment

Archived

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


×
×
  • Create New...