Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AUTO_RECEIVE_SCHEDULE has wrong number set #608

Open
2 tasks done
fnordson opened this issue Oct 25, 2024 · 2 comments
Open
2 tasks done

AUTO_RECEIVE_SCHEDULE has wrong number set #608

fnordson opened this issue Oct 25, 2024 · 2 comments

Comments

@fnordson
Copy link

The problem

Every time at 22:00 I'm getting the following error:

GIN] 2024/10/24 - 22:00:38 | 400 |  5.150884749s |       127.0.0.1 | GET      "/v1/receive/+491567846056?ignore_attachments=false&ignore_stories=false&send_read_receipts=false&timeout=10"
time="2024-10-24T22:00:38Z" level=error msg="AUTO_RECEIVE_SCHEDULE: Couldn't call receive for number +491567846056: {User +491567846056 is not registered.\n}"

I have no idea where +491567846056 came from (guess it's a default) and how to change it.
I followed the instructions to install the addon on home assistant. Besides this issue, it works flawlessly.
I would like to keep auto receive since I'm not interested in the msgs there atm, but I'll have to set my number there.

Could someone help me out there?

Are you using the latest released version?

  • Yes

Have you read the troubleshooting page?

  • Yes

What type of installation are you running?

Home Assistant Signal Addon

In which mode are you using the docker container?

Normal Mode

What's the architecture of your host system?

arm64

Additional information

No response

@bbernhard
Copy link
Owner

Could it be, that you maybe (accidentally) configured that number? Maybe from an old installation?

@fnordson
Copy link
Author

fnordson commented Nov 3, 2024

It might be, however the add-on works well otherwise.
It just appears in the logs and I don't know how to get rid of it or if it might cause trouble.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants