Re: [mh] Impossible to sync all insteon links routines

H Plato <[email protected]>
Newsgroups gmane.comp.misc.misterhouse.user
Message-ID <[email protected]>
Sorry for chiming in late. I don’t think there were many insteon changes with some of the last releases. The stuff I did mainly focused on ia7, homebridge, razberry, yeelights — so I don’t think there’s much value in reverting.

My insteon stuff works, is sometimes flakey though, scanning link table sometimes takes multiple tries. But it all works, I probably have around 20 or so devices.  

Kevin any comments about this: https://github.com/TD22057/insteon-mqtt ?  It seems current and MH does have MQTT support.

> On Apr 5, 2020, at 6:45 PM, Marc MERLIN <[email protected]> wrote:
> 
> On Sun, Apr 05, 2020 at 09:56:05AM -0700, Kevin Robert Keegan wrote:
>> Hi Marc,
>> 
>> Sorry you are having so many problems, that is certainly very irritating.
>> I don't really know what is going on.  I haven't used misterhouse in a
>> while and haven't looked at the code in years.  My best suggestion is to
>> try and roll back to a prior version of misterhouse when everything was
>> working.  Otherwise, the only other suggestion is to move away from
>> misterhouse to a maintained insteon library.  Sadly, most of those don't
>> support i1 devices very well.
> 
> Yeah, and I still have some amount of I1 devices I'm not super keen on
> ripping out, just because.
> Sure, they suck when you sync all links, but I do that less than once a
> year, so...
> 
> Now, I didn't think anyone really touched the insteon syncing code since
> you last did, so I'm not sure rolling back a lot is likekly to fix
> things.
> H Plato/Lieven, do you remember? Is it worth me playing with git history
> and going way back to see if insteon sync/rescan was broken?
> 
> Anyone else: anyone still using decent insteon installs (dozens or
> hundred+ nodes if you count KPL buttons)?
> Is scan all/sync all working for you?
> 
> Thanks,
> Marc
> 
>> Sorry I wasn't more help
>> 
>> Kevin
>> 
>> On Sat, Apr 4, 2020 at 12:11 PM Marc MERLIN <[email protected] <mailto:[email protected]>> wrote:
>> 
>>> Howdy,
>>> 
>>> This is with misterhouse git master, but been true for several years, now.
>>> 
>>> I know insteon isn't really mainteained, but I need help, my house has
>>> been getting more and more out of sync as devices die and mh has been
>>> unable to reconcile things.
>>> 
>>> Scan all links works.
>>> 04/04/2020 12:02:08  [Scan all link tables] Completed scanning of all
>>> regular items.
>>> 
>>> Audit sync all links immediately fails, though. Why are my ALDBs considered
>>> changed even though nothing changed?
>>> [Insteon::BaseController] (AUDIT) Unable to add the following responder
>>> record to $lvr_kpl_mbr_kpl from $mbr_kpl because the aldb of
>>> $lvr_kpl_mbr_kpl is changed
>>> add; data3 = 07; group = 01; is_controller = 0; ramp_rate = 2;
>>> [Sync all links] WARN: failure occurred when syncing links for $mbr_kpl.
>>> Resuming sync queue if it exists.
>>> 
>>> I've tried a force scan of all link tables, but it doesn't really help,
>>> outside
>>> of taking maybe 1h to scan everything (lots of devices, many I1).
>>> I thought maybe MH had some broken cached dbs, so I deleted the entire data
>>> directory and let it be re-created, but it didn't help.
>>> 
>>> I also need to delete orphan links, which would run, but that's totally
>>> unsafe
>>> to run, because it would delete a fair amount of half established links
>>> (the
>>> other half is missing because sync all links is broken).
>>> 
>>> So, I'm stuck, and that's been true for years now. I have to link devices
>>> manually using the buttons, it's a real pain.
>>> 
>>> Am I the only one in this situation? Any suggestions?
>>> 
>>> Thanks,
>>> Marc
>>> 
>>> More logs:
>>> [Insteon::BaseController] (AUDIT) Unable to add the following responder
>>> record to $lvr_kpl_mbr_kpl from $mbr_kpl because the aldb of
>>> $lvr_kpl_mbr_kpl is changed
>>> add; data3 = 07; group = 01; is_controller = 0; ramp_rate = 2;
>>> [Sync all links] WARN: failure occurred when syncing links for $mbr_kpl.
>>> Resuming sync queue if it exists.
>>> [Sync all links] Now syncing: $mbr_lamp2 (2 of 125)
>>> [Insteon::BaseController] (AUDIT) Unable to add the following responder
>>> record to $lvr_kpl_mbr_lamp2 from $mbr_lamp2 because the aldb of
>>> $lvr_kpl_mbr_lamp2 is changed
>>> add; data3 = 08; group = 01; is_controller = 0; ramp_rate = 1;
>>> [Sync all links] WARN: failure occurred when syncing links for $mbr_lamp2.
>>> Resuming sync queue if it exists.
>>> [Sync all links] Now syncing: $mbr_lamp3 (3 of 125)
>>> [Insteon::BaseController] Nothing to do when syncing links for $mbr_lamp3
>>> [Sync all links] Now syncing: $mbr_outside (4 of 125)
>>> [Insteon::BaseController] Nothing to do when syncing links for $mbr_outside
>>> [Sync all links] Now syncing: $br2_sw (5 of 125)
>>> [Insteon::BaseController] (AUDIT) Unable to add the following responder
>>> record to $lvr_kpl_br2_sw from $br2_sw because the aldb of $lvr_kpl_br2_sw
>>> is changed
>>> oup = 01; ramp_rate = 2; data3 = 06; cmd = add; on_level = 100;
>>> [Sync all links] WARN: failure occurred when syncing links for $br2_sw.
>>> Resuming sync queue if it exists.
>>> [Sync all links] Now syncing: $br2_lamp (6 of 125)
>>> [Insteon::BaseController] Nothing to do when syncing links for $br2_lamp
>>> [Sync all links] Now syncing: $fmr_kpl (7 of 125)
>>> [Insteon::BaseController] (AUDIT) Unable to add the following responder
>>> record to $lvr_kpl_fmr_all from $fmr_kpl because the aldb of
>>> $lvr_kpl_fmr_all is changed
>>> 
>>> (many lines not pasted)
>>> 
>>> [Sync all links] All links have completed syncing
>>> [Sync all links] WARN! Failures occured, some links involving the
>>> following objects remain out-of-sync: $mbr_kpl, $mbr_lamp2, $br2_sw,
>>> $fmr_kpl, $fmr_slav, $fmr_lamp, $entryway, $lvr_kpl, $lvr_lamp,
>>> $yard_lights, $kitchen_kpl, $dining_kpl, $garage_desk, $garage1_neon_kpl,
>>> $garage2_neon_kpl, $gar_outlights_kpl, $corridor_fmr, $corridor_mbr,
>>> $corridor_kpl, $fmr_kpl_kitchen_kpl, $fmr_kpl_dining_kpl,
>>> $fmr_kpl_entryway, $fmr_kpl_lvr_kpl, $fmr_kpl_gar_outlights,
>>> $fmr_kpl_yard_lights, $fmr_slav_kitchen_kpl, $fmr_slav_dining_kpl,
>>> $fmr_slav_entryway, $fmr_slav_lvr_kpl, $kitchen_kpl_fmr_all,
>>> $kitchen_kpl_dining_kpl, $kitchen_kpl_entryway, $kitchen_kpl_lvr_kpl,
>>> $kitchen_kpl_corridor_kpl, $kitchen_kpl_gar_outlights,
>>> $dining_kpl_kitchen_kpl, $dining_kpl_fmr_all, $dining_kpl_entryway,
>>> $dining_kpl_lvr_kpl, $dining_kpl_corridor_kpl, $dining_kpl_kplG,
>>> $dining_kpl_crows, $lvr_kpl_lvr_lamp, $lvr_kpl_entryway,
>>> $lvr_kpl_kitchen_kpl, $lvr_kpl_fmr_all, $lvr_kpl_br2_sw, $lvr_kpl_mbr_kpl,
>>> $lvr_kpl_mbr_lamp2, $corridor_kpl_br2_sw, $corridor_kpl_mbr_kpl,
>>> $corridor_kpl_lamp2, $corridor_kpl_kitchen_kpl, $mbr_kpl_corridor_kpl,
>>> $mbr_kpl_br2_sw, $garage1_neon_kpl_garage2_neon,
>>> $garage1_neon_kpl_gar_outlights, $garage1_neon_kpl_yard_lights,
>>> $garage2_neon_kpl_garage1_neon, $garage2_neon_kpl_kplB,
>>> $garage2_neon_kpl_gar_outlights, $garage2_neon_kpl_yard_lights,
>>> $gar_outlights_kpl_garage1_neon, $gar_outlights_kpl_garage2_neon,
>>> $gar_outlights_kpl_yard_lights, $all_unused_scene, $fmr_all_scene,
>>> $all_out_scene, $mbr_all_scene, $fmr_lvr_scene, $fmr_lvr_scene_slow,
>>> $crows_scene, $gar_outlights_kpls, $garage1_neon_kpls, $garage2_neon_kpls,
>>> $fmr_kpls, $kitchen_kpls, $dining_kpls, $entryway_kpls, $lvr_kpls,
>>> $lvr_lamp_kpls, $yard_lights_kpls, $mbr_kpls, $mbr_lamp2_kpls,
>>> $corridor_kpls, $br2_sw_kpls,
>>> 
>>> 
>>> --
>>> "A mouse is a device used to point at the xterm you want to type in" -
>>> A.S.R.
>>> 
>>> Home page: http://marc.merlins.org/                       | PGP
>>> 7F55D5F27AAF9D08
>>> 
> 
> -- 
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
> 
> Home page: http://marc.merlins.org/ <http://marc.merlins.org/>

________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.