Open ekkesa opened 1 year ago
I confirm. A similar problem with the inability to add a device via a qr code. HA 2023.6
Same here, whatsapp addon are not länger sending message, I reinsalled the addon as well, now not posible to connect via QR code, ( always get the message... please try later error occured )
a possible fix it to update the version on src/Defaults/baileys-version.json to "version": [2, 2323, 4] but i do not use HA supervised so cannot test this
a possible fix it to update the version on src/Defaults/baileys-version.json to "version": [2, 2323, 4] but i do not use HA supervised so cannot test this
I made a fork and did the change there - It seemed to have resolved the issue. The fork is https://github.com/ekkesa/ha-addons - I will delete the fork once this repo is updated.
Might have spoken to soon - It seems to resolve the QR code issue and the client not connecting, but it seems to fail on sending messages.
From the logs it seems to look for the old addon container, not the fork I added. The listen for events is working so the connection to WA is working
UPDATE: A restart resolved the issue - All is working as intended. The fork is https://github.com/ekkesa/ha-addons - I will delete the fork once this repo is updated.
How can i install your fork in HA? i have it running now as addon but don't seem to be able to install it from your fork....
Same method as the original - Just add my repo to HA and install. Remember to stop/remove the original one beforehand.
UPDATE: it seems to be ok....i installed it, pairing with whatsapp worked, restarted HA completly and it's sending out messages again....thnx...
ok thnx for the answer....but if i add your repository (https://github.com/ekkesa/ha-addons) i get the other one in my overvies? Is this normal (i removed the original repositories..)
Correct - The labelling and all stayed the same - I didn't bother with it as it is only temporary till the original is fixed.
It's not the same for me. I get error when I scan qr...
Correct - The labelling and all stayed the same - I didn't bother with it as it is only temporary till the original is fixed.
Can you help me?
Hi,
This was working very well, but stopped working on Friday morning (23/06/02). The log shows no errors, it just never reaches client ready status. I can see that node index is running and consuming resources on the host machine, but it just never finishes the start up.
I tried adding a second client, when scanning the QR code I got an error stating that the QR code in invalid, and I must ensure that it is from WA web, Desktop or other authorised app. Perhaps they changed something on their side which broke the add-on?