Skip to content

Can't Define a new Raspberry pi4 as a child #143

Answered by cxrodgers
DearNebReddey asked this question in Q&A
Discussion options

You must be logged in to vote

Thanks for posting. I have noticed this bug and hadn't gotten around to posting it yet, sorry. Yes, define it as a second Pilot, not as a Child. Then, on the next few screens, you have the option to set the PARENTID and PARENTIP to be the name and ip of the parent Pilot, respectively. That is how it "knows" it's a Child.

Also, during the setup of the Parent Pi, you can tell it the name of the Child in the field CHILDID. You can change this directly in prefs.json as well.

I think we need to remove that initial choice to "setup as Child", since I think it just generates the error message you posted.

In response to your other question, the Terminal should be completely fine with having multi…

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@sneakers-the-rat
Comment options

@DearNebReddey
Comment options

@sneakers-the-rat
Comment options

Answer selected by sneakers-the-rat
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants