Reconnecting

[mbio16]

Hello,

I use your skill in node-red for a long time. I got a problem in my code and it is showing reconnecting. I know that I got account ok because I can log in on your website and even Alexa can see the devices. However my node-red server can not see the devices.

Thank you, Martin

[hardillb]

If it is constantly reconnecting that means you have 2 instances running at once for that user id. You can only have one, this is by design to stop 2 instances trying to respond.

[homing1923]

Hi,

Here got similar issue, successful login on website and discover-able device in alexa but always reconnecting in node-red. Then I try to reinstall the module and now the npm also pop up the similar error. getaddrinfo EAI_AGAIN

[hardillb]

@homing1923 that error has nothing to do with the node or skill, it means npm can not resolve one of npmjs.org's servers.

As I said in the previous answer, you can only have one instance of the config node at one time. Check the config nodes side bar to be sure there is only one.

[homing1923]

@homing1923 that error has nothing to do with the node or skill, it means npm can not resolve one of npmjs.org's servers.

@hardillb Alright, i finally get the module after 1000s.

added 128 packages in 1137.695s

Here is the real one. Error: getaddrinfo EAI_AGAIN alexa-node-red.hardill.me.uk:8883

I made a brand new acct

and made a new device, also discovered in the alexa app.

to exclude from this issue.

If it is constantly reconnecting that means you have 2 instances running at once for that user id. You can only have one, this is by design to stop 2 instances trying to respond.

Still, I cannot find any device on the node properties.

and the error keeps on popping up in the debug

So what would causing this issue? thanks

[hardillb]

The port 8883 error is not a problem, it's just the node trying to use one of the fall back addresses, if you leave it 30 seconds it will connect on port 1883. Unfortunately there is no easy to suppress the error message

[hardillb]

Actually the EAI_AGAIN means you have a DNS problem, this is the same problem that was effecting npm, it sounds like your pi is having problems looking up addresses

[mbio16]

I only have one instance with my user ID. When I try configure account it does not find it because when I try to find device in node-red It can not find any.

[homing1923]

Finally, I found what I messed up.

Now everything works fine, many thanks @hardillb