thank you!
Do I understand correctly, this component cannot be used at the moment due to a change in the signal API and there is currently no workaround?
That's what I get from reading the issue. I'd suggest adding a note in the issue saying you are having the problem too. Maybe that will help spur the author to fix it.
And before you ask, no I don't know of a replacement node for the Signal app. I can say that a lot of people use Telegram with Node-RED. (a search of the forum will show you some threads about Telegram)
Signal will likely always be quite difficult to work with. Indeed, there wasn't anything you could do with it for quite a while. One of the main reasons for this is that the priority for Signal is security and privacy and it stands out from a crowded market by offering the best security and privacy by a long way. Which is why we use it professionally for times when our main Microsoft Platform isn't working or when we need higher secrecy than usual.
Telegram, on the other hand, isn't as secure or private - though it is still pretty good over all - but it has possibly the easiest to use bot framework of all. That's why I'm happy to use it for my home automation. I have a couple of live bots plus a bunch of test bots. One live bot is "chatty" with lots of information coming out and I keep that muted so I'm not bombarded with notifications but can look at what is happening when I like. The other bot only gives the most critical information such as when the doorbell goes or if an external door has been left open too long. I can also send commands through to Node-RED to do things like control lighting.
