You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
The problem
Every time at 22:00 I'm getting the following error:
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?
Have you read the troubleshooting page?
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
The text was updated successfully, but these errors were encountered: