Logging in as admin at the repeater from a companion device #66

Closed
opened 2026-10-27 09:31:12 +01:00 by adam · 13 comments
Owner

Hi There,
I am trying to login as admin at the repeater via my companion T1000-e device with the latest Meshcore firmware. I am using both the web client (https://app.meshcore.nz/) and the Meshcore iOS app.
I have added the security settings for the repeater at the repeater section, but I after several tries, I am not able to login with the credentials set.

  security:
    admin_password: "admin123"
    max_clients: 3
    guest_password: "guest123"
    allow_read_only: true

I do see that packets arrive at the debug log on the repeater when I try to login, but no login is established. I have used admin and guest credentials but same result.

Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,414 - SX1262_wrapper - DEBUG - [RX] RX_DONE interrupt (0x0002)
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,415 - SX1262_wrapper - DEBUG - [RX] Terminal interrupt 0x0002 - waking background task
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,415 - SX1262_wrapper - DEBUG - [RX] RX_DONE event triggered!
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,416 - SX1262_wrapper - DEBUG - [RX] Packet received: length=53, RSSI=-25dBm, SNR=14.75dB
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,417 - SX1262_wrapper - DEBUG - [RX] Packet data: 1d00cc2052565c16227bf8e386f3c848... (53 bytes)
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,417 - Dispatcher - INFO - [RX DEBUG] Processing packet: 53 bytes, data: 1d00cc2052565c16227bf8e386f3c848...
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,418 - Dispatcher - INFO - [RX DEBUG] Packet parsed successfully
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,418 - Dispatcher - INFO - [RX DEBUG] Packet type: 07
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,418 - Dispatcher - INFO - [RX DEBUG] Dispatching packet to handlers
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,419 - Dispatcher - INFO - RX ANON_REQ (7)
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,419 - Dispatcher - DEBUG - Received packet type ANON_REQ, payload length: 51
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,419 - Dispatcher - DEBUG - Payload preview: cc2052565c16227bf8e3
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,420 - RepeaterHandler - DEBUG - RX packet: header=0x1d, payload_len=51, path_len=0, rssi=-25, snr=14.75, mode=forward
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,420 - RepeaterHandler - DEBUG - Route=FLOOD, len=51B, airtime=888.8ms, delay=0.804s
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,421 - RepeaterHandler - DEBUG - Packet header=0x1d, type=7, route=1
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,421 - StorageCollector - DEBUG - Recording packet: type=7, transmitted=True
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,477 - SX1262_wrapper - DEBUG - [RX] Restored RX continuous mode after IRQ 0x0002
Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,641 - RepeaterHandler - DEBUG - Recorded noise floor: -116.0 dBm
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,281 - SX1262_wrapper - DEBUG - TX timing SF8/62.5kHz CR4/8 54B: symbol=4.096ms, preamble=87.0ms, tmp=444, payload_syms=176.0, payload=720.9ms, air_time=807.9ms, timeout=1808ms, driver_timeout=115712
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,282 - SX1262_wrapper - DEBUG - Setting TX timeout: 1808ms (tOut=115712) for 54 bytes
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,309 - SX1262_wrapper - DEBUG - [RX Task] Status check #159500, noise_floor=-115.9dBm
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,315 - SX1262_wrapper - DEBUG - CAD operation started - checking channel with peak=23, min=11
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,316 - SX1262_wrapper - DEBUG - [CAD] Channel clear detected (0x0080)
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,316 - SX1262_wrapper - DEBUG - CAD operation completed - IRQ status: 0x0080
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,317 - SX1262_wrapper - DEBUG - CAD result: CLEAR - no channel activity detected
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,321 - SX1262_wrapper - DEBUG - CAD check clear - channel available after 1 attempts
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,332 - SX1262_wrapper - DEBUG - [TX] Waiting for TX completion (timeout: 2.308s)
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,911 - SX1262_wrapper - DEBUG - [TX] TX_DONE interrupt (0x0001)
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,912 - SX1262_wrapper - DEBUG - [TX] TX completion interrupt received!
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,913 - SX1262_wrapper - DEBUG - Final interrupt status: 0x0000
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,913 - SX1262_wrapper - DEBUG - [TX->RX] Starting RX mode restoration after transmission
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,914 - SX1262_wrapper - DEBUG - [TX->RX] RX mode restoration completed
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,914 - Dispatcher - INFO - TX 54 bytes (type=ANON_REQ, route=FLOOD)
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,915 - AirtimeManager - DEBUG - TX recorded:  938.0ms (total:  4297ms)
Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,915 - RepeaterHandler - INFO - Retransmitted packet (51 bytes, 938.0ms airtime)

I am using the Waveshare LoRa hat setup in combination with Raspberry PI.
The repeater works fine and is discovered by the companion device and can be pinged.

Any clue?

Hi There, I am trying to login as admin at the repeater via my companion T1000-e device with the latest Meshcore firmware. I am using both the web client (https://app.meshcore.nz/) and the Meshcore iOS app. I have added the security settings for the repeater at the repeater section, but I after several tries, I am not able to login with the credentials set. ```yaml security: admin_password: "admin123" max_clients: 3 guest_password: "guest123" allow_read_only: true ``` I do see that packets arrive at the debug log on the repeater when I try to login, but no login is established. I have used admin and guest credentials but same result. ```bash Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,414 - SX1262_wrapper - DEBUG - [RX] RX_DONE interrupt (0x0002) Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,415 - SX1262_wrapper - DEBUG - [RX] Terminal interrupt 0x0002 - waking background task Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,415 - SX1262_wrapper - DEBUG - [RX] RX_DONE event triggered! Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,416 - SX1262_wrapper - DEBUG - [RX] Packet received: length=53, RSSI=-25dBm, SNR=14.75dB Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,417 - SX1262_wrapper - DEBUG - [RX] Packet data: 1d00cc2052565c16227bf8e386f3c848... (53 bytes) Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,417 - Dispatcher - INFO - [RX DEBUG] Processing packet: 53 bytes, data: 1d00cc2052565c16227bf8e386f3c848... Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,418 - Dispatcher - INFO - [RX DEBUG] Packet parsed successfully Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,418 - Dispatcher - INFO - [RX DEBUG] Packet type: 07 Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,418 - Dispatcher - INFO - [RX DEBUG] Dispatching packet to handlers Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,419 - Dispatcher - INFO - RX ANON_REQ (7) Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,419 - Dispatcher - DEBUG - Received packet type ANON_REQ, payload length: 51 Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,419 - Dispatcher - DEBUG - Payload preview: cc2052565c16227bf8e3 Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,420 - RepeaterHandler - DEBUG - RX packet: header=0x1d, payload_len=51, path_len=0, rssi=-25, snr=14.75, mode=forward Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,420 - RepeaterHandler - DEBUG - Route=FLOOD, len=51B, airtime=888.8ms, delay=0.804s Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,421 - RepeaterHandler - DEBUG - Packet header=0x1d, type=7, route=1 Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,421 - StorageCollector - DEBUG - Recording packet: type=7, transmitted=True Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,477 - SX1262_wrapper - DEBUG - [RX] Restored RX continuous mode after IRQ 0x0002 Mar 26 17:15:40 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:40,641 - RepeaterHandler - DEBUG - Recorded noise floor: -116.0 dBm Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,281 - SX1262_wrapper - DEBUG - TX timing SF8/62.5kHz CR4/8 54B: symbol=4.096ms, preamble=87.0ms, tmp=444, payload_syms=176.0, payload=720.9ms, air_time=807.9ms, timeout=1808ms, driver_timeout=115712 Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,282 - SX1262_wrapper - DEBUG - Setting TX timeout: 1808ms (tOut=115712) for 54 bytes Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,309 - SX1262_wrapper - DEBUG - [RX Task] Status check #159500, noise_floor=-115.9dBm Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,315 - SX1262_wrapper - DEBUG - CAD operation started - checking channel with peak=23, min=11 Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,316 - SX1262_wrapper - DEBUG - [CAD] Channel clear detected (0x0080) Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,316 - SX1262_wrapper - DEBUG - CAD operation completed - IRQ status: 0x0080 Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,317 - SX1262_wrapper - DEBUG - CAD result: CLEAR - no channel activity detected Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,321 - SX1262_wrapper - DEBUG - CAD check clear - channel available after 1 attempts Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,332 - SX1262_wrapper - DEBUG - [TX] Waiting for TX completion (timeout: 2.308s) Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,911 - SX1262_wrapper - DEBUG - [TX] TX_DONE interrupt (0x0001) Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,912 - SX1262_wrapper - DEBUG - [TX] TX completion interrupt received! Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,913 - SX1262_wrapper - DEBUG - Final interrupt status: 0x0000 Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,913 - SX1262_wrapper - DEBUG - [TX->RX] Starting RX mode restoration after transmission Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,914 - SX1262_wrapper - DEBUG - [TX->RX] RX mode restoration completed Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,914 - Dispatcher - INFO - TX 54 bytes (type=ANON_REQ, route=FLOOD) Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,915 - AirtimeManager - DEBUG - TX recorded: 938.0ms (total: 4297ms) Mar 26 17:15:41 meshcore-cerberus pymc-repeater[25380]: 2026-03-26 17:15:41,915 - RepeaterHandler - INFO - Retransmitted packet (51 bytes, 938.0ms airtime) ``` I am using the Waveshare LoRa hat setup in combination with Raspberry PI. The repeater works fine and is discovered by the companion device and can be pinged. Any clue? <!-- github-sync-id:4145437271 -->
adam closed this issue 2026-10-27 09:31:12 +01:00
Author
Owner

Are you using the default password? Thanks.

Are you using the default password? Thanks. <!-- github-comment-id:4136410592 -->
Author
Owner

I have tried default password, but also others. Simply can not login.

I have tried default password, but also others. Simply can not login. <!-- github-comment-id:4136692985 -->
Author
Owner

You have not set it up right. I did the same first time too

Best to start again


From: H00die.Gr3y @.>
Sent: Thursday, March 26, 2026 17:09
To: rightup/pyMC_Repeater @.
>
Cc: Subscribed @.***>
Subject: Re: [rightup/pyMC_Repeater] Logging in as admin at the repeater from a companion device (Issue #161)

[https://avatars.githubusercontent.com/u/38109035?s=20&v=4]h00die-gr3y left a comment (rightup/pyMC_Repeater#161)https://github.com/rightup/pyMC_Repeater/issues/161#issuecomment-4136692985

I have tried default password, but also others. Simply can not login.

—
Reply to this email directly, view it on GitHubhttps://github.com/rightup/pyMC_Repeater/issues/161?email_source=notifications&email_token=BBW7EP6QZDVO4NQ3TA65H7D4SVP3LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJTGY3DSMRZHA22M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4136692985, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBW7EP3A4GQ3IU4FDJPNRDD4SVP3LAVCNFSM6AAAAACXAWE736VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMZWGY4TEOJYGU.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

You have not set it up right. I did the same first time too Best to start again ________________________________ From: H00die.Gr3y ***@***.***> Sent: Thursday, March 26, 2026 17:09 To: rightup/pyMC_Repeater ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [rightup/pyMC_Repeater] Logging in as admin at the repeater from a companion device (Issue #161) [https://avatars.githubusercontent.com/u/38109035?s=20&v=4]h00die-gr3y left a comment (rightup/pyMC_Repeater#161)<https://github.com/rightup/pyMC_Repeater/issues/161#issuecomment-4136692985> I have tried default password, but also others. Simply can not login. — Reply to this email directly, view it on GitHub<https://github.com/rightup/pyMC_Repeater/issues/161?email_source=notifications&email_token=BBW7EP6QZDVO4NQ3TA65H7D4SVP3LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJTGY3DSMRZHA22M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4136692985>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBW7EP3A4GQ3IU4FDJPNRDD4SVP3LAVCNFSM6AAAAACXAWE736VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMZWGY4TEOJYGU>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> <!-- github-comment-id:4137930445 -->
Author
Owner

Ok, what do you mean?
You should be able to configure it in the yaml file and set your own credentials right?

Ok, what do you mean? You should be able to configure it in the yaml file and set your own credentials right? <!-- github-comment-id:4137987606 -->
Author
Owner

I tried that didn't work. Ended up setting it up properly and never had an issue with it when I do it right. And to be fair it's really quick tooOn 26 Mar 2026, at 20:25, H00die.Gr3y @.***> wrote:h00die-gr3y left a comment (rightup/pyMC_Repeater#161)
Ok, what do you mean?
You should be able to configure it in the yaml file and set your own credentials right?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

I tried that didn't work. Ended up setting it up properly and never had an issue with it when I do it right. And to be fair it's really quick tooOn 26 Mar 2026, at 20:25, H00die.Gr3y ***@***.***> wrote:h00die-gr3y left a comment (rightup/pyMC_Repeater#161) Ok, what do you mean? You should be able to configure it in the yaml file and set your own credentials right? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***> <!-- github-comment-id:4138244476 -->
Author
Owner

@Thisone2 ,
Help me out here. How did you configure it properly?

@Thisone2 , Help me out here. How did you configure it properly? <!-- github-comment-id:4138505516 -->
Author
Owner

Morning,

Sorry I have been out of the country on holiday.

These are my notes for setting it up

Log in as a normal user, don't change the directory unless told to do so below

Update package list and install all updates

sudo apt update && sudo apt upgrade -y

enter pi hardware config (this is needed to enable the SLI using option 3)

sudo raspi-config

Install Git if not already on

sudo apt install git -y

Clone Git Rep (this is for pyMC_Repeater)

git clone https://github.com/rightup/pyMC_Repeater.git

Changed dir to the new install

cd pyMC_Repeater

Change to the Dev branch (not always needed, can change branch at any point but would need to reinstall)

git switch dev

configure the system for first run2

sudo ./manage.sh

Select Option 1 to install then follow the onscreen instructions, once done open a web browser this should then take you through the rest of the setup

Give me a shout if you have issues

Thanks


From: H00die.Gr3y @.>
Sent: Thursday, March 26, 2026 21:51
To: rightup/pyMC_Repeater @.
>
Cc: Thisone2 @.>; Mention @.>
Subject: Re: [rightup/pyMC_Repeater] Logging in as admin at the repeater from a companion device (Issue #161)

[https://avatars.githubusercontent.com/u/38109035?s=20&v=4]h00die-gr3y left a comment (rightup/pyMC_Repeater#161)https://github.com/rightup/pyMC_Repeater/issues/161#issuecomment-4138505516

@Thisone2https://github.com/Thisone2 ,
Help me out here. How did you configure it properly?

—
Reply to this email directly, view it on GitHubhttps://github.com/rightup/pyMC_Repeater/issues/161?email_source=notifications&email_token=BBW7EP6I4UE4G4LTXOKKAXL4SWQ67A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJTHA2TANJVGE3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4138505516, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBW7EP75YIKOZAW3RYZFMYT4SWQ67AVCNFSM6AAAAACXAWE736VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMZYGUYDKNJRGY.
You are receiving this because you were mentioned.Message ID: @.***>

Morning, Sorry I have been out of the country on holiday. These are my notes for setting it up Log in as a normal user, don't change the directory unless told to do so below # Update package list and install all updates sudo apt update && sudo apt upgrade -y # enter pi hardware config (this is needed to enable the SLI using option 3) sudo raspi-config # Install Git if not already on sudo apt install git -y # Clone Git Rep (this is for pyMC_Repeater) git clone https://github.com/rightup/pyMC_Repeater.git # Changed dir to the new install cd pyMC_Repeater # Change to the Dev branch (not always needed, can change branch at any point but would need to reinstall) git switch dev # configure the system for first run2 sudo ./manage.sh Select Option 1 to install then follow the onscreen instructions, once done open a web browser this should then take you through the rest of the setup Give me a shout if you have issues Thanks ________________________________ From: H00die.Gr3y ***@***.***> Sent: Thursday, March 26, 2026 21:51 To: rightup/pyMC_Repeater ***@***.***> Cc: Thisone2 ***@***.***>; Mention ***@***.***> Subject: Re: [rightup/pyMC_Repeater] Logging in as admin at the repeater from a companion device (Issue #161) [https://avatars.githubusercontent.com/u/38109035?s=20&v=4]h00die-gr3y left a comment (rightup/pyMC_Repeater#161)<https://github.com/rightup/pyMC_Repeater/issues/161#issuecomment-4138505516> @Thisone2<https://github.com/Thisone2> , Help me out here. How did you configure it properly? — Reply to this email directly, view it on GitHub<https://github.com/rightup/pyMC_Repeater/issues/161?email_source=notifications&email_token=BBW7EP6I4UE4G4LTXOKKAXL4SWQ67A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJTHA2TANJVGE3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4138505516>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBW7EP75YIKOZAW3RYZFMYT4SWQ67AVCNFSM6AAAAACXAWE736VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMZYGUYDKNJRGY>. You are receiving this because you were mentioned.Message ID: ***@***.***> <!-- github-comment-id:4141099620 -->
Author
Owner

Thanks @Thisone2, I already followed your setup and my repeater technically works fine.

I was just wondering how the admin_password and guest_passwords works. Checked the current code base, and for what I can see, these settings are not implemented yet.

I did a full search and admin_password is not used anywhere in the code and that applies for other configuration settings in the config file like identities roles such as room_servers and companions.

So that probably explains why logging in via a companion device is not working

Thanks @Thisone2, I already followed your setup and my repeater technically works fine. I was just wondering how the `admin_password` and `guest_passwords` works. Checked the current code base, and for what I can see, these settings are not implemented yet. I did a full search and `admin_password` is not used anywhere in the code and that applies for other configuration settings in the config file like `identities` roles such as `room_servers` and `companions`. So that probably explains why logging in via a companion device is not working <!-- github-comment-id:4141132166 -->
Author
Owner

I do see that you are on the dev branch, so let me try that because I am on the main branch.

I do see that you are on the dev branch, so let me try that because I am on the main branch. <!-- github-comment-id:4141249485 -->
Author
Owner

I do see that you are on the dev branch, so let me try that because I am on the main branch.

I had this same problem last week. Main branch install does not take you through the first run experience where you get the web interface that allows you to set the password. Main branch install also doesn't seem to recognize the password even after manually configuring it in the yaml file.

Also note that even the dev branch does not seem to recognize any guest password even after the admin password is enabled and demonstrated to work.

> I do see that you are on the dev branch, so let me try that because I am on the main branch. I had this same problem last week. Main branch install does not take you through the first run experience where you get the web interface that allows you to set the password. Main branch install also doesn't seem to recognize the password even after manually configuring it in the yaml file. Also note that even the dev branch does not seem to recognize any guest password even after the admin password is enabled and demonstrated to work. <!-- github-comment-id:4143968598 -->
Author
Owner

I am actually now on companion branch but I wrote that when on the dev one and once you are up and running you can use the GUI to change branch and update On 27 Mar 2026, at 16:55, porkrind @.***> wrote:porkrind left a comment (rightup/pyMC_Repeater#161)

I do see that you are on the dev branch, so let me try that because I am on the main branch.

I had this same problem last week. Main branch install does not take you through the first run experience where you get the web interface that allows you to set the password. Main branch install also doesn't seem to recognize the password even after manually configuring it in the yaml file.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

I am actually now on companion branch but I wrote that when on the dev one and once you are up and running you can use the GUI to change branch and update On 27 Mar 2026, at 16:55, porkrind ***@***.***> wrote:porkrind left a comment (rightup/pyMC_Repeater#161) I do see that you are on the dev branch, so let me try that because I am on the main branch. I had this same problem last week. Main branch install does not take you through the first run experience where you get the web interface that allows you to set the password. Main branch install also doesn't seem to recognize the password even after manually configuring it in the yaml file. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***> <!-- github-comment-id:4144795749 -->
Author
Owner

I am not sure if this is relevant.. just trying to contribute to assist (newbie)

with my RAK Wireless Tag i can log into my pyMC repeater via admin ONLY, get status info but fails to load neighbours.

Both via Mobile App and Webapp. Running a Luckbox Ultra with an E22P on a hat

I am not sure if this is relevant.. just trying to contribute to assist (newbie) with my RAK Wireless Tag i can log into my pyMC repeater via admin ONLY, get status info but fails to load neighbours. Both via Mobile App and Webapp. Running a Luckbox Ultra with an E22P on a hat <!-- github-comment-id:4146859283 -->
Author
Owner

Thanks everybody, I switched to the development branch and reinstalled the repeater.
It solved my login problems.
I am on:
Repeater: v1.0.8 Dev Build: 67
Core: v1.0.7

Thanks everybody, I switched to the development branch and reinstalled the repeater. It solved my login problems. I am on: Repeater: v1.0.8 Dev Build: 67 Core: v1.0.7 <!-- github-comment-id:4148415171 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/pyMC_Repeater#66