adam/pyMC_Repeater
1
0 Fork 0
mirror of https://github.com/pyMC-dev/pyMC_Repeater.git synced 2026-10-31 04:01:59 +01:00
Code Issues 41 Packages Projects Releases Wiki Activity

Room servers - companions can't see messages #103

New Issue
Closed
opened 2026-10-27 09:33:22 +01:00 by adam · 3 comments
adam commented 2026-10-27 09:33:22 +01:00
Owner
Copy link
Copy source

Repeater:
v1.0.11
Dev Build: 44
Core:
v1.0.13

When setting up a room server on pyMC, it seems that messages aren't being synced to companions upon companion login.

Setup

I can send messages from the pyMC console, and upon refreshing the console, open the messages view and see that they have persisted for the room.

I can also send messages successfully from companions to the room.

Expected Outcome

  1. I expect to see the name of the companion that sent the message when viewing the room messages via the pyMC console and the timestamp of the sent message.
  2. When signing into the room via a companion, I expect to see previously sent messages (up to the maximum number in history) .

Actual Outcome

  1. When I open the messages view on the console to see the messages in there.
Image
  • For messages sent using the Room Server console, the name of the room is displayed for the message.
  • For messages sent by a companion, the companion name is missing; just the hash is displayed.
  • The timestamp for all messages is also set to unknown.
  1. When I sign into the room from either the companion that previously sent a test message, or a new companion that has not visited before, no messages are displayed in the companion app
Image
Repeater: v1.0.11 Dev Build: 44 Core: v1.0.13 When setting up a room server on pyMC, it seems that messages aren't being synced to companions upon companion login. # Setup I can send messages from the pyMC console, and upon refreshing the console, open the messages view and see that they have persisted for the room. I can also send messages successfully from companions to the room. # Expected Outcome 1. I expect to see the name of the companion that sent the message when viewing the room messages via the pyMC console and the timestamp of the sent message. 2. When signing into the room via a companion, I expect to see previously sent messages (up to the maximum number in history) . # Actual Outcome 1. When I open the messages view on the console to see the messages in there. <img width="1331" height="878" alt="Image" src="https://github.com/user-attachments/assets/82812947-1157-47ea-860a-8cd640557591" /> - For messages sent using the Room Server console, the name of the room is displayed for the message. - For messages sent by a companion, the companion name is missing; just the hash is displayed. - The timestamp for all messages is also set to unknown. 2. When I sign into the room from either the companion that previously sent a test message, or a new companion that has not visited before, no messages are displayed in the companion app <img width="576" height="1280" alt="Image" src="https://github.com/user-attachments/assets/2aae002e-20f1-4fe2-843e-d08ae515f902" /> <!-- github-sync-id:4619588189 -->
adam closed this issue 2026-10-27 09:33:22 +01:00
adam commented 2026-10-27 09:33:23 +01:00
Author
Owner
Copy link
Copy source

Additional info:

I noticed that even with a companion logged into the room server, if I send a message from the pyMC console to the room, the message is never delivered.

This does seem to set off a chain of events whereby the server attempts to re-sync all unread messages to the companion. If I leave the companion logged in and active long enough, the server starts repeatedly pushing the first message in its history to the companion. I just opened the companion app again and see over 200 unread messages in the room, and I see the following never-ending, periodic timeout reports in the logs (I've only grepped RoomServer):

Jun 10 04:25:15 zero pymc-repeater[6131]: 2026-06-10 04:25:15,815 - RoomServer - WARNING - Room 'Newport-Room': Push to 0xA9 timed out
Jun 10 04:25:53 zero pymc-repeater[6131]: 2026-06-10 04:25:53,375 - RoomServer - WARNING - Room 'Newport-Room': Push to 0xA9 timed out
Jun 10 04:26:31 zero pymc-repeater[6131]: 2026-06-10 04:26:31,224 - RoomServer - WARNING - Room 'Newport-Room': Push to 0xA9 timed out
Jun 10 04:27:08 zero pymc-repeater[6131]: 2026-06-10 04:27:08,255 - RoomServer - WARNING - Room 'Newport-Room': Push to 0xA9 timed out
Jun 10 04:27:44 zero pymc-repeater[6131]: 2026-06-10 04:27:44,733 - RoomServer - WARNING - Room 'Newport-Room': Push to 0xA9 timed out
Additional info: I noticed that even with a companion logged into the room server, if I send a message from the pyMC console to the room, the message is never delivered. This does seem to set off a chain of events whereby the server attempts to re-sync all unread messages to the companion. If I leave the companion logged in and active long enough, the server starts repeatedly pushing the first message in its history to the companion. I just opened the companion app again and see over 200 unread messages in the room, and I see the following never-ending, periodic timeout reports in the logs (I've only grepped RoomServer): ``` Jun 10 04:25:15 zero pymc-repeater[6131]: 2026-06-10 04:25:15,815 - RoomServer - WARNING - Room 'Newport-Room': Push to 0xA9 timed out Jun 10 04:25:53 zero pymc-repeater[6131]: 2026-06-10 04:25:53,375 - RoomServer - WARNING - Room 'Newport-Room': Push to 0xA9 timed out Jun 10 04:26:31 zero pymc-repeater[6131]: 2026-06-10 04:26:31,224 - RoomServer - WARNING - Room 'Newport-Room': Push to 0xA9 timed out Jun 10 04:27:08 zero pymc-repeater[6131]: 2026-06-10 04:27:08,255 - RoomServer - WARNING - Room 'Newport-Room': Push to 0xA9 timed out Jun 10 04:27:44 zero pymc-repeater[6131]: 2026-06-10 04:27:44,733 - RoomServer - WARNING - Room 'Newport-Room': Push to 0xA9 timed out ``` <!-- github-comment-id:4666600640 -->
adam commented 2026-10-27 09:33:24 +01:00
Author
Owner
Copy link
Copy source

Curious, does your room server have a guest password (ie a not blank pwd)

In my case with no guest password, i can login as guest but nothing really works. When i set guest password and login as guest w/ an actual pwd, things started flowing. Logging in as admin (w/ pwd) always seemed to work.

Im hearing blank password should be fine so I was going to raise an issue but I wonder if its the same thing here.

Curious, does your room server have a guest password (ie a not blank pwd) In my case with no guest password, i can login as guest but nothing really works. When i set guest password and login as guest w/ an actual pwd, things started flowing. Logging in as admin (w/ pwd) always seemed to work. Im hearing blank password should be fine so I was going to raise an issue but I wonder if its the same thing here. <!-- github-comment-id:4713108868 -->
adam commented 2026-10-27 09:33:24 +01:00
Author
Owner
Copy link
Copy source

Interesting. No, in my case I have a "hello" pasword

Interesting. No, in my case I have a "hello" pasword <!-- github-comment-id:4774501121 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/pyMC_Repeater#103