From: Gregg L. <gr...@li...> - 2009-04-15 10:53:47
|
Marc MERLIN wrote: > On Tue, Apr 14, 2009 at 09:49:58PM -0400, Gregg Liming wrote: >> Marc MERLIN wrote: >> >> [... large snip ...] >> >>> I suppose that'll wait for the insteon refactor, >> yes. pretty much everything insteon-related must wait > > Understood. > My workaround for now is to resubmit the changes several times, rescan all, > delete orphans, sync all. It's heavy weight since a full run of the 3 takes > 30 minutes-ish, but it beats me configuring 100-ish link relationships by > hand ;) > > If I have more problems, I may just try and find where your retry code is > and up it from 3 to 6 or something. Most times I got nailed because the huge > amount of traffic my resyncs now generate get things a bit unhappy > sometimes, and 2 retries is not always enough. > You might want to consider making the number of retries an option in your > new code. I'll definitely add that ability. If it were me, however, I'd focus on solving the environmental problems that obviously exist as you have a recurring problem w/ signal delivery. In the mean time, you can find the retry limit by searching for "_retry_count" in Insteon_Device.pm. Look for the comparison: _retry_count < 2. Change 2 to whatever you want. Note that making this change is global. Gregg |