Open phreaq opened 4 years ago
Hello, unfortunately I have the same problem. The debug node shows the following: "nora (k6Mr8): socket connection error: user already connected" I did an update of the Nora plugin, without success. I cleared the cache from the Google Home app, without success. I created and entered a new token, without success. I was able to create two lights before the problem, and when I made changes, it was no longer possible to connect ...
Home Assistant version 0.103.0 is running on my RPi Version 5.0 of NodeRED and the Nora plugin is version 0.0.30
I would be grateful for help with troubleshooting
Hello, just wanted to inform you that "Nora" is working again ....
Hello VolkerKa i've the same problem. How do you have resolved?
Nevermind. It worked again automatically.
Getting this message since today constantly. There's only one instance of node-red running. I already updated my access token, re-installed the extension in node-red, re-installed node-red completely, unlinked and re-linked Nora in my Google Home app. Unfortunately, no success.
Try changing the group
That did it! Thanks @andrei-tatar!
I unfortunately experienced the same. Adding the group didn't resolve the problem. I revoked the token, got a new one, changed the config. Unlinked NORA in Google Home Assistant, relinked, but now the devices of the old token still appear. How can I get rid of these? Thanks!
I unfortunately experienced the same. Adding the group didn't resolve the problem. I revoked the token, got a new one, changed the config. Unlinked NORA in Google Home Assistant, relinked, but now the devices of the old token still appear. How can I get rid of these? Thanks!
@geertvercamer did you find a solution to remove the old devices?
@simonbove I had it again the other day after moving to new hardware. Nothing was working. Asked for new token, changed config. Nothing. Relinked Nora in GH. Nothing. Changed group in Nora config. Nothing. Removed and reinstalled Nora in GH. Double devices, confusing GH as it didn't know what device to use, obviously. Had a browser window open with the old token, revoked it. In the config I changed the group back to the old name, refreshed Nora in GH and all was fine. I can't give you a clear explanation, sorry. It's a bit of try and error and patience, I guess
@geertvercamer thanks for your reply. Yeah it is really irritating. Sadly I don't have the old token open anywhere. Hopefully @andrei-tatar have a solution?
I've been having issues lately with Nora connecting with Node-Red after a deployment, with the first attempt at using Nora devices failing, but subsequent attempts working.
Now, I have an issue with it connecting altogether, with the following error:
"nora (tHncc): socket connection error: user already connected"
It reattempts to connect every minute or so, then fails again.
I've tried restarting Node-Red, a new Nora key, as well as removed/re-added Nora to google home, no change.
Any thoughts?