Active TopicsActive Topics  Display List of Forum MembersMemberlist  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin
PowerHome General
 PowerHome Messageboard : PowerHome General
Subject Topic: Adding a ctrlr / Flagged Create / Rebuild Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
jeffw_00
Super User
Super User


Joined: June 30 2007
Online Status: Offline
Posts: 929
Posted: March 08 2013 at 18:25 | IP Logged Quote jeffw_00

Hi – Ok, I’m missing something here. I tried to add a recently acquired (used) ControlLinc (CL) to my system. I added it to devices, went to Insteon Explorer, selected the CL, added 5 responder links to it for the PLM, hit save, cleared the PLM database, and did an Add Full.

It “sort of” worked. Button presses on the CL appeared PH Status, but after each button push the LED on the CL went dim for a few seconds and then blinked quickly for a few more. The Ctl Link Status was stuck in “flagged create”

So I hard-reset the CL, deleted it from everything in PH, exited and re-started PH, and tried again from scratch. This time, I couldn’t get the CL appear in PH Status no matter what I tried.

Finally, I tried manually tap-linking the buttons and that worked. It’s now working perfectly. But still…

- The Ctl Link Status for the responders links shows “FLAGGED CREATE”.

- I was never able to get “Rebuild” to do anything. I suspect that’s my main issue. The device is NOT disabled, either in InsteonExplorer/Devices or in the main Devices window. I suspect this is my main problem. If I could get Rebuild to work I wouldn’t have had to manually link.

I tried a 2nd CL (I acquired two) and had similar behavior…

What’s the missing step?

Thanks!
/j

Back to Top View jeffw_00's Profile Search for other posts by jeffw_00
 
jeffw_00
Super User
Super User


Joined: June 30 2007
Online Status: Offline
Posts: 929
Posted: March 10 2013 at 14:18 | IP Logged Quote jeffw_00

no one? 8-{
Back to Top View jeffw_00's Profile Search for other posts by jeffw_00
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: March 10 2013 at 21:15 | IP Logged Quote dhoward

Jeff,

There is a bug in the current I2CS patch which will sometimes cause a device to not have links or other background operations completed and I suspect this is probably your problem.

To correct it, on the Devices tab of the Insteon Explorer, change the IEngine from whatever type it currently is (for the CL's its probably Legacy) to a different value. Save your changes (Save/Refresh). Now just change it back and save your changes again. Make sure that the device isnt flagged Disabled or is flagged as COMM disabled and links and other background operations should start working.

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 
jeffw_00
Super User
Super User


Joined: June 30 2007
Online Status: Offline
Posts: 929
Posted: March 11 2013 at 07:59 | IP Logged Quote jeffw_00

Hi Dave - Thanks for the post. It's not disabled or COMM disabled, but the iEngine type was blank. Here's what I did...


iEtype => legacy / save/ try rebuild - nothing
notice that disabled got checked. uncheck/save/ try rebuild - i got a single operation (built 1 link)

ietype -> I2 /save re-open IE, type is still legacy, rebuild does nothing.

Links for device are still FLAGGED CREATE. Device still seems to work fine.

So it's not an immediate problem (my workaround seemed to work), but if you want me to try anything else I'm happy to help you debug (or whatever else you need for the greater glory of PH 8-})

best
/j

Back to Top View jeffw_00's Profile Search for other posts by jeffw_00
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: March 11 2013 at 12:22 | IP Logged Quote dhoward

Jeff,

Hmm...its strange that it won't let you set the IEngine to I2. I'll have to do a little more digging as I thought I understood the nature of this problem.

Will keep you posted.

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 
jeffw_00
Super User
Super User


Joined: June 30 2007
Online Status: Offline
Posts: 929
Posted: March 11 2013 at 12:34 | IP Logged Quote jeffw_00

thanks Dave - but again - it's working now, so don't sweat it on my behalf.
Back to Top View jeffw_00's Profile Search for other posts by jeffw_00
 
jeffw_00
Super User
Super User


Joined: June 30 2007
Online Status: Offline
Posts: 929
Posted: March 16 2013 at 15:40 | IP Logged Quote jeffw_00

Hi Dave - I inherited some additional CLs recently and I tried to add another one and ran into the same problem. I can only link it manually and Rebuild has no effect.

let me know when you have thoughts on this and I'm happy to place test case.

best
/j

(another clue?   Auto-discover as you mentioned on the other post didn't work with it either...)

Edited by jeffw_00 - March 16 2013 at 15:41
Back to Top View jeffw_00's Profile Search for other posts by jeffw_00
 
jeffw_00
Super User
Super User


Joined: June 30 2007
Online Status: Offline
Posts: 929
Posted: May 05 2013 at 10:25 | IP Logged Quote jeffw_00

so today I had to change the battery on a motion sensor. After doing so i COULD NOT get it to re-link back to the controller. Rebuild did nothing, deleting/replacing the links didn't help, etc. Finally, I tried setting the type to I2CS and things started to work - but I don't think the motion sensor is an I2CS device - could this be the bug Dave mentioned, and setting to I2CS is the workaround? I have a lot of older devices and don't know if this workaround will work on them, so I'm hoping Dave can/will address his bug soon - thanks!

/j
Back to Top View jeffw_00's Profile Search for other posts by jeffw_00
 
BeachBum
Super User
Super User
Avatar

Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
Posted: May 05 2013 at 12:30 | IP Logged Quote BeachBum

This seems to be the trend for now. Been having the same problem using the same procedure.

__________________
Pete - X10 Oldie
Back to Top View BeachBum's Profile Search for other posts by BeachBum
 
jeffw_00
Super User
Super User


Joined: June 30 2007
Online Status: Offline
Posts: 929
Posted: May 05 2013 at 12:43 | IP Logged Quote jeffw_00

Thanks BB - good to know it's not just me.   Funny, though, not like Dave to delay on a wide-impact bugfix. Hope all is well with him.

best
/j

Edited by jeffw_00 - May 05 2013 at 12:43
Back to Top View jeffw_00's Profile Search for other posts by jeffw_00
 
jeffw_00
Super User
Super User


Joined: June 30 2007
Online Status: Offline
Posts: 929
Posted: October 12 2013 at 11:55 | IP Logged Quote jeffw_00

Hi - Is there any update here? It's still true that when I have to add a new link, I kind of muck around, trying the same thing a few times until finally it sort of magically works. (Sometimes it doesn't, but I try later and it does). Rebuild seems like an important command. It needs to reliably work.

(sorry to be a pain about this, but PH is such a production-quality tool otherwise).

Thanks!
/j
Back to Top View jeffw_00's Profile Search for other posts by jeffw_00
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: October 13 2013 at 11:47 | IP Logged Quote dhoward

Jeff,

Have been working on version 2.1.5 but is taking much
longer than I expected. Im tracing a bug where PowerHome
will just "lockup" requiring either a reboot or a hard
kill to correct. Once I get past this issue, 2.1.5
should be ready.

In the meantime, what seems to work best is to add new
devices via Auto-discovery. This process will also
autodetect the device type and create any appropriate
entries. Once the device and type has been
autodiscovered, all that may remain is properly setting
the IEngine column and the Use ext for ALDB columns.

We still have the problem where a manually entered device
will leave these two fields as null which causes the
"Disabled" column to be checked anytime a background
operation involving this device comes into play. If you
scan through your Devices tab and see any devices with a
check in the "Disabled" column (that you didnt purposely
put there), then it will be caused by one or both of
these columns being null.

If you're getting a different problem, let me know and
I'll see what I can do.

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 
jeffw_00
Super User
Super User


Joined: June 30 2007
Online Status: Offline
Posts: 929
Posted: October 13 2013 at 12:24 | IP Logged Quote jeffw_00

Hi Dave - if the fix for "Rebuild does nothing" is in 2.1.5 I'm happy to wait. I add a new device pretty rarely. I'm sorry to say that the last time I tried it (some time ago) I remember trying auto discover and it also didn't solve it (although admittedly it could have been cockpit error). If I remember correctly, I got to the same place and stuck at the same point (difficulty getting it to establish the link).

Again, I'm not a good person to help you debug because it's a pretty rare thing for me, but I posted because you had mentioned a known bug and I'm hoping that when it's fixed, rebuild for I2CS devices will just work and there will be no more workarounds. If 2.1.5 holds that promise I'm happy to wait for the release.

best
/j
Back to Top View jeffw_00's Profile Search for other posts by jeffw_00
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum