Constant high CPU for the addon about signal-addon

[haberda]

Hi. I haven't seen this issue, I'm running the same setup. Is this a fresh install, or is it configured? Do you have groups, or do anything else with the rest api? I don't do much to the upstream container, I just set some environment variables.

Can you make a backup and then wipe the container data, see if it has high usage then?

[EDelsman]

I feel silly because I forgot step one in case of any trouble: check the logs. There are constant error messages with regard to a phone number I entered incorrectly (left out the area code):
time="2022-05-13T10:14:30+02:00" level=error msg="Couldn't read data for number +babphonenumber: EOF. Is the number properly registered?"

I checked my notifier section in configuration.yaml but the wrong number isn't there, I do have a working notification, so I guess I first tried to register my phone number without the area code, then "corrected" my mistake by trying again with the right one. I actually see this in the logs as there are two numbers found, the right one and the wrong one.

So the big question is: can I unregister the wrong phone number with the rest API wityhout needing to go through the hassle of registering the right one all over again? I'm on haos so I don't think I have direct access to the container - uninstalling and reinstalling is about all I can imagine on my own. And I'm betting the reset_data option also resets the working connection?

I took a wild stab, selected 'normal' mode and and tried: curl -X POST -H "Content-Type: application/json" http://IP:8080/v1/unregister/+badphonenumber
But that got me an error message saying the user +badphonenumber is not registered. Which kind of figures, because I could not have completed the registration with that number. After that I found the actual rest api doc and also tried it with the proper data, but the result is the same for all combinations.

Probably not unexpected, but the high load is not there in normal or native mode.

[EDelsman]

I put in an issue with the Signal api to ask for a way to remove the bad phone number, this issue can be closed as I think it is caused by the rest api itself and not the addon itself.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[EDelsman]

I would still like a way to remove unwanted phone numbers that are not/no longer registered with Signal on HAOS, where there is no access to files in docker.

[EDelsman]

I still closed it as I now realize this is not the right place.